Hi,
I dont't think differential container
configuration is broken.
Looks like the same problem I had with
the jbosstest bmp.jar:
The name specified in jboss.xml does
not match a name in standardjboss.xml,
and the entire configuration is
specified there.
In this case whoever wrote jboss.xml
has chosen not to do differential
container configuration, so unless
the configuration name is changed
to the right template in
standardjboss.xml, the interceptor
chain *will* have to be specified.
Best Regards,
Ole Husgaard.
Scott M Stark wrote:
>
> > |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
> >
> Ok, I must be missing where the notion of the default stateless session
> bean container config is being picked up. I'll go through it again and find
> it. I did test the case of a custom container not specifying the
>container-interceptors
> and these were correctly picked up from the standardjboss.xml config,
> so if the jboss.xml container name does not matter this should be working.
> I'll verify it in detail.
>
> Dewayne did not post what his standardjboss.xml "Standard Stateless SessionBean"
> config looked like. The problem could be as simple as it being out of date with
> respect to what is required post the container-interceptors addition. Dewayne,
> what does your standardjboss.xml look like?
