Rickard �berg wrote:
>
> 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.
Request for clarification: when you say "B returns it to A". My
understanding is that you're not supposed to send EJBObjects around (are
they serializable?). A and B could be on different machines in which
case an EJBObject on A may not work in B.
Am I wrong and that you are able to pass EJBObjects around to different
EJB's, clients, etc?
Thanks,
--
Joel Shellman
Chief Software Architect
The virally-driven B2B marketplace for outsourcing projects
http://www.ants.com/90589781
