You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2013/07/23 07:38:49 UTC
[jira] [Resolved] (CXF-5143) http-conf:server blueprint
configuration doesn't work
[ https://issues.apache.org/jira/browse/CXF-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-5143.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.7.7
2.6.10
3.0.0
> http-conf:server blueprint configuration doesn't work
> -----------------------------------------------------
>
> Key: CXF-5143
> URL: https://issues.apache.org/jira/browse/CXF-5143
> Project: CXF
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 3.0.0, 2.6.10, 2.7.7
>
>
> miss class type cause NPE when unmarshall the configuration
> {code}
> mapElementToJaxbProperty(context, bean, element,
> new QName(HTTP_NS, "server"), "server", null);//should specify HTTPServerPolicy.class but not null here
> mapElementToJaxbProperty(context, bean, element,
> new QName(HTTP_NS, "fixedParameterOrder"), "fixedParameterOrder", null); //need fix here similarly
> mapElementToJaxbProperty(context, bean, element,
> new QName(HTTP_NS, "contextMatchStrategy"), "contextMatchStrategy", null);//need fix here similarly
> {code}
> though use standalone jetty transport isn't neat in OSGi container, I think we should avoid the NPE here, just in case someone wanna use it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira