Petals SE Notification

Performance issues on XML Notification processing (read and write)

Details

  • Type: Improvement Request Improvement Request
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.0.1
  • Fix Version/s: 1.0.3
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    This part of the noticiation processing is done with WS Star notification.
    A profiling of the notification process shows that some improvements can be done on the read and write processes (Dom, JDom, Jaxb conversion for exemple, factory creation and so on).

    Show
    This part of the noticiation processing is done with WS Star notification. A profiling of the notification process shows that some improvements can be done on the read and write processes (Dom, JDom, Jaxb conversion for exemple, factory creation and so on).
  • Environment:
    petals-se-notification 1.0.1, ws-notification-* 1.0

Attachments

  1. Text File
    unmarshall-source.patch
    (2 kB)
    Christophe DENEUX
    Mon, 6 Sep 2010 - 19:42:52 +0200

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Mon, 6 Sep 2010 - 19:31:15 +0200

A first optimization is to used only one unmarshaller instead of created one when unmarshalling is needed. Caution to the concurrency on unmarshalling.

Show
Christophe DENEUX added a comment - Mon, 6 Sep 2010 - 19:31:15 +0200 A first optimization is to used only one unmarshaller instead of created one when unmarshalling is needed. Caution to the concurrency on unmarshalling.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 6 Sep 2010 - 19:42:52 +0200 - edited

An other optimization could be to deprecate the API using DOM Document and replace it by an API using a Source. See the attachment 'unmarshall-source.patch'

Show
Christophe DENEUX added a comment - Mon, 6 Sep 2010 - 19:42:52 +0200 - edited An other optimization could be to deprecate the API using DOM Document and replace it by an API using a Source. See the attachment 'unmarshall-source.patch'
Hide
Permalink
Christophe DENEUX added a comment - Mon, 6 Sep 2010 - 20:37:01 +0200

Caution don't deprecate the DOM API because using a API based on Source generates a XML parsing. So if on the client side the XML is already parsed as DOM document, use the DOM API. Otherwise, if the XML is not parsed, use the Source API. Please add a note on the usage of each API.

Show
Christophe DENEUX added a comment - Mon, 6 Sep 2010 - 20:37:01 +0200 Caution don't deprecate the DOM API because using a API based on Source generates a XML parsing. So if on the client side the XML is already parsed as DOM document, use the DOM API. Otherwise, if the XML is not parsed, use the Source API. Please add a note on the usage of each API.

People

Dates

  • Created:
    Mon, 6 Sep 2010 - 17:40:11 +0200
    Updated:
    Tue, 2 Nov 2010 - 17:25:04 +0100
    Resolved:
    Mon, 20 Sep 2010 - 15:54:10 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.