[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1065:
----------------------------------------
Pete, when you write such parser, what do you do about validation of the XML? Do you
delegate it to the schema? Or do you do that while parsing too? The type of validations
I'm refering to is about the number of possible instances of a particular element, the
allowed values for an XML attribute...etc.
I see some benefit from having docs in schema and that's the fact that IDE or other
tools can piggyback on that to offer information to the user while typing the XML, without
having to go to the config doc.
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: Vladimir Blagojevic
Labels: jaxb
Fix For: 5.1.0.BETA1, 5.1.0.Final
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira