> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: 25. mars 2003 21:57 > To: 'Maven Users List' > Subject: Container start/stop + packaging (was RE: WebLogic Server > plugin) > > > Hi Michal, > > Some ideas about container start/stop and application packaging: > > * The Cactus project is currently starting/stopping/configuring several > containers (Orion, Resin, JBoss, WebLogic, Tomcat, etc). We have > recognized that this is not Cactus specific and are slowly working > towards externalizing this (we're lacking time ATM unfortunately). > > * We would potentially like to start a jakarta-commons project, whose > goal would be to provide an "API" for starting/stopping containers and > then provide an "SPI" for the different containers. Maybe another > project in jakarta-commons would be in charge of generating completely > configured applications (including directory structure and config files > for a given app server) >
This sounds like a very interesting approach. If I understand you correctly, you would like to move the start/stop logic currently in Cactus and Maven's appserver plugin to this new project. I suggest the name "Jakarta Commons Appserver" (Container is too generic and J2EE is discriminating for app servers like Tomcat and Jetty). > * Obviously this project would implement the upcoming JSR (117 or > something like that - Not sure if this JSR is only about deployment or > if it also about starting/stopping containers) > JSR 117 is about J2EE Application Availability. I think you mean JSR 88 (The J2EE Deployment API): http://java.sun.com/j2ee/tools/deployment/ http://www.jcp.org/en/jsr/detail?id=88 However, the J2EE Deployment API says nothing about starting and stopping servers (only about J2EE components). AFAIK there is no JSR or standard API for that. > * Anyway, we believe it is better to implement this in a commons project > rather than in a Maven plugin as an important feature is that it should > be able to start/stop containers from different front ends (Maven, Ant, > Eclipse, etc). > I agree. > * ATM, the way Cactus implements container start/stop and application > packaging is using Ant. This allows us to reuse the Ant scripts from the > Maven plugin, from Ant (of course) and also from our Eclipse plugin > (which internally calls Ant). > It can be implemented as pure java classes (no ties to Ant) and still be possible to use from Ant. It is no longer necessary to extend Ant's Task class in order to be used in a <taskdef>. The only thing you need is an execute() method. If a "proper" Ant task is really needed, I'd prefer it as a simple wrapper around the "core" API. (I hate it when useful functionality is too tightly integrated with Ant.) > I'm curious to know what others think? > It would be really nice to add a broader set of functionality than start/stop to this API: o A high level API for configuration of an Appserver (setting up JDBC Connection pools, JMS etc) o JSP and EJB precompilation (not sure if this belongs in Vincent's proposed Commons API though) Cheers, Aslak > Thanks > -Vincent > > > -----Original Message----- > > From: michal.maczka [mailto:[EMAIL PROTECTED] > > Sent: 25 March 2003 13:18 > > To: Maven Users List > > Subject: RE: WebLogic Server plugin > > > > It think that definitely the best place for it would be appserver > plugin. > > > > Maybe you can look at Cactus plugin? There is a part of such > functionality > > implemented there. > > > > I think once more such plugins like yours exists it will be easier to > see > > how to control > > different application server in common manner + make plugins like > Cactus > > use appserver plugin. > > > > > > Michal > > > > > > > > > > > > > > > > > -----Original Message----- > > > From: Aslak Helles�y [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, March 25, 2003 9:37 AM > > > To: Maven Users List > > > Subject: WebLogic Server plugin > > > > > > > > > Hi! > > > > > > A colleague and I have been working on a weblogic plugin for Maven. > This > > > plugin has the following functionality: > > > > > > o Stub-generation with weblogic.ejbc > > > o JSP compilation with weblogic.jspc > > > o Deployment of J2EE components (EAR, WAR and EJB) using the > > > weblogic.deploy > > > class > > > o Execution of WLShell scripts (see http://tinyurl.com/83ns) > > > o Creation of empty weblogic domains (from a template included in > the > > > plugin) > > > > > > 1) Has anyone else been working on this? > > > > > > 2) Would anyone be interested if we contributed this plugin to > Maven? > > > > > > 3) In > maven/src/plugins-build/examples/exampleear-1.0/project.properties > > > there are some maven.weblogic.* properties. I can't see these being > used > > > anywhere. Can anyone enlighten me on what these were intended for? > > > > > > Cheers, > > > Aslak > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
