Re: Embedding pluto with maven-jetty-plugin - Cannot resolve ToolTips.properties resource bundle

Nils-Helge Garli wrote:
> Hi!
> 
> I'm currently trying to embed pluto with the maven-jetty-plugin to be
> able to run my maven portlet projects by simply issuing the command
> "mvn jetty:run". I have used the information in the faq about "What's
> the easiest way to include a portlet in my webapp" and looking through
> the sources, and I've managed to run my portlet with the jetty plugin
> (I've compiled a list of the steps I had to go through here:
> http://portletwork.blogspot.com/2007/07/mvnjetty-and-portlets.html)
> 
> (I'm not sure if this is the correct way to do it, or maybe a solution
> for this already exists, so if anybody has any corrections/objections,
> please let me know)

Nice work!  Can you link to your post from the pluto wiki?  Perhaps 
under the "Quick Links" section?  http://wiki.apache.org/portals/Pluto

I've wanted to do exactly what you've done, but just haven't devoted the 
effort.  I agree that iterative portlet development using Jetty is worth 
the trouble of getting it all set up.

> But one of the things I have not been able to solve yet is using the
> pluto:modeAnchor and pluto:windowStateAnchor tags in the jsp file that
> acts as the portal. The problem is that it cannot resolve the
> ToolTips.properties resource bundle. I assume this is a classloader
> issue. I have tried putting the ToolTips.properties in the
> WEB-INF/classes folder (also in various sub folders) without success.
> I've even tried putting it in the same jar as the tag classes, but
> still no luck. Any ideas where I should put the ToolTips.properties
> file, or what I have done wrong since my "embedded pluto" project
> cannot resolve it?

The class that needs the ToolTips.properties file is 
org.apache.pluto.driver.tags.ToolTips which is normally packaged as part 
of the pluto-portal-driver jar, as are the pluto portal tags.  The 
ToolTips.properties file is normally packaged under WEB-INF/classes of 
the pluto-portal war.  Normally all of these dependencies (the classes 
and properties file) are executed from within a single classloader.

The requirement is that the ToolTips.properties file needs to be 
accessible from the ToolTips class's classloader, per 
http://java.sun.com/j2se/1.4.2/docs/api/java/util/ResourceBundle.html#getBundle(java.lang.String)

I'm not altogether familiar with Jetty's classloading.  Do you have a 
stack trace and perhaps a listing of files showing how you have Pluto 
deployed in Jetty?

Thanks,
Elliot