[wildfly-dev] API differences javax EE6 vs JBoss EE6 specs

[Sebastian Łaskawiec]

Hi

There is a very nice example in Adam Bien's blog: (
http://www.adam-bien.com/roller/abien/entry/trouble_with_crippled_java_ee).
He tried to mock EntityManager and got java.lang.ClassFormatError, just as
Chis described.

You can also find pretty interesting information about Java EE specs
project in Shelly McGowan's blog:
https://community.jboss.org/blogs/donnamishelly/2011/04/29/jboss-java-ee-api-specs-project

Best regards
Sebastian


2014-05-21 12:52 GMT+02:00 Chris Ritchie <morgan.c.ritchie at gmail.com>:

> The official bundles contained classes with empty methods, causing errors
> in some use cases, such as Arquillian tests.
>
> See this post:
> https://community.jboss.org/wiki/WhatsTheCauseOfThisExceptionJavalangClassFormatErrorAbsentCode
>
> From this blog:
> "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"
>
> 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.
>
> Cheers
>
> Chris
>
>
>
>> Message: 7
>> Date: Wed, 21 May 2014 03:03:44 -0500
>> From: "hanasaki at gmail.com" <hanasaki at gmail.com>
>> Subject: [wildfly-dev] API differences javax EE6 vs JBoss EE6 specs
>> To: wildfly-dev at lists.jboss.org
>> Message-ID: <537C5DE0.8010505 at gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>>
>> What are the differences between the JBoss EE6 API and the Oracle EE6
>> API as specified by the below maven dependencies?  What issues, if any,
>> are there in using the oracle javax api spec?  Since the spec is final,
>> wouldn't there be no differences to expect?
>>
>> Thank you.
>>
>> reference info below:
>>
>>          <dependency>
>>              <groupId>javax</groupId>
>>              <artifactId>javaee-api</artifactId>
>>              <version>6.0</version>
>>              <scope>compile</scope>
>>          </dependency>
>>
>> <groupId>org.jboss.spec</groupId>
>>         <artifactId>jboss-javaee-6.0</artifactId>
>>         <artifactId>jboss-javaee-all-6.0</artifactId>
>>         <version>3.0.2.Final</version>
>> </dependency>
>>
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Wed, 21 May 2014 10:26:05 +0200
>> From: Emmanuel Bernard <emmanuel at hibernate.org>
>> Subject: Re: [wildfly-dev] API differences javax EE6 vs JBoss EE6
>>         specs
>> To: "hanasaki at gmail.com" <hanasaki at gmail.com>
>> Cc: wildfly-dev at lists.jboss.org
>> Message-ID: <20140521082605.GD12589 at hibernate.org>
>> Content-Type: text/plain; charset=us-ascii
>>
>>
>> They are binary identical as it is checked by the TCK.
>>
>> The reason we have our own AFAIR is that
>> - when we work on a preview of the spec, we need to write our own
>>   anyways as the Oracle teams don't necessarily have the same timeframe
>> - there is some license subtleties involved and we prefer to write our
>>   own from a clean room.
>> - some APIs have actual code - and thus bugs - and we want to be able to
>>   fix them - and have.
>>
>> Emmanuel
>>
>> On Wed 2014-05-21  3:03, hanasaki at gmail.com wrote:
>> > What are the differences between the JBoss EE6 API and the Oracle EE6
>> > API as specified by the below maven dependencies?  What issues, if any,
>> > are there in using the oracle javax api spec?  Since the spec is final,
>> > wouldn't there be no differences to expect?
>> >
>> > Thank you.
>> >
>> > reference info below:
>> >
>> >          <dependency>
>> >              <groupId>javax</groupId>
>> >              <artifactId>javaee-api</artifactId>
>> >              <version>6.0</version>
>> >              <scope>compile</scope>
>> >          </dependency>
>> >
>> > <groupId>org.jboss.spec</groupId>
>> >       <artifactId>jboss-javaee-6.0</artifactId>
>> >       <artifactId>jboss-javaee-all-6.0</artifactId>
>> >       <version>3.0.2.Final</version>
>> > </dependency>
>> > _______________________________________________
>> > wildfly-dev mailing list
>> > wildfly-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>> ------------------------------
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> End of wildfly-dev Digest, Vol 14, Issue 7
>> ******************************************
>>
>
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



-- 
Sebastian Łaskawiec
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20140521/6ab3411f/attachment-0001.html