Wolf,
It looks like, when there are EJB3 beans involved, everything is processed by
the EJB3 deployer. We actually tried migrating all the session beans to EJB3.
It still fails, this time because it doesn't find the entity (2.1) beans. But
we can't go on and migrate the entity beans to JPA, the
As for the first problem, I think there is a bug in the deployment descriptor
processing.
Could you post your deploment descriptor?
The second problem is a bean trying to bind it's home interface over a JNDI
name that's already taken.
In EJB 3 a stateful session bean can be created directly via
OK, so after much effort, (frustration), and time, I can confirm that it does
not work. I'm giving up on JBoss 4.2.1. We'll stick to 3.2.6 until an stable
release EJB3/Java EE 5 is made.
I hope this helps the JBoss team to improve their product.
View the original post :
http://www.jboss.com/i
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,
Have you got by any chance a deployment descriptor containing a transaction
attribute override on the setAgeingSteps method?
If so, try the following method parameter: [Lcom.xxx.yyy.server.process.MyClass;
Or try without any method parameters.
View the original post :
http://www.jboss.com/index.
Yes, I am using 4.2.1 GA. The exception I'm getting is posted here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=117754
The class that is not being found is passed as a parameter to a session bean
(stateless, remote). Note that even when I changed myClass[] for Object[] I get
the sam
Yes. Make sure you're using AS 4.2.1.GA, if so bring on the exceptions.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080728#4080728
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080728
___
