<vendor>

Id download Sybase EAServer which allows you to not only install a C++
component and run it in the server, but expose it as an EJB with a Home and
Remote interface, do a JNDI lookup for it, etc.   And like William suggests,
Id reccomend also downloading comparing this to WebLogic.  You will be
pleasently surprised.

</vendor>

Dave Wolf
Internet Applications Division
Sybase


> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Delahunty
> Sent: Monday, September 04, 2000 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: Exposing a native component as an EJB.
>
>
> Hi guru's
>
> I am building a system that will make extensive use of a component that is
> built in C++. However the supplier of this component also have a Java
> interface to using this compoent. So i will access this component
> via Java.
>
> The rest of my system is written in EJB and so i would like to expose this
> component as an EJB. However the ejb spec states that ejb must not load a
> native libarary. Now i presume this means that the EJB container
> classloader
> does not load the native component. However i would like to write a helper
> class that access the component via it's Java interface.
>
> So, does this still constitute loading a native libarary ?
>
> The only other way i can see is to use corba, however it seems a long way
> around to go from Java (the EJB code) through CORBA to Java (the component
> interface code). Rather than just java to java.
>
> any ideas ?
>
> ==================================================================
> =========
> 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".

Reply via email to