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]

Reply via email to