On Wed, Feb 28, 2001 at 09:44:43PM +0100, Ole Husgaard wrote:
> Hi,
> 
> Toby Allsopp wrote:
> > On Wed, Feb 28, 2001 at 05:00:54PM +0100, Schouten, Andreas wrote:
> > > How can I connect a CORBA server from a jBoss j2ee application?
> > 
> > First, this is a question for jboss-user, not jboss-dev, IMHO.
> 
> This way posted to jboss-user, and
> Marc asked for a redirect to this
> list.

Yes, I saw that later.

> Makes sense to me, as I think it is
> time we start thinking about how to
> support CORBA.

Doesn't make any sense to me. What does wanting to be a CORBA client
have to do with JBoss supporting CORBA?

> A simple MBean (like the one Andreas
> wrote) to support it it that first
> step.

Are you talking about having an MBean that binds the ORB into JNDI? I can
see how that would be useful.

> Later we can think about adding
> support for propagating contexts (in
> particular transaction and security
> contexts) over IIOP. Even later we
> can think about creating an IIOP
> invocation layer for JBoss EJB calls.

I have to admit that you lose me at this point. I will leave this part
of the discussion to people who know about such things.

> But a simple MBean for the CORBA
> service is IMHO first thing to do.
> This should be independent of the
> actual CORBA implementation used.
> At first this service would be
> quite simple, but later it would
> also be responsible to initialize
> hooks to the rest of JBoss for the
> propagation of contexts.
> 
> I don't think that creating JCA
> resources for every possible CORBA
> service is the way to go. Instead
> we should use the CORBA hooks
> available for seemless integration.

http://www.bath.ac.uk/~masjpf/maillists/rosegarden/msg00559.html :-)
Or did you mean "seamless"?

Are you saying that we should propagate the transaction and security
contexts directly over the IIOP invocation rather than going through
the JCA interfaces? That makes sense for CORBA services that are aware
of such things, in fact it makes a lot of sense.

For CORBA services that are simply a way of exposing some external
legacy system the JCA approach would make more sense.

> As for the actual problems that
> Andreas has here, I agree that we
> need more information to be able to
> help. Product and version information,
> and stack traces of exceptions in
> particular.

I can see this turning into an involved technical thread where the
original poster is left without a solution to his immediate problem.

Andreas - please do reply with an exact description of what you're doing
and what's going wrong.

Toby.

Reply via email to