[jboss-as7-dev] mappedname behavior ?

[Carlo de Wolf]

The test is wrong. mappedName is a bit of a bummer.

Basically if I specify @Stateless(mappedName="A") and 
@EJB(mappedName="A") they should match up via the interface of the @EJB 
as view. The registry that is used for mappedName is left unspecified.

Carlo

On 05/31/2011 12:24 PM, Jaikiran Pai wrote:
> On Tuesday 31 May 2011 03:47 PM, Max Rydahl Andersen wrote:
>>
>>>  From what I can understand and see JBoss EJB3 have had different implementations of this over time and in AS 7 have moved to simply completely ignore the mappedname attribute.
> mappedName on @Stateless, @Stateful and @MessageDriven has always been
> ignored by JBoss EJB3 and isn't something new in AS7.
>
> mappedName on @Resource and @EJB is expected to work in AS7 (and
> previous versions). If this is currently broken in AS7 upstream, then it
> is a bug. I don't think it's broken because we have a testcase for
> exactly this specific attribute
> https://github.com/jbossas/jboss-as/tree/master/testsuite2/spec/src/test/java/org/jboss/as/test/spec/injection/mappedname.
> If there's some specific application running into a problem, then please
> point me to that.
>
> -Jaikiran
>> Does there exist any forum threads and documentation (beyond the  that outlines
>> the reasons why JBoss EJB3 isn't aligning with what seems to be the consensus across the various servers ?
>>
>> I'm asking since it would make not only users but also tool developers life much easier if one could actually write and generate almost portable code ;)
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev