|The issue is that the jboss.xml container configuration uses
|container names of
|"Optimized Stateless" and "Non Optimized Stateless'. There are no
|such container
|names in the standardjboss.xml config and so there is no means to match
|up against the "Standard Stateless SessionBean"
|container-interceptors configuration.
huh? ok...
well they *were* there for sure... and it USED to work... (hence the
jboss.xml btw) what happened there... we really need this "guidelines for
commiters".
|We would need the notion of extending a default container config and have
|the jboss.xml container-configuration specific the
|standardjboss.xml config via a
no no, the standardjboss.xml is in code and automated. We know if you are
running stateless or stateful etc etc so you DON'T have to specify ANYTHING
for the standard configuration.
|new element like:
|
|<container-configurations>
| <container-configuration>
| <container-name>Optimized Stateless</container-name>
| <default-container-name>Standard Stateless
|SessionBean</default-container-name>
| <call-logging>false</call-logging>
|...
| </container-configuration>
In other words,
no to the above
|
|The other solution is to add the "Standard Stateless SessionBean"
|container-interceptors
|element to each custom container-configuration in the jboss.xml file.
NO!!! that is where we were the first day... really bad! it feels like this
group is going backwards under its own weight!!!!
this used to work.
marc
|
|----- Original Message -----
|From: "marc fleury" <[EMAIL PROTECTED]>
|To: "jBoss Developer" <[EMAIL PROTECTED]>
|Sent: Saturday, February 10, 2001 10:53 AM
|Subject: RE: [jBoss-Dev] Re: [jBoss-User] Apache+Tomcat+jBoss
|
|
|> 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>
|> |
|> |
|>
|>
|>
|
|
