Try making an ear file containing the ejb-jar file and a war file, which 
in turn contains your servlet. The servlet will then see the interface 
classes directly out of the ejb-jar file. look at the tomcat test .ear 
file in the jboss-tomcat distribution (or get it out of the contrib 
module in CVS and build it)

-danch

Edilmar Alves wrote:

> Hi,
> 
> I have an environment with NT 4 + Apache 1.3.12
> + Tomcat 3.2.1 + JBoss 2.2.1. I already had Tomcat
> installed and working fine when I installed JBoss.
> Then, because my env is for development, I decided
> to run Tomcat independent from JBoss, not starting
> both together.
> 
> I made an Application, a Servlet and a Bean.
> First of all, I tested Application+Bean, something
> like the sample into JBoss manual pages. All fine!
> 
> Then, I tested Servlet+Bean. I made a Servlet JAR
> file with the following classes: servlet, remote
> and local interface to Bean, and other utility
> classes needed. The error arised from Tomcat was
> the same that occurred into JBoss manual pages,
> talking about setting class path for home interface.
> "javax.naming.CommunicationException: [Root ...Home].
> 
> I tried the following solutions:
> 1st) Set Class-Path into Manifest.mf: it didn't work!
> 2nd) Extract the interface classes to ./classes/...
>      It didn't work!

> 3nd) Put into Tomcat wrapper.properties the path to
>      find the classes into the bean.
>      wrapper.class_path=c:\jboss-2.2.1\deploy\testebean.jar
>      IT WORKED FINE!
> Is this the only way to do this???
> 
> PS: My email client arises an exception and I don't know
> if this message was sent. Sorry for this confirmation...
> 
> 
> 
> 
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user



_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to