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

Kristina Petkova commented on AXIOM-436:
----------------------------------------

Hello, Andreas,
This issue was actually tested with AXIOM 1.2.7 and we are not sure if it's 
going to be reproduced again in 1.2.13 because we're still migrating and this 
is one of the patches we need to merge. I'll now edit the description to 
contain 1.2.7 as a version as well. 
                
> 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.7, 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