[jboss-jira] [JBoss JIRA] (WFLY-3838) Wildcard (*) for ejb-name should work for all applicable occurences of the ejb-name element

Stuart Douglas (JIRA) issues at jboss.org
Sun Sep 21 18:12:02 EDT 2014


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

Stuart Douglas updated WFLY-3838:
---------------------------------
       Issue Type: Feature Request  (was: Bug)
    Fix Version/s: Awaiting Volunteers
         Assignee:     (was: Stuart Douglas)


Marking as awaiting volunteers. Given that this is only useful if all/most EJB's in a deployment have a method with the same name, so this feature seems of limited use.

> Wildcard (*) for ejb-name should work for all applicable occurences of the ejb-name element
> -------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3838
>                 URL: https://issues.jboss.org/browse/WFLY-3838
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>    Affects Versions: 8.1.0.Final
>            Reporter: Jan Martiska
>             Fix For: Awaiting Volunteers
>
>
> As implemented via WFLY-3497, ejb-name element of jboss-ejb3.xml now accepts a wildcard (*) to denote all EJBs in a deployment. This should work for applicable occurences, but it only seems to work when specifying transaction timeouts.
> This currently doesn't work:
> - assembly-descriptor/exclude-list/method/ejb-name=* (to declare method exclusions)
> - assembly-descriptor/method-permission/method/ejb-name=* (to declare method permissions)
> I prepared a testcase which demonstrates this (and is currently failing): https://github.com/jmartisk/wildfly/commit/eaad1da5e9a6553f4365d650f408214f99522df6



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list