> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 25 March 2003 22:20
> To: Maven Users List
> Subject: Re: Container start/stop + packaging (was RE: WebLogic Server
> plugin)
>
> I'd much rather it was 'pure' java rather than Ant tasks as the
> implementation.
Agreed. However, we may not be talking exactly about the same thing.
There are several features that I'd like to see (in one or several
projects):
1/ start/stop of containers. I agree that a Java API is the best for
this. Actually the Ant project already has an interface for that and
several tasks for different containers. The new project could use those
as a start point (we could ask/help Ant to them make use of them in the
existing tasks).
2/ fully packaging an application for a given container (and for a given
environment). For example, if I am using weblogic, it would generate a
zip with the following:
<my domain name>
|_ applications
|_ myear.ear
|_ lib
|_ [some jars that need to be put in the system cp]
|_ classes
|_ [some classes that need to be put in the system cp]
|_ config.xml
|_ DefaultAuthenticatorInit.ldift
|_ fileRealm.properties
|_ SerializedSystemIni.dat
|_ wlDefaultKeyStore.jks
|_ startContainer.cmd|startContainer.sh
|_ stopContainer.cmd|stopContainer.sh
The way I see it, this project would provide these default files (with
basic default values - best guesses) but the user would also be able to
supply them (i.e. pass them as input). Note: This is what is done by the
Cactus Ant Integration for all containers
For this project, I believe a Java API is not the best. Ant seems to me
the best common denominator. I may be wrong though.
I believe the start/stop project and this packaging project should be 2
separate projects.
Ideas? Comments?
Thanks
-Vincent
>
> I also work closely with WebSphere and have start/stop jelly scripts
for
> that at the moment.
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 26/03/2003 07:56:56
AM:
>
> > 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)
> >
> > * 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)
> >
> > * 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).
> >
> > * 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).
> >
> > I'm curious to know what others think?
> >
> > 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
