Replies inline.
On 04/14/2011 08:08 AM, Mark McLoughlin wrote:
This fairly straightforward WAR:
http://markmc.fedorapeople.org/rhevm-api-mock.war
includes RESTEasy, Spring and uses JAX-B.
Test using:
[..]
resteasy-jaxb-provider pulls in stax-api, but we exclude it from the
WAR
in order to avoid this error with EAP5:
[..]
(A similar error is seen under AS7 if stax-api is included)
This will be covered when
https://issues.jboss.org/browse/JBAS-8983 is
fixed.
However, we see this error under AS7:
[..]
Now, some of the packages in stax-api are already exported by the
javax.api module:
This is what we technical types call "Bad". I'm fairly certain that the
right approach here is going to be to filter these classes out of
javax.api and use the ones from javax.xml.stream.api instead. Jason,
what do you think?
An alternate apparoach would be to fold javax.xml.stream.api into
javax.api completely.
This is also possible, but it runs rather opposite to what we've done in
the past with javax.api, which is to err towards splitting it up into
constituent APIs rather than not.
That said the javax.xml.stream.api module definitely ought to be a part
of javaee.api.
--
- DML