Here's my setup. I have ejb1 that I'm testing with cactus. ejb1 uses ejb2,
via remote interface, that exists in a separate container. ejb2, is
basically a dao, findOrderItemsBy( String ProductCode), etc. To test ejb1,
I'd like my cactus test use ejb2 to verify the data is actually there. for
instance. if i submit an order using ejb1.submitOrder( orderSubmit ), I'd
like to make sure that the order and the order items exist after submitting
the order.
I'm most likely not explaining this very well, but what's the easiest/best
way to get a handle to ejb2 from my cactus test classes? ejb1 has the
JNDI_URL and context factory (needed to get ic from ejb2 container) as part
of its deployment descriptors. is there some way that i can modify my
cactified war so that its jndi has this stuff? Can i specify that stuff via
the xml that is used for mergewebxml?
ejb1 has the following in the dd to get its remote bean. the jndi_url is
placed in from the ant script to allow varried environments.
<env-entry>
<env-entry-name>cbc.initial.context.factory</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>weblogic.jndi.WLInitialContextFactory</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>cbc.jndi.url</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>@JNDI_URL@</env-entry-value>
</env-entry>
any insights would be most appreciated!!!
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.528 / Virus Database: 324 - Release Date: 10/16/2003
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
