Re: class hierarchy and extending a Cactus Test Case
Hi, In article [EMAIL PROTECTED], Tue, 17 Jul 2007 11:11:25 -0500, Jay Baker [EMAIL PROTECTED] wrote: jbaker.work I am using ServletTestCase. Extending this test case works just fine. No jbaker.work problem. However, I have an existing object hierarchy that I would like to jbaker.work preserve. Although all of the Cactus documentation discusses extending one jbaker.work of the Cactus tests, I figured I could just implement some appropriate jbaker.work interface(s) and use delegation. As I read further, I understood the use of jbaker.work publicly accessible attributes of the various Cactus test cases. If this jbaker.work access were done through getters and setters, I would have no problem. I cannot understand what you want to do, so am having questions. Q1: What is the object for which you want to preserve its object hierarchy? Q2: What is the relation of the object and Cactus? Q3: How should the object and Cactus work together? A safe example would be helpful. Best Regards, Kazuhito SUGURI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Writing Cactus test cases for EJB 3.0 and JBoss 4.2 GA.
Hi Vincent, My project is currently using EJB 3.0 and JBoss 4.2 GA. I have few queries regarding using Cactus with this. Here are my queries: 1. Does Cactus fully support EJB 3.0 (J2EE 1.5)? The latest release of Cactus version: 1.7.2 is only J2EE 1.3 compliant. 2. I know that Cargo (http://cargo.codehaus.org http://cargo.codehaus.org/ ) is supporting Jboss 4.x container. Has this been integrated with Cactus so that the cactus Ant task can be used with JBoss 4.x? a. If yes could you provide me the details of how can I get a developer build of Cactus including the Cargo integration for JBoss 4.x? b. If not could you provide me the details of how can I integrate Cargo with the current Cactus release so that I can run the test cases with JBoss 4.x? 3. When is the next Cactus release with support for JBoss 4.x and EJB 3.0(J2EE 1.5) scheduled? We require this information since we are not able to test the EJBs and automate the build to run the test cases. Regards, Rakesh Shete DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails.
Re: class hierarchy and extending a Cactus Test Case
Thank you for your interest. Let's say that I have a base class that is used
for regular (not in container) test cases. Call this MyBaseTestCase. I have
other test classes that extend this base class. The base class provides
services that I need and the current design uses inheritance. For example,
it uses a template pattern approach to enforce that some metadata is
available. So we have:
public class TestCase03 extends MyBaseTestCase {
... }
Now I want to add in container testing using Cactus. I could do:
public class TestCase04 extends ServletTestCase {
... }
but I don't want to because of the existing hierarchy I have.
So I tried:
public class TestCase04 extends MyBaseTestCase implements CactusTestCase {
...}
and delegated to an instance of ServletTestCase for the implementation of
the CactusTestCase interface. That did not work however. To check things
out, I created my own class MyCactusBaseTestCase that looks very much like
ServletTestCase but it extends MyBaseTestCase. This works, but I would
prefer to not rely on the source code of ServletTestCase.
I hope that clarifies things a bit and thanks for your help.
-- Jay
On 7/18/07, Kazuhito SUGURI [EMAIL PROTECTED] wrote:
Hi,
In article [EMAIL PROTECTED],
Tue, 17 Jul 2007 11:11:25 -0500,
Jay Baker [EMAIL PROTECTED] wrote:
jbaker.work I am using ServletTestCase. Extending this test case works
just fine. No
jbaker.work problem. However, I have an existing object hierarchy that I
would like to
jbaker.work preserve. Although all of the Cactus documentation discusses
extending one
jbaker.work of the Cactus tests, I figured I could just implement some
appropriate
jbaker.work interface(s) and use delegation. As I read further, I
understood the use of
jbaker.work publicly accessible attributes of the various Cactus test
cases. If this
jbaker.work access were done through getters and setters, I would have no
problem.
I cannot understand what you want to do, so am having questions.
Q1: What is the object for which you want to preserve its object
hierarchy?
Q2: What is the relation of the object and Cactus?
Q3: How should the object and Cactus work together?
A safe example would be helpful.
Best Regards,
Kazuhito SUGURI
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Writing Cactus test cases for EJB 3.0 and JBoss 4.2 GA.
Can anyone let me know about this? I require this information as soon as possible to decide the next course of action. --Regards, Rakesh Shete = Hi Vincent, My project is currently using EJB 3.0 and JBoss 4.2 GA. I have few queries regarding using Cactus with this. Here are my queries: 1. Does Cactus fully support EJB 3.0 (J2EE 1.5)? The latest release of Cactus version: 1.7.2 is only J2EE 1.3 compliant. 2. I know that Cargo (http://cargo.codehaus.org http://cargo.codehaus.org/ ) is supporting Jboss 4.x container. Has this been integrated with Cactus so that the cactus Ant task can be used with JBoss 4.x? a. If yes could you provide me the details of how can I get a developer build of Cactus including the Cargo integration for JBoss 4.x? b. If not could you provide me the details of how can I integrate Cargo with the current Cactus release so that I can run the test cases with JBoss 4.x? 3. When is the next Cactus release with support for JBoss 4.x and EJB 3.0(J2EE 1.5) scheduled? We require this information since we are not able to test the EJBs and automate the build to run the test cases. Regards, Rakesh Shete DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails.
