Hey
Saurabh Sahai wrote:
> >No it doesn't. :-) The container could generate a class (during runtime)
> >which calls the ejbFindByPrimaryKey-method. Since that technique relies
> >on compile-time knowledge (i.e. the generated class uses the specific
> >EntityBean) reflection is not necessary.
>
> Yes. But but there could be containers that do not generate class at
> deployment time. For them there is no other option but to use reflection
> (crappy it may sound, but I guess the container will need to live with that)
Well, containers have to generate the EJBObject and EJBHome
implementations. No option there. Could you explain how a container
could be compliant with EJB1.0 and not generate classes?
/Rickard
--
Rickard Oberg
Computer Science student@LiTH
@home: +46 177937
Email: [EMAIL PROTECTED]
Homepage: http://move.to/rickard
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
