[infinispan-issues] [JBoss JIRA] (ISPN-1065) Use a better mechanism to parse config files
Galder Zamarreño (Updated) (JIRA)
jira-events at lists.jboss.org
Tue Nov 22 03:27:48 EST 2011
[ https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreño updated ISPN-1065:
-----------------------------------
Fix Version/s: 5.1.0.CR1
(was: 5.1.0.BETA5)
> Use a better mechanism to parse config files
> --------------------------------------------
>
> Key: ISPN-1065
> URL: https://issues.jboss.org/browse/ISPN-1065
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 4.2.1.FINAL
> Reporter: Manik Surtani
> Assignee: Pete Muir
> Priority: Blocker
> Labels: jaxb
> Fix For: 5.1.0.CR1
>
>
> The current codebase heavily relies on JAXB to:
> 1. Generate a XSD schema from a Configuration bean
> 2. Generate a parser to use with an XML configuration
> This is known to be slow, and can significantly add to start up time:
> {quote}
> We did some analysis of our AS6 descriptor code which was using JAXB (800ms), compared to straight stax (10ms)
> {quote}
> A possible solution could be to still use JAXB to generate the schema, but to also write a Maven plugin which would generate a STAX parser based on the XSD schema and Configuration bean at build time. Infinispan would then use this STAX parser rather than a JAXB generated parser, which would be a lot faster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list