[jboss-jira] [JBoss JIRA] Updated: (JBAS-6221) Implement some kind of jboss.xml template mechanism within EJB3

[Adrian Brock (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Brock updated JBAS-6221:
-------------------------------

    Summary: Implement some kind of jboss.xml template mechanism within EJB3  (was: Default JmsActivationSpec ignore configuration in standardjboss.xml)


> Implement some kind of jboss.xml template mechanism within EJB3
> ---------------------------------------------------------------
>
>                 Key: JBAS-6221
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6221
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.3.GA
>            Reporter: mark.lowe
>            Assignee: Carlo de Wolf
>
> Configuring an external MQ provider as DefaultJMSProvider works until there's an error and hence the genericdql handler is called into action. The GenericDQLHandler is broken is doesn't increment the JMSXDeliveryCount header, so being able to change the DLQHander implementation would be handy.. However, changing the values in standardjboss.xml has no effect. So you're forced into defining the DLQHander property in the ejb-jar.xml or worse still annotations for MDBs. 
> This also creates problems when attempting to change the confguration of any invokers used in these cases.. Mapping the invokers /containers in jboss.xml also has no effect.. The defaukt values of JmsActivationSpec is all you have.. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira