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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev