[jboss-user] [EJB 3.0] - Re: EJB 2.1 and 3 coexisting?

[goldrimtang]

Hi Wolf,

Thanks for your reply. Yes, the method has a transaction attribute (RequiresNew). If I change the parameter from an array (Object[]) to a type 'Vector', it stops complaining about this during deployment type. I can live with that ... the problem is that then another exception happens, also at deployment time:


  | 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
  | 
  | java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
  | 
  | 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
  | 
  | 	at org.jboss.util.naming.Util.rebind(Util.java:125)
  | 
  | 	at org.jboss.util.naming.Util.rebind(Util.java:113)
  | 
  | 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
  | 

Which makes me wonder why all these problems just because a totally unrelated stateless session bean EJB 3 is being deployed.

Thanks again for your time.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081054#4081054

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081054