6:04 p.m.
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: Manik Surtani
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
4:20 p.m.
New subject: [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:
----------------------------------------
It'd be interesting to see what Trustin's suggestion of http://www.schematron.com
has to offer as opposed to STAX or JAXB too.
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: Manik Surtani
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
6:19 p.m.
New subject: [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....
]
Jesper Pedersen commented on ISPN-1065:
---------------------------------------
I would just write the whole thing - feel free to rip from the IronJacamar setup:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/jboss-jca/tru...
.api.metadata for the API
.metadata for the implementation
Handles the schemas defined here - http://docs.jboss.org/ironjacamar/schema/
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: Manik Surtani
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
6:31 p.m.
New subject: [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....
]
Manik Surtani commented on ISPN-1065:
-------------------------------------
@Jesper the reason I don't want to write the parser by hand is that the Configuration
bean changes from release to release. We're at a stage where we do add more features
with every release and I don't want to be in a position to have to update:
* A schema
* A parser
* Configuration docs
with every change to Configuration.java. This is why we used JAXB to solve problems 1 and
2, and we have a custom doclet to generate config docs for problem 3. :-)
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: Manik Surtani
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
8:22 p.m.
New subject: [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....
]
Manik Surtani commented on ISPN-1065:
-------------------------------------
Bill Burke did write (incomplete) a StAX parser generator based on JAXB annotations;
finding where he is with this would make sense since we can use this generator to create a
StAX parser which will perform much better than a JAXB one.
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: Manik Surtani
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
8:22 p.m.
New subject: [JBoss JIRA] Assigned: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Manik Surtani reassigned ISPN-1065:
-----------------------------------
Assignee: Vladimir Blagojevic (was: Manik Surtani)
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
11:42 a.m.
New subject: [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....
]
Pete Muir commented on ISPN-1065:
---------------------------------
I think we should strongly consider writing a Stax parser by hand. Previous experience
tells me that this will result in a much more elegant architecture for our code (much
simpler to keep up to date as a result) and will perform much better. I would also propose
using a tool to read the docs from the schema and create a config doc, meaning all that
needs keeping up to date is the schema and parser.
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
11:22 a.m.
New subject: [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
12:37 p.m.
New subject: [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....
]
Pete Muir commented on ISPN-1065:
---------------------------------
We would need to fully validate the configuration as it comes into the config model itself
as the route to this could be via XML, programmatic, some other DSL. At the same time,
it's important to put as many validations as possible in the XSD. This means we get
feedback to the user as quickly as possible (when they write the xml). The other thing to
consider with this is it's really important to report back to the user the
line/position where they made the mistake - just saying you had an error with an element
name is less than useful.
The way I've handled this in the past is to create a generic "Location"
object which can report details on where the config originated. This just exposes a couple
of methods like String getLocation(); - and then we have an XML impl which can point at
the file name, the line etc. We then populate this Location object for every configuration
element the user provides, and pass it to the configuration model along with the XML
transformed config. This way, when an error occurs in the config model, we can report
exactly where it originated.
And yes, we definitely want to make sure the XSD has full docs in in it so that these get
auto-suggested for the user. There are tools out there that will generate a nice html page
from the XSD.
We still of course would need to align the config (java) model docs and the schema docs
somehow.
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
12:58 p.m.
New subject: [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....
]
Manik Surtani commented on ISPN-1065:
-------------------------------------
Wrt. alignment, the original motivation behind using JAXB was that I wanted a single place
to define config and docs, such that XSD, online docs and a parser could all be generated
from it. The end result was a Configuration bean (and a set of related beans) that
defined the programmatic configuration, appropriately Javadoc'd. Appropriate
annotations applied to this bean was then used by JAXB to generate the XSD and parser, and
a custom doclet Vladimir wrote scanned the bean, JAXB annotations and Javadocs to generate
the online config doc: http://docs.jboss.org/infinispan/5.0/apidocs/config.html
Whatever solution we end up with to replace JAXB, and any evolution of the Configuration
beans, should still adhere to DRY and producing coherent and aligned resources for users,
without any repetition on the part of the developer. Otherwise things do get forgotten
and left out.
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
5:14 p.m.
New subject: [JBoss JIRA] Assigned: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Manik Surtani reassigned ISPN-1065:
-----------------------------------
Assignee: Pete Muir (was: Vladimir Blagojevic)
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
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
4:18 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1065:
--------------------------------
Priority: Blocker (was: Major)
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.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
4:29 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1065:
--------------------------------
Fix Version/s: 5.1.0.ALPHA1
(was: 5.1.0.BETA1)
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
11:59 a.m.
New subject: [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....
]
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
1:01 p.m.
New subject: [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....
]
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
1:05 p.m.
New subject: [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....
]
Sanne Grinovero commented on ISPN-1065:
---------------------------------------
Right, something like the components configuration in Seam would be awesome, but then
without JAXB ;)
I'm definitely not an expert about XML, so I'm just pointing out what I'd like
to use, so we collect requirements and leave it up to Pete on what is possible, and how.
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
5:22 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Pete Muir updated ISPN-1065:
----------------------------
Fix Version/s: 5.1.0.ALPHA2
(was: 5.1.0.FINAL)
(was: 5.1.0.ALPHA1)
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.ALPHA2
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
6:04 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Pete Muir updated ISPN-1065:
----------------------------
Fix Version/s: 5.1.0.BETA1
(was: 5.1.0.ALPHA2 )
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.BETA1
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
2:34 p.m.
New subject: [JBoss JIRA] (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 updated ISPN-1065:
-----------------------------------
Fix Version/s: 5.1.0.BETA2
(was: 5.1.0.BETA1)
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.BETA2
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
8:24 a.m.
New subject: [JBoss JIRA] (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 updated ISPN-1065:
-----------------------------------
Fix Version/s: 5.1.0.BETA3
(was: 5.1.0.BETA2)
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.BETA3
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
3:19 p.m.
New subject: [JBoss JIRA] (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 updated ISPN-1065:
-----------------------------------
Fix Version/s: 5.1.0.BETA4
(was: 5.1.0.BETA3)
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.BETA4
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
6:48 p.m.
New subject: [JBoss JIRA] (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 updated ISPN-1065:
-----------------------------------
Fix Version/s: 5.1.0.BETA5
(was: 5.1.0.BETA4)
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.BETA5
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
9:27 a.m.
New subject: [JBoss JIRA] (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 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
5:38 p.m.
New subject: [JBoss JIRA] (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 updated ISPN-1065:
-----------------------------------
Fix Version/s: 5.1.0.CR2
(was: 5.1.0.CR1)
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.CR2
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
1:17 a.m.
New subject: [JBoss JIRA] (ISPN-1065) Use a better mechanism to parse config files
[
https://issues.jboss.org/browse/ISPN-1065?page=com.atlassian.jira.plugin....
]
Sanne Grinovero resolved ISPN-1065.
-----------------------------------
Resolution: Done
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.CR2
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
4504
days inactive
4748
days old
infinispan-issues@lists.jboss.org
24 comments
8 participants
participants (8)
-
Dan Berindei (JIRA) -
Galder Zamarreño (JIRA)
-
Galder Zamarreño (Updated) (JIRA)
-
Jesper Pedersen (JIRA)
-
Manik Surtani (JIRA)
-
Pete Muir (JIRA)
-
Sanne Grinovero (JIRA)
-
Sanne Grinovero (Resolved) (JIRA)