Hi Berin, an Info : the using of the Reflection-API in Fortress isn?t generally denied. The EJB-Spec does only not allow to access information about security, but normal Reflection for Classes is therefore allowed. (the classloading-mechanism is the bigger problem, and knock-down-criteria for me)
Binding Fortress to JNDI does not solve the problem. (that?s what I understand without any problems). Because one thing that is missing the Spec is the "fortress-lookup"-Method inside an EJB, although I get the reference to fortress by JNDI. But, how would you bind the services to JNDI that an EJB can use it without missing the Spec ? That seems not clear to me. Any hints to me ? Thanks, Marco -----Ursprungliche Nachricht----- Von: Berin Loritsch [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 30. Mai 2003 17:04 An: Avalon framework users Betreff: Re: AW: EJB-Spec and Fortress Geiger, Marco (FF) wrote: > ReHi, > > mhh.. that sounds not good :-( > Any idea to come out of this situation ? > ...back to ECM ? ECM does the same things that Fortress is doing. THe only thing I can think of is to bind the services hosted by FOrtress to JNDI, and have Fortress hosted in another context--like the Servlet space or something. -- "You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, The Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. And the 3 most powerful men in America are named 'Bush', 'Dick', and 'Colon' (sic)". -----Chris Rock --------------------------------------------------------------------- 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]
