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

[mark.lowe (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12439347#action_12439347 ] 

mark.lowe commented on JBAS-6221:
---------------------------------

Thanks for the clarification, of course humble apologies for any "misguided speculation".. However even when the provider provides the JMSXDeliveryCount the GenericDLQHandler doesn't work, which is a shame because it would be kind of cool if it did.. Unless by working you mean allowing an MDB to infinitely attempt to process a broken message, maxing out the container and requiring a restart, in which case I stand corrected.  

More relevant to the original point raised, not being able to reference the standardjboss.xml in the ejb3 is all very well and good, however seeing as it appears that ActivationConfig settings in jboss.xml packaged in EJB modules seem to be ignored. Its tricky to see how one configures such things without making modules non portable.. 

In light of the fact that standardjboss.xml has nothing to do with ejb3, I guess this "bug report" would be better focusing on the settings not being read from the jboss.xml file. I'll try better next time I promise.

> 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