Also usually you would ref the concrete datasource in the PU, or leave the container to
use the default one, and then the web components would ref the PU, not the datasource. Had
a look at your code and in fact you’re just testing the datasource in in JNDI, but relying
only on the PU for the app logic.
—E
On 31 Jan 2014, at 15:31, Eduardo Martins <emartins(a)redhat.com> wrote:
On 31 Jan 2014, at 14:33, Martin Andersson
<martin.andersson(a)purplescout.se> wrote:
> I agree. I don't think mapping a datasource in jboss-web.xml is such an exotic
use case. I should just work. Also, there is no hint anywere that there is a property you
can set to make it work.
>
> The proprietary jboss namespace is not an option since I want to be vendor neutral,
but ear/java:app is definitely an option.
>
Well, aren’t you using it already in jboss-web xml?
—E
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev