Basically deploying to both portals works fine, but the portlets do not show up in the portlet list of Jetspeed.
Here's the console output after placing the war files in C:\Apache\Jetspeed2\webapps\jetspeed\WEB-INF\deploy:
Note that i tried both the CompaniesAndPeoplePortlet (essentially a HelloWorld portlet) and ImageDisplayPortlet povided by Cameron McKenzie in a similar thread:
I noticed that Cameron's output did not end with the initialization done message, but also included the following lines (for yet another MyAjax portlet) which seems to be exactly what i'm missing here:
I've never seen anyone mention the registry entries in the tutorials. As I said deploying ImageDisplayPortlet fails about the same way so to me it looks like the problem with Jetspeed configuration.
Please share your ideas,
Brad Gardner wrote:What version of jetspeed are you using? Also, could you post your web.xml and portlet.xml? Lastly, if you look in your webapps folder, there should be a deployed instance of your portlet, does it have a generated jetspeed-portlet.xml?
It's jetspeed 2.2.0. The file jetspeed-potlet.xml is NOT generated. I also noticed there's a folder deploy\local which has the following README.txt
This is the default auto deployment folder where you can put portlet application
war files to be automatically deployed as local portlet application by Jetspeed
without a "jetspeed-" prefix in the name as is required for local portlet application
when deployed in the "normal" auto deployment folder (by default this parent deploy folder).
Well, I see no activity in the terminal if I drop a war file here. And the behavior is the same as before if I drop into deploy folder whether or not the file name or <portlet-name> is prefixed with jetspeed-.
Once again the very same archive works just fine under websphere. Thanks!