[
https://issues.apache.org/jira/browse/CXF-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2397.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.4
2.1.7
Assignee: Daniel Kulp
> Make use of ControlledValidationXmlBeanDefinitionReader optional depending
> upon existence of FastInfoSet.jar
> ------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2397
> URL: https://issues.apache.org/jira/browse/CXF-2397
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.2.3
> Reporter: Mike Youngstrom
> Assignee: Daniel Kulp
> Fix For: 2.1.7, 2.2.4
>
>
> I work on a project where Classloader size and distribution size is rather
> important. So we're trying to keep our number of required dependencies to a
> minimum.
> One area where we found this might be able to improve is in the use of
> ControlledValidationXmlBeanDefinitionReader and its dependence on
> FastInfoSet. It would be nice if an application who didn't wish to benefit
> from the improved startup time of ControlledValidationXmlBeanDefinitionReader
> could not use it if they wished.
> I wonder if this could simply be a matter of checking in
> BusApplicationContext.loadBeanDefinitions() if
> com.sun.xml.fastinfoset.stax.StAXDocumentParser is on the classpath. If it's
> not then log a warning or an info about its absence and the potential
> performance impact then simply use a regular XmlBeanDefinitionReader instead?
> Or perhaps in TunedDocumentLoader only use a
> com.sun.xml.fastinfoset.stax.StAXDocumentParser if fastinfoset is on the
> classpath. Otherwise use a default stax implementation?
> This would allow me to make FastInfoSet an optional dependency in my project.
> Mike
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
