I would like to say but if I replace the ICommand with and AbstractCmdObject it all work without even casting why?
----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 24, 2001 4:41 PM Subject: RE: java.rmi.MarshalException Corba Bad_Param - anybody?????????????????? pls 1) Then you can try reorder the jar files in classpath, 'cos classloader is loading also all underlying classes for your class, and you can have diferent versions of them in diferent jar files. Did you have this problem from the point when you start modification of this class or was it working fine before? 2) Did you tried following: ( it's possible the remote class loader can't implicitly cast CreateCmd to ICommand and then you must use the explicit casting, but this is not known to compiler at the compile time, so there is no exception when compile files) CreateCmd c = new CreateCmd() CmdProcessor.Process ((ICommand) c) Rah > -----Original Message----- > From: Glenn Dickson [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 24, 2001 3:07 AM > To: [EMAIL PROTECTED] > Subject: java.rmi.MarshalException Corba Bad_Param - > anybody?????????????????? pls > > > There are no older CmdProcessor versions around. I've looked > in the spec but > infortunately not really helpful. > > I'm not using Corba explicitly but the J2EE App server that > comes with Sun > j2EE JDK seems to. > > I'm really desparate so pls any coments???????? > > > Generally, MarshalException is RMI Exception and is thrown, > when for some > > reason serializing of Object and sending it to client > fails, for more see > > the Java RMI Spec. > > > > I had sometimes same problem when somewhere in the > classpath exists the > > older version of class and RMI ClassLoader tried to use it. > In your case, > > try find if you don't have somewhere CmdProcess bean remote > interface with > > method CmdProcessor.Process (AbstractCmd aCmd) and delete it, then > recompile > > your source and try again. > > Hope this helps > > > > Rah > > > > -----Original Message----- > > From: Glenn Dickson [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, October 23, 2001 9:25 AM > > To: [EMAIL PROTECTED] > > Subject: java.rmi.MarshalException Corba Bad_Param - > > anybody?????????????????? pls > > > > > > Hi! > > > > Just wanted to know if anyone has ever come a across the error : > > > > java.rmi.MarshalException Corba Bad_Param > > > > > > Stateless Bean > > --------------------- > > My stateless session bean (CmdProcessor) has a method signature of : > > CmdProcessor.Process (ICommand aCmd) > > > > Client > > -------- > > My client creates the object (it implements the ICommand > interface) : > > CreateCmd c = new CreateCmd() > > (CreateCmd implements the java.io.Serialization class) > > > > The client calls the Process method in the session bean > like so passing > the > > : > > CmdProcessor.Process (CreateCmd) > > > > I receive the MarshalException error message. > > > > Now using Abstract Class > > ------------------------------- > > It works if I replace the CmdProcessor.Process (ICommand aCmd) > > with an object and make the CreateCmd EXTEND AbstractCmd: > > CmdProcessor.Process (AbstractCmd aCmd) > > > > Is it that I cannot use an interface class with EJB method ??? > > What is the cause of this MalshalException error ? > > > > Any ideas would be appreciated. > > Thanks in advance > > > > Glenn > > > > ========================= > > 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".
