Re: [wildfly-dev] Issues accessing UserTransaction in WildFly
NameNotFoundException is a NamingException, which should make the change in WildFly
harmless. Also, according to Jaikiran, and the fact Seam expects that specific type seems
to indicate that too, in the past we were throwing NameNotFoundException.
Even if the specs and tck do not clearly define which exception to throw, align behaviour
with the Java EE 7 RI / Glassfish is a bonus for users migrating to WildFly.
—E
On 27 Feb 2014, at 14:39, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
On Thu, Feb 27, 2014 at 2:32 PM, Scott Marlow <smarlow(a)redhat.com> wrote:
The above change would help Seam applications to work on WildFly 8.0.1.
What if we just fix seam itself?
We already have few seam specific hacks in WildFly as it is.
Let fix seam properly sounds like better idea.
--
tomaz
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Attachments:
- attachment.html (text/html — 1.9 KB)