<div dir="ltr">Yes. But I can add deployment descriptors for other application servers and have the same binary run in both production and dev setups.<div><pre style="color:rgb(0,0,0)">Br,
Martin Andersson
Java EE developer at <a href="http://www.purplescout.se">www.purplescout.se</a></pre></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 31, 2014 at 4:31 PM, Eduardo Martins <span dir="ltr"><<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 31 Jan 2014, at 14:33, Martin Andersson <<a href="mailto:martin.andersson@purplescout.se">martin.andersson@purplescout.se</a>> wrote:<br>
<br>
> 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.<br>
><br>
> The proprietary jboss namespace is not an option since I want to be vendor neutral, but ear/java:app is definitely an option.<br>
><br>
<br>
</div>Well, aren’t you using it already in jboss-web xml?<br>
<span class="HOEnZb"><font color="#888888"><br>
—E</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Hälsningar,<div>Martin Andersson</div><div>Purple Scout AB</div><div>+46 732 05 14 01</div></div>
</div>