Beta3 - but I should move to CR1 I can see ;)
But what wolfc and jaikarian said on #jboss-as7 yesterday was:
Jaikiran: mappedName isn't used for any of the @Stateless or @Stateful or @MDB
Jaikiran: the spec says that it's upto the container to decide how to handled
mappedName
and later on:
wolfc: we now ignore mappedName everywhere
maxandersen: wolfc: new behavior in AS7 or ?
wolfc: yes
and then eventually I got referred to section 4.4 in
http://www.jcp.org/en/jsr/detail?id=318 of the ejb spec
as the way to go but those names/examples in there are horryifing complex to maintain/read
in comparison
to the EJB 3 tutorials/docs that uses mappedName with much simpler/relative names.
With AS7-900 i'm now even more confused what will actually work/not work in AS 7 :)
/max
On Tue, May 31, 2011 at 1:17 PM, Max Rydahl Andersen <max.andersen(a)redhat.com>
wrote:
Hi,
I've started trying to use various examples about JEE5/JEE6 which all seem to use
mappedname as Glassfish, Weblogic and recently Websphere is using it (as a name that can
be used at both declaration and resource lookup time within the same module)
I know that mappendname is left unspecified in the spec, but it seems most other JEE
vendors have aligned (or at least seem to have aligned).
>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.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
---
Nik
/max
http://about.me/maxandersen