On Fri, 13 Aug 2004 10:35:40 +0200, Vincent Massol <[EMAIL PROTECTED]> wrote:
Can you give me the same laundry list of things to do to adapt the ant integration?
* There are 2 Ant tasks: <cactifywar> and <cactus>. How is a portlet deployed? As a WAR file? If so, you need to modify cactifywar so that it supports cactifying a portlet war.
* For the <cactus> task, you need to implement the classes that starts/ stops the container you're working with (which is?) and the code that configures/deploys the portlet archive. For this, create a o.a.c.integration.ant.container.[containername] package. You can check the other similar packages to see how it's done for the other containers.
Let me know if you have more specific questions.
Hi Vincent,
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. This is called a portlet application. There is no URL mapping information in the portlet.xml file. It's up to the portal (a separate peice of software, often "installed" on the app server, not deployed) to determine how to call the portlets. The common pattern is that a portal renders pages with portlets on them, so there is no direct link between a portlet and the URL that invokes it. Most portals do however have some URL syntax that allows you to invoke a portlet directly for testing purposes. As I mentioned earlier, all portals do this differently.
Currently the catifywar task modifies the web.xml to add the URL mapping to the appropriate redirector. This isn't meaningful in the portlet case because there is no mapping to the portlet in the portlet war.
What I need to do is add some parameter to the cactus task to specify the URL to use to get the portal to render the portlet redirector. 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?
I'm currently deploying our (Novell's) own portable portal and portlet container on JBoss 3.2.5, but we can run on the Novell ExteNd app server as well as WebLogic, WebSphere and straight Tomcat. The current appserver specific invocation code should work fine, we just need a way to tell it what URL to invoke.
Thoughts?
Thanks -John
-- ---------------------------------------------------------------- John Rousseau [EMAIL PROTECTED] Novell, Inc. Phone: +1 781 464 8377 404 Wyman Street Fax: +1 781 464 8100 Waltham, MA 02451 http://www.novell.com ----------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
