0 Replies Latest reply on Jan 7, 2006 3:07 PM by Mateusz Zajakala

    MDB deploy ignores @activateConfig in 5.0 alpha

    Mateusz Zajakala Newbie

      I deploy an EJB3.0 message-driven bean

      @MessageDriven(activateConfig =
       {
       @ActivationConfigProperty(propertyName="destinationType",
       propertyValue="javax.jms.Queue"),
       @ActivationConfigProperty(propertyName="destination",
       propertyValue="queue/reducts")
       })
      public class RulesGeneratorMDB implements MessageListener {
      ...
      

      packaged in .ejb3 archive and get the following messages during deployment:

      20:49:10,422 WARN [MDB] No message-driven-destination given; using; guessing type
      20:49:10,422 WARN [MDB] Could not determine destination type, defaults to: javax.jms.Topic
      20:49:10,482 WARN [MDB] destination not found: topic/RulesGeneratorMDB reason: javax.naming.NameNotFoundException: topic/RulesGeneratorMDB
      20:49:10,482 WARN [MDB] creating a new temporary destination: topic/RulesGeneratorMDB
      20:49:10,542 INFO [RulesGeneratorMDB] Bound to JNDI name: topic/RulesGeneratorMDB


      It seems that activateConfig is simply ignored. I think this might be a bug in 5.0alpha since the same jar works nicely in 4.0.3.

      I'm using JBoss 5.0alpha [ build: CVSTag=HEAD date=200601072000 ].

      Any sugestions? (Like reporting this to JIRA?)
      Mateusz