Marc, Yes, I have been able to test local interfaces with Cactus on WebLogic 6.1. There should be no difference from the point of view of your test cases whether you test for local interfaces or remote interfaces. However, you do need to set them correctly in the various deployment files (web.xml, web logic.xml - whatever it is on Borland. It is the mapping of external JNDI names to internal representation - + EJB deployment files).
NameNotFoundException seems to that the proprietary JNDI mapping file is either not there or not well configured (for weblogic, it is the weblogic.xml file that you put in your WEB-INF directory, next to web.xml - again, that's for weblogic). It seems to me this issue has more to do with calling local interfaces from a servlet environment than really cactus. Do you already have a servlet from which you call your local interfaces ? If so, then you must use exactly the same for any cactus test. Thanks -Vincent > -----Original Message----- > From: Calello, Marc [mailto:[EMAIL PROTECTED]] > Sent: 08 January 2002 20:04 > To: '[EMAIL PROTECTED]' > Subject: Testing Local Interfaces > > Has anyone been able to successfully test against local interfaces? I may > be experiencing > container-specific issues, we are using Borland Enterprise Server 5.0. > > I am able to lookup remote interfaces but we get the NameNotFoundException > when looking up local interfaces. > > Marc T. Calello > > > -- > To unsubscribe, e-mail: <mailto:cactus-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:cactus-user- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
