Hi!
marc fleury wrote:
> > able to deploy with several protocols at once. Just don't see how it
> > could work)
>
> Again I don't see a fundamental problem. It can be all modeled as
> contextual information that travels with the MethodInvocation...
No. When you call getEJBObject() you get one object back. That should be
used to communicate with the container. This object can only support one
protocol to talk to the container. You're saying "use the contextual
information". And just what would that "contextual information be"? The
name of the protocol used by the "client"? That won't give you much
though. For example, client X may call session A through protocol Foo,
which calls session B through protocol Bar, which in turn calls
getEJBObject. The "client" in this case used Bar, so lets return an
EJBObject using the Bar protocol. So now B returns it to A which returns
it to X. But X can't use the EJBObject since it doesn't know how to do
the Bar protocol.
And that is the problem. If beans couldn't call beans it would be much
simpler, because then the above wouldn't happen.
I suggest that you also spend some "considerable thought" on this before
call it "not a fundamental problem". Which it is. :-/
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
