[ 
https://issues.apache.org/jira/browse/AXIOM-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416117#comment-13416117
 ] 

Andreas Veithen commented on AXIOM-436:
---------------------------------------

With old Axiom versions that were still using the isSetPrefixBeforeStartElement 
property, I understand that there was a performance issue (see e.g. 
ABDERA-267). However, I don't see how the SOAPBodyFirstChildElementQName 
property will be queried 40 times for a single request/response. Are you sure 
about that?
                
> Axiom-api module: Many IllegalArgumentExceptions raised for unknown property 
> configuration keys
> -----------------------------------------------------------------------------------------------
>
>                 Key: AXIOM-436
>                 URL: https://issues.apache.org/jira/browse/AXIOM-436
>             Project: Axiom
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 1.2.13
>         Environment: Windows 7
>            Reporter: Kristina Petkova
>            Priority: Minor
>
> While reviewing the thread dumps I realized some Axiom-api classes are 
> raising IllegalArgumentExceptions for property key which is not defined:
> org.apache.axiom.SOAPBodyFirstChildElementQName
> The methods where this happens are MTOMXMLStreamWriter.getProperty() and 
> StAXBuilder.getReaderProperty() .
> It would be wonderful if this can be resolved (e.g. seed defaults if none 
> were defined, perhaps?) During my simple service request/response, I saw 40 
> exceptions raised, so this has potential to really help our performance 
> numbers.
> Thanks in advance! 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to