You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2008/02/01 23:53:07 UTC
[jira] Updated: (AXIS2-3490) Performance: Swap lookup order in
AxisService.getOperationsBySOAPAction
[ https://issues.apache.org/jira/browse/AXIS2-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle updated AXIS2-3490:
----------------------------------
Description:
History:
AXIS2-2873 added code to AxisService.getOperationsBySOAPAction to iterate the operations looking for
a local name that matched the provided soap action. Using an iterator to walk the operations is ill-performant.
Solution:
The solution is to swap the iterative search and the map search.
The operationsAliasMap should be searched first (since this was the purpose of building the map).
If that search fails, then fall back to the iterative search by operation name.
Kudos:
David Strite of the IBM Performance team found this problem and provided the suggested change.
I am testing a change right now.
was:
History:
AXIS2-2873 added code to AxisService.getOperationsBySOAPAction to iterate the operations looking for
a local name that matched the provided soap action. Using an iterator is ill-performant to walk the operations is ill-performant.
Solution:
The solution is to swap the iterative search and the map search.
The operationsAliasMap should be searched first (since this was the purpose of building the map).
If that search fails, then fall back to the iterative search by operation name.
Kudos:
David Strite of the IBM Performance team found this problem and provided the suggested change.
> Performance: Swap lookup order in AxisService.getOperationsBySOAPAction
> -----------------------------------------------------------------------
>
> Key: AXIS2-3490
> URL: https://issues.apache.org/jira/browse/AXIS2-3490
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> History:
> AXIS2-2873 added code to AxisService.getOperationsBySOAPAction to iterate the operations looking for
> a local name that matched the provided soap action. Using an iterator to walk the operations is ill-performant.
> Solution:
> The solution is to swap the iterative search and the map search.
> The operationsAliasMap should be searched first (since this was the purpose of building the map).
> If that search fails, then fall back to the iterative search by operation name.
> Kudos:
> David Strite of the IBM Performance team found this problem and provided the suggested change.
> I am testing a change right now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org