Hey
Ashwin Dinakar wrote:
> >Generally speaking, I would not do this. Instead I would package this
> >kind of functionality in a separate library that is available to the
> >beans, but not through the classpath of the EJB-jar, but rather through
> >the system classloader or similar. As has been noted in earlier posts,
> >the classloader is the key to avoiding the restrictions of EJB.
> >
> >/Rickard
>
> Rickard,
> Am I right in stating that I could follow the same principle with Enterprise
>Java Beans (either a session or entity) talking to socket-based servers as well ?
> Put the client socket code in a different jar file ( all I want is a bean to talk to
>a tcp/ip socket server). Import the classes in my bean code and load these classes
>using the system classpath.
Exactly. Your code would be what soon will be called Connector (see the
Connector API JSR at JDC :-). This is how all vendors will do legacy
system integration.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
