Hi Christian,
The configuration looks good for me.
So I doubt it may be a JAXP issue, please let me know if it still there
after you upgrade the version of Service.
Willem
On 4/26/11 3:09 AM, Christian Mueller wrote:
Hello Willem!
Sorry for not answering so long, but last week I worked together with Ade on
a production issue for one of our customers...
We see this issue (more) often in our stress tests. We use the same request,
but changing one of the request identifiers (e.g. the financial transaction
id). We are using
{noformat}
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
{noformat}
on
{noformat}
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
{noformat}
Our camel cxf configuration looks like the following:
{code}
<camel-cxf:cxfEndpoint id="sspCoreService_1"
address="http://server:8080/services/OrderEntry";
serviceClass="com.company.product.interfaces.module.OrderEntryWebService"
endpointName="xxx:OrderEntryWebServicePort"
serviceName="xxx:OrderEntryService"
wsdlURL="META-INF/product/module/orderEntry.wsdl"
xmlns:xxx="http://www.company.com/module/services/1_0_0";>
<camel-cxf:properties>
<entry key="schema-validation-enabled" value="true" />
</camel-cxf:properties>
<camel-cxf:inInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingInInterceptor" />
</camel-cxf:inInterceptors>
<camel-cxf:inFaultInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingInInterceptor" />
</camel-cxf:inFaultInterceptors>
<camel-cxf:outInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingOutInterceptor" />
</camel-cxf:outInterceptors>
<camel-cxf:outFaultInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingOutInterceptor" />
</camel-cxf:outFaultInterceptors>
</camel-cxf:cxfEndpoint>
{code}
The WSDL file, the XSD file and the generated sources are imported from a
different bundle (which only generates the sources and packge it together
with the WSDL and XSD files) because we use it in multiple bundles.
It's not possible to run these services in an actual SMX version in short
time, because this requires some code changes. We also work on an upgrade to
SMX 4.3.1-fuse-xx-yy, but it take some time...
Best,
Christian
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com
