<div dir="ltr"><div dir="ltr"><div>Hi</div><div><br></div><div>There is a very nice example in Adam Bien's blog: (<a href="http://www.adam-bien.com/roller/abien/entry/trouble_with_crippled_java_ee" target="_blank">http://www.adam-bien.com/roller/abien/entry/trouble_with_crippled_java_ee</a>). He tried to mock EntityManager and got java.lang.ClassFormatError, just as Chis described.<br>
</div>
<div><br></div><div>You can also find pretty interesting information about Java EE specs project in Shelly McGowan's blog: <a href="https://community.jboss.org/blogs/donnamishelly/2011/04/29/jboss-java-ee-api-specs-project" target="_blank">https://community.jboss.org/blogs/donnamishelly/2011/04/29/jboss-java-ee-api-specs-project</a></div>
<div><br></div><div>Best regards</div><div>Sebastian</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-21 12:52 GMT+02:00 Chris Ritchie <span dir="ltr"><<a href="mailto:morgan.c.ritchie@gmail.com" target="_blank">morgan.c.ritchie@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify">The official bundles contained classes with empty methods, causing errors in some use cases, such as Arquillian tests. </span></div>
<div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify">See this post: <a href="https://community.jboss.org/wiki/WhatsTheCauseOfThisExceptionJavalangClassFormatErrorAbsentCode" target="_blank">https://community.jboss.org/wiki/WhatsTheCauseOfThisExceptionJavalangClassFormatErrorAbsentCode</a></span><br>
</div><div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify">From this blog:</span></div>
<div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify">"</span><span style="color:rgb(61,61,61);font-family:'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:13px;line-height:19px">Sun/Oracle stripped out the code from classes that are classified as "implementations". So all the interfaces are code complete, yet any abstract class or implementation class has no code in it"</span></div>
<div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify"><br></span></div><div style="text-align:justify"><font color="#333333" face="Arial, Tahoma, Helvetica, FreeSans, sans-serif"><span style="font-size:14.44444465637207px;line-height:17.98611068725586px">For piece of mind, I would suggest using the same version of jars shipped with the application server you are using. If you are using JBoss/WildFly, stick to the jboss bundles.</span></font></div>
<div style="text-align:justify"><font color="#333333" face="Arial, Tahoma, Helvetica, FreeSans, sans-serif"><span style="font-size:14.44444465637207px;line-height:17.98611068725586px"><br></span></font></div><div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify">Cheers</span></div>
<div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify">Chris</span></div>
<div><span style="color:rgb(51,51,51);font-family:Arial,Tahoma,Helvetica,FreeSans,sans-serif;font-size:14px;line-height:18px;text-align:justify"><br></span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Message: 7<br>
Date: Wed, 21 May 2014 03:03:44 -0500<br>
From: "<a href="mailto:hanasaki@gmail.com" target="_blank">hanasaki@gmail.com</a>" <<a href="mailto:hanasaki@gmail.com" target="_blank">hanasaki@gmail.com</a>><br>
Subject: [wildfly-dev] API differences javax EE6 vs JBoss EE6 specs<br>
To: <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
Message-ID: <<a href="mailto:537C5DE0.8010505@gmail.com" target="_blank">537C5DE0.8010505@gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<div class=""><br>
<br>
What are the differences between the JBoss EE6 API and the Oracle EE6<br>
API as specified by the below maven dependencies? What issues, if any,<br>
are there in using the oracle javax api spec? Since the spec is final,<br>
wouldn't there be no differences to expect?<br>
<br>
Thank you.<br>
<br>
reference info below:<br>
<br>
<dependency><br>
<groupId>javax</groupId><br>
<artifactId>javaee-api</artifactId><br>
<version>6.0</version><br>
<scope>compile</scope><br>
</dependency><br>
<br>
<groupId>org.jboss.spec</groupId><br>
<artifactId>jboss-javaee-6.0</artifactId><br>
<artifactId>jboss-javaee-all-6.0</artifactId><br>
<version>3.0.2.Final</version><br>
</dependency><br>
<br>
<br></div>
------------------------------<br>
<br>
Message: 8<br>
Date: Wed, 21 May 2014 10:26:05 +0200<br>
From: Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>><br>
Subject: Re: [wildfly-dev] API differences javax EE6 vs JBoss EE6<br>
specs<br>
To: "<a href="mailto:hanasaki@gmail.com" target="_blank">hanasaki@gmail.com</a>" <<a href="mailto:hanasaki@gmail.com" target="_blank">hanasaki@gmail.com</a>><br>
Cc: <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
Message-ID: <<a href="mailto:20140521082605.GD12589@hibernate.org" target="_blank">20140521082605.GD12589@hibernate.org</a>><br>
Content-Type: text/plain; charset=us-ascii<div><div class="h5"><br>
<br>
They are binary identical as it is checked by the TCK.<br>
<br>
The reason we have our own AFAIR is that<br>
- when we work on a preview of the spec, we need to write our own<br>
anyways as the Oracle teams don't necessarily have the same timeframe<br>
- there is some license subtleties involved and we prefer to write our<br>
own from a clean room.<br>
- some APIs have actual code - and thus bugs - and we want to be able to<br>
fix them - and have.<br>
<br>
Emmanuel<br>
<br>
On Wed 2014-05-21 3:03, <a href="mailto:hanasaki@gmail.com" target="_blank">hanasaki@gmail.com</a> wrote:<br>
> What are the differences between the JBoss EE6 API and the Oracle EE6<br>
> API as specified by the below maven dependencies? What issues, if any,<br>
> are there in using the oracle javax api spec? Since the spec is final,<br>
> wouldn't there be no differences to expect?<br>
><br>
> Thank you.<br>
><br>
> reference info below:<br>
><br>
> <dependency><br>
> <groupId>javax</groupId><br>
> <artifactId>javaee-api</artifactId><br>
> <version>6.0</version><br>
> <scope>compile</scope><br>
> </dependency><br>
><br>
> <groupId>org.jboss.spec</groupId><br>
> <artifactId>jboss-javaee-6.0</artifactId><br>
> <artifactId>jboss-javaee-all-6.0</artifactId><br>
> <version>3.0.2.Final</version><br>
> </dependency><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">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>
<br>
<br></div></div>
------------------------------<div class=""><br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">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>
<br></div>
End of wildfly-dev Digest, Vol 14, Issue 7<br>
******************************************<br>
</blockquote></div><br><br clear="all"><div><br></div><br>
</div></div>
<br>_______________________________________________<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></blockquote></div><br><br clear="all"><br>-- <br>Sebastian Łaskawiec
</div>