No.
I use reflection to emulate component inheritance and polymorphism in my
EJBs. However, my code only uses the reflection API query classes that ARE
accessible to my EJB component (there is <ejb-ref> information in my
ejb-jar.xml, etc.), so I'm following the rules.
If reflection makes sense for your application use it. I read the
restriction as a good one: you shouldn't be using reflection to try and get
around the security rules or use it to get access to resources you wouldn't
otherwise be entitled to.
Kurt in Atlanta
>-----Original Message-----
>From: Rong Sang [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, September 13, 2000 3:06 PM
>To: [EMAIL PROTECTED]
>Subject: Reflection API in EJB
>
>
>Could someone please explain the following restriction
>in EJB programming?
>
>"Using the Reflection API to query classes that are
>not otherwise accessible to the EJB component due to
>Java's security rules."
>
>Does this mean we should totally abandon Reflection in
>both EJB classes and any helper classes?
>
>Thanks,
>
>Rong
>
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Mail - Free email you can access from anywhere!
>http://mail.yahoo.com/
>
>===============================================================
>============
>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".
>
===========================================================================
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".
