in the meantime i switched to JBoss 4.2.3 but the problem is
still there. From my point of view there are exaclty 2 choice
for an explanation of this problem:
1) I misunterstood something and overseen some <container-..>
configurations in jboss.xml. The following posting on the
JAVA greenhorn ranch shows a similar problem. But for any
reason, this behaviour was clear to the author (but not me;)
Can anybody explain me, what he talks about?
2) There may be a problem with the deployment for JEE-1.3/1.4
ear's on a JEE-5 Application server or some settings to be done,
when you want to run that old application on a novel app server.
that was my fault. In jboss.xml deployment descriptor
i have overseen, that assigned in a stateful session bean
the following standard setting:
<configuration-name>Standard Stateless Sessionbean</configuration-name>
That has in turn no instance-cache assignment in the default container
definition. The good this is, that a started to understand the cool
architecture of jboss.
Thanks for your audience;-)