Thanks Krishnan,
I just read the first white paper "Strategies for integrating OSS/J systems with
CORBA" and it documents some of the same prototyping techniques that I have done with
our current system.
Btw- our legacy CORBA servers are in C++ and of the "un-modifiable" type.
My similar example has a SLSB callout to a legacy CORBA server supplying a Callback
objref. The objref is supported by a servant class as follows:
public class CallbackImpl
: implements CallbackOperations
{
// IDL method
public void _notify() { }
}
My question is why do I need to call this a proxy that "delegates" to a separte EJB
class? I.e., if I want this same servant to be an EJB then all I need to do is also
implement the SessionBean interface, i.e.
public class CallbackImpl
: implements CallbackOperations, SessionBean
{
// add all required EJB methods
}
This compiled and worked fine using the JDK 1.4.05 ORB generated classes for within a
Weblogic 8.1 container.
But more importantly, my real question is to whether this is spec compliant. I.e., we
now have an EJB that can be invoked in an ORB thread that the container has no idea
of. That's not legal, is it?
Btw- In my example, I do not have the servant implement the SessionBean interface but
rather, have it send a message to a JMS queue (via a separate SLSB for pooling
reasons) to be picked up and worked by a MDB.
Thanks again for the pointers,
Mike
----
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED] Behalf Of Krishnan Subramanian
Sent: Tuesday, May 11, 2004 10:03 AM
To: [EMAIL PROTECTED]
Subject: Re: idl-to-CCI classes
Michael,
You might want to take a look at the Borland white papers
on integrating CORBA and EJBs:
http://tinyurl.com/yrmz9
There are number of papers in the above link . . .
If your application server correctly implements the IIOP
stack, then at least the code on the EJB side would not
need to take care of CORBA OTS, CORBA Security etc
explicitly, when invoking CORBA application services.
-krish
> -----Original Message-----
> From: McKnerney, Michael D (US SSA)
> [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 11, 2004 6:53 PM
> To: [EMAIL PROTECTED]
> Subject: Re: idl-to-CCI classes
>
> Your right, CCI was the wrong choice of words.
>
> I guess my question is whether or not someone out there
> provides a "CORBA CA Resource Adapter".
>
> The idea being that EJBs would access the adapter using
> generated classes produced by a special IDL compiler
> (generates java classes, not CCI).
>
> The supplied resource adapter would take care of all CA
> required system interfaces and communicate with a
> ResourceManager running in some "CORBA Connect Engine" that
> communicates with CORBA application services (the EIS in this
> case) that support the same IDL.
>
> The benefit to me is that I don't have to deal with an
> alternative approach of directly communicating with backend
> app services over IIOP and dealing with using (possibly)
> CORBA OTS, CORBA security, etc.
>
> Is this a pipe dream that makes sense?
>
> thanks,
> Mike
>
> -----Original Message-----
> From: Johan Eltes [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 11, 2004 3:48 AM
> To: McKnerney, Michael D (US SSA)
> Subject: Re: idl-to-CCI classes
>
>
> Why would you need CCI?
> /Johan
>
> On 2004-05-11, at 01.48, McKnerney, Michael D (US SSA) wrote:
>
> > Hi,
> >
> > We'd like to integrate a legacy CORBA service with a J2EE
> app server
> > and one alternative is to use the J2EE Connector architecture.
> >
> > As such, does anyone know of a tool that can generate CCI
> java classes
> > automatically from IDL?
> >
> > Even if the method bodies need to be coded manually that
> would still
> > be a vast improvement from having nothing.
> >
> > Also, is this the preferred approach to EJB-CORBA integration?
> >
> > thanks,
> > Mike
> >
> >
> ======================================================================
> > =
> > ====
> > 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".
>
===========================================================================
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".
