在骆驼路由中的CXF SOAP端点中启用XML验证

我正在JBoss Fuse内开发一个代码优先的SOAP服务。我用输入和输出类定义了一个接口my.endpoint.Interface。 wsdl生成良好，服务正在运行。端点由调用我的骆驼路由的CXF处理。在骆驼路由中的CXF SOAP端点中启用XML验证

版本：
的JBoss 6.2.1保险丝
Apache的骆驼2.15.1
的Apache CXF 3.0.4

这是我包的构造：

<blueprint> 

    <cxf:cxfEndpoint id="myEndpoint" 
     address="/my/" 
     serviceClass="my.endpoint.Interface"> 
    </cxf:cxfEndpoint> 

    <camelContext> 

     <route> 
      <from uri="cxf:bean:myEndpoint" /> 
      <to uri="bean:doProcess" /> 
     </route> 

    </camelContext> 

</blueprint>

我想使用XSD将XML验证应用于传入的有效内容。

如何在此特定环境中配置CXF？

我没有找出指定XSD CxfEndpointConfigurer接口：

<!-- blueprint file --> 
<from uri="cxf:bean:myEndpoint?cxfEndpointConfigurer=configurer" /> 

// java file 
@Override 
public void configureServer(Server server) { 
    // where do I set XSD in here? 
}

配置在蓝图文件cxfEndpoint提出了在运行时

<cxf:cxfEndpoint id="readingsEndpoint" 
       address="/readings/" 
       serviceClass="my.endpoint.Interface"> 
    <cxf:schemaLocations> 
     <schemaLocation>classpath:my/endpoint/schema1.xsd</schemaLocation> 
    </cxf:schemaLocations> 
</cxf:cxfEndpoint>

一个异常不起作用，引发以下异常：

Unable to start blueprint container for bundle my.bundle/0.0.0.SNAPSHOT 
java.lang.NullPointerException 
    at org.apache.aries.blueprint.container.RecipeBuilder.getValue(RecipeBuilder.java:355)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.RecipeBuilder.getValue(RecipeBuilder.java:334)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.RecipeBuilder.createBeanRecipe(RecipeBuilder.java:278)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.RecipeBuilder.createRecipe(RecipeBuilder.java:110)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.RecipeBuilder.createRepository(RecipeBuilder.java:93)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.BlueprintContainerImpl.getRepository(BlueprintContainerImpl.java:481)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:328)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:269)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)[23:org.apache.aries.blueprint.core:1.4.4] 
    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[17:org.apache.aries.util:1.1.0] 
    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[17:org.apache.aries.util:1.1.0] 
    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[17:org.apache.aries.util:1.1.0] 
    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[17:org.apache.aries.util:1.1.0] 
    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[17:org.apache.aries.util:1.1.0] 
    at org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1127)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4429)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.felix.framework.Felix.startBundle(Felix.java:2100)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.felix.framework.Felix.updateBundle(Felix.java:2412)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:994)[org.apache.felix.framework-4.4.1.jar:] 
    at org.apache.karaf.shell.dev.watch.BundleWatcher.run(BundleWatcher.java:120)[43:org.apache.karaf.shell.dev:2.4.0.redhat-621084] 
    at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]

来源

2017-03-02 Alessandro Da Rugna

如果您的XSD与WSDL分开，即不同的文件，则可以使用验证器组件。

<camelContext> 

    <route> 
     <from uri="cxf:bean:myEndpoint" /> 
     <to uri="validator:my/endpoint/schema1.xsd" /> 
     <to uri="bean:doProcess" /> 
    </route> 

</camelContext>

你或许应该也罩住了doTry/doCatch或添加错误处理程序，以您的路线或上下文。

要配置CXF端点到Exchange身体设置为实际的SOAP体：你可以到以下几点：

<cxf:cxfEndpoint id="readingsEndpoint" 
      address="/readings/" 
      serviceClass="my.endpoint.Interface"> 
    <cxf:properties> 
     <entry key="dataFormat" value="PAYLOAD"/> 
    </cxf:properties> 
</cxf:cxfEndpoint>

来源

2017-03-02 19:17:47 noMad17

此时，交易所的主体已经被解散到POJO。是否有一些配置可以告诉CXF在验证之后不要解组并自行完成？ –

我明白了。是的，你可以将dataFormat属性设置为“PAYLOAD”，我会更新我的答案。 – noMad17

在我的合同，第一个设置启用模式验证中，像这样的蓝图情境：

<cxf:cxfEndpoint id="cxfEndpoint" address="http://0.0.0.0:${cxf.port}/${application-path}" serviceClass="my.generated.service.Class" > 
    <cxf:properties> 
     <entry key="schema-validation-enabled" value="true" /> 
    </cxf:properties> 
</cxf:cxfEndpoint>

这应该也适用于代码第一。

来源

2017-03-03 10:17:08 Ralf

在骆驼路由中的CXF SOAP端点中启用XML验证

回答

相关问题