]
Max Rydahl Andersen commented on JBIDE-6708:
--------------------------------------------
just to be clear, we cannot change the WTP styled wizard, it uses the spec/assumed
defaults.
Any non-spec/hornetq specific setup is to be done in the non-wtp wizard.
MDB WTP Wizard Annotations for HornetQ
--------------------------------------
Key: JBIDE-6708
URL:
https://jira.jboss.org/browse/JBIDE-6708
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.1
Environment: JBDS 3.0.1 , EAP 5.1 Beta, HornetQ 2.1
Reporter: Gary Lamperillo
Fix For: 3.1.2
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.
-
If you think it was sent incorrectly contact one of the administrators: