AFAIK, The remote and home interfaces shouldn't be serializable,
just their parameters and arguments.
I'm still trying to get the hang of this, too. Send me your home
and remote interfaces, your bean implementation and any referenced classes
and let me see if I can help. Send them to [EMAIL PROTECTED]
---
Michael R. Maraya
> ----------
> From: Frederick N. Brier[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Wednesday, July 11, 2001 11:51 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] More on RMI/IIOP warnings
>
> SomeClass and AnotherClass are interfaces that extend EJBObject which in
> turn extend java.rmi.Remote. I don't believe you are supposed to define
> and interface as both Serializable and Remote.
>
> So these are Remote interfaces for classes which I assume are dynamically
> generated by JBoss and act as front end redirectors (for the Bean classes)
>
> whose stubs are the actual objects serialized and should be able to be
> passed and returned as parameters. These redirectors are associated with
> the EJB container and then feed into the chain of interceptors that
> execute
> prior to invoking the method in the bean. Maybe I'm babbling, but I think
>
> I'm getting the hang of the architecture. I'm just confused as to why the
>
> verifier is giving me this error.
>
> Is there a debug switch, log trace, or a suggested approach to trace into
> the JBoss verifier that could perhaps give me more insight into what I
> might be doing wrong? BTW, I did try Fred Loney's suggestion and removed
> all data member references of the EJB's EJBObject interface type. No
> change in the error messages. Please, HELP! Suggestions?!??
>
> Fred.
>
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
