Hi Vincent,
Sorry for the delay in responding. I was away for a few days.
On Mon, 23 Aug 2004 10:59:39 +0200, Vincent Massol <[EMAIL PROTECTED]> wrote:
I'm a bit stuck with the ant tasks. Let me give you a little background.
A portlet (or set of portlets) is deployed as a class(es) in a WAR file. It's a regular WAR file which also contains a /WEB-INF/portlet.xml descriptor.
Ok. So there is no web.xml file, right?
Yes there it. It's a regular WAR file. Portlets can include (properly written) servlets and JSPs through a RequestDispatcher. The portlet model is very similar to the servlet one in many ways. There is no association with the servlets and servlet mappings in the web.xml with the portlets in the WAR though. There's also a required portlet.xml DD, which we probably should modify so that it lists the PortletTestRedirector, but there is no direct URL assoication with the portlets in the portlet.xml. It's all up to the portal.
The portlet redirector will be deployed in the portlet WAR being tested. Any ideas on how you would like the task syntax to look to handle this?
From what I understood, there are no web.xml file in a portlet application and thus the cactifywar should not try modify the web.xml file. However it should add the Cactus jars. Then at execution time (i.e. the <cactus> task, we need to pass some information, namely the URLs to call the portlet redirector.
I think the best solution would be to:
1/ create a separate Ant task: <cactifyportletwar> or something like this that would reuse some code from cactifywar but not try to modify a web.xml file. Alternatively maybe there is a possibility of modifying the existing cactifywar and add an attribute to it (such as: cactifywebxml = "true|false", defaults to true).
Ok. Sounds good.
2/ create a nested element for the <cactus> task, say <novellportal> (I don't know the portal container name) and make it support the portlet redirector URLs as attributes.
Yeah. We need this for all the common portals. It's a tiny bit of code for each portal, but I don't think a simple "redirectorUrl" element will suffice.
Of course it won't be that easy (there might be some issues with ping URLs for example) :-).
Yup. Already ran into this. :-)
Ok. Thanks. Others reading this list have already sent me mail privately, so there does seem to be some interest.
I'm still waiting for Novell to say it's ok for me to contribute. Once that happens, I'll send you my code to review.
Thanks -Vincent
Thanks -John
-- ---------------------------------------------------------------- John Rousseau [EMAIL PROTECTED] Novell, Inc. http://www.novell.com ----------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
