I started to detach the portlet container stuff last week, but I have not removed it yet
from 2.6 until I have the detached container able to run the testsuite using the web
integration SPI.
The status on the web integration SPI is that for now it works with tomcat which means
that it is able to modify tomcat deployed war files to insert the request dispatch servlet
and produce added/removed events to the registered listeners. This is not unit tested yet.
It requires to put jars in the lib directory of tomcat and to modify tomcat
conf/server.xml to add a listener class that setup the web application registry. Later of
course we want to try to have other implementation of the web SPI when it is needed.
I started to write a test portal based on the web SPI and the JBoss MC 2.0 Beta3 that
boostrap a few beans for the moment. On the web SPI add/removed event for web applications
it takes the usual PortletApplicationImpl and PortletContainerImpl and let JBoss MC take
care of the instantiation and the life cycle of the beans. So this is a good progress imho
(thanks Ales for helping me on that :-) ).
So only the deployment stuff is integrated (yet not unit tested). What is left is the
runtime stuff which consist in being able to translate web request into portlet container
interactions. Previous implementation was based on the server module (in 2.6). We will
probably have for now a simpler implementation for now that will use a simple servlet.
I worked also on the test module and worked on having it being able to use Cargo and JBoss
Remoting instead of JBoss 4.x MainDeployer and JMX Remoting. This is not yes commited in
the SVN. The goal here is to be able to use the test framework with any environment since
Cargo is able to deploy to multiple containers and JBoss Remoting seems to provide also an
easy to use remoting layer.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076065#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...