You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Pulyaev (JIRA)" <ji...@apache.org> on 2009/08/19 13:44:14 UTC
[jira] Commented: (CXF-2342) Performance issue in StaxInInterceptor
[ https://issues.apache.org/jira/browse/CXF-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745010#action_12745010 ]
Sergey Pulyaev commented on CXF-2342:
-------------------------------------
I cannot access XMLOutputFactory because of this patch - so i cannot specify required flags - for example - AUTOMATIC_EMPTY_ELEMENTS.
I have done an interceptor that changes XML output factory properties - but it's not work now.
XMLOutputFactory outputFactory = StaxOutInterceptor.getXMLOutputFactory(message);
if(WstxOutputFactory.class.isAssignableFrom(outputFactory.getClass())){
WstxOutputFactory of = (WstxOutputFactory)outputFactory;
of.getConfig().setProperty(XMLOutputFactory2.P_AUTOMATIC_EMPTY_ELEMENTS, false);
}
Now StaxOutInterceptor.getXMLOutputFactory always returns NULL - so i have no way to specify this flag anymore.
> Performance issue in StaxInInterceptor
> --------------------------------------
>
> Key: CXF-2342
> URL: https://issues.apache.org/jira/browse/CXF-2342
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.2.2
> Reporter: Kevin Conaway
> Assignee: Daniel Kulp
> Fix For: 2.1.6, 2.2.3
>
> Attachments: CXF-2342.patch
>
>
> From this mailing list thread [Performance issue in StaxInInterceptor|http://www.nabble.com/Performance-issue-in-StaxInInterceptor-td24499018.html]:
> In cxf-2.2.2, StaxInInterceptor#handleMessage() synchronizes on the XMLInputFactory before calling XMLInputFactory#createXMLStreamReader(InputStream, String).
> Profiling our application reveals this to be a pain point in high volume situations
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.