Well, I have successfully embedded Fortress inside an EJB running in JBoss, so these EJB spec restrictions do not seem to be an issue inside JBoss. And I do not need to be portable between servers, so all is fine with me. However, to access these from client, I need some sort of wrapper...and it seems I'll end up writing it myself. I do not want to export Fortress through JNDI, as this would mean that all my components would have to be serializable and this does not have to be the case always.


Rgds,
Neeme

Farr, Aaron wrote:



-----Original Message-----
From: Neeme Praks [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2003 7:16 AM
To: Avalon Developers List
Subject: Re: fortress .roles file doc?

No ideas/suggestions about this?

Neeme Praks wrote:


[snip]

I'm a little confused. Are you trying to write an EJB wrapper for fortress?

From your code example:



public Object invoke(String role, String methodName, Class[] argumentTypes, Object[] argumentValues) throws Exception {



That looks like a wrapper to me.


This has been discussed before [1] and you may want to search the mailing
list archives [2].  However, unless you _have_ to use EJB, you might want to
consider some other alternatives, such as straight JNDI lookup of the
Fortress Container or use AltRMI (or EOB) for remote beans.  Some options
for service exporting can be found in the wiki [3] but it's not very
complete yet.

jaaron

[1] http://marc.theaimsgroup.com/?t=105430164500001&r=1&w=2
[2] http://marc.theaimsgroup.com/?l=avalon-users
[3] http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonObjectBrokering


--------------------------------------------------------------------- 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