[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1065) Use a better mechanism to parse config files

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615359#comment-12615359 ] 

Sanne Grinovero commented on ISPN-1065:
---------------------------------------

I'd love to be able to add structured configuration options to the Query engine, i.e. not to pass a list of properties but have a set of proper elements which users could validate via XSD.
The tricky part is that this structure is defined by the query submodule, so I wonder if we can make this while still having the infinispan-query.jar optional: the parser should be able to self-register extensions for different parts, or ignore unknown elements.

I don't expect the XSD to be dynamic too, so this might need to be built upfront from the aggregation of all extension modules.

If not possible, what are the alternatives? shall we separate configuration files?

> 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