Hi Jesper,

WRT this issue you had, I'm proposing to move this discussion and
implementation in the Cargo project (http://cargo.codehaus.org) as
everything that has to do with containers
configuration/start/stop/deployment is now moved there and I'm refactoring
the Cactus Ant/Maven integrations to use Cargo.

Join us there on cargo-dev if you wish to follow the discussion.

Thanks
-Vincent

> -----Original Message-----
> From: Jesper Linvald [mailto:[EMAIL PROTECTED]
> Sent: vendredi 2 juillet 2004 10:43
> To: Cactus Users List
> Subject: RE: Cactus and weblogic 8.1
> 
> Hi Vincent
> 
> Jesper Linvald
> MAERSK DATA TRANSPORT
> Tel no.: +45 3911 1891
> e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> "Vincent Massol" <[EMAIL PROTECTED]>
> 01-07-2004 20:42
> Please respond to
> "Cactus Users List" <[EMAIL PROTECTED]>
> 
> 
> To
> "'Cactus Users List'" <[EMAIL PROTECTED]>
> cc
> 
> Subject
> RE: Cactus and weblogic 8.1
> 
> 
> 
> 
> 
> 
> Hi Jesper,
> 
> > -----Original Message-----
> > From: Jesper Linvald [mailto:[EMAIL PROTECTED]
> > Sent: mercredi 30 juin 2004 13:00
> > To: Cactus Users List
> > Subject: RE: Cactus and weblogic 8.1
> >
> > Sure I can explain what I mean by hardcoded:
> > The code speaks for it self:
> 
> Yes :-)
> 
> See below
> 
> >
> > public final void startUp()
> >     {
> >         try
> >         {
> >             prepare("cactus/weblogic7x");
> >             Java java = createJavaForStartUp();
> >             java.setDir(new File(tmpDir, "testdomain"));
> >             java.createJvmarg().setValue("-hotspot");
> >             java.createJvmarg().setValue("-Xms32m");
> >             java.createJvmarg().setValue("-Xmx200m");
> >             File serverDir = new File(dir, "server");
> >             java.addSysproperty(createSysProperty("weblogic.Name", "
> > testserver"));
> >             java.addSysproperty(createSysProperty("bea.home", beaHome));
> >             java.addSysproperty(createSysProperty("
> > weblogic.management.username", "weblogic"));
> >             java.addSysproperty(createSysProperty("
> > weblogic.management.password", "weblogic"));
> > java.addSysproperty(createSysProperty("java.security.policy",
> > "=./server/lib/weblogic.policy"));
> >             Path classpath = java.createClasspath();
> >             classpath.createPathElement().setLocation(new
> File(serverDir,
> > "lib/weblogic_sp.jar"));
> >             classpath.createPathElement().setLocation(new
> File(serverDir,
> > "lib/weblogic.jar"));
> >             java.setClassname("weblogic.Server");
> >             java.execute();
> >         }
> >         catch(IOException ioe)
> >         {
> >             getLog().error("Failed to startup the container", ioe);
> >             throw new BuildException(ioe);
> >         }
> >     }
> >
> > This is the code that gets called from the Maven Cactus plugin....i
> think!
> 
> It is
> 
> > If that is the case the call to weblogic.Server is hardcoded with some
> > important values that I need to set. I.e. if I use my own config.xml it
> > specify a domain, and a server name, password etc.
> >
> > Isn�t it so?
> 
> You're right. ATM we haven't externalized the domain, server name,
> password,
> etc. because nobody asked. My idea was to provide an attribute so that
> users
> would be able to point to an existing weblogic domain directory instead of
> a
> config.xml file. Would you think that it will help?
> --> Sure - I am all for it - it would make the plugin more flexible and
> open towards different deployment scenarios which is a good thing!
> 
> Just a question fro you: why is it important that you run weblogic with
> your
> exact domain name, username and password? We're talking about testing
> albeit
> integration testing.
> --> If these things are not provided correctly when trying to start from
> my config.xml (which do specify these credentials) I will be prompted
> (someclass.askHumanBeing()) for those various credentials or it wont start
> up at all because the "testdomain" is not what was specified in my
> config.xml.
> We have multiple subprojects/components in our project and they each
> specify a config.xml with highly customized content. It is not something
> that I should have to adjust/change in order for the tests to run.
> 
> However, I don't see how these parameters can affect the tests. That said,
> it's true that it's nice to be running with the exact same parameters as
> the
> runtime application.
> --> I agree
> 
> I'd be happy to try to make the <weblogic7x> task as customizable as
> possible to that users do not have to bother about knowing how to
> start/stop
> WebLogic. If you have any idea please fire them.
> --> The only thing I can think of is to open up for all the possible
> parameters to weblogic.Server and/or weblogic.Deployer (which I am using
> in the plugin I just made)!
> 
> Thanks for your help and thoughts!
> 
> Regards :)esper
> 
> Thanks
> -Vincent
> 
> >
> > Regards
> >
> > Jesper Linvald
> > MAERSK DATA TRANSPORT
> > Tel no.: +45 3911 1891
> > e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> > "Vincent Massol" <[EMAIL PROTECTED]>
> > 30-06-2004 07:40
> > Please respond to
> > "Cactus Users List" <[EMAIL PROTECTED]>
> >
> >
> > To
> > "'Cactus Users List'" <[EMAIL PROTECTED]>
> > cc
> >
> > Subject
> > RE: Cactus and weblogic 8.1
> >
> >
> >
> >
> >
> >
> > Hi Jesper,
> >
> > Do you think you could explain what you mean by "hardcoded" so that we
> > improve the task?
> >
> > For example, if you check here
> > (
> >
> http://jakarta.apache.org/cactus/integration/ant/task_cactus.html#weblogic
> > 7
> >
> > x) you'll see that you can provide your own config.xml.
> >
> > In addition the <cactus> task always expect a cactified war/ear so that
> > shouldn't be a problem either.
> >
> > All that said, I'm not sure that the <weblogic7x> task works for WL 8.1.
> >
> > Thanks
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Jesper Linvald [mailto:[EMAIL PROTECTED]
> > > Sent: mercredi 30 juin 2004 00:03
> > > To: 'Cactus Users List'
> > > Subject: RE: Cactus and weblogic 8.1
> > >
> > >
> > > Thank you guys,
> > >
> > > I have tested both approaches and I think the weblogic7x is a bit to
> > > "hardcoded" for my needs - I need to create/run a container based
> pretty
> > > much only on a predefined config.xml and my ear file is precactified
> so
> > my
> > > approach has been to create my own plugin invoking weblogic.Server and
> > > weblogic.Deployer directly and I additionally created a simple test
> > caller
> > > that simply calls the test url and adds its output to a maven report.
> > This
> > > almost works now :)
> > >
> > > Thanks for the input!
> > >
> > > Regards Jesper
> > >
> > > >-----Original Message-----
> > > >From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > > >Sent: 29. juni 2004 07:39
> > > >To: 'Cactus Users List'
> > > >Subject: RE: Cactus and weblogic 8.1
> > > >
> > > >Oh ok. I thought you were using the existing <weblogic7x> container
> > > >element.
> > > >
> > > >Thanks
> > > >-Vincent
> > > >
> > > >> -----Original Message-----
> > > >> From: Bret Kumler [mailto:[EMAIL PROTECTED]
> > > >> Sent: mardi 29 juin 2004 01:06
> > > >> To: 'Cactus Users List'
> > > >> Subject: RE: Cactus and weblogic 8.1
> > > >>
> > > >> I actually use
> > > >>
> > > >> <containerset>
> > > >>                                             <generic name="Weblogic
> > 8.1.2.0"
> > > >> port="${test.port}"/>
> > > >> </containerset>
> > > >>
> > > >> And I use the following to start & stop the server.
> > > >>
> > > >>
> > > >> <target name="start.weblogic">
> > > >>                             <java classname="weblogic.Server"
> > fork="yes"
> > > >> dir="${target.weblogic81.dir}/testdomain">
> > > >>                                             <classpath>
> > > >> <pathelement
> > > >> location="${weblogic.home.81}/weblogic81/server/lib/weblogic.jar"/>
> > > >>                                             </classpath>
> > > >>                                             <jvmarg
> > value="-hotspot"/>
> > > >>                                             <jvmarg
> value="-ms256m"/>
> > > >>                                             <jvmarg
> value="-mx256m"/>
> > > >>                                             <jvmarg
> > > >> value="-
> > > >>
> Djava.library.path=${java.library.path};${weblogic.home.81}/weblogic
> > > >> 81/server/bin"/>
> > > >>                                             <jvmarg value="-
> > > >Dweblogic.Name=testserver"/>
> > > >>                                             <jvmarg value="-
> > > >Dbea.home=${weblogic.home.81}"/>
> > > >>                                             <jvmarg value="-
> > > >Dbitfone.home=${bitfone.home}"/>
> > > >>                                             <jvmarg
> > > >> value="-Dweblogic.management.username=${weblogic.username}"/>
> > > >>                                             <jvmarg
> > > >> value="-Dweblogic.management.password=${weblogic.password}"/>
> > > >>                                             <jvmarg
> > > >> value="-Djava.security.policy==./server/lib/weblogic.policy"/>
> > > >>                             </java>
> > > >>             </target>
> > > >>
> > > >>             <target name="stop.weblogic">
> > > >>                             <java classname="weblogic.Admin"
> > fork="yes">
> > > >>                                             <classpath>
> > > >> <pathelement
> > > >>
> > location="${weblogic.home.81}/weblogic81/server/lib/weblogic.sp.jar"/>
> > > >> <pathelement
> > > >> location="${weblogic.home.81}/weblogic81/server/lib/weblogic.jar"/>
> > > >>                                             </classpath>
> > > >>                                             <arg line="-url
> > > >t3://${machine}:${test.port}"/>
> > > >>                                             <arg line="-username
> > > >${weblogic.username}"/>
> > > >>                                             <arg line="-password
> > > >${weblogic.password}"/>
> > > >>                                             <arg
> > value="FORCESHUTDOWN"/>
> > > >>                             </java>
> > > >>             </target>
> > > >>
> > > >> -----Original Message-----
> > > >> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > > >> Sent: Saturday, June 26, 2004 10:54 AM
> > > >> To: 'Cactus Users List'
> > > >> Subject: RE: Cactus and weblogic 8.1
> > > >>
> > > >> I haven't tried it but it should work fine. It seems others like
> Bret
> > > >have
> > > >> it working using the <weblogic7x> element, even though it's not
> > > >officially
> > > >> supported yet (we need to create a <weblogic8x> nested element).
> > > >>
> > > >> Thanks
> > > >> -Vincent
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Jesper Linvald [mailto:[EMAIL PROTECTED]
> > > >> > Sent: samedi 26 juin 2004 15:54
> > > >> > To: [EMAIL PROTECTED]
> > > >> > Subject: Cactus and weblogic 8.1
> > > >> >
> > > >> >
> > > >> > Hi all,
> > > >> >
> > > >> > Regarding the Maven Cactus plugin and its use with Weblogic 8.1:
> > > >> >
> > > >> > The question is simply whether it is possible to use the plugin
> > with
> > > >> this
> > > >> > container (which tweaks do I need to perform to make it work?) or
> > > >should
> > > >> I
> > > >> > just forget about it and write my own Maven plugin?
> > > >> >
> > > >> > As of now I can�t even start up the container through the plugin!
> > > >> >
> > > >> > I can see you are in the middle of a discussion on the subject
> but
> > I
> > > am
> > > >> > not
> > > >> > quite sure what to make of it :)
> > > >> > Are you working on updating the plugin and if so - when do you
> > figure
> > > >it
> > > >> > will be released?
> > > >> >
> > > >> > Thank you and best regards
> > > >> >
> > > >> > ____________________________
> > > >> > :)esper Linvald
> > > >> >
> > > >> >
> > > >> > ---
> > > >> > Outgoing mail is certified Virus Free.
> > > >> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > >> > Version: 6.0.708 / Virus Database: 464 - Release Date: 18-06-2004
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > >> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> > > >> >
> > > >> >
> > > >> > ---
> > > >> > Incoming mail is certified Virus Free.
> > > >> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > >> > Version: 6.0.711 / Virus Database: 467 - Release Date: 25/06/2004
> > > >> >
> > > >>
> > > >> ---
> > > >> Outgoing mail is certified Virus Free.
> > > >> Checked by AVG anti-virus system (http://www.grisoft.com).
> > > >> Version: 6.0.711 / Virus Database: 467 - Release Date: 25/06/2004
> > > >>
> > > >>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> 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]
> > > >
> > > >
> > > >---
> > > >Incoming mail is certified Virus Free.
> > > >Checked by AVG anti-virus system (http://www.grisoft.com).
> > > >Version: 6.0.708 / Virus Database: 464 - Release Date: 18-06-2004
> > > >
> > >
> > > ---
> > > Outgoing mail is certified Virus Free.
> > > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > Version: 6.0.708 / Virus Database: 464 - Release Date: 18-06-2004
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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]

Reply via email to