Hi Marc, my replies inline
regards, Achim > Hi! > > I am trying to integrate portlet functionality (JSR 168 / JSR 286) into > an OSGi environment using Apache Pluto and PAX Web. I have a first > working proof-of-concept which supports portlet views and actions and > pluggable themes. > > What I have done to get a portlet application deployed is a little hack > in pax-web-extender-war WebAppPublishingHttpServiceListener. Whenever a > war-bundle is deployed as a web application, it looks for the existence > of a portlet.xml file. If the file exists, a portlet servlet is added to > the web app context and handed over to a portlet-container service. The > service then deploys the registered portlets using the servlet and its > servlet context. ok, as I mentioned in my "first" thought, this sounds like a extender pattern, just like the war extender works. So it looks to me we could need another "extender" here. Maybe just another bundle with a Activator listening on the portlet.xml file just like the war-extender does and registering a new "Portlet" servlet throught the httpservice or the whiteboard extension could do the job. > I would prefer a better solution to trigger the portlet deployment and > don't want the war extender bundle to depend on my portlet service API. > Has anybody here an idea how to do this in a way that fits into the war > extender? What my service needs is at least the bundle instance and the > web app HttpContext to be able to add additional (portlet-) servlets to > the existing context. The service (or a listener) should be notified > whenever a webapp is registered or unregistered. > > Is there already a event mechanism that can be used to achieve that? Is > it a good idea to propagate the HttpContext instance with events? > > Any idea and help is appreciated! > > Thanks, > Marc > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
