XB-wise it means all XB users must be on Java annotation-based binding,
XSD-based bindings won't be supported in the AS.
On 2/16/2010 3:03 PM, Richard Opalka wrote:
Hi Dimitrios,
you're right, we have to remove our dependency on both xerces and xalan.
For xerces I created:
*
https://jira.jboss.org/jira/browse/JBXB-238
*
https://jira.jboss.org/jira/browse/JBWS-2936
For xalan I created (already fixed issues):
*
https://jira.jboss.org/jira/browse/SECURITY-452
*
https://jira.jboss.org/jira/browse/JBWS-2919
However we still have the dependency on the xalan :(
* bsf.jar (support for XSLT - do we want support XSLTs via our dynamic
languages integration?)
* xmlsec.jar (apache project reused in both JBossSecurity and JBossWS
projects)
Rio
On 02/16/2010 11:49 AM, Dimitris Andreadis wrote:
> Since jbossxb is in the top level JBOSS_HOME/lib, I'm not sure it can
> see common/lib?
>
> Removing the dependency all together from jbossxb, would be preferable.
>
> Richard Opalka wrote:
>> I can't see any reasonable argument why:
>> * resolver.jar
>> * xercesImpl.jar
>> should be in lib/endorsed? I'm going to refactor them to:
>> * client/
>> * common/lib/
>> If nobody will complain I'll do it this week.
>>
>> Just FYI the dependencies are:
>> ---
>> resolver.jar is cunsumed by xercesImpl.jar only
>> xercesImpl.jar is consumed by jbossws-native-core.jar, jbossxb.jar,
>> xalan.jar and richfaces-impl-jsf2-3.3.3.Beta1.jar
>>