Yes it is.
An EJB bean is defined as a combination of classes, only one of these
classes need to suppor the EJB API, the class that is directly accessed
from the outside world.
However, your server might have a problem recognizing the non EJB class
when it performs the RMI serialization due to not so obvious class
loader issues.
arkin
Thibault Cuvillier wrote:
>
> Hi,
>
> I wrote an EJB which try to pass by value a serializable object to the
> client.
> I get a ClassNotFound from the server. Is it legal to deploy non EJB classes
> into the EJB jar file ? I did that but it do not works.
>
> Any idea ?
> Tibo.
>
> ===========================================================================
> 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".
