<div dir="ltr">Agreed, that is why I am saying that javaee6 jar is not really representative, what was done with javaee7 one is completely different story.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, May 21, 2014 at 5:16 PM, Shelly McGowan <span dir="ltr"><<a href="mailto:smcgowan@redhat.com" target="_blank">smcgowan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Tomaz,<br>
<br>
Those are provided by reference implementation. We started the Java EE Spec API project a while ago for the reasons listed here:<br>
<a href="https://github.com/jboss/jboss-javaee-specs/blob/master/README.md" target="_blank">https://github.com/jboss/jboss-javaee-specs/blob/master/README.md</a><br>
<br>
These APIs were later promoted with the WELD archetypes[1] as the recommended approach due to a few issues with the javaee-api JAR from GlassFish repository; specifically,<br>
<br>
- It's a shaded JAR, so you have no idea what it actually bundles<br>
- The code is stripped out of all the method bodies, so you get an Absent Code exception if you try to touch any of the classes<br>
<br>
<br>
Shelly<br>
<br>
<br>
[1]<a href="https://community.jboss.org/thread/179735" target="_blank">https://community.jboss.org/thread/179735</a><br>
<div class="im HOEnZb"><br>
<br>
----- Original Message -----<br>
From: "Tomaž Cerar" <<a href="mailto:tomaz.cerar@gmail.com">tomaz.cerar@gmail.com</a>><br>
To: "Andrey Ponomarenko" <<a href="mailto:aponomarenko@rosalab.ru">aponomarenko@rosalab.ru</a>><br>
Cc: <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
Sent: Wednesday, May 21, 2014 11:01:14 AM<br>
Subject: Re: [wildfly-dev] API differences javax EE6 vs JBoss EE6 specs<br>
<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Wed, May 21, 2014 at 4:27 PM, Andrey Ponomarenko < <a href="mailto:aponomarenko@rosalab.ru">aponomarenko@rosalab.ru</a> > wrote:<br>
<br>
<br>
<br>
<a href="http://download.java.net/" target="_blank">http://download.java.net/</a> maven/2/javax/j<br>
<br>
<br>
I know where it is from, but question is, is it official javaee artifact?, AFAIK only with JEE7 did this became mandatory as part of JSR<br>
for example just compare<br>
<br>
<a href="http://repo1.maven.org/maven2/javax/javaee-api/7.0/javaee-api-7.0.pom" target="_blank">http://repo1.maven.org/maven2/javax/javaee-api/7.0/javaee-api-7.0.pom</a><br>
vs<br>
<a href="http://repo1.maven.org/maven2/javax/javaee-api/6.0/javaee-api-6.0.pom" target="_blank">http://repo1.maven.org/maven2/javax/javaee-api/6.0/javaee-api-6.0.pom</a><br>
<br>
to see what I mean,<br>
tomaz<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>