|
Home > Archive > WebSphere Portal Server > January 2004 > portlet update
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Giovanna Arnone 2004-01-19, 2:59 pm |
| Hi all,
I have a couple of questions about the portlet update mechanism. When I
update a portlet while many users are connected to the page to which the
portlet belong, I have to wait many minutes. The update seems
successfull but the portlet is still the old one (I can check this
looking at the log files in which I see the messages coming from the old
one). How can I force the update of the portlet?
Another question: what is the mechanism of updating a portlet, moreover
what happens in WAS when a portlet is updated?
Any help will be greatly appreciated.
| |
|
| hello........
I think that if you delete the cache of the AppServer
(<installroot>\WebSphere\AppServer\temp (delete all folders under this
directory)) will resolve. Maybe you have that delete your browser cach too.
The another question, is better you give more details. Like, what process
are you using for publish.
"Giovanna Arnone" <giovanna_arnone@it.ibm.com> wrote in message
news:3F700697.9090405@it.ibm.com...quote:
> Hi all,
> I have a couple of questions about the portlet update mechanism. When I
> update a portlet while many users are connected to the page to which the
> portlet belong, I have to wait many minutes. The update seems
> successfull but the portlet is still the old one (I can check this
> looking at the log files in which I see the messages coming from the old
> one). How can I force the update of the portlet?
> Another question: what is the mechanism of updating a portlet, moreover
> what happens in WAS when a portlet is updated?
> Any help will be greatly appreciated.
>
|
|
|
|
|