-
1. Re: ClassCastException when casting to remote interface
james ahlborn Dec 7, 2006 11:16 AM (in response to novad protikin)in 4.0.5.GA the naming value to change is now in:
deploy/naming.sar/META-INF/jboss-service.xml -
2. Re: ClassCastException when casting to remote interface
novad protikin Dec 8, 2006 7:54 AM (in response to novad protikin)I have set CallByValue to true in deploy/naming.sar/META-INF/jboss-service.xml.
The ClassCastException is still there.
Is there anything else I have to do? -
3. Re: ClassCastException when casting to remote interface
Santosh Kottamasu Dec 16, 2006 3:14 AM (in response to novad protikin)Hello, I ran into a similar problem few days ago, and the issue was with packaging the ear, there were some class files copied incorrectly.
How are you packaging your ear? can you list the contents? -
4. Re: ClassCastException when casting to remote interface
novad protikin Dec 18, 2006 4:01 AM (in response to novad protikin)Hi,
as I wrote in my original post, I use Eclipse to generate the EAR archive (for the EJB project) and WAR archive (for the web project). I'm not sure but I think this is a function provided by the Exadel Studio plugin that I use.
The only thing to do in Eclipse is to add a reference of the EJB project to the web project. With this, a jar file containing the EJB-project's class files will be automatically included in the WAR file, in
WEB-INF\lib
I don't see any possibility to influence this behavior. -
5. Re: ClassCastException when casting to remote interface
Alex Grönholm Dec 18, 2006 7:19 AM (in response to novad protikin)as I wrote in my original post, I use Eclipse to generate the EAR archive (for the EJB project) and WAR archive (for the web project). I'm not sure but I think this is a function provided by the Exadel Studio plugin that I use.
You should package only the remote interface files in your Web project. I have a similar thing going on, and I have an extra project for the remote interface files.
It is quite likely that the problem stems from having two copies of the same code deployed.
Besides, I packaged the WAR inside the EAR, and not separately. -
6. Re: ClassCastException when casting to remote interface
max payn Jan 2, 2007 3:27 AM (in response to novad protikin)Salam,
With ECLIPSE, when you create the war file, don't include the interfaces classes by specifying this on the packaging configuration.
you can see the JBoss Tutorial for creating EJB. -
7. Re: ClassCastException when casting to remote interface
Alex Grönholm Jan 2, 2007 11:33 AM (in response to novad protikin)With ECLIPSE, when you create the war file, don't include the interfaces classes by specifying this on the packaging configuration.
you can see the JBoss Tutorial for creating EJB.
I must remind that the "packaging configuration" is a JBossIDE specific feature. Normally, you create an EAR project and add your Web and EJB projects in it. That approach works with all application servers.