[ https://jira.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin.s... ] Gary Lamperillo updated JBIDE-6708: ----------------------------------- Description: Using the Message Driven Bean WTP Wizard that is in JBDS 3.0.1, an annotation in the format is created: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), mappedName=mappedName = "queue/testQueue") HornetQ will need an annotation in the following format: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"), @ActivationConfigProperty(propertyName = "useLocalTx", propertyValue = "true") } Either HornetQ will need to correspond to WTPs expectation or the wizard will need to be modified to accept the hornetq specific changes. Since the tooling will still need to work with other providers such as JBoss Messaging, a radio button will need to be added to the Wizard as well to select HornetQ. I believe the main issue is that the MappedName specifying the queue name is not used and we now need a destination property. Can hornetQ correspons to the old style? Do we need to a way to add other properties such as transaction related, ie @ActivationConfigProperty(propertyName = "useLocalTx", propertyValue = "true" that the examples doc/examples/hornetq-examples/javaee/ use? was: Using the Message Driven Bean WTP Wizard that is in JBDS 3.0.1, an annotation in the format is created: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") HornetQ will need an annotation in the following format: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"), @ActivationConfigProperty(propertyName = "useLocalTx", propertyValue = "true") }, mappedName = "queue/testQueue") Either HornetQ will nee to correspond to WTPs expectation or the wizard will need to be modified to accept the hornetq specific changes. Since the tooling will still need to work with other providers such as JBoss Messaging, a radio button will need to be added to the Wizard as well to select HornetQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBIDE-6708: ------------------------------------------ Yeah, I was just scratching my head on this one as I've never heard of that particular wizard before... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin.s... ] Max Andersen updated JBIDE-6708: -------------------------------- Priority: Minor (was: Major) Assignee: Max Andersen Fix Version/s: 3.2.0.Beta2 (was: 3.1.2) Component/s: JBossAS -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin.s... ] Max Andersen commented on JBIDE-6708: ------------------------------------- Clebert, sounds great - for my info, is what we generated JBoss Messaging specific or a standard approach ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin.s... ] Max Andersen updated JBIDE-6708: -------------------------------- Fix Version/s: 3.2.0.CR1 (was: 3.2.0.Beta2) Clebert, any insight/news or can I assume we can close this and it will be fixed in HornetQ/EAP 5.1 ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin... ] Max Andersen updated JBIDE-6708: -------------------------------- Fix Version/s: 3.2.x (was: 3.2.0.CR1) Moving off JBoss Tools release since we seem to be generating standard annotations - hornetq ignoring them. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-6708: -------------------------------------------- Andy, mappedName is part of javax.ejb.MessageDriven. Are you saying that is not part of the spec ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-6708: -------------------------------------------- Andy, ok sounds good. Might be its the AS that is not feeding you the info properly ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira