[jira] Updated: (RAMPART-230) Rampart expands message object model unnecessarily

["Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RAMPART-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nandana Mihindukulasooriya updated RAMPART-230:
-----------------------------------------------

    Fix Version/s: 1.5

> Rampart expands message object model unnecessarily
> --------------------------------------------------
>
>                 Key: RAMPART-230
>                 URL: https://issues.apache.org/jira/browse/RAMPART-230
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>            Reporter: Dennis Sosnoski
>            Assignee: Ruchith Udayanga Fernando
>             Fix For: 1.5
>
>
> In performance testing I've found that Rampart appears to expand the message object model in situations where this expansion should not be required, causing in a major performance hit. One example is when Rampart is engaged in client code, even with no security policy supplied (and hence no security headers needing to be generated). However, even in many cases where security headers are being used Rampart should not need to expand the message object model (with UsernameToken, for instance).
> My testing used the Axis2 1.5 code and a recent nightly build of Rampart. The object model expansion with Rampart engaged is shown in debug logging messages such as "OMSourceElementImpl:244 - forceExpand: expanding element {http://ws.sosnoski.com/seismic/types}matchQuakes" occurring during the 'Apache Rampart outflow handler' processing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.