[JBoss Messaging] - Re: JBoss 5.0.0 Messaging Samples
by gaohoward
It's not ok. Take a look at the destination-service.xml file, there are some entries and you can just copy and paste, making some modification, that all. Here is a simple example entry fyi:
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=testQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="noacc" read="false" write="false" create="false"/>
| </security>
| </attribute>
| </mbean>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237651#4237651
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237651
17 years, 1 month
[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?
by kennardconsulting
jaikiran,
Okay I believe I have located the problem. I have not opened a JIRA yet because this may well be spec, though it seems a strange spec to me (and certainly different from JBoss 4.2.3).
Basically: the presence of an <app.ear>/<ejbs.jar>/META-INF/ejb-jar.xml file, even an empty one, short-circuits the annotation-based detection completely. I have put together a little example here:
http://kennardconsulting.com/tmp/avant-ss-app.zip
You will need to extract it into the deploy/ folder of a fresh JBoss 5.1.0.GA installation.
You will find it deploys okay (it errors if you don't give it a -ds.xml, but that's okay) but it has the JBMETA-4 warning and does not set up the JNDI. But if you go in and delete the ejb-jar.xml then it detects the bean via the annotations.
This may be intentional. But in 4.2.3 you could specify some beans in your ejb-jar.xml and leave the annotation processing to find the rest. In particular, you could configure some beans with <env-entry>'s and the like without having to specify every bean.
So has this changed deliberately? And is there a way to revert to the old behaviour?
Richard.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237647#4237647
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237647
17 years, 1 month
[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?
by kennardconsulting
jaikiran,
Okay I believe I have located the problem. I have not opened a JIRA yet because this may well be spec, though it seems a strange spec to me (and certainly different from JBoss 4.2.3).
Basically: the presence of an <app.ear>/<ejbs.jar>/META-INF/ejb-jar.xml file, even an empty one, short-circuits the annotation-based detection completely. I have put together a little example here:
http://kennardconsulting.com/tmp/avant-ss-app.zip
You will need to extract it into the deploy/ folder of a fresh JBoss 5.1.0.GA installation.
You will find it deploys okay (it errors if you don't give it a -ds.xml, but that's okay) but it has the JBMETA-4 warning and does not set up the JNDI. But if you go in and delete the ejb-jar.xml then it detects the bean via the annotations.
This may be intentional. But in 4.2.3 you could specify some beans in your ejb-jar.xml and leave the annotation processing to find the rest. In particular, you could configure some beans with <env-entry>'s and the like without having to specify every bean.
So has this changed deliberately? And is there a way to revert to the old behaviour?
Richard.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237646#4237646
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237646
17 years, 1 month