1 Reply Latest reply on Mar 30, 2010 12:36 PM by jaikiran pai

    destination-service.xml deployed in wrong order?

    Michal Glowacki Novice

      please take a look first at my jms-destination-service.xml:

       

       

      <server> 
      <mbean code="org.jboss.jms.server.destination.QueueService"
            name="jboss.messaging.destination:service=Queue,name=A"
            xmbean-dd="xmdesc/Queue-xmbean.xml">
            <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
            <depends>jboss.messaging:service=PostOffice</depends>
         </mbean>
         <mbean code="org.jboss.jms.server.destination.TopicService"
            name="jboss.messaging.destination:service=Topic,name=Alerts"
            xmbean-dd="xmdesc/Topic-xmbean.xml">
            <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>    
         </mbean>
      </server>
      After I have added TopicService part, when my JBoss 5.1 is starting up Topic is not installed and my message-driven beans don't work. I need to redeploy the xml file. It is fine now, in development (however annoying) but not acceptable in production. Please advise me what can I do.