In both 3.0 and 3.1 the specification of the invoker to use for a
bean is being done in the enterprise-beans element rather than in a
container-configuration element. The invoker(s) is really more of a
container config element associated with the client interceptor stack
which is defined in the
In both 3.0 and 3.1 the specification of the invoker to use
for a bean is being done in the enterprise-beans element
rather than in a container-configuration element. The
invoker(s) is really more of a container config element
associated with the client interceptor stack which is defined
- Original Message -
From: marc fleury [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 14, 2002 11:44 AM
Subject: RE: [JBoss-dev] Shouldn't the ejb invoker binding be in the
container-configuration section
In both 3.0 and 3.1 the specification of the invoker to use
What I would like to see is something like this:
jboss
enterprise-beans
session
ejb-nameMySession/ejb-name
configuration-nameStandard Stateless
SessionBean/configuration-name
client-configuration-names
The
invocation protocol for all stateless session beans should be
defined at a container related level, not a particular
Negative, detached invokers.
In the future you will configure your client at the JMX level. Saying
for this client give me this interface, this stack of client
]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Sunday, July 14, 2002 2:03 PM
Subject: Re: [JBoss-dev] Shouldn't the ejb invoker binding be in the
container-configuration section
This is pretty much what we have in 3.1. Look at the jboss.xml file of
the hellojrmpiiop test:
http
