this fairly describes our production system with a couple exceptions:
1. all of our commands/responses are fully qualified method calls. if
reflection can process the call, it'll happen. exception otherwise.
2. we haven't yet built the corba adapter, but it'll be simple to do when we
need it.
i'd like to trade war stories sometime if you're game Rubens.
seeya,
jim
> -----Original Message-----
> From: Rubens Gomes [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, June 08, 1999 11:58 AM
> To: [EMAIL PROTECTED]
> Subject: Re: CORBA-EJB
>
> We have implemented a data-driven interface to
> our core EJB services (XML for instance.) If you are
> coming in from a Corba client, then define a simple
> IDL with tag/value structures for commands and responses.
> And establish a contract between client and server on what is
> expected on those tags (maybe something like an XML dtd).
> Develop a parser on the server side to honor the contract, and
> have the parser delegate calls to respective beans. Some of
> your tags could be a hint to what bean and method is going to be
> called. We have made some of our tags to be the same as the
> fully qualified session bean class name so that we can use
> introspection in the corba-ejb adaptor.
>
> I cannot publish our IDL in this list, because it has not
> been made public yet.
>
> @java.sun.com 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".
