In a recent thread I found this example for a MDB configuration.@MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") }, mappedName = "queue/MessageBeanQueue")#Is it required to include the destinationType property? Maybe this is an old questions which has been answered (many times) before: if a queue with the name #queue/MessageBeanQueue is mapped in the broker, is there a reason why the bean also hasto declare that it is a queue?
In a recent thread I found this example for a MDB configuration.@MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") }, mappedName = "queue/MessageBeanQueue")
Is it required to include the destinationType property? Maybe this is an old questions which has been answered (many times) before: if a queue with the name #queue/MessageBeanQueue is mapped in the broker, is there a reason why the bean also hasto declare that it is a queue?
Is it required to include the destinationType property? Maybe this is an old questions which has been answered (many times) before: if a queue with the name
queue/MessageBeanQueue is mapped in the broker, is there a reason why the bean also hasto declare that it is a queue?
Reply to this message by going to Community
Start a new discussion in Beginner's Corner at Community