This has to do with the container externalization done recently... if the
stuff finds jboss.xml but you don't specify the stacks then it dies ... We
need to look in it.
Does the container externalization work in case we specify a configuration?
it seems not in a differential way (just specify the configuration you want
like it was in tomcat's jboss.xml below
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Dewayne McNair
|Sent: Friday, February 09, 2001 8:57 PM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Re: [jBoss-User] Apache+Tomcat+jBoss
|
|
|Sorry to flood everyone, but, problem solved!
|
|I added a set of <container-interceptors> and
|<persistence-manager></persistence-manager> to both of the
|<container-configurations> and JBoss started picking them up. The
|tomcat-test.ear file now works perfectly. I'm going to complete the docos
|and commit the changes ASAP.
|
|----- Original Message -----
|From: "Dewayne McNair" <[EMAIL PROTECTED]>
|Sent: Friday, February 09, 2001 10:25 PM
|Subject: Re: [jBoss-Dev] Re: [jBoss-User] Apache+Tomcat+jBoss
|
|
|> I'm on to something... if I comment out the container lines in the
|> jboss.xml, everything works. So, it's something to do with the container
|> information. Below is the jboss.xml file from CVS. If I comment out
|> everything between <jboss> and </jboss> the servlet calls the EJB just
|fine.
|> Can anyone spot a problem? For some reason, the new
|> container-configurations are not being picked up.
|>
|> contrib/tomcat/src/resources/test/META-INF/jboss.xml
|
|<snip>
|
|
