I think I have mentioned this before, but I also see this error if jetspeed has already deployed my updated webapp, but it has not yet finished the process of deleting all the old registry entries and re-registering the portlets.
My portlet.xml file is getting out of control (time to break up my app in to multiple apps) so I think this is why that process is taking so long. Thankfully in production it is fast, so no bother... On 7/17/06, David Sean Taylor <[EMAIL PROTECTED]> wrote:
Stephen Hitchner wrote: > Yes the portlet application does appear in the PORTLETS_APPLICATIONS table. > Thanks though. Ive looked into this some more, and for me, when I get the "Portlet X Not available" error, if I go look at Tomcat's webapps/ directory, I see that the portlet application is only partially expanded, like Tomcat hit an error upon expansion. Unfortunately, I have found no information logged in the tomcat logs. If I then expand out the war file into the partially expanded web app, without shutting down tomcat, the portlet application suddenly becomes available (as it was failing to find the jar files when we intercept the class loader) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
