Thanks for the reply and investigation. It is hard for us to upgrade now to
JBoss 4.2.1, but maybe there is workaround to this. Could we just replace a
class file in any jar ? or maybe whole jar file. Or maybe there exists any
patch to solve this problem ?
We use security-role-ref a lot and can
Descriptor file: (it contains declarations for EJB2.1 session beans only - EJB3
beans use annotations for the whole appserver staff).
|
|
| http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
h
I'm using annotations in my EJB3.0 beans without any deployment XML descriptor.
I don't want any deployment descriptor for these beans. Deployment descriptor
contains only informations about EJB2.1 beans. Should I also put informations
about EJB3.0 beans in the deployment descriptor ?
The real
Hi!
We've got the same problem. How to deploy EJB 2.1 and EJB 3.0 (mixed mode)
packed in the same jar on JBoss 4.2GA ?
Marcin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086536#4086536
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=po
