[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-1065:
------------------------------------
If this was only about the XSD, you could design the Infinispan configuration so that
different modules could add their own configuration:
http://www.datypic.com/books/defxmlschema/chapter21.html
Seems like there's even a way to parse it with JAXB:
http://stackoverflow.com/questions/420533/how-do-i-ensure-schema-extensib...
The user will have to add the query module namespace declaration, and they won't have
proper validation for the top query configuration element, but they will have validation
inside it.
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.ALPHA1, 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