[jboss-jira] [JBoss JIRA] (WFLY-1167) AS7/EAP6 @Stateless/mappedName behaviour could be made consistent with AS5/EAP5

[Stuart Douglas (JIRA)]

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

Stuart Douglas closed WFLY-1167.
--------------------------------
    Resolution: Rejected


If we do this now it would just break compatibility for existing EAP6/Wildfly users. 

> AS7/EAP6 @Stateless/mappedName behaviour could be made consistent with AS5/EAP5
> -------------------------------------------------------------------------------
>
>                 Key: WFLY-1167
>                 URL: https://issues.jboss.org/browse/WFLY-1167
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>         Environment: Windows7
>            Reporter: Baptiste MATHUS
>              Labels: regression
>
> Though I agree mappedName was never meant to be standard, as reminded in the link below, at least it was something done within JBoss AS, and I wonder if something better for *JBoss* users&customers couldn't be made to help them.
> How difficult would it be for example to bind SLSB to the given mappedName (in addition to the standard portable jndi naming, sure)?
> I admit we've certainly been using it the wrong way in our shop, but that's how it is now, and today this change is currently being one of the biggest PITA for us to migrate between EAP5 and EAP6...
> By the way, even a special patch or workaround that could make that possible would be perfect.
> WDYT?
> Thanks!
> (Note: I already read carefully the following thread: http://lists.jboss.org/pipermail/jboss-as7-dev/2011-May/002246.html I searched the jiras without finding one about that subject, so I eventually decided to create this entry for potential reference).



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