Return to Jive Software

Skip navigation
Up to Discussions in Support
532 Views 1 Reply Last post: Oct 27, 2009 5:18 PM by kevin.imber RSS
pratapmaddi Novice
pratapmaddi
32 posts since
Jul 5, 2009
Currently Being Moderated

Oct 14, 2009 5:56 AM

Latest content not retrieved when accesed through REST web services.

Hi,

We are trying to surface the jive content on our portal by making web service calls from our portal. On our portal we display the content like recent 5 blogs, discussion, top 5 blogs, discussions etc. The content will be displayed on our portal by making jive REST web service calls from our portlets.

 

Unfortunately, when we add the content in jive like a blog post or a discussion, the content from jive is not getting shown automatically in our portal. We had to restart the jive server to see the latest content in our portal. The content can be seein in jive application. But it is not getting rendered when accesed through web services. Our guess is that some configuration is missing which is causing this issue. Not sure what is that. Can someone please help us in resolving this?

 

 

 

We have even waited for some time to see if the data is in memory (or cache) and needs to get refreshed. But no luck.

 

Regards,

Pratap

Tags: webservice, content, refresh, latest
kevin.imber Jive Employee
kevin.imber
2,726 posts since
Oct 19, 2009
Currently Being Moderated
Oct 27, 2009 5:18 PM in response to: pratapmaddi
Re: Latest content not retrieved when accesed through REST web services.

Hi Pratap,

 

The web services that we provide don't do any type of callbacks, so the data that you enter won't come back to you right after you put it up.  If you'd like to see the latest items, you'll have to make calls to get all the information right after you post your new item.  Let me know if you have any other questions.

 

Thanks,

Kevin

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.