> That's a good idea, thanks for the info.
Not as good as yours:
adding the ejb-jar to the classpath in jboss' startup script also seems to break
jboss' auto-deploy feature :-(
> I solved the problem differently - I added my jar to JBOSS_HOME/dist/lib/ext. But
>it accomplishes the same thing
: Bernd Proissl [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 29, 2001 7:23 AM
To: [EMAIL PROTECTED]
Subject: RE: solved: calling stateless EJB via SOAP
It was at least a classpath problem, i did the follwing:
- dropped soap.war in in jboss/deploy (thanks to
http://www.jboss.org/forums/
mcat's classpath the the ejb-jar?
Bernd
> > -Original Message-
> > From: Winkler Lisa-P29719 [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, November 28, 2001 9:45 PM
> > To: '[EMAIL PROTECTED]'
> > Cc: '[EMAIL PROTECTED]'
> >
put my
>ejb jar to make SOAP happy. I even
> tried stuffing it in the soap.war that is deployed in Tomcat, which I shouldn't have
>to do but I was getting desperate!
> Has anyone solved this problem?
>
> Thanks,
> Lisa
>
> -
is deployed in Tomcat, which I shouldn't have to do
but I was getting desperate! Has anyone solved this problem?
Thanks,
Lisa
-
List: soap-user
Subject: calling stateless EJB via SOAP
From: "Cook, Martin" <[EMAIL PROTECTED]>
Date: 2
I am attempting to use Apache ver 2.2 SOAP to call a stateless EJB deployed
in JBOSS ver 2.2.2. The error I get back from Apache is:
Fault Code = SOAP-ENV:Server
Fault String = Error in connecting to EJB
The JBOSS log shows this:
[EmbeddedTomcatSX] In TemplateProvider.locate()
[Embed
