gmane.comp.jakarta.cactus.user

RE: Using cactus with maven

Juan Jose Aragones Guillen — 2012-01-05T16:04:57

Hello
I got cactus to work and create the EAR files for each module (so much thanks for your help!). I'm now struggling with something else: I have to get these EARs to be used by WID. I've understood that the right plugin to be used is was6:servicedeploy:
Reading http://mojo.codehaus.org/was6-maven-plugin/examples/generating-process-server-ears.html and it's example I just don't get it right. I already have the EARs so I assume I only really need from this example "A POM project that calls ServiceDeploy" getting the EAR filenames some way. That's the first stop: how do I get it to use the plugin with each of the EARs?.

Thanks, 
 JUAN JOSÉ ARAGONÉS

RE: Using cactus with maven

Juan Jose Aragones Guillen — 2012-01-05T16:04:57

Hello
I got cactus to work and create the EAR files for each module (so much thanks for your help!). I'm now struggling with something else: I have to get these EARs to be used by WID. I've understood that the right plugin to be used is was6:servicedeploy:
Reading http://mojo.codehaus.org/was6-maven-plugin/examples/generating-process-server-ears.html and it's example I just don't get it right. I already have the EARs so I assume I only really need from this example "A POM project that calls ServiceDeploy" getting the EAR filenames some way. That's the first stop: how do I get it to use the plugin with each of the EARs?.

Thanks, 
 JUAN JOSÉ ARAGONÉS

RE: Using cactus with maven

Juan Jose Aragones Guillen — 2012-01-05T16:04:57

Hello
I got cactus to work and create the EAR files for each module (so much thanks for your help!). I'm now struggling with something else: I have to get these EARs to be used by WID. I've understood that the right plugin to be used is was6:servicedeploy:
Reading http://mojo.codehaus.org/was6-maven-plugin/examples/generating-process-server-ears.html and it's example I just don't get it right. I already have the EARs so I assume I only really need from this example "A POM project that calls ServiceDeploy" getting the EAR filenames some way. That's the first stop: how do I get it to use the plugin with each of the EARs?.

Thanks, 
 JUAN JOSÉ ARAGONÉS

AW: Using cactus with maven

2011-12-20T13:21:08

Hello

Your console output shows three EARs being built (application 1 - 3). So I assume you have set up a multi module build. Therefore I would guess you have something like three <module> sections in your POM. These <module> sections are the EAR specific parts I was talking of.

Make sure you clearly understand the difference between <pluginManagement> and <plugin>. Module specific parts should go in a <plugin> section under <module>.

If you need some explanation on this, there is a free online Maven book called "Maven: The Complete Reference".


Best regards
Christian Schima


-----Ursprüngliche Nachricht-----
Von: Juan Jose Aragones Guillen [mailto:jaragones< at >kana.com] 
Gesendet: Dienstag, 20. Dezember 2011 13:10
An: Cactus Users List
Betreff: RE: Using cactus with maven

Hello
Thanks for answering. I understand everything but the last part. EAR specific sections of my POM? Don't have any. Can you put an example (or a link to one)? Also if you can which section should they go in...

Thanks, 
 JUAN JOS

RE: Using cactus with maven

Juan Jose Aragones Guillen — 2011-12-20T12:10:23

Hello
Thanks for answering. I understand everything but the last part. EAR specific sections of my POM? Don't have any. Can you put an example (or a link to one)? Also if you can which section should they go in...

Thanks, 
 JUAN JOSÉ ARAGONÉS
BUILD'N'RELEASE ENGINEER
e : jaragones< at >kana.com
EMEA Headquarters
209 Airport Road West
Belfast, Northern Ireland BT3 9EZ

SOLUTIONS | CASE STUDIES | KANA.COM | LAGAN.COM






The information in this email and any attachments is confidential and intended solely for the attention and use of the named addressee(s). It may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it, and should notify us immediately

-----Original Message-----
From: Christian.Schima< at >t-systems.com [mailto:Christian.Schima< at >t-systems.com] 
Sent: 20 December 2011 12:04
To: cac

AW: Using cactus with maven

2011-12-20T12:04:25

Hello

When you declare your cactus.integration.maven2 plugin in the section <pluginManagement>  this declaration is valid for all spots in your POM where you reference this declared plugin.

Since you have included the <configuration> in the <pluginManagement> section, this configuration is used everywhere in your POM unless you overwrite it (obviously you haven't).

This means each of your EAR builds is using the same Cactus plugin <configuration> and therefore processes the same EAR file.

The solution would be to move the <configuration> section of your cactus plugin in the EAR specific sections of your POM. Only keep the general aspects of your cactus plugin in the <pluginManagement> section.


Best regards
Christian Schima

________________________________
Von: Juan Jose Aragones Guillen [mailto:jaragones< at >kana.com]
Gesendet: Dienstag, 20. Dezember 2011 12:36
An: cactus-user< at >jakarta.apache.org
Betreff: Using cactus with maven

Hello,
I know cactus have been moved to the Attic but my supervisor has given

Using cactus with maven

Juan Jose Aragones Guillen — 2011-12-20T11:36:25

Hello,
I know cactus have been moved to the Attic but my supervisor has given me the job to make he project work using this plugin with maven 3.0.3.
We are using Jenkins for CI and the idea is to run cactus from there (we already run junit tests as it's possible to invoke top-level maven targets just writing the goals).
Right now I'm testing cactus with the project in which we run the junit tests (no worries, several VM's and snapshots -and not touching the base project-  just in case I screw something). But here are several thing I don't really understand. I'll only write some questions and, if I get any feedback will go on with the questions:
- I'm using "mvn cactus:cactifyear" as the idea is to create an EAR and get it deployed in Websphere using WAS6 plugin for maven. The thing is I don't really understand what does cactifyear do or how it works. I have no idea what to use as srcfile. Here you have what I have in my pom.xml:
<project>
   ...
    <dependencies>
        <dependency>
          <groupId>org.

Re: Failed to recognize cactifywar

Vinay Nagrik — 2011-11-30T22:46:54

Hello group,

I am working on cactus and running test remotely on TeamCity server.  I get
following errors.  Could someone please help me with these, so that I can
remove them and run my tests successfully.

BUILD FAILED
/homes/build-jmp/JMP/release-branches/R11.4/CEMS/buildSpace.xml:262: The
following error occurred while executing this line:
/homes/build-jmp/JMP/release-branches/R11.4/CEMS/remoteTestSetup.xml:131:
Problem: failed to create task or type cactifywar
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

Failed to recognize cactifywar

Vinay Nagrik — 2011-11-21T19:22:48

Hello group,

I am working on cactus and running test remotely on TeamCity server.  I get
following errors.  Could someone please help me with these, so that I can
remove them and run my tests successfully.

BUILD FAILED
/homes/build-jmp/JMP/release-branches/R11.4/CEMS/buildSpace.xml:262: The
following error occurred while executing this line:
/homes/build-jmp/JMP/release-branches/R11.4/CEMS/remoteTestSetup.xml:131:
Problem: failed to create task or type cactifywar
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

failed to create cactify war

Vinay Nagrik — 2011-11-18T22:04:37

Hello group,

I am working on cactus and running test remotely on TeamCity server.  I get
following errors.  Could someone please help me with these, so that I can
remove them and run my tests successfully.

BUILD FAILED
/homes/build-jmp/JMP/release-branches/R11.4/CEMS/buildSpace.xml:262: The
following error occurred while executing this line:
/homes/build-jmp/JMP/release-branches/R11.4/CEMS/remoteTestSetup.xml:131:
Problem: failed to create task or type cactifywar
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

Need pointers on Cactus integration with Webshphere commerce server.

Ramakrishna Dulam — 2011-10-18T16:38:11

Hi,

 

I am using Cactus for the first time and finding it difficult for
setting up cactus and integrating with websphere commerce server.

Any pointers/documentation on the same will be very helpful.

 

Appreciate you help on this aspect.

 

Thanks,

Ram.



-----------------------------------------
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or
entity to which it is addressed. If the reader of this e-mail is
not the intended recipient or his or her authorized agent, the
reader is hereby notified that any dissemination, distribution or
copying of this e-mail is prohibited. If you have received this
e-mail in error, please notify the sender by replying to this
message and delete this e-mail immediately.

Jakarta Cactus moving to the Attic

Henri Yandell — 2011-08-06T07:25:51

A heads up for the Jakarta Cactus user community that the Cactus project has
been 'moved to the Attic'. This means that the Jakarta developers (more
formally its Project Management Committee) have voted to retire Cactus
and move the responsibility for its oversight over to the Attic project.

Loosely speaking this means that the projects resources will be moved to a
read-only state.

You can read more about the Apache Attic and the process of moving to the
Attic at http://attic.apache.org.

You can follow this process in JIRA:

  https://issues.apache.org/jira/browse/ATTIC-120

Thanks,

Henri Yandell on behalf of Jakarta Cactus + the Attic.

Cactus Ant Task - unable to look up data source

K Hein — 2011-05-09T02:59:28

Hi everyone,

I am using Cactus Ant Task to execute the unit testing classes and I am
facing the problem with data source look up. The tests are failed with
exception saying unable to look up the data source. However, if I invoke the
tests from the browser manually, everything is fine and all the tests are
executed successfully. Does anyone have encounter this problem before? Could
anybody provide any solution. Thanks.

Regards,

Kyi Hein

tests in separate ear

Jakub 1983 — 2011-04-21T12:47:51

Can test be put into separate ear, or they should be put in the same ear as
tested ejb3 ?

Can I access local session beans from separate ear (but deployed in the same
jboss) ?

Cactus issues with JBoss 5.1.0

Shay Thompson — 2011-02-27T21:07:50


Hi fellow Cactus users.  We've been using Cactus 1.7.2 running in JBoss 4.2.1 for a couple years now without any problems.  We recently upgraded to JBoss 5.1.0 and now our ear is failing to deploy.  We use the Ant target cactifyear to modify our product ear to include the cactus.war with our tests.  The ear deploys fine if we don't cactify it.  We haven't changed anything with regards to cactus.

I was wondering if anyone else has moved to JBoss 5.1.0 and has some suggestions on steps I can take to get our ear working?

Errors I see in the JBoss log:

2011-02-25 18:20:59,969 ERROR [org.apache.catalina.core.StandardContext] (main) Context [/cactus] startup failed due to previous errors
java.lang.RuntimeException: could not find <ejb-local-ref>'s local interface com.adobe.idp.um.businesslogic.directoryservices.DirectorySynchronizationManager in web.xml of cactus.war
..
2011-02-25 18:20:59,969 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss.web

Problem with Cookie Manager: Not adding all cookies to next request

Matti Simperi — 2011-01-18T14:19:35

Hello!

I'm having a problem with cookie manager, which I can't understand. The
cookie manager is working well in all other situation, but once it is not
"parsing" all cookies for the next request. The only different I can see is
that that cookie is much longer then other cookies. I tried to change cookie
policies, but without any help. The only different is that this
missing cookie is set to different path then others. My next URL address is
still to that path.

Any ideas what could be the problem?


Best regards,
Matti



*Response from url X*

Response headers:
HTTP/1.1 302 Moved Temporarily
Date: Tue, 18 Jan 2011 14:10:57 GMT
Server: Apache-Coyote/1.1
Cache-Control: private
Cache-Control: no-cache
Cache-Control: no-store
Cache-Control: must-revalidate
Cache-Control: max-age=0
Pragma: no-cache
Expires: 0
Set-Cookie: uas.master=_8539ca8a89456809f7478481447a10bdca9faf8c; Path=/has;
Secure
Set-Cookie:
a3b51706c02ca92e=LQVEOrnybFdHdNaC43ozMdEKhbcIp8oRwUHL5LbpOHCTNbJhw4r0-O5UafBgWsE1FlQ0BfFRZNZvbGPXJLXqI5MPh94

RE: Cactus tutorial needs updating

Jim Babka — 2010-11-10T21:56:28

Well, the tutorial classes are not in a separate package. They are in the 
default package, so there is no package name to specify. Does Tomcat or 
Cactus have a problem with the default package?

Jim Babka
Senior S/W Engineer and Team Lead, Context Aware Dynamic Selection
(512)286-5195, tie line 363-5195
babka< at >us.ibm.com



From:   <chris.persichetti< at >thomsonreuters.com>
To:     <cactus-user< at >jakarta.apache.org>
Date:   11/10/2010 03:23 PM
Subject:        RE: Cactus tutorial needs updating




I had the same problem.  You need to include the package name of the class 
in the url.

http://localhost:8080/test/ServletTestRunner?suite=com.company.TestSampleServlet


--Chris
-----Original Message-----
From: Jim Babka [mailto:babka< at >us.ibm.com] 
Sent: Wednesday, November 10, 2010 2:14 PM
To: Cactus Users List
Subject: RE: Cactus tutorial needs updating

OK, so I got Tomcat 5.5.31, copied all the Cactus JARs to Tomcat's 
common/lib directory, then followed the tutorial instructions. I

RE: Cactus tutorial needs updating

2010-11-10T21:19:25

I had the same problem.  You need to include the package name of the class in the url.

http://localhost:8080/test/ServletTestRunner?suite=com.company.TestSampleServlet

--Chris
-----Original Message-----
From: Jim Babka [mailto:babka< at >us.ibm.com] 
Sent: Wednesday, November 10, 2010 2:14 PM
To: Cactus Users List
Subject: RE: Cactus tutorial needs updating

OK, so I got Tomcat 5.5.31, copied all the Cactus JARs to Tomcat's 
common/lib directory, then followed the tutorial instructions. I set up a 
web app as directed, with the following directory structure under webapps:

├──test
│  └──WEB_INF
│     └──classes

The classes directory has:

SampleServlet.class      TestSampleServlet.class

However, when I try to browse to 
http://localhost:8080/test/ServletTestRunner?suite=TestSampleServlet, I 
get this error. Is there something else I need to do in order to enable 
Tomcat to find the class? Should the class be in a different place than 
the test/WEB-INF/classes directory?

HTTP Status 500

RE: Cactus tutorial needs updating

Jim Babka — 2010-11-10T21:14:08

OK, so I got Tomcat 5.5.31, copied all the Cactus JARs to Tomcat's 
common/lib directory, then followed the tutorial instructions. I set up a 
web app as directed, with the following directory structure under webapps:

├──test
│  └──WEB_INF
│     └──classes

The classes directory has:

SampleServlet.class      TestSampleServlet.class

However, when I try to browse to 
http://localhost:8080/test/ServletTestRunner?suite=TestSampleServlet, I 
get this error. Is there something else I need to do in order to enable 
Tomcat to find the class? Should the class be in a different place than 
the test/WEB-INF/classes directory?

HTTP Status 500 - 

type Exception report
message 
description The server encountered an internal error () that prevented it 
from fulfilling this request.
exception 
javax.servlet.ServletException: Failed to load test suite 
[TestSampleServlet], Reason is [Class not found "TestSampleServlet"]
 
org.apache.cactus.server.runner.ServletTestRunner

RE: Cactus tutorial needs updating

Bennett, Jeffrey — 2010-11-10T14:15:52

 
Jim-

Can't speak officially, but I use Cactus 1.8.1 with Tomcat 5.5.30 (which
does still have the common/lib structure).  I don't think you need any
of those jars in Tomcat itself, although you probably need to place them
in the cactified-war.  In the setup I use, I only see aspectjrt (but we
do some AspectJ stuff) and commons-logging (necessary, as we want Tomcat
to use Log4J for its own logs) from the list you provided.  However,
commons-discovery, commons-httpclient, cargo, cactus, jasper and junit
are in most of the cactified wars we operate on.

Good Luck-
-Jeff

P.S. Anyone successful at taking Cactus to Tomcat 7 yet?  Pretty sure
it's impossible due to cactus's use of Cargo 1.0B2 (short of recompiling
Cactus), but just curious.


-----Original Message-----
From: Jim Babka [mailto:babka< at >us.ibm.com] 
Sent: Tuesday, November 09, 2010 7:00 PM
To: cactus-user< at >jakarta.apache.org
Subject: Cactus tutorial needs updating

The Cactus tutorial needs to be updated. It talks about Tomcat 4 (which
you can't even

Cactus tutorial needs updating

Jim Babka — 2010-11-10T00:00:00

The Cactus tutorial needs to be updated. It talks about Tomcat 4 (which 
you can't even get anymore). The real issue, though, is it says this:

----------------------------
Copy the following jars to [tomcat-root]/common/lib: 
cactus.jar 
commons-httpclient.jar 
commons-logging.jar 
junit.jar 
aspectjrt.jar 
----------------------------

First, there is no common/lib directory in Tomcat 6, and second, those 
JARs do not exist in the Cactus 1.8.1 distribution. Here are the JARs that 
are there now:

aspectjrt-1.5.3.jar
cactus.core.framework.uberjar.javaEE.14-1.8.1.jar
cactus.integration.ant-1.8.1.jar
cactus.integration.shared.api-1.8.1.jar
cargo-ant-1.0-beta-2.jar
cargo-core-container-jonas-1.0-beta-2.jar
cargo-core-uberjar-1.0-beta-2.jar
commons-discovery-0.4.jar
commons-httpclient-3.1.jar
commons-logging-1.1.jar
geronimo-ejb_2.1_spec-1.1.jar
geronimo-j2ee-management_1.0_spec-1.1.jar
httpunit-1.6.jar
jasper-compiler-5.5.9.jar
jasper-runtime-5.5.9.jar
junit-3.8.2.jar
mx4j-3.0.2.jar
mx4j-remote-3.0.2.jar
nekoh