[
https://issues.jboss.org/browse/JBIDE-6708?page=com.atlassian.jira.plugin...
]
Andy Taylor commented on JBIDE-6708:
------------------------------------
according to the spec yes, see section B.2, however this is on the activationconfig not
the messagedriven object, from an implementation point of view we only deal with the
activation config when setting up the resource adapter, I'm guessing this is something
handled in the JCA layer rather than by us so even if we added a mappedName method it
probably wouldn't make any difference. let me check the jca code to see how this is
hanging together.
MDB WTP Wizard Annotations for HornetQ
--------------------------------------
Key: JBIDE-6708
URL:
https://issues.jboss.org/browse/JBIDE-6708
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.1
Environment: JBDS 3.0.1 , EAP 5.1 Beta, HornetQ 2.1
Reporter: Gary Lamperillo
Assignee: Max Rydahl Andersen
Priority: Minor
Fix For: 3.2.x
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?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira