[jbosstools-issues] [JBoss JIRA] (JBIDE-13249) Improve MDB support

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741373#comment-12741373 ] 

Max Rydahl Andersen commented on JBIDE-13249:
---------------------------------------------

in JBT with Eclipse there are two wizards:

"EJB3 Message Driven Bean"
 Wich generates:

 public @MessageDriven class test implements MessageListener {

 }

and

"Message Driven Bean (EJB-3.x)"
which has some more options and can generate stuff like:

"@MessageDriven(
		activationConfig = { @ActivationConfigProperty(
				propertyName = "destinationType", propertyValue = "javax.jms.Queue"
		) }, 
		mappedName = "herewego")
@TransactionManagement(TransactionManagementType.BEAN)
public class test2 implements MessageListener {"

Seems to me there are a annotations etc.
                
> Improve MDB support
> -------------------
>
>                 Key: JBIDE-13249
>                 URL: https://issues.jboss.org/browse/JBIDE-13249
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: ejb3
>            Reporter: Clebert Suconic
>            Assignee: Rob Stryker
>
> I have recently tried creating an MDB and it seems out of date.
> It's not adding any annotations and not asking the user for any parameters.
> You could do something like this:
> - Ask what provider is going to be used...
> Ask what's the queue name to be used
> What Resource Adapter's name. (It would be great if you could inspect the server being used here for the RA's names. Each hornetq pooled connection factory will be a resource adapter name BTW).
> What Queue Name
> you could also provide additional activation properties by either selecting a list of providers. Or even better you could inspect the list of available activation properties, so it would be more generic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira