Please post WebLogic-specific questions and issues to the BEA WebLogic newsgroups (NNTP server: www4.weblogic.com).
<vendor>
The ClassCastException is typically caused by classes being accessible from two or more classpaths (i.e., Java Classpath, WebLogic classpath, and/or Servlet classpath). In general, you should put classes that are going to be used by servlets and EJBs (which are loaded by different class loaders) in the WebLogic classpath.
</vendor>
Thanks,
Robert
At 09:14 AM 2/28/00 -0700, you wrote:
I understand that "deployment" is proprietary on the different application servers. I was told this by BEA systems. I know that the myBeanHomeImpl_ServiveStub class is generated by the ejbc (EJB compiler). So, maybe the EJB Compiler is the "deployment" piece. (I originally thought they were referring to the deployment descriptor, however it appears to be pretty generic) So, I would think that all of those classes need to be regenerated on the SUN box for deployment on the SUN box. The ejbc utility comes with weblogic, so you should be able to run your classes through it on SUN to get new stub and skel classes.
Betsy Barker
Parikshit wrote:
Hello all,I have a Stateful Session Bean and a servlet is used to invoke it , i.e. I am getting the homeInterface of the bean in the servlet and then getting the RI and using it's business methods.Both the servlet and session bean are registered with the application server(Weblogic).This thing is working fine with the Weblogic server on NT but if I use the same .class file with Weblogic server on SunSolaris and doall the required things(like registration in properties file) I am getting a class Cast Exception at (myBeanHomeImpl_ServiveStub.I feel that the object which is returned after lookup cannot be casted to myHome.I am not able to figureout why this is not working with Solaris while it is working with NT.I will be thankful if anyone can provide me any info. to solve this problem.Thanks in advance,Payal.
