This content has been marked as final. Show 1 reply
I just want to ask again... but I have to admit that my session bean is a mbean, not a session bean!
Here is the code:
@Resource(mappedName="topic/myMessageTopic") protected Topic messageTopic;
My jboss-service.xml (in same JAR-file, as my MBean)
<?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="org.jboss.jms.server.destination.TopicService" name="jboss.messaging.destination:service=Topic,name=myMessageTopic" xmbean-dd="xmdesc/Topic-xmbean.xml"> <attribute name="JNDIName">topic/myMessageTopic</attribute> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> <depends>jboss.messaging:service=PostOffice</depends> </mbean> </server>
As I said, the deployment of the mbean fails. After the deployment of the most of the jar, I see that the topic is startet... I think it is just a problem of timing: my mbean is deployed before jboss starts the topic...