In EJB3, the metadata needed would probably be on the implementation class.
Ideally you wouldn't expose that to the client.  You'd just expose the
remote interface.  And, stateful session beans would be supported by default
also.  You can look them up in the same manner as you do stateless session
beans (using the "simplified" API).

-----Original Message-----
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 18, 2006 10:24 AM
To: hivemind-dev@jakarta.apache.org
Subject: Re: EJB3 and EJBProxyFactory...

It would be nice if there was some meta data some where so that the
factory service could automatically adapt and retrieve the EJB
instance the correct way.  Also, it would be nice if the service would
allow access to a stateful bean, as well as a stateless bean.

On 1/18/06, James Carman <[EMAIL PROTECTED]> wrote:
> All,
>
> EJBProxyFactory currently doesn't support EJB3 if you're using the
> "simplified" API, since you don't use "home" objects.  The bean itself is
> retrieved via a JNDI lookup.  To support EJB3, we can either change
> EJBProxyFactory or create a new SimplifiedEJBProxyFactory.  What do you
guys
> want to do?  If we modify the current code, we could assume the simplified
> API if the home interface is omitted maybe.  We could also not require the
> JNDI name anymore, since it defaults to the name of the remote interface.
>
> James
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to