castor

Castor should reuse parsers

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Number of attachments :
    2

Description

Following up this thread (http://old.nabble.com/Castors-not-pooling-the-parsers---causes-performance-issues-under-extreme-load-td33327042.html) about performance issues caused by JAXP/JAXB (http://www.jdom.org/pipermail/jdom-interest/2006-September/015537.html), what about providing constructors and methods in castor (marshal/unmarshal) that accepts parsers as arguments?
In this way concurrency and thread-safety must be garantee by application

  1. Text File
    c3226.20121001.patch
    01/Oct/12 4:13 PM
    3 kB
    Werner Guttmann
  2. Text File
    castor.c3226.patch
    24/Jul/12 3:41 PM
    5 kB
    Werner Guttmann

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Werner Guttmann added a comment -

So you'd like to see additional constructors and methods on e.g. the XMLContext against JAXP SAXBuilder(Factory) classes, correct ?

Show
Werner Guttmann added a comment - So you'd like to see additional constructors and methods on e.g. the XMLContext against JAXP SAXBuilder(Factory) classes, correct ?
Hide
Permalink
Marco Quaranta added a comment -

Yes, it's correct. Is it feasible?

Show
Marco Quaranta added a comment - Yes, it's correct. Is it feasible?
Hide
Permalink
Werner Guttmann added a comment -

It's too early to say, as I'd have to investigate how Castor actually interacts with JAXP and its factories, and how to work with those abstractions in place. Feel free to get a picture yourself ...

Show
Werner Guttmann added a comment - It's too early to say, as I'd have to investigate how Castor actually interacts with JAXP and its factories, and how to work with those abstractions in place. Feel free to get a picture yourself ...
Hide
Permalink
Werner Guttmann added a comment -

Initial patch for review. I have had a close look, and decided to allow a SAXParserFactory instance to be cached in AbstractInternalContext. All SAXParser and XMLReader creation will happen off this SAXParserFactory.

Show
Werner Guttmann added a comment - Initial patch for review. I have had a close look, and decided to allow a SAXParserFactory instance to be cached in AbstractInternalContext. All SAXParser and XMLReader creation will happen off this SAXParserFactory.
Hide
Permalink
Werner Guttmann added a comment -

Updated patch after a few commits.

Show
Werner Guttmann added a comment - Updated patch after a few commits.

People

  • Assignee:
    Unassigned
    Reporter:
    Marco Quaranta
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: