Nabble - ServiceMix - User

Camel 2.1 with Servicemix 3.3.1

2009-12-09T14:23:33Z

I've been using Camel 2.0 with a patched version of the servicemix-camel.zip file. Is there a patch available for Camel 2.1 yet?

thanks...

Ben - Senior Consultant
using SMX 3.3.1/Camel 2.0

Re: Bridging two ServiceMix instances in same VM

2009-12-09T12:06:29Z

On Wed, Dec 9, 2009 at 7:54 AM, Anto Paul <antopaul.list@...> wrote:

> Any help on this?
>
> Anto
>
> On Fri, Dec 4, 2009 at 10:45 AM, Anto Paul <antopaul.list@...> wrote:
>
>> Hi,
>> I am using ServiceMix lw container and it is deployed as a WAR file in
>> JBoss. There are two WAR files and has its own ServiceMix container. Now I
>> need to communicate between these two instances. Since both are deployed in
>> same VM I don't want to use any remote client that will pass the payload
>> over wire. I am looking for a simple and efficient way of exchanging payload
>> from on instance to another using an API call. Also I am using InOut MEP for
>> that so I am expecting immediate response from second SMX instance.
>> Ways I can think of is to bind SMX client to JNDI and use this client
>> to communicate. But this will give class cast exceptions as both WAR files
>> has ServiceMix JARs. Is there any other way to achieve it?
>>
>> Thanks in advance for help.
>>
>> Anto
>>
>

Have a look at http://activemq.apache.org/vm-transport-reference.html

//HW

Re: org.apache.cxf.interceptor.Fault: Index: 1, Size: 1 using CXF client on SMIX 4.0

2009-12-09T09:41:49Z

The problem was actually in our implementation in that we were adding
the wrong parameter type(s) to the params list.

The document at http://camel.apache.org/cxf.html (paragraph 'How to
prepare the message for the camel-cxf endpoint in POJO data format')
says:
"First you need to specify the operation name in the message header,
then add the method parameters to a list, and initialize the message
with this parameter list."

Actually the camel-cxf client in POJO mode expects the sequence of
elements that constitutes the wsdl parameter (in our case not the
singleMms element itself, but its contents, unwrapped).

2009/12/8 Max Ferrari <mana.lists@...>:

> Hi Willem,
> on the cxf endpoint we use http as transport.
>
> We're working in POJO mode so we're following
> http://camel.apache.org/cxf.html paragraph "How to prepare the message
> for the camel-cxf endpoint in POJO data format": so we're
> - creating an object of type SingleMms (that's the param type
> required by the operation),
> - populate it,
> - marshal it and
> - put it onto the params list that's used to initialize the message
> body (I've added a sample in my original message).
>
> We've tried also by adding / removing our 'callerIdentity' cxf header
> from the exchange to see if that made any difference, but it didn't.
>
> Thanks
>
> Max
>
> 2009/12/8 Willem Jiang <willem.jiang@...>:
>> Do you use jms transport on the CXF endpoint?
>> I fixed an error (with the same error message) of camel-cxf recently, which
>> was caused by the CXF jms transport can't deal with exception message
>> rightly.
>>
>> If not, can you tell me what kind of message do you send to CXF client ?
>>
>> Willem
>>
>> Max Ferrari wrote:
>>>
>>> Hi list,
>>> I have managed to reproduce on SMIX 4.0.0 vanilla (camel 1.6.0 and cxf
>>> 2.1.4) an issue that we are experiencing also on Fuse ESB 4.1.
>>>
>>> In one of our bundles we have defined a CXF client with datamode set
>>> to POJO and MTOM enabled.
>>>
>>> Our customer's WSDL (see below) has an implicit header for
>>> authentication (the header is defined in the wsdl:binding section but
>>> not in the wsdl:portType).
>>> We use the maven cxf-codegen-plugin to execute wsdl2java to generate
>>> client sources.
>>>
>>> The problem arises when - from one of our routes - we generate a
>>> message and send it to the cxf client bean; before it even reaches the
>>> server we get the following exception and then the exchange is routed
>>> to the dead letter queue:
>>>
>>> 11:52:24,685 | WARN | nerContainer-973 | PhaseInterceptorChain |
>>> org.apache.cxf.endpoint.ClientImpl 471 | Interceptor has thrown
>>> exception, unwinding now
>>> org.apache.cxf.interceptor.Fault: Index: 1, Size: 1
>>> at
>>> org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:119)
>>> ...
>>> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
>>> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>>> at java.util.ArrayList.get(ArrayList.java:322)
>>> at
>>> com.intersec.schema.mcms._3.SingleMms_WrapperTypeHelper1.createWrapperObject(Unknown
>>> Source)
>>> at
>>> org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:103)
>>> ... 39 more
>>>
>>> Of course the com.intersec package has to do with the cxf-generated client
>>> code.
>>>
>>> Now, I've dug a bit but the only relevant result I could find is a cxf
>>> issue with out-of-band headers that was fixed in cxf 2.0.3:
>>> https://issues.apache.org/jira/browse/CXF-1129
>>>
>>> Not sure if what I'm seeing in our route is our mistake, a new issue
>>> with cxf or a regression, however I've tried with the workaround
>>> suggested in that cxf Jira entry (running the wsdl2java with '-exsh
>>> true'), unfortunately with no results (we get the same error).
>>>
>>> Any pointers anyone?
>>>
>>> Relevant excerpts of our source code:
>>>
>>> //
>>> -----------------------------------------------------------------------CXF
>>> client definition
>>>
>>> <cxf:cxfEndpoint
>>> id="cxfClientMTOM"
>>> serviceClass="com.intersec.schema.mcms._3.MCMSPortType"
>>> address="${cxfclient.serviceURI}">
>>> <cxf:inInterceptors>
>>> <ref bean="logInbound"/>
>>> </cxf:inInterceptors>
>>> <cxf:outInterceptors>
>>> <ref bean="logOutbound"/>
>>> 
>>> </cxf:outInterceptors>
>>> <cxf:properties>
>>> <entry key="dataFormat" value="POJO" />
>>> <entry key="mtom-enabled" value="true" />
>>> </cxf:properties>
>>> </cxf:cxfEndpoint>
>>>
>>> // -----------------------------------------------------------------------
>>> sample WSDL
>>>
>>> <?xml version="1.0"?>
>>>
>>> <wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
>>> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>>> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
>>> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:tns="http://schema.intersec.com/mcms/3"
>>> targetNamespace="http://schema.intersec.com/mcms/3"
>>> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
>>> xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
>>> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>>> >
>>> <wsdl:types>
>>> <xsd:schema targetNamespace="http://schema.intersec.com/mcms/3">
>>> <xsd:import namespace="http://www.w3.org/2005/05/xmlmime"
>>> schemaLocation="xmime.xsd" />
>>> <xsd:complexType name="attachmentArray">
>>> <xsd:sequence>
>>> <xsd:element name="attachment" type="tns:attachment"
>>> minOccurs="0" maxOccurs="unbounded" />
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> <xsd:complexType name="attachment">
>>> <xsd:sequence>
>>> <xsd:element minOccurs="0" name="fileName" type="xsd:string" />
>>> <xsd:element minOccurs="0" name="binaryData"
>>> type="xmime:base64Binary" />
>>> </xsd:sequence>
>>> </xsd:complexType>
>>>
>>> <xsd:element name="singleMms">
>>> <xsd:complexType>
>>> <xsd:sequence>
>>> <xsd:element name="oadc" type="xsd:string"
>>> minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="msisdn_to" type="xsd:string"
>>> minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="subject" type="xsd:string"
>>> minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="smil"
>>> type="xmime:base64Binary" xmime:expectedContentTypes="text/xml"
>>> minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="attachments"
>>> type="tns:attachmentArray" minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="allow_adaptations" type="xsd:boolean"
>>> minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="message_priority" type="xsd:int"
>>> minOccurs="1" maxOccurs="1"/>
>>> <xsd:element name="message_expiration" type="xsd:int"
>>> minOccurs="1" maxOccurs="1"/>
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> </xsd:element>
>>> <xsd:element name="singleMmsResponse">
>>> <xsd:complexType>
>>> <xsd:sequence>
>>> <xsd:element name="singleMmsReturn" type="xsd:boolean"/>
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> </xsd:element>
>>> <xsd:element name="callerIdentity">
>>> <xsd:complexType>
>>> <xsd:sequence>
>>> <xsd:element name="login" type="xsd:string" minOccurs="1"
>>> maxOccurs="1" />
>>> <xsd:element name="password" type="xsd:string"
>>> minOccurs="1" maxOccurs="1" />
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> </xsd:element>
>>> </xsd:schema>
>>> </wsdl:types>
>>> <wsdl:message name="identityHeader">
>>> <wsdl:part name="request_header" element="tns:callerIdentity"/>
>>> </wsdl:message>
>>> <wsdl:message name="singleMmsRequest">
>>> <wsdl:part name="parameters" element="tns:singleMms"/>
>>> </wsdl:message>
>>> <wsdl:message name="singleMmsResponse">
>>> <wsdl:part name="parameters" element="tns:singleMmsResponse"/>
>>> </wsdl:message>
>>> <wsdl:portType name="MCMSPortType">
>>> <wsdl:operation name="singleMms">
>>> <wsdl:input message="tns:singleMmsRequest" />
>>> <wsdl:output message="tns:singleMmsResponse" />
>>> </wsdl:operation>
>>> </wsdl:portType>
>>> <wsdl:binding name="MCMSBinding" type="tns:MCMSPortType">
>>> <soap:binding style="document"
>>> transport="http://schemas.xmlsoap.org/soap/http"/>
>>> <wsdl:operation name="singleMms">
>>> <soap:operation soapAction="" />
>>> <wsdl:input>
>>> <soap:header use="literal" part="request_header"
>>> message="tns:identityHeader" />
>>> <soap:body use="literal" />
>>> </wsdl:input>
>>> <wsdl:output>
>>> <soap:body use="literal" />
>>> </wsdl:output>
>>> </wsdl:operation>
>>> </wsdl:binding>
>>> <wsdl:service name="MCMS">
>>> <wsdl:port name="MCMSPort" binding="tns:MCMSBinding">
>>> <soap:address location="http://localhost:8000/soap/"/>
>>> </wsdl:port>
>>> </wsdl:service>
>>> </wsdl:definitions>
>>>
>>>
>>>
>>> //
>>> -----------------------------------------------------------------------Sample
>>> route code
>>>
>>> [...]
>>>
>>> .process(new Processor() {
>>>
>>> @Override
>>> public void process(Exchange x) throws Exception {
>>>
>>> SingleMms soapSingleMMS = new SingleMms();
>>> // ... populate the mms fields ...
>>>
>>> List<String> params = new LinkedList<String>();
>>> JAXBContext mcmsJC =
>>> JAXBContext.newInstance("com.intersec.schema.mcms._3");
>>> Marshaller ma = mcmsJC.createMarshaller();
>>> StringWriter mcmsWriter = new StringWriter();
>>> ma.marshal(soapSingleMMS, mcmsWriter);
>>>
>>> // set in request
>>> params.add(mcmsWriter.toString());
>>> Map<String, Object> requestContext = new HashMap<String, Object>();
>>> requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
>>> "http://localhost:9080");
>>>
>>> // create & add caller identity header
>>> CallerIdentity identity = new CallerIdentity();
>>> identity.setLogin("dummy");
>>> identity.setPassword("dummy");
>>> List<Header> headers = new ArrayList<Header>();
>>>
>>> Header identityHeader = new Header(new
>>> QName("com.intersec.schema.mcms._3", "callerIdentity"), identity, new
>>> JAXBDataBinding(CallerIdentity.class));
>>> headers.add(identityHeader);
>>> x.getOut().setHeader(Header.HEADER_LIST, headers);
>>> x.getOut().setBody(params);
>>> x.getOut().setHeader(Client.REQUEST_CONTEXT , requestContext);
>>> x.getOut().setHeader(CxfConstants.OPERATION_NAME, "singleMms");
>>>
>>> }
>>> })
>>>
>>> // web service request
>>> .to("cxf:bean:" + getCxfEndpointId())
>>>
>>> [...]
>>>
>>>
>>> --
>>> Max
>>>
>>
>>
>

--
Max

issues recovering AMQ message store

2009-12-09T09:25:47Z

Whenever I restart servicemix I get this warning message..."The ReferenceStore is not valid - recovering"...is this normal?

Also, the message store recovers quickly on my Windows7 dev box (~10 seconds for 30k persistent messages), but hangs on our Solaris box with identical builds. It takes 30-60 minutes to recover with less than a 1k persisted messages...why would that be?

I'm using SMX 3.3.1, AMQ 5.2, Camel 2.0...with the following AMQ persistence config...

<amq:persistenceAdapter>
<amq:amqPersistenceAdapter directory="file:./data/amq"/>
</amq:persistenceAdapter>

Are there any other config settings which would effect this recovery?

thanks in advance...

Ben - Senior Consultant
using SMX 3.3.1/Camel 2.0

Re: Cluster two Servicemix instances in two separate hosts

2009-12-09T07:37:21Z

I'm assuming that configuring conf/activemq.xml and conf/servicemix.xml properly, a SMX instance endpoint on host1 will be able to route messages to another SMX instance endpoint on host2 without any change to SUs xbean.xml file.
Is this assumption correct? Or am I wrong?

Thanks,
Andrea

o endpoint, service or interface name specified for routing: Camel -> JBI

2009-12-09T06:04:20Z

Hi guys,

I have a cxfbc jbi package into an OSGi. When I list my nmr contents here is what I have:

.....
servicemix-http
servicemix-jms
root
servicemix-wsn2005
{http://servicemix.org/wsnotification}NotificationBroker:
{http://servicemix.org/wsnotification}Publisher:Anonymous
{http://servicemix.org/wsnotification}CreatePullPoint:Bro
{http://tempuri.org/}Service:ServiceSoap
{http://tempuri.org/}ServiceConsumer:ServiceSoapConsumer
I can successfully send a request from {http://tempuri.org/}Service:ServiceSoap to {http://tempuri.org/}ServiceConsumer:ServiceSoapConsumer using the SoapUI tool.

However, when I try to send from a camel application the ESB kept sayin no matching endpoints. Here is my configuration.
<route>
<from uri="nmr:nauRoute"/>
<to uri="jbi:endpoint:http://tempuri.org/Service/ServiceSoap" />
</route>
Here is the err msg:
12:48:17,929 | ERROR | tenerContainer-1 | EndpointMessageListener | rg.apache.camel.processor.Logger 248 | java.lang.IllegalStateException: No endpoint, service or interface name specified for routing
org.apache.camel.RuntimeCamelException: java.lang.IllegalStateException: No endpoint, service or interface name specified for routing
at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1037)
at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:103)
at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:543)
at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:482)
at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:451)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:323)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:982)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: No endpoint, service or interface name specified for routing

Re: Cluster two Servicemix instances in two separate hosts

2009-12-09T04:52:09Z

Thanks for the reply Jean-Baptiste,

before describing what happened, two words about the deployment:
host1 contain simply a file poller, host2 simply a file sender, to assure that the two SUs are properly configured I deployed them locally (in two separate SAs) before trying with separate hosts, and they work correctly together.

I applied what you told me for separate hosts, configuring conf/activemq.xml like that:

<amq:transportConnector uri="tcp://192.168.0.5:61616" />

<amq:networkConnector uri="static://(tcp://192.168.0.5:61616,tcp://192.168.0.2:61616)"/>

with these settings now I can see the NetworkBridge voice under jConsole, and under the voice "org.apache.activemq/Queue" appears the other host endpoint (the file sender) listed, I don't see any error or warning messages on screen, also.
But when I put a file in the poller directory in host1 it can't find the sender endpoint in host2, and it throws a MessagingException "Could not find route for exchange..."

Am I missing anything?

Thanks for the help,
Andrea

Re: Bridging two ServiceMix instances in same VM

2009-12-08T22:54:16Z

Any help on this?

Anto

On Fri, Dec 4, 2009 at 10:45 AM, Anto Paul <antopaul.list@...> wrote:

> Hi,
> I am using ServiceMix lw container and it is deployed as a WAR file in
> JBoss. There are two WAR files and has its own ServiceMix container. Now I
> need to communicate between these two instances. Since both are deployed in
> same VM I don't want to use any remote client that will pass the payload
> over wire. I am looking for a simple and efficient way of exchanging payload
> from on instance to another using an API call. Also I am using InOut MEP for
> that so I am expecting immediate response from second SMX instance.
> Ways I can think of is to bind SMX client to JNDI and use this client
> to communicate. But this will give class cast exceptions as both WAR files
> has ServiceMix JARs. Is there any other way to achieve it?
>
> Thanks in advance for help.
>
> Anto
>

Re: Cluster two Servicemix instances in two separate hosts

2009-12-08T22:40:00Z

Hi Andrea

1/ if address1 == address2 == localhost, you need to use a different
port number for the ActiveMQ broker. For example, the first node on
61616 and the second one on 616167.
2/ The ActiveMQ transportConnectors should match the networkConnectors.
If you define a transportConnectors like this:
<amq:transportConnector uri="tcp://localhost:616161"
discoveryUri="multicast://default"/>
you should have a networkConnectors like this:
<amq:networkConnector uri="multicast://default"/>
The networkConnector is responsible of the ActiveMQ brokers plug.
3/ If you use localhost as address, you can't use multicast as it's not
supported by the lo interface. In that case, you need to use static
ActiveMQ broker declaration like this:
<amq:transportConnectors>
<amq:transportConnector uri="tcp://localhost:61616"/>
</amq:transportConnectors>
<amq:networkConnectors>
<amq:networkConnector
uri="static://(tcp://localhost:61616,tcp://localhost:616167)"/>
</amq:networkConnectors>

Regards
JB

andrealibero.valori wrote:

> Hi, I'm a student working on a project based on Servicemix.
> The project need to run two Servicemix 3.3.1 instances in two separate hosts
> in the same network, one with poller endpoints, the other with writer
> endpoints, and possibly use transparent routing between the SMX instances.
> I tried following instructions from mailing lists and the SMX website with
> no success.
>
> In particular:
> - name the two JBI container with different names in servicemix.xml
> - set the JBI container flowName to "jms"
> - name the two ActiveMQ brokers with different names in actimemq.xml
> - set the AMQ connectors to:
> SMX instance 1
> <amq:transportConnector uri="tcp://[address1]:61616"
> discoveryUri="multicast://default"/>
> SMX instance 2
> <amq:transportConnector uri="tcp://[address2]:61616"
> discoveryUri="multicast://default"/>
>
> when [address1] = [address2] = localhost one of the SMX instances writes
> repeatedly
> WARN - DiscoveryNetworkConnector could not start NetworkBridge...
> java.net.UnknownHostException: PC1
>
> when [address1] = [address2] = 0.0.0.0 no instance write anything on screen,
> but they don't see each other, and there is no "NetworkBridge" in jConsole
> under "org.apache.activemq/localhost"
>
> when [address1] = 192.168.0.2 and [address2] = 192.168.0.5 one of the
> instances writes repeatedly
> WARN - DiscoveryNetworkConnector could not start NetworkBridge...
> java.net.ConnectException: Connection timed out
>
>
> Can someone help me?
> Thanks in advance
>
>

Cluster two Servicemix instances in two separate hosts

2009-12-08T14:22:01Z

Hi, I'm a student working on a project based on Servicemix.
The project need to run two Servicemix 3.3.1 instances in two separate hosts in the same network, one with poller endpoints, the other with writer endpoints, and possibly use transparent routing between the SMX instances.
I tried following instructions from mailing lists and the SMX website with no success.

In particular:
- name the two JBI container with different names in servicemix.xml
- set the JBI container flowName to "jms"
- name the two ActiveMQ brokers with different names in actimemq.xml
- set the AMQ connectors to:
SMX instance 1
<amq:transportConnector uri="tcp://[address1]:61616" discoveryUri="multicast://default"/>
SMX instance 2
<amq:transportConnector uri="tcp://[address2]:61616" discoveryUri="multicast://default"/>

when [address1] = [address2] = localhost one of the SMX instances writes repeatedly
WARN - DiscoveryNetworkConnector could not start NetworkBridge... java.net.UnknownHostException: PC1

when [address1] = [address2] = 0.0.0.0 no instance write anything on screen, but they don't see each other, and there is no "NetworkBridge" in jConsole under "org.apache.activemq/localhost"

when [address1] = 192.168.0.2 and [address2] = 192.168.0.5 one of the instances writes repeatedly
WARN - DiscoveryNetworkConnector could not start NetworkBridge... java.net.ConnectException: Connection timed out

Can someone help me?
Thanks in advance

Does EIP AsyncBridge block processing?

2009-12-08T11:25:05Z

I have a service unit composed of an eip:async-bridge configured with a certain number of seconds for timeout. When I send a message into this service unit, it hands it off to another service to create a response message. If I delay the response message or simply do not return a response message, I've noticed that it appears that I cannot process other request/response pairs through my service unit during the timeout duration.

So is it accurate that the eip:async-bridge will block for the timeout duration while waiting for the response message to come back?

If so, is there away to accomplish the async-bridge functionality that does not hold up processing of other messages?

Re: Migrating from SMX3 to SMX4

2009-12-08T09:06:51Z

Freeman,

We did it that way because we have several cxf-bc endpoints that are spread across multiple SA's and all run on the same port, this is the workaround we figured from you post in april 2009.

http://cwiki.apache.org/SM/discussion-forums.html#nabble-td23066349

Has this been fixed in SMX3.3.1, where we can set busCfg=cxf.xml for multiple cxf-bc endpoints in xbean.xml of the SA?

thanks
-gopal

Freeman Fang wrote:

Hi,

Even you use SMX3 with JBI package SAs/SUs, you should put busConfig
files(cxf.xml in your case) in SAs/SUs, but not put it in SMX_HOME/
conf.

Freeman
On 2009-12-7, at 上午2:22, GNarra wrote:

>
> Lukasz,
>
> We have a installation of SMX3.3.1 with CXF BC, CXF SE, SA's, We
> want to
> move to SMX 4 by deploying these existing SA's in SMX4 and then move
> the
> SA's to OSGi Bundles, If we start migrating to OSGi bundles as our
> starting
> step, it is going to take significant time before our system is
> ready to
> test.
>
> So I am looking to how to migrate quickly and then move to OSGi
> bundles. I
> looked at SMX 4 documentation for migrating but all that says is
> deploy the
> SA's in deploy directory. We have stand alone jars that are not part
> of SA's
> and deployed in the lib folder. I am wondering how do I move all this
> configuration(servicemix.conf) to SMX 4.
>
> cxf.xml was used by the CXF BC and CXF SE to initiliaze the port for
> the
> whole bus(CXFBusImp)l, I see that CXF BC is still on 2009.01 version
> in SMX
> 4, so where do I deploy the cxf.xml bus configuration.
>
> thanks for your help
> -gopal
>
>
> Lukasz Dywicki wrote:
>>
>> Hello,
>> Changes that ServiceMix team made in SMX 4 is really big.
>> 1) It depends, because SMX 4 is built on OSGi. In OSGi world class
>> loading
>> are very strict. In SMX 3 the conf directory was classpath element.
>> In
>> SMX4 configuration is no longer classpath element so you have to
>> enable it
>> in own bundle.
>> 2) In SMX 4 the JBI is only one feature from set of provided. If
>> you had
>> defined beans in servicemix.xml you should enable it as services in
>> OSGi
>> bundle. SMX4 offers support for JBI 1.0 but preffered programming
>> is based
>> on OSGi bundles. First of all it allows you to define many different
>> endpoints in one bundle (Maven project) - CXF BC, CXF SE or event
>> embedded
>> Camel.
>> 3) The default broker is on deploy directory.
>> 4) You can add own keystore using -Djavax.net.ssl.keyStore parameter.
>>
>> Best regards,
>> Lukasz Dywicki
>>
>>
>> GNarra wrote:
>>>
>>> Hi All,
>>>
>>> We are evaluating on making the move from SMX3.3.1 to SMX4 and
>>> have a few
>>> questions.
>>>
>>> 1) In SMX 3.3.1, we deployed servicemix/conf/cxf.xml which has the
>>> <httpj:engine-factory><httpj:engine port="0000">, where do you
>>> deploy
>>> cxf.xml in SMX4 configuration?
>>> 2) what is the equivalent of servicemix.xml "jbi" container
>>> configuration?
>>> 3) Where is the DefaultBroker class in smx4?
>>> 4) In SMX4 there is no keystore.jks file,
>>>
>>> any help is greatly appreciated
>>>
>>> thanks
>>> -gopal
>>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Migrating-from-SMX3-to-SMX4-tp26646562p26667505.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

Re: "stax read exception" with cxf-bc & cxf-se

2009-12-08T02:12:11Z

Hi,

thank you for the hint. I looked into jira, but couldn't find the issue.

-- Ingo

Freeman Fang wrote:

Hi,

As you are using mac, I believe you run into a known issue tracked by
SMXCOMP-600[1], this issue already get fixed and would be in
servicemix-cxf-bc-2009.02 release

[1]https://issues.apache.org/activemq/browse/SMXCOMP-600

Freeman
On 2009-12-8, at 上午12:18, devylon wrote:

>
> i did my tests with soap ui and generated sample requests. what i
> figured out
> is:
>
> when is submit this envelop:
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>
> <soapenv:Body>
> <typ:GetPerson
> xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types">
> <typ:personId>1</typ:personId>
> </typ:GetPerson>
> </soapenv:Body>
> </soapenv:Envelope>
>
> everything is fine, BUT if i submit this envelop:
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types"
>>
> <soapenv:Body>
> <typ:GetPerson >
> <typ:personId>1</typ:personId>
> </typ:GetPerson>
> </soapenv:Body>
> </soapenv:Envelope>
>
> i get the stax exception. i'm little bit confused and couldn't
> explain the
> difference
> to me ?!?
>
>
>
>
> devylon wrote:
>>
>> Hi,
>>
>> I'm testing the cxf-bc and cxf-se components. But unfortunatly i
>> get the
>> following error with the wsdl-first sample:
>>
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@2e2acb47 dequeued
>> exchange: InOut[
>> id: ID:10.41.20.39-12569e5f07a-4:1
>> status: Error
>> role: consumer
>> interface: {http://servicemix.apache.org/samples/wsdl-first}Person
>> service: {http://servicemix.apache.org/samples/wsdl-
>> first}PersonService
>> endpoint: PersonImplPort
>> operation: {http://servicemix.apache.org/samples/wsdl-
>> first}GetPerson
>> in: <?xml version="1.0" encoding="UTF-8"?>
>> <jbi:message name="GetPersonRequest" type="msg:GetPersonRequest"
>> version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper
>> "
>> xmlns:msg="http://servicemix.apache.org/samples/wsdl-first"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-
>> instance"><jbi:part><typ:GetPerson>
>> <typ:personId>1</typ:personId>
>> </typ:GetPerson></jbi:part></jbi:message>
>> error: org.apache.cxf.interceptor.Fault: stax read exception
>> ]
>> DEBUG - DeliveryChannelImpl - Notifying exchange
>> ID:10.41.20.39-12569e5f07a-4:1(386d346c) in
>> DeliveryChannel{servicemix-cxf-bc} from
>> processInboundSynchronousExchange
>> DEBUG - DeliveryChannelImpl - Notified:
>> ID:10.41.20.39-12569e5f07a-4:1(386d346c) in
>> DeliveryChannel{servicemix-cxf-bc} from sendSync
>> 07.12.2009 17:08:48 org.apache.cxf.phase.PhaseInterceptorChain
>> doIntercept
>> INFO: Interceptor has thrown exception, unwinding now stax read
>> exception
>>
>>
>> My environment is:
>> - OS: OSX 10.6
>> - Java: Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219)
>> Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode)
>> - ServiceMix : 3.3.1
>>
>> I have no clue whats going wrong :(
>>
>> -- devylon
>>
>
> --
> View this message in context: http://old.nabble.com/%22stax-read-exception%22-with-cxf-bc---cxf-se-tp26679548p26679639.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

Re: cxfbc provider sample

2009-12-08T00:47:38Z

Thanks for the response.

I am a little confused on how to use that. It seems like a test unit for a java webservice deployed on the ESB.

May be what I should ask is how do I integrate this into my camel application in order to use it to call a remote webservice over http/soap hosted on another IP?

Kind Regards.

Freeman Fang wrote:

Hi,

Take a look at CxfBcProviderTest[1]

[1]https://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/src/test/java/org/apache/servicemix/cxfbc/CxfBcProviderTest.java

Freeman
On 2009-12-8, at 下午3:42, lekkie wrote:

>
> I have not come across a sample cxfbc provider sample. If it exists
> can
> someone point me to it?
>
> I understand same can be achieved with camel-cxf component, but the
> components' samples available have been an integration with java
> classes
> (jaxws).
>
> I actually need something to integrate with a remote webservice url.
>
> Knd Rgds.
> --
> View this message in context: http://old.nabble.com/cxfbc-provider-sample-tp26689856p26689856.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

Re: cxfbc provider sample

2009-12-07T23:57:33Z

Hi,

Take a look at CxfBcProviderTest[1]

[1]https://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/src/test/java/org/apache/servicemix/cxfbc/CxfBcProviderTest.java

Freeman
On 2009-12-8, at 下午3:42, lekkie wrote:

>
> I have not come across a sample cxfbc provider sample. If it exists
> can
> someone point me to it?
>
> I understand same can be achieved with camel-cxf component, but the
> components' samples available have been an integration with java
> classes
> (jaxws).
>
> I actually need something to integrate with a remote webservice url.
>
> Knd Rgds.
> --
> View this message in context: http://old.nabble.com/cxfbc-provider-sample-tp26689856p26689856.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

Re: org.apache.cxf.interceptor.Fault: Index: 1, Size: 1 using CXF client on SMIX 4.0

2009-12-07T23:45:27Z

Hi Willem,
on the cxf endpoint we use http as transport.

We're working in POJO mode so we're following
http://camel.apache.org/cxf.html paragraph "How to prepare the message
for the camel-cxf endpoint in POJO data format": so we're
- creating an object of type SingleMms (that's the param type
required by the operation),
- populate it,
- marshal it and
- put it onto the params list that's used to initialize the message
body (I've added a sample in my original message).

We've tried also by adding / removing our 'callerIdentity' cxf header
from the exchange to see if that made any difference, but it didn't.

Thanks

Max

2009/12/8 Willem Jiang <willem.jiang@...>:

> Do you use jms transport on the CXF endpoint?
> I fixed an error (with the same error message) of camel-cxf recently, which
> was caused by the CXF jms transport can't deal with exception message
> rightly.
>
> If not, can you tell me what kind of message do you send to CXF client ?
>
> Willem
>
> Max Ferrari wrote:
>>
>> Hi list,
>> I have managed to reproduce on SMIX 4.0.0 vanilla (camel 1.6.0 and cxf
>> 2.1.4) an issue that we are experiencing also on Fuse ESB 4.1.
>>
>> In one of our bundles we have defined a CXF client with datamode set
>> to POJO and MTOM enabled.
>>
>> Our customer's WSDL (see below) has an implicit header for
>> authentication (the header is defined in the wsdl:binding section but
>> not in the wsdl:portType).
>> We use the maven cxf-codegen-plugin to execute wsdl2java to generate
>> client sources.
>>
>> The problem arises when - from one of our routes - we generate a
>> message and send it to the cxf client bean; before it even reaches the
>> server we get the following exception and then the exchange is routed
>> to the dead letter queue:
>>
>> 11:52:24,685 | WARN | nerContainer-973 | PhaseInterceptorChain |
>> org.apache.cxf.endpoint.ClientImpl 471 | Interceptor has thrown
>> exception, unwinding now
>> org.apache.cxf.interceptor.Fault: Index: 1, Size: 1
>> at
>> org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:119)
>> ...
>> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
>> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>> at java.util.ArrayList.get(ArrayList.java:322)
>> at
>> com.intersec.schema.mcms._3.SingleMms_WrapperTypeHelper1.createWrapperObject(Unknown
>> Source)
>> at
>> org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:103)
>> ... 39 more
>>
>> Of course the com.intersec package has to do with the cxf-generated client
>> code.
>>
>> Now, I've dug a bit but the only relevant result I could find is a cxf
>> issue with out-of-band headers that was fixed in cxf 2.0.3:
>> https://issues.apache.org/jira/browse/CXF-1129
>>
>> Not sure if what I'm seeing in our route is our mistake, a new issue
>> with cxf or a regression, however I've tried with the workaround
>> suggested in that cxf Jira entry (running the wsdl2java with '-exsh
>> true'), unfortunately with no results (we get the same error).
>>
>> Any pointers anyone?
>>
>> Relevant excerpts of our source code:
>>
>> //
>> -----------------------------------------------------------------------CXF
>> client definition
>>
>> <cxf:cxfEndpoint
>> id="cxfClientMTOM"
>> serviceClass="com.intersec.schema.mcms._3.MCMSPortType"
>> address="${cxfclient.serviceURI}">
>> <cxf:inInterceptors>
>> <ref bean="logInbound"/>
>> </cxf:inInterceptors>
>> <cxf:outInterceptors>
>> <ref bean="logOutbound"/>
>> 
>> </cxf:outInterceptors>
>> <cxf:properties>
>> <entry key="dataFormat" value="POJO" />
>> <entry key="mtom-enabled" value="true" />
>> </cxf:properties>
>> </cxf:cxfEndpoint>
>>
>> // -----------------------------------------------------------------------
>> sample WSDL
>>
>> <?xml version="1.0"?>
>>
>> <wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
>> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
>> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:tns="http://schema.intersec.com/mcms/3"
>> targetNamespace="http://schema.intersec.com/mcms/3"
>> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
>> xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
>> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>> >
>> <wsdl:types>
>> <xsd:schema targetNamespace="http://schema.intersec.com/mcms/3">
>> <xsd:import namespace="http://www.w3.org/2005/05/xmlmime"
>> schemaLocation="xmime.xsd" />
>> <xsd:complexType name="attachmentArray">
>> <xsd:sequence>
>> <xsd:element name="attachment" type="tns:attachment"
>> minOccurs="0" maxOccurs="unbounded" />
>> </xsd:sequence>
>> </xsd:complexType>
>> <xsd:complexType name="attachment">
>> <xsd:sequence>
>> <xsd:element minOccurs="0" name="fileName" type="xsd:string" />
>> <xsd:element minOccurs="0" name="binaryData"
>> type="xmime:base64Binary" />
>> </xsd:sequence>
>> </xsd:complexType>
>>
>> <xsd:element name="singleMms">
>> <xsd:complexType>
>> <xsd:sequence>
>> <xsd:element name="oadc" type="xsd:string"
>> minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="msisdn_to" type="xsd:string"
>> minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="subject" type="xsd:string"
>> minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="smil"
>> type="xmime:base64Binary" xmime:expectedContentTypes="text/xml"
>> minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="attachments"
>> type="tns:attachmentArray" minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="allow_adaptations" type="xsd:boolean"
>> minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="message_priority" type="xsd:int"
>> minOccurs="1" maxOccurs="1"/>
>> <xsd:element name="message_expiration" type="xsd:int"
>> minOccurs="1" maxOccurs="1"/>
>> </xsd:sequence>
>> </xsd:complexType>
>> </xsd:element>
>> <xsd:element name="singleMmsResponse">
>> <xsd:complexType>
>> <xsd:sequence>
>> <xsd:element name="singleMmsReturn" type="xsd:boolean"/>
>> </xsd:sequence>
>> </xsd:complexType>
>> </xsd:element>
>> <xsd:element name="callerIdentity">
>> <xsd:complexType>
>> <xsd:sequence>
>> <xsd:element name="login" type="xsd:string" minOccurs="1"
>> maxOccurs="1" />
>> <xsd:element name="password" type="xsd:string"
>> minOccurs="1" maxOccurs="1" />
>> </xsd:sequence>
>> </xsd:complexType>
>> </xsd:element>
>> </xsd:schema>
>> </wsdl:types>
>> <wsdl:message name="identityHeader">
>> <wsdl:part name="request_header" element="tns:callerIdentity"/>
>> </wsdl:message>
>> <wsdl:message name="singleMmsRequest">
>> <wsdl:part name="parameters" element="tns:singleMms"/>
>> </wsdl:message>
>> <wsdl:message name="singleMmsResponse">
>> <wsdl:part name="parameters" element="tns:singleMmsResponse"/>
>> </wsdl:message>
>> <wsdl:portType name="MCMSPortType">
>> <wsdl:operation name="singleMms">
>> <wsdl:input message="tns:singleMmsRequest" />
>> <wsdl:output message="tns:singleMmsResponse" />
>> </wsdl:operation>
>> </wsdl:portType>
>> <wsdl:binding name="MCMSBinding" type="tns:MCMSPortType">
>> <soap:binding style="document"
>> transport="http://schemas.xmlsoap.org/soap/http"/>
>> <wsdl:operation name="singleMms">
>> <soap:operation soapAction="" />
>> <wsdl:input>
>> <soap:header use="literal" part="request_header"
>> message="tns:identityHeader" />
>> <soap:body use="literal" />
>> </wsdl:input>
>> <wsdl:output>
>> <soap:body use="literal" />
>> </wsdl:output>
>> </wsdl:operation>
>> </wsdl:binding>
>> <wsdl:service name="MCMS">
>> <wsdl:port name="MCMSPort" binding="tns:MCMSBinding">
>> <soap:address location="http://localhost:8000/soap/"/>
>> </wsdl:port>
>> </wsdl:service>
>> </wsdl:definitions>
>>
>>
>>
>> //
>> -----------------------------------------------------------------------Sample
>> route code
>>
>> [...]
>>
>> .process(new Processor() {
>>
>> @Override
>> public void process(Exchange x) throws Exception {
>>
>> SingleMms soapSingleMMS = new SingleMms();
>> // ... populate the mms fields ...
>>
>> List<String> params = new LinkedList<String>();
>> JAXBContext mcmsJC =
>> JAXBContext.newInstance("com.intersec.schema.mcms._3");
>> Marshaller ma = mcmsJC.createMarshaller();
>> StringWriter mcmsWriter = new StringWriter();
>> ma.marshal(soapSingleMMS, mcmsWriter);
>>
>> // set in request
>> params.add(mcmsWriter.toString());
>> Map<String, Object> requestContext = new HashMap<String, Object>();
>> requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
>> "http://localhost:9080");
>>
>> // create & add caller identity header
>> CallerIdentity identity = new CallerIdentity();
>> identity.setLogin("dummy");
>> identity.setPassword("dummy");
>> List<Header> headers = new ArrayList<Header>();
>>
>> Header identityHeader = new Header(new
>> QName("com.intersec.schema.mcms._3", "callerIdentity"), identity, new
>> JAXBDataBinding(CallerIdentity.class));
>> headers.add(identityHeader);
>> x.getOut().setHeader(Header.HEADER_LIST, headers);
>> x.getOut().setBody(params);
>> x.getOut().setHeader(Client.REQUEST_CONTEXT , requestContext);
>> x.getOut().setHeader(CxfConstants.OPERATION_NAME, "singleMms");
>>
>> }
>> })
>>
>> // web service request
>> .to("cxf:bean:" + getCxfEndpointId())
>>
>> [...]
>>
>>
>> --
>> Max
>>
>
>

Re: Getting error when using Apache camel inside servicemix.

2009-12-07T23:43:22Z

Thank you willem....

I am able to write in a file using CamelContextFactory...
I am adding the way i did for future reference.

1) Create an Activator class which implements BundleActivator.
Store the BundleContext variable in a static variable added by us in the Activator class.

Do the following code where u want to create the CamelContext instance

bundleContext = Activator.getBundleContext(); //static BundleContext
camelContextFactory = new CamelContextFactory();

camelContextFactory.setBundleContext(bundleContext);
camel = camelContextFactory.createContext();

camel.addComponent("file", new FileComponent());
camel.start();

Harbeer kadian

willem.jiang wrote:

Hi,

Since there are some difference between the OSGi and normal java class
for loading the files in META-INF (camel component, lanaguage and type
converter finding are based on it ) . We introduce a camel-osgi module
to resolve these kind of issue.

You can use the CamelContextFactory in the camel-osig module to create
the CamelContext and you need to set the BundleContext before calling
the createContext method.

Willem

Harbeer Kadian wrote:
> Hi,
>
> I created one webservice in the OSGI format and installed it in the
> servicemix.
> The webservice worked fine and i was able to send and receive requests
> through SoapUI software.
>
> I tried to add some apache camel code inside this so that i can send a
> string to a file.
>
> The implementation is as follows
> This is my webservice implementation class.
>
> package com.webservice.calculator;
>
> import java.util.logging.Logger;
> import javax.jws.WebMethod;
> import javax.jws.WebParam;
> import javax.jws.WebResult;
> import javax.jws.WebService;
> import javax.xml.bind.annotation.XmlSeeAlso;
> import javax.xml.ws.RequestWrapper;
> import javax.xml.ws.ResponseWrapper;
>
> import org.apache.camel.CamelContext;
> import org.apache.camel.Component;
> import org.apache.camel.Endpoint;
> import org.apache.camel.Exchange;
> import org.apache.camel.Producer;
> import org.apache.camel.ProducerTemplate;
> import org.apache.camel.component.file.FileComponent;
> import org.apache.camel.component.log.LogComponent;
> import org.apache.camel.impl.DefaultCamelContext;
>
> import com.progress.pso.payments_api.PaymentsApi;
>
> /**
> * This class was generated by Apache CXF 2.2.5
> * Tue Dec 01 17:46:59 IST 2009
> * Generated source version: 2.2.5
> *
> */
>
> @javax.jws.WebService(
> serviceName = "CalculatorService",
> portName = "CalculatorSoapPort",
> targetNamespace = "http://calculator.webservice.com",
> wsdlLocation =
> "file:/D:/harbeer/Maven_Project/payment-web-service-osgi/src/main/resources/wsdl/Calculator.wsdl",
> endpointInterface =
> "com.webservice.calculator.CalculatorPortType")
>
> public class CalculatorPortTypeImpl implements CalculatorPortType {
>
> private static final Logger LOG =
> Logger.getLogger(CalculatorPortTypeImpl.class.getName());
> private PaymentsApi paymentApi;
> private CamelContext camel;
> private ProducerTemplate template;
>
>
> public CalculatorPortTypeImpl() throws Exception {
> camel = new DefaultCamelContext();
> template = camel.createProducerTemplate();
> camel.addComponent("file", new FileComponent());
> camel.start();
> }
>
> public void setPaymentApi(PaymentsApi paymentApi) {
> this.paymentApi = paymentApi;
> }
>
> /* (non-Javadoc)
> * @see
> com.webservice.calculator.CalculatorPortType#subtractNumbers(java.math.BigInteger
> inputOne ,)java.math.BigInteger inputTwo )*
> */
> public java.math.BigInteger subtractNumbers(java.math.BigInteger
> inputOne,java.math.BigInteger inputTwo) {
> try {
> sendToCamelFile("harbeer");
> return paymentApi.subtractNumbers(inputOne, inputTwo);
> } catch (Exception ex) {
> ex.printStackTrace();
> throw new RuntimeException(ex);
> }
> }
>
>
> private void sendToCamelFile(String name) {
> try {
>
> // get the log component
> Component component = camel.getComponent("file");
>
> Endpoint endpoint =
> component.createEndpoint("file:///D:/harbeer");
> Exchange exchange = endpoint.createExchange();
> exchange.getIn().setBody(name);
> exchange.getIn().setHeader(FileComponent.HEADER_FILE_NAME,
> "harbeer.txt");
>
> // now we want to send the exchange to this endpoint and we then
> need a producer
> // for this, so we create and start the producer.
> Producer producer = endpoint.createProducer();
> System.out.println(producer);
> producer.start();
> System.out.println(name);
> producer.process(exchange);
> producer.stop();
>
> } catch (Exception e) {
> // we ignore any exceptions and just rethrow as runtime
> throw new RuntimeException(e);
>
> }
>
> }
>
> }
>
> I installed this new webservice implementation inside servicemix 4 as an
> osgi bundle.
> I got following exception when i called webservice method subtractNumbers();
>
>
> Caused by: org.apache.camel.NoTypeConversionAvailableException: No type
> converte
> r available to convert from type: class
> org.apache.camel.component.file.FileMess
> age to the required type: java.io.InputStream with value FileMessage:
> D:\harbeer
>
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.doConvertTo(Defa
> ultTypeConverter.java:147)
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(Defaul
> tTypeConverter.java:90)
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(Defaul
> tTypeConverter.java:86)
> at
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:85)
> at
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:52)
> at
> org.apache.camel.util.ExchangeHelper.getMandatoryInBody(ExchangeHelpe
> r.java:130)
> at
> org.apache.camel.component.file.FileProducer.process(FileProducer.jav
> a:78)
> at
> org.apache.camel.component.file.FileProducer.process(FileProducer.jav
> a:61)
> at
> com.webservice.calculator.CalculatorPortTypeImpl.sendToCamelFile(Calc
> ulatorPortTypeImpl.java:129)
> ... 31 more
>
> Please help if i am missing some thing.
>
> With Regards
> Harbeer Kadian

cxfbc provider sample

2009-12-07T23:42:03Z

I have not come across a sample cxfbc provider sample. If it exists can someone point me to it?

I understand same can be achieved with camel-cxf component, but the components' samples available have been an integration with java classes (jaxws).

I actually need something to integrate with a remote webservice url.

Knd Rgds.

apache ODE-Database configuration error

2009-12-07T22:05:52Z

Hello there,

I have deployed ODE jbi version 1.3.3 through web console. But when i starting the service using web console, I get following db configuration error as follows

><![CDATA[javax.jbi.JBIException: Database configuration error.

at org.apache.ode.jbi.OdeLifeCycle.initDataSource(OdeLifeCycle.java:181)

at org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:114)

at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java:201)

at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.java:287)

at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.java:216)

at org.apache.servicemix.jbi.framework.AdminCommandsService.startComponent(AdminCommandsService.java:156)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252)

at org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStandardMBean.java:323)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)

at org.springframework.jmx.access.MBeanClientInterceptor.invokeOperation(MBeanClientInterceptor.java:371)

at org.springframework.jmx.access.MBeanClientInterceptor.invoke(MBeanClientInterceptor.java:302)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)

at $Proxy51.startComponent(Unknown Source)

at org.apache.servicemix.web.controller.ComponentLifeCycle.handleRequest(ComponentLifeCycle.java:57)

at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)

at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:857)

at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:792)

at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:475)

at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:440)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)

at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)

at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)

at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)

at org.apache.servicemix.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:81)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)

at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)

at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

at weblogic.security.service.SecurityManager.runAs(Unknown Source)

at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)

at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)

at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Caused by: java.lang.RuntimeException: TransactionManager is not recoverable.

at org.apache.ode.il.dbutil.Database.initInternalDb(Database.java:180)

at org.apache.ode.il.dbutil.Database.initEmbeddedDb(Database.java:233)

at org.apache.ode.il.dbutil.Database.initDataSource(Database.java:148)

at org.apache.ode.il.dbutil.Database.start(Database.java:99)

at org.apache.ode.jbi.OdeLifeCycle.initDataSource(OdeLifeCycle.java:177)

... 46 more

]]></stack-trace>
</exception-info>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
</jbi-task-result>
</jbi-task>

at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:115)
at org.apache.servicemix.jbi.framework.AdminCommandsService.startComponent(AdminCommandsService.java:159)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252)
at org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStandardMBean.java:323)
... 35 more

Any idea on this ?

Regards,

Brijesh N K

Re: Getting error when using Apache camel inside servicemix.

2009-12-07T18:44:24Z

Hi,

Since there are some difference between the OSGi and normal java class
for loading the files in META-INF (camel component, lanaguage and type
converter finding are based on it ) . We introduce a camel-osgi module
to resolve these kind of issue.

You can use the CamelContextFactory in the camel-osig module to create
the CamelContext and you need to set the BundleContext before calling
the createContext method.

Willem

Harbeer Kadian wrote:

> Hi,
>
> I created one webservice in the OSGI format and installed it in the
> servicemix.
> The webservice worked fine and i was able to send and receive requests
> through SoapUI software.
>
> I tried to add some apache camel code inside this so that i can send a
> string to a file.
>
> The implementation is as follows
> This is my webservice implementation class.
>
> package com.webservice.calculator;
>
> import java.util.logging.Logger;
> import javax.jws.WebMethod;
> import javax.jws.WebParam;
> import javax.jws.WebResult;
> import javax.jws.WebService;
> import javax.xml.bind.annotation.XmlSeeAlso;
> import javax.xml.ws.RequestWrapper;
> import javax.xml.ws.ResponseWrapper;
>
> import org.apache.camel.CamelContext;
> import org.apache.camel.Component;
> import org.apache.camel.Endpoint;
> import org.apache.camel.Exchange;
> import org.apache.camel.Producer;
> import org.apache.camel.ProducerTemplate;
> import org.apache.camel.component.file.FileComponent;
> import org.apache.camel.component.log.LogComponent;
> import org.apache.camel.impl.DefaultCamelContext;
>
> import com.progress.pso.payments_api.PaymentsApi;
>
> /**
> * This class was generated by Apache CXF 2.2.5
> * Tue Dec 01 17:46:59 IST 2009
> * Generated source version: 2.2.5
> *
> */
>
> @javax.jws.WebService(
> serviceName = "CalculatorService",
> portName = "CalculatorSoapPort",
> targetNamespace = "http://calculator.webservice.com",
> wsdlLocation =
> "file:/D:/harbeer/Maven_Project/payment-web-service-osgi/src/main/resources/wsdl/Calculator.wsdl",
> endpointInterface =
> "com.webservice.calculator.CalculatorPortType")
>
> public class CalculatorPortTypeImpl implements CalculatorPortType {
>
> private static final Logger LOG =
> Logger.getLogger(CalculatorPortTypeImpl.class.getName());
> private PaymentsApi paymentApi;
> private CamelContext camel;
> private ProducerTemplate template;
>
>
> public CalculatorPortTypeImpl() throws Exception {
> camel = new DefaultCamelContext();
> template = camel.createProducerTemplate();
> camel.addComponent("file", new FileComponent());
> camel.start();
> }
>
> public void setPaymentApi(PaymentsApi paymentApi) {
> this.paymentApi = paymentApi;
> }
>
> /* (non-Javadoc)
> * @see
> com.webservice.calculator.CalculatorPortType#subtractNumbers(java.math.BigInteger
> inputOne ,)java.math.BigInteger inputTwo )*
> */
> public java.math.BigInteger subtractNumbers(java.math.BigInteger
> inputOne,java.math.BigInteger inputTwo) {
> try {
> sendToCamelFile("harbeer");
> return paymentApi.subtractNumbers(inputOne, inputTwo);
> } catch (Exception ex) {
> ex.printStackTrace();
> throw new RuntimeException(ex);
> }
> }
>
>
> private void sendToCamelFile(String name) {
> try {
>
> // get the log component
> Component component = camel.getComponent("file");
>
> Endpoint endpoint =
> component.createEndpoint("file:///D:/harbeer");
> Exchange exchange = endpoint.createExchange();
> exchange.getIn().setBody(name);
> exchange.getIn().setHeader(FileComponent.HEADER_FILE_NAME,
> "harbeer.txt");
>
> // now we want to send the exchange to this endpoint and we then
> need a producer
> // for this, so we create and start the producer.
> Producer producer = endpoint.createProducer();
> System.out.println(producer);
> producer.start();
> System.out.println(name);
> producer.process(exchange);
> producer.stop();
>
> } catch (Exception e) {
> // we ignore any exceptions and just rethrow as runtime
> throw new RuntimeException(e);
>
> }
>
> }
>
> }
>
> I installed this new webservice implementation inside servicemix 4 as an
> osgi bundle.
> I got following exception when i called webservice method subtractNumbers();
>
>
> Caused by: org.apache.camel.NoTypeConversionAvailableException: No type
> converte
> r available to convert from type: class
> org.apache.camel.component.file.FileMess
> age to the required type: java.io.InputStream with value FileMessage:
> D:\harbeer
>
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.doConvertTo(Defa
> ultTypeConverter.java:147)
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(Defaul
> tTypeConverter.java:90)
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(Defaul
> tTypeConverter.java:86)
> at
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:85)
> at
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:52)
> at
> org.apache.camel.util.ExchangeHelper.getMandatoryInBody(ExchangeHelpe
> r.java:130)
> at
> org.apache.camel.component.file.FileProducer.process(FileProducer.jav
> a:78)
> at
> org.apache.camel.component.file.FileProducer.process(FileProducer.jav
> a:61)
> at
> com.webservice.calculator.CalculatorPortTypeImpl.sendToCamelFile(Calc
> ulatorPortTypeImpl.java:129)
> ... 31 more
>
> Please help if i am missing some thing.
>
> With Regards
> Harbeer Kadian

Re: Migrating from SMX3 to SMX4

2009-12-07T18:31:01Z

Hi,

Even you use SMX3 with JBI package SAs/SUs, you should put busConfig
files(cxf.xml in your case) in SAs/SUs, but not put it in SMX_HOME/
conf.

Freeman
On 2009-12-7, at 上午2:22, GNarra wrote:

>
> Lukasz,
>
> We have a installation of SMX3.3.1 with CXF BC, CXF SE, SA's, We
> want to
> move to SMX 4 by deploying these existing SA's in SMX4 and then move
> the
> SA's to OSGi Bundles, If we start migrating to OSGi bundles as our
> starting
> step, it is going to take significant time before our system is
> ready to
> test.
>
> So I am looking to how to migrate quickly and then move to OSGi
> bundles. I
> looked at SMX 4 documentation for migrating but all that says is
> deploy the
> SA's in deploy directory. We have stand alone jars that are not part
> of SA's
> and deployed in the lib folder. I am wondering how do I move all this
> configuration(servicemix.conf) to SMX 4.
>
> cxf.xml was used by the CXF BC and CXF SE to initiliaze the port for
> the
> whole bus(CXFBusImp)l, I see that CXF BC is still on 2009.01 version
> in SMX
> 4, so where do I deploy the cxf.xml bus configuration.
>
> thanks for your help
> -gopal
>
>
> Lukasz Dywicki wrote:
>>
>> Hello,
>> Changes that ServiceMix team made in SMX 4 is really big.
>> 1) It depends, because SMX 4 is built on OSGi. In OSGi world class
>> loading
>> are very strict. In SMX 3 the conf directory was classpath element.
>> In
>> SMX4 configuration is no longer classpath element so you have to
>> enable it
>> in own bundle.
>> 2) In SMX 4 the JBI is only one feature from set of provided. If
>> you had
>> defined beans in servicemix.xml you should enable it as services in
>> OSGi
>> bundle. SMX4 offers support for JBI 1.0 but preffered programming
>> is based
>> on OSGi bundles. First of all it allows you to define many different
>> endpoints in one bundle (Maven project) - CXF BC, CXF SE or event
>> embedded
>> Camel.
>> 3) The default broker is on deploy directory.
>> 4) You can add own keystore using -Djavax.net.ssl.keyStore parameter.
>>
>> Best regards,
>> Lukasz Dywicki
>>
>>
>> GNarra wrote:
>>>
>>> Hi All,
>>>
>>> We are evaluating on making the move from SMX3.3.1 to SMX4 and
>>> have a few
>>> questions.
>>>
>>> 1) In SMX 3.3.1, we deployed servicemix/conf/cxf.xml which has the
>>> <httpj:engine-factory><httpj:engine port="0000">, where do you
>>> deploy
>>> cxf.xml in SMX4 configuration?
>>> 2) what is the equivalent of servicemix.xml "jbi" container
>>> configuration?
>>> 3) Where is the DefaultBroker class in smx4?
>>> 4) In SMX4 there is no keystore.jks file,
>>>
>>> any help is greatly appreciated
>>>
>>> thanks
>>> -gopal
>>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Migrating-from-SMX3-to-SMX4-tp26646562p26667505.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

Re: servicemix-quartz endpoints cause ClassNotFoundException

2009-12-07T18:24:37Z

Hi,

The embeded container configuration like
<sm:container id="jbi" embedded="true">
<sm:activationSpecs>
are not supported in smx4 any longer.

If you want to use quartz component in smx4, you may need take a look
at simple example shipped with kit.

Freeman
On 2009-12-8, at 上午4:49, Bill Simms wrote:

> <sm:container id="jbi" embedded="true">
> <sm:activationSpecs>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

Re: org.apache.cxf.interceptor.Fault: Index: 1, Size: 1 using CXF client on SMIX 4.0

2009-12-07T18:21:32Z

Do you use jms transport on the CXF endpoint?
I fixed an error (with the same error message) of camel-cxf recently,
which was caused by the CXF jms transport can't deal with exception
message rightly.

If not, can you tell me what kind of message do you send to CXF client ?

Willem

Max Ferrari wrote:

> Hi list,
> I have managed to reproduce on SMIX 4.0.0 vanilla (camel 1.6.0 and cxf
> 2.1.4) an issue that we are experiencing also on Fuse ESB 4.1.
>
> In one of our bundles we have defined a CXF client with datamode set
> to POJO and MTOM enabled.
>
> Our customer's WSDL (see below) has an implicit header for
> authentication (the header is defined in the wsdl:binding section but
> not in the wsdl:portType).
> We use the maven cxf-codegen-plugin to execute wsdl2java to generate
> client sources.
>
> The problem arises when - from one of our routes - we generate a
> message and send it to the cxf client bean; before it even reaches the
> server we get the following exception and then the exchange is routed
> to the dead letter queue:
>
> 11:52:24,685 | WARN | nerContainer-973 | PhaseInterceptorChain |
> org.apache.cxf.endpoint.ClientImpl 471 | Interceptor has thrown
> exception, unwinding now
> org.apache.cxf.interceptor.Fault: Index: 1, Size: 1
> at org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:119)
> ...
> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at com.intersec.schema.mcms._3.SingleMms_WrapperTypeHelper1.createWrapperObject(Unknown
> Source)
> at org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:103)
> ... 39 more
>
> Of course the com.intersec package has to do with the cxf-generated client code.
>
> Now, I've dug a bit but the only relevant result I could find is a cxf
> issue with out-of-band headers that was fixed in cxf 2.0.3:
> https://issues.apache.org/jira/browse/CXF-1129
>
> Not sure if what I'm seeing in our route is our mistake, a new issue
> with cxf or a regression, however I've tried with the workaround
> suggested in that cxf Jira entry (running the wsdl2java with '-exsh
> true'), unfortunately with no results (we get the same error).
>
> Any pointers anyone?
>
> Relevant excerpts of our source code:
>
> // -----------------------------------------------------------------------CXF
> client definition
>
> <cxf:cxfEndpoint
> id="cxfClientMTOM"
> serviceClass="com.intersec.schema.mcms._3.MCMSPortType"
> address="${cxfclient.serviceURI}">
> <cxf:inInterceptors>
> <ref bean="logInbound"/>
> </cxf:inInterceptors>
> <cxf:outInterceptors>
> <ref bean="logOutbound"/>
> 
> </cxf:outInterceptors>
> <cxf:properties>
> <entry key="dataFormat" value="POJO" />
> <entry key="mtom-enabled" value="true" />
> </cxf:properties>
> </cxf:cxfEndpoint>
>
> // -----------------------------------------------------------------------
> sample WSDL
>
> <?xml version="1.0"?>
>
> <wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:tns="http://schema.intersec.com/mcms/3"
> targetNamespace="http://schema.intersec.com/mcms/3"
> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
> xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
> xmlns:apachesoap="http://xml.apache.org/xml-soap"
> >
> <wsdl:types>
> <xsd:schema targetNamespace="http://schema.intersec.com/mcms/3">
> <xsd:import namespace="http://www.w3.org/2005/05/xmlmime"
> schemaLocation="xmime.xsd" />
> <xsd:complexType name="attachmentArray">
> <xsd:sequence>
> <xsd:element name="attachment" type="tns:attachment"
> minOccurs="0" maxOccurs="unbounded" />
> </xsd:sequence>
> </xsd:complexType>
> <xsd:complexType name="attachment">
> <xsd:sequence>
> <xsd:element minOccurs="0" name="fileName" type="xsd:string" />
> <xsd:element minOccurs="0" name="binaryData"
> type="xmime:base64Binary" />
> </xsd:sequence>
> </xsd:complexType>
>
> <xsd:element name="singleMms">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="oadc" type="xsd:string"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element name="msisdn_to" type="xsd:string"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element name="subject" type="xsd:string"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element name="smil"
> type="xmime:base64Binary" xmime:expectedContentTypes="text/xml"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element name="attachments"
> type="tns:attachmentArray" minOccurs="1" maxOccurs="1"/>
> <xsd:element name="allow_adaptations" type="xsd:boolean"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element name="message_priority" type="xsd:int"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element name="message_expiration" type="xsd:int"
> minOccurs="1" maxOccurs="1"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> <xsd:element name="singleMmsResponse">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="singleMmsReturn" type="xsd:boolean"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> <xsd:element name="callerIdentity">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="login" type="xsd:string" minOccurs="1"
> maxOccurs="1" />
> <xsd:element name="password" type="xsd:string"
> minOccurs="1" maxOccurs="1" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
> </wsdl:types>
> <wsdl:message name="identityHeader">
> <wsdl:part name="request_header" element="tns:callerIdentity"/>
> </wsdl:message>
> <wsdl:message name="singleMmsRequest">
> <wsdl:part name="parameters" element="tns:singleMms"/>
> </wsdl:message>
> <wsdl:message name="singleMmsResponse">
> <wsdl:part name="parameters" element="tns:singleMmsResponse"/>
> </wsdl:message>
> <wsdl:portType name="MCMSPortType">
> <wsdl:operation name="singleMms">
> <wsdl:input message="tns:singleMmsRequest" />
> <wsdl:output message="tns:singleMmsResponse" />
> </wsdl:operation>
> </wsdl:portType>
> <wsdl:binding name="MCMSBinding" type="tns:MCMSPortType">
> <soap:binding style="document"
> transport="http://schemas.xmlsoap.org/soap/http"/>
> <wsdl:operation name="singleMms">
> <soap:operation soapAction="" />
> <wsdl:input>
> <soap:header use="literal" part="request_header"
> message="tns:identityHeader" />
> <soap:body use="literal" />
> </wsdl:input>
> <wsdl:output>
> <soap:body use="literal" />
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
> <wsdl:service name="MCMS">
> <wsdl:port name="MCMSPort" binding="tns:MCMSBinding">
> <soap:address location="http://localhost:8000/soap/"/>
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
>
>
>
> // -----------------------------------------------------------------------Sample
> route code
>
> [...]
>
> .process(new Processor() {
>
> @Override
> public void process(Exchange x) throws Exception {
>
> SingleMms soapSingleMMS = new SingleMms();
> // ... populate the mms fields ...
>
> List<String> params = new LinkedList<String>();
> JAXBContext mcmsJC = JAXBContext.newInstance("com.intersec.schema.mcms._3");
> Marshaller ma = mcmsJC.createMarshaller();
> StringWriter mcmsWriter = new StringWriter();
> ma.marshal(soapSingleMMS, mcmsWriter);
>
> // set in request
> params.add(mcmsWriter.toString());
> Map<String, Object> requestContext = new HashMap<String, Object>();
> requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
> "http://localhost:9080");
>
> // create & add caller identity header
> CallerIdentity identity = new CallerIdentity();
> identity.setLogin("dummy");
> identity.setPassword("dummy");
> List<Header> headers = new ArrayList<Header>();
>
> Header identityHeader = new Header(new
> QName("com.intersec.schema.mcms._3", "callerIdentity"), identity, new
> JAXBDataBinding(CallerIdentity.class));
> headers.add(identityHeader);
> x.getOut().setHeader(Header.HEADER_LIST, headers);
> x.getOut().setBody(params);
> x.getOut().setHeader(Client.REQUEST_CONTEXT , requestContext);
> x.getOut().setHeader(CxfConstants.OPERATION_NAME, "singleMms");
>
> }
> })
>
> // web service request
> .to("cxf:bean:" + getCxfEndpointId())
>
> [...]
>
>
> --
> Max
>

Re: "stax read exception" with cxf-bc & cxf-se

2009-12-07T18:03:53Z

Hi,

As you are using mac, I believe you run into a known issue tracked by
SMXCOMP-600[1], this issue already get fixed and would be in
servicemix-cxf-bc-2009.02 release

[1]https://issues.apache.org/activemq/browse/SMXCOMP-600

Freeman
On 2009-12-8, at 上午12:18, devylon wrote:

>
> i did my tests with soap ui and generated sample requests. what i
> figured out
> is:
>
> when is submit this envelop:
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>
> <soapenv:Body>
> <typ:GetPerson
> xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types">
> <typ:personId>1</typ:personId>
> </typ:GetPerson>
> </soapenv:Body>
> </soapenv:Envelope>
>
> everything is fine, BUT if i submit this envelop:
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types"
>>
> <soapenv:Body>
> <typ:GetPerson >
> <typ:personId>1</typ:personId>
> </typ:GetPerson>
> </soapenv:Body>
> </soapenv:Envelope>
>
> i get the stax exception. i'm little bit confused and couldn't
> explain the
> difference
> to me ?!?
>
>
>
>
> devylon wrote:
>>
>> Hi,
>>
>> I'm testing the cxf-bc and cxf-se components. But unfortunatly i
>> get the
>> following error with the wsdl-first sample:
>>
>> DEBUG - SedaQueue -
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@2e2acb47 dequeued
>> exchange: InOut[
>> id: ID:10.41.20.39-12569e5f07a-4:1
>> status: Error
>> role: consumer
>> interface: {http://servicemix.apache.org/samples/wsdl-first}Person
>> service: {http://servicemix.apache.org/samples/wsdl-
>> first}PersonService
>> endpoint: PersonImplPort
>> operation: {http://servicemix.apache.org/samples/wsdl-
>> first}GetPerson
>> in: <?xml version="1.0" encoding="UTF-8"?>
>> <jbi:message name="GetPersonRequest" type="msg:GetPersonRequest"
>> version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper
>> "
>> xmlns:msg="http://servicemix.apache.org/samples/wsdl-first"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-
>> instance"><jbi:part><typ:GetPerson>
>> <typ:personId>1</typ:personId>
>> </typ:GetPerson></jbi:part></jbi:message>
>> error: org.apache.cxf.interceptor.Fault: stax read exception
>> ]
>> DEBUG - DeliveryChannelImpl - Notifying exchange
>> ID:10.41.20.39-12569e5f07a-4:1(386d346c) in
>> DeliveryChannel{servicemix-cxf-bc} from
>> processInboundSynchronousExchange
>> DEBUG - DeliveryChannelImpl - Notified:
>> ID:10.41.20.39-12569e5f07a-4:1(386d346c) in
>> DeliveryChannel{servicemix-cxf-bc} from sendSync
>> 07.12.2009 17:08:48 org.apache.cxf.phase.PhaseInterceptorChain
>> doIntercept
>> INFO: Interceptor has thrown exception, unwinding now stax read
>> exception
>>
>>
>> My environment is:
>> - OS: OSX 10.6
>> - Java: Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219)
>> Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode)
>> - ServiceMix : 3.3.1
>>
>> I have no clue whats going wrong :(
>>
>> -- devylon
>>
>
> --
> View this message in context: http://old.nabble.com/%22stax-read-exception%22-with-cxf-bc---cxf-se-tp26679548p26679639.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com

servicemix-quartz endpoints cause ClassNotFoundException

2009-12-07T12:49:14Z

Recently any attempts to deploy a service assembly with a Quartz service unit have caused ClassNotFoundExceptions. I have tested this on fresh installs of ServiceMix 4.0.0 (kernel 1.1.0), including the FUSE distribution. The exceptions alternate between the QuartzComponent and QuartzEndpoint classes, depending on the spring configuration file. I have noticed that there is a Jira entry for incompatabilities with jbi and osgi on servicemix components. Is this a symptom of that incompatability? Are there any known ways around this?

javax.jbi.management.DeploymentException: <component-task-result xmlns="http://java.sun.com/xml/ns/jbi/management-message">
<component-name>servicemix-bean</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg><msg-loc-info><loc-token/><loc-message>Could not deploy xbean service unit</loc-message></msg-loc-info></task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<msg-loc-info>
<loc-token />
<loc-message>Configuration problem: Bean class [org.apache.servicemix.quartz.QuartzEndpoint] not found
Offending resource: file [C:\ServiceMix\data\jbi\job-schedule-sa\sus\job-schedule-su\xbean.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: org.apache.servicemix.quartz.QuartzEndpoint in classloader org.apache.xbean.spring.context.FileSystemXmlApplicationContext@1d1775</loc-message>
<stack-trace><![CDATA[org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [org.apache.servicemix.quartz.QuartzEndpoint] not found
Offending resource: file [C:\ServiceMix\data\jbi\job-schedule-sa\sus\job-schedule-su\xbean.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: org.apache.servicemix.quartz.QuartzEndpoint in classloader org.apache.xbean.spring.context.FileSystemXmlApplicationContext@1d1775
at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:288)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:484)
at org.apache.xbean.spring.context.v2c.XBeanBeanDefinitionParserDelegate.parseBeanDefinitionElement(XBeanBeanDefinitionParserDelegate.java:58)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:389)
at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:223)
at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:271)
at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:155)
at org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:49)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1297)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1287)
at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:84)
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507)
at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212)
at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113)
at org.apache.xbean.spring.context.FileSystemXmlApplicationContext.loadBeanDefinitions(FileSystemXmlApplicationContext.java:168)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
at org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:87)
at org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
at org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
at org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:100)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:204)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
at org.apache.servicemix.jbi.deployer.impl.DeploymentService.deploy(DeploymentService.java:95)
at org.apache.servicemix.jbi.deployer.impl.AdminCommandsImpl.deployServiceAssembly(AdminCommandsImpl.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: org.apache.servicemix.quartz.QuartzEndpoint in classloader org.apache.xbean.spring.context.FileSystemXmlApplicationContext@1d1775
at org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:206)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at org.springframework.util.ClassUtils.forName(ClassUtils.java:211)
at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(BeanDefinitionReaderUtils.java:89)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.createBeanDefinition(BeanDefinitionParserDelegate.java:610)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:465)
... 64 more
]]></stack-trace>
</msg-loc-info>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
at org.apache.servicemix.common.ManagementSupport.failure(ManagementSupport.java:46)
at org.apache.servicemix.common.AbstractDeployer.failure(AbstractDeployer.java:43)
at org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:117)
at org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
at org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
at org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:100)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:204)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
at org.apache.servicemix.jbi.deployer.impl.DeploymentService.deploy(DeploymentService.java:95)
at org.apache.servicemix.jbi.deployer.impl.AdminCommandsImpl.deployServiceAssembly(AdminCommandsImpl.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
16:22:04,984 | ERROR | -192.153.129.187 | ServiceAssemblyInstaller | er.impl.ServiceAssemblyInstaller 100 | Error deploying SU job-schedule-su
16:22:04,984 | ERROR | -192.153.129.187 | DeploymentService | .deployer.impl.DeploymentService 101 | Error deploying service assembly
javax.jbi.JBIException: java.lang.Exception: Error deploying SU job-schedule-su
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:101)
at org.apache.servicemix.jbi.deployer.impl.DeploymentService.deploy(DeploymentService.java:95)
at org.apache.servicemix.jbi.deployer.impl.AdminCommandsImpl.deployServiceAssembly(AdminCommandsImpl.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.Exception: Error deploying SU job-schedule-su
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:210)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
... 34 more
Caused by: javax.jbi.management.DeploymentException: <component-task-result xmlns="http://java.sun.com/xml/ns/jbi/management-message">
<component-name>servicemix-bean</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg><msg-loc-info><loc-token/><loc-message>Could not deploy xbean service unit</loc-message></msg-loc-info></task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<msg-loc-info>
<loc-token />
<loc-message>Configuration problem: Bean class [org.apache.servicemix.quartz.QuartzEndpoint] not found
Offending resource: file [C:\ServiceMix\data\jbi\job-schedule-sa\sus\job-schedule-su\xbean.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: org.apache.servicemix.quartz.QuartzEndpoint in classloader org.apache.xbean.spring.context.FileSystemXmlApplicationContext@1d1775</loc-message>
<stack-trace><![CDATA[org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Bean class [org.apache.servicemix.quartz.QuartzEndpoint] not found
Offending resource: file [C:\ServiceMix\data\jbi\job-schedule-sa\sus\job-schedule-su\xbean.xml]
Bean ''; nested exception is java.lang.ClassNotFoundException: org.apache.servicemix.quartz.QuartzEndpoint in classloader org.apache.xbean.spring.context.FileSystemXmlApplicationContext@1d1775
at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:288)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:484)
at org.apache.xbean.spring.context.v2c.XBeanBeanDefinitionParserDelegate.parseBeanDefinitionElement(XBeanBeanDefinitionParserDelegate.java:58)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:389)
at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:223)
at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:271)
at org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:155)
at org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:49)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1297)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1287)
at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:84)
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507)
at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212)
at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113)
at org.apache.xbean.spring.context.FileSystemXmlApplicationContext.loadBeanDefinitions(FileSystemXmlApplicationContext.java:168)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
at org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:87)
at org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
at org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
at org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:100)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:204)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
at org.apache.servicemix.jbi.deployer.impl.DeploymentService.deploy(DeploymentService.java:95)
at org.apache.servicemix.jbi.deployer.impl.AdminCommandsImpl.deployServiceAssembly(AdminCommandsImpl.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: org.apache.servicemix.quartz.QuartzEndpoint in classloader org.apache.xbean.spring.context.FileSystemXmlApplicationContext@1d1775
at org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:206)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at org.springframework.util.ClassUtils.forName(ClassUtils.java:211)
at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(BeanDefinitionReaderUtils.java:89)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.createBeanDefinition(BeanDefinitionParserDelegate.java:610)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:465)
... 64 more
]]></stack-trace>
</msg-loc-info>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
at org.apache.servicemix.common.ManagementSupport.failure(ManagementSupport.java:46)
at org.apache.servicemix.common.AbstractDeployer.failure(AbstractDeployer.java:43)
at org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:117)
at org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
at org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
at org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:100)
at org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:204)
... 35 more

----------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>


<beans xmlns:scripting="http://servicemix.apache.org/quartz/1.0"
xmlns:replaceMe="http://servicemix.apache.org/replaceMe"
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://servicemix.apache.org/quartz/1.0 http://servicemix.apache.org/schema/servicemix-quartz-3.4.0.2-fuse.xsd
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">


<quartz:endpoint service="replaceMe:service" endpoint="endpoint1" targetService="replaceMe:receiver1">
<quartz:trigger>
<quartz:cron cronExpression="0/5 * * * * ?" />
</quartz:trigger>
</quartz:endpoint>


<quartz:endpoint service="replaceMe:service" endpoint="endpoint2" targetService="replaceMe:receiver2">
<quartz:trigger>
<quartz:simple repeatCount="0" repeatInterval="1000" />
</quartz:trigger>
</quartz:endpoint>


<quartz:endpoint service="replaceMe:service" endpoint="endpoint3" targetService="replaceMe:receiver3">
<quartz:jobDetail>
<quartz:jobDetail>
<quartz:jobDataAsMap>
<quartz:property key="xml"><![CDATA[
<hello>world</hello>
]]></quartz:property>
</quartz:jobDataAsMap>
</quartz:jobDetail>
</quartz:jobDetail>

<quartz:triggers>
<quartz:simple repeatCount="0" repeatInterval="1000" />
<quartz:cron cronExpression="0 * 1 * * ?" />
</quartz:triggers>

</quartz:endpoint>

</beans>

org.apache.cxf.interceptor.Fault: Index: 1, Size: 1 using CXF client on SMIX 4.0

2009-12-07T09:50:08Z

Hi list,
I have managed to reproduce on SMIX 4.0.0 vanilla (camel 1.6.0 and cxf
2.1.4) an issue that we are experiencing also on Fuse ESB 4.1.

In one of our bundles we have defined a CXF client with datamode set
to POJO and MTOM enabled.

Our customer's WSDL (see below) has an implicit header for
authentication (the header is defined in the wsdl:binding section but
not in the wsdl:portType).
We use the maven cxf-codegen-plugin to execute wsdl2java to generate
client sources.

The problem arises when - from one of our routes - we generate a
message and send it to the cxf client bean; before it even reaches the
server we get the following exception and then the exchange is routed
to the dead letter queue:

11:52:24,685 | WARN | nerContainer-973 | PhaseInterceptorChain |
org.apache.cxf.endpoint.ClientImpl 471 | Interceptor has thrown
exception, unwinding now
org.apache.cxf.interceptor.Fault: Index: 1, Size: 1
at org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:119)
...
Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at com.intersec.schema.mcms._3.SingleMms_WrapperTypeHelper1.createWrapperObject(Unknown
Source)
at org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:103)
... 39 more

Of course the com.intersec package has to do with the cxf-generated client code.

Now, I've dug a bit but the only relevant result I could find is a cxf
issue with out-of-band headers that was fixed in cxf 2.0.3:
https://issues.apache.org/jira/browse/CXF-1129

Not sure if what I'm seeing in our route is our mistake, a new issue
with cxf or a regression, however I've tried with the workaround
suggested in that cxf Jira entry (running the wsdl2java with '-exsh
true'), unfortunately with no results (we get the same error).

Any pointers anyone?

Relevant excerpts of our source code:

// -----------------------------------------------------------------------CXF
client definition

<cxf:cxfEndpoint
id="cxfClientMTOM"
serviceClass="com.intersec.schema.mcms._3.MCMSPortType"
address="${cxfclient.serviceURI}">
<cxf:inInterceptors>
<ref bean="logInbound"/>
</cxf:inInterceptors>
<cxf:outInterceptors>
<ref bean="logOutbound"/>

</cxf:outInterceptors>
<cxf:properties>
<entry key="dataFormat" value="POJO" />
<entry key="mtom-enabled" value="true" />
</cxf:properties>
</cxf:cxfEndpoint>

// -----------------------------------------------------------------------
sample WSDL

<?xml version="1.0"?>

<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://schema.intersec.com/mcms/3"
targetNamespace="http://schema.intersec.com/mcms/3"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
>
<wsdl:types>
<xsd:schema targetNamespace="http://schema.intersec.com/mcms/3">
<xsd:import namespace="http://www.w3.org/2005/05/xmlmime"
schemaLocation="xmime.xsd" />
<xsd:complexType name="attachmentArray">
<xsd:sequence>
<xsd:element name="attachment" type="tns:attachment"
minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="attachment">
<xsd:sequence>
<xsd:element minOccurs="0" name="fileName" type="xsd:string" />
<xsd:element minOccurs="0" name="binaryData"
type="xmime:base64Binary" />
</xsd:sequence>
</xsd:complexType>

<xsd:element name="singleMms">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="oadc" type="xsd:string"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="msisdn_to" type="xsd:string"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="subject" type="xsd:string"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="smil"
type="xmime:base64Binary" xmime:expectedContentTypes="text/xml"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="attachments"
type="tns:attachmentArray" minOccurs="1" maxOccurs="1"/>
<xsd:element name="allow_adaptations" type="xsd:boolean"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="message_priority" type="xsd:int"
minOccurs="1" maxOccurs="1"/>
<xsd:element name="message_expiration" type="xsd:int"
minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="singleMmsResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="singleMmsReturn" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="callerIdentity">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="login" type="xsd:string" minOccurs="1"
maxOccurs="1" />
<xsd:element name="password" type="xsd:string"
minOccurs="1" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="identityHeader">
<wsdl:part name="request_header" element="tns:callerIdentity"/>
</wsdl:message>
<wsdl:message name="singleMmsRequest">
<wsdl:part name="parameters" element="tns:singleMms"/>
</wsdl:message>
<wsdl:message name="singleMmsResponse">
<wsdl:part name="parameters" element="tns:singleMmsResponse"/>
</wsdl:message>
<wsdl:portType name="MCMSPortType">
<wsdl:operation name="singleMms">
<wsdl:input message="tns:singleMmsRequest" />
<wsdl:output message="tns:singleMmsResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MCMSBinding" type="tns:MCMSPortType">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="singleMms">
<soap:operation soapAction="" />
<wsdl:input>
<soap:header use="literal" part="request_header"
message="tns:identityHeader" />
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="MCMS">
<wsdl:port name="MCMSPort" binding="tns:MCMSBinding">
<soap:address location="http://localhost:8000/soap/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

// -----------------------------------------------------------------------Sample
route code

[...]

.process(new Processor() {

@Override
public void process(Exchange x) throws Exception {

SingleMms soapSingleMMS = new SingleMms();
// ... populate the mms fields ...

List<String> params = new LinkedList<String>();
JAXBContext mcmsJC = JAXBContext.newInstance("com.intersec.schema.mcms._3");
Marshaller ma = mcmsJC.createMarshaller();
StringWriter mcmsWriter = new StringWriter();
ma.marshal(soapSingleMMS, mcmsWriter);

// set in request
params.add(mcmsWriter.toString());
Map<String, Object> requestContext = new HashMap<String, Object>();
requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
"http://localhost:9080");

// create & add caller identity header
CallerIdentity identity = new CallerIdentity();
identity.setLogin("dummy");
identity.setPassword("dummy");
List<Header> headers = new ArrayList<Header>();

Header identityHeader = new Header(new
QName("com.intersec.schema.mcms._3", "callerIdentity"), identity, new
JAXBDataBinding(CallerIdentity.class));
headers.add(identityHeader);
x.getOut().setHeader(Header.HEADER_LIST, headers);
x.getOut().setBody(params);
x.getOut().setHeader(Client.REQUEST_CONTEXT , requestContext);
x.getOut().setHeader(CxfConstants.OPERATION_NAME, "singleMms");

}
})

// web service request
.to("cxf:bean:" + getCxfEndpointId())

[...]

--
Max

Sending request to a remote webservice over http

2009-12-07T08:32:01Z

I have the ffg as the content of my camelcontext.xml and I am trying to send a request to a remote service.

<osgi:camelContext xmlns="http://camel.apache.org/schema/spring" trace="true">
<route>
<from uri="nmr:nauRoute"/>
<to uri="jbi:endpoint:http://tempuri.org/Service/ServiceSoap?mep=in-out&operation={http://tempuri.org/}GetDataInterswitch" />
</route>

Here is the config in my jbi xbean.xml

<cxfbc:provider wsdl="classpath:Service.wsdl"
locationURI="http://remoteip.com/Service.asmx"
service="nau:Service"
endpoint="ServiceSoap"
interfaceName="ServiceSoap"/>

<bean class="org.apache.servicemix.common.osgi.EndpointExporter" />

but when I send a request to this service this is all I see in my log:

17:24:50,316 | INFO | auRoute-thread-1 | ManagementEndpointRegistry | ement.ManagementEndpointRegistry 56 | Registering endpoint: org.apache.servicemix.nmr.core.InternalEndpointWrapper@e9541f4c with properties {objectClass=[Ljava.lang.String;@1812b51, jbi.external=true, javax.jbi.servicedesc.ServiceEndpoint=org.apache.servicemix.common.ExternalEndpoint@142f67d, service.id=282, SERVICE_NAME={http://camel.apache.org/schema/jbi}provider, NAME={http://camel.apache.org/schema/jbi}provider:ID:41.219.206.86-12569a4fe1a-4:0, UNTARGETABLE=true, ENDPOINT_NAME=ID:41.219.206.86-12569a4fe1a-4:0}

pls kindly advise.

Re: "stax read exception" with cxf-bc & cxf-se

2009-12-07T08:18:43Z

i did my tests with soap ui and generated sample requests. what i figured out is:

when is submit this envelop:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>
<soapenv:Body>
<typ:GetPerson xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types">
<typ:personId>1</typ:personId>
</typ:GetPerson>
</soapenv:Body>
</soapenv:Envelope>

everything is fine, BUT if i submit this envelop:

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://servicemix.apache.org/samples/wsdl-first/types"
>
<soapenv:Body>
<typ:GetPerson >
<typ:personId>1</typ:personId>
</typ:GetPerson>
</soapenv:Body>
</soapenv:Envelope>

i get the stax exception. i'm little bit confused and couldn't explain the difference
to me ?!?

devylon wrote:

Hi,

I'm testing the cxf-bc and cxf-se components. But unfortunatly i get the following error with the wsdl-first sample:

DEBUG - SedaQueue - org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@2e2acb47 dequeued exchange: InOut[
id: ID:10.41.20.39-12569e5f07a-4:1
status: Error
role: consumer
interface: {http://servicemix.apache.org/samples/wsdl-first}Person
service: {http://servicemix.apache.org/samples/wsdl-first}PersonService
endpoint: PersonImplPort
operation: {http://servicemix.apache.org/samples/wsdl-first}GetPerson
in: <?xml version="1.0" encoding="UTF-8"?>
<jbi:message name="GetPersonRequest" type="msg:GetPersonRequest" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" xmlns:msg="http://servicemix.apache.org/samples/wsdl-first" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><jbi:part><typ:GetPerson>
<typ:personId>1</typ:personId>
</typ:GetPerson></jbi:part></jbi:message>
error: org.apache.cxf.interceptor.Fault: stax read exception
]
DEBUG - DeliveryChannelImpl - Notifying exchange ID:10.41.20.39-12569e5f07a-4:1(386d346c) in DeliveryChannel{servicemix-cxf-bc} from processInboundSynchronousExchange
DEBUG - DeliveryChannelImpl - Notified: ID:10.41.20.39-12569e5f07a-4:1(386d346c) in DeliveryChannel{servicemix-cxf-bc} from sendSync
07.12.2009 17:08:48 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now stax read exception

My environment is:
- OS: OSX 10.6
- Java: Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219)
Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode)
- ServiceMix : 3.3.1

I have no clue whats going wrong :(

-- devylon

"stax read exception" with cxf-bc & cxf-se

2009-12-07T08:12:23Z

Hi,

I'm testing the cxf-bc and cxf-se components. But unfortunatly i get the following error with the wsdl-first sample:

DEBUG - SedaQueue - org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@2e2acb47 dequeued exchange: InOut[
id: ID:10.41.20.39-12569e5f07a-4:1
status: Error
role: consumer
interface: {http://servicemix.apache.org/samples/wsdl-first}Person
service: {http://servicemix.apache.org/samples/wsdl-first}PersonService
endpoint: PersonImplPort
operation: {http://servicemix.apache.org/samples/wsdl-first}GetPerson
in: <?xml version="1.0" encoding="UTF-8"?>
<jbi:message name="GetPersonRequest" type="msg:GetPersonRequest" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper" xmlns:msg="http://servicemix.apache.org/samples/wsdl-first" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><jbi:part><typ:GetPerson>
<typ:personId>1</typ:personId>
</typ:GetPerson></jbi:part></jbi:message>
error: org.apache.cxf.interceptor.Fault: stax read exception
]
DEBUG - DeliveryChannelImpl - Notifying exchange ID:10.41.20.39-12569e5f07a-4:1(386d346c) in DeliveryChannel{servicemix-cxf-bc} from processInboundSynchronousExchange
DEBUG - DeliveryChannelImpl - Notified: ID:10.41.20.39-12569e5f07a-4:1(386d346c) in DeliveryChannel{servicemix-cxf-bc} from sendSync
07.12.2009 17:08:48 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now stax read exception

My environment is:
- OS: OSX 10.6
- Java: Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219)
Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode)
- ServiceMix : 3.3.1

I have no clue whats going wrong :(

-- devylon

Re: Servicemix-bean send messages

2009-12-07T05:49:58Z

Hi,

My problem is, that I want to send a message from the Camel timer to my ListenerBean. Routed by Camel. From my ListenerBean I want to send another message to my second bean (MyBean). I would like to configure this route also in Camel. When I use the following configuration in Camel I get an exception. I can send you the log file if it helps.

How can I configure the "to(...)" and "from(...)" routes in Camel?

public class MyRouteBuilder extends RouteBuilder {

public void configure() {

from("timer://tutorial?fixedRate=true&delay=3000&period=10000")
.setBody(constant("<message>SRQ</message>"))
.to("jbi:endpoint:urn:org:apache:servicemix:example:bean:jms:provider");

from("jbi:endpoint:urn:org:apache:servicemix:example:bean:jms:consumer")
.to("jbi:endpoint:org:apache:servicemix:example:bean:bean:bean1");

from("jbi:endpoint:org:apache:servicemix:example:bean:bean:bean1")
.to("jbi:endpoint:org:apache:servicemix:example:bean2:bean:bean2");
}
}

Many thanks in advance, best regards

Michael Preuß

Gert Vanthienen wrote:

Michael,

Everytime you start route with from("jbi:..."), you get a new endpoint
you can use to send exchanges to. Your ListenerBean already has the
necessary code to send to an endpoint with service name
{org:apache:servicemix:example:bean2}bean. To create this endpoint
from a Camel route, you would have to create a route that starts with
from('jbi:service:org:apache:servicemix:example:bean2:bean")...

If you want to create a route that sits between the existing
ListenerBean and the bean2 endpoint, you have to add another endpoint
in the middle. E.g. you camel route could look like:
from('jbi:endpoint:urn:test:service:endpoint").to("jbi:service:org:apache:servicemix:example:bean2:bean");

The code in your ListenerBean would then look like this:
InOnly sendExchange = ...
sendExchange.setService(new QName("urn:test", "service");

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/

2009/12/3 Michael-P. <Michael.Preuss@ses-astra.com>:
>
> Hi again,
>
> I solved the problem, but not in my preferred way.
> At the moment I use the Camel RouteBuilder (Code:
> http://old.nabble.com/file/p26628850/MyRouteBuilder.java MyRouteBuilder.java
> ) to send a message from the Camel timer to a JMS Queue and from there to
> one of my servicemix-bean components.
> In the onMessageExchange method I create another Exchange and send it to a
> second servicemix-bean component (Code:
> http://old.nabble.com/file/p26628850/ListenerBean.java ListenerBean.java ).
> The second bean just prints out the message (Code:
> http://old.nabble.com/file/p26628850/MyBean.java MyBean.java ).
>
> This works but it would be nice if I would configure the route for the
> message in the Camel RouteBuilder. Unfortunately I didn't find an example
> which shows me the way to do it.
>
> I would like to have:
>
> public void configure(){
>
> ...
>
> from(bean1) <-- What should be typed in here (The URI of
> bean1 is wrong)
> .to(URI of bean2);
>
> }
>
> Does anybody know how to do it?
>
> Thanks in advance, best regards
>
> Michael Preuß
>
>
> Michael-P. wrote:
>>
>> Hi,
>>
>> you're right about the endpoints being the same and I want to start a new
>> MessageExchange from within my bean.
>> I want to send a message from the servicemix-bean to another component (In
>> my example to the camel logging service). I guess the problem is to
>> configure the route in the Camel RouteBuilder from my bean to the camel
>> logging service. Forget all my code and explanations, what do I have to
>> use (URI) in the from definition in the Camel RouteBuilder when I want to
>> route a message exchange from my servicemix-bean to wherever?
>>
>> Additionally have you an example which showes the servicemix-bean code to
>> send a message out? I found this page:
>> http://servicemix.apache.org/client-api.html, but the client API link
>> leads to a completely different page and I don't know how I have to create
>> the "client" object (where can I get the "context" object?).
>>
>>
>> Gert Vanthienen wrote:
>>>
>>> Michael,
>>>
>>> First of all, sorry it took me so long to get back to you.
>>>
>>> After taking another look at this, I think I'm beginning to see where
>>> the problem is. I'm guessing you have a servicemix-bean endpoint
>>> that's called {org.apache.servicemix.bean}bean and you want to log
>>> everything that's going to that endpoint, right?
>>>
>>> Now, whever you start to a Camel route with from("jbi:..."), the
>>> endpoint referred to in the from will itself become an endpoint on the
>>> NMR. So, by doing this, you get a duplicate name (one for the
>>> servicemix-bean endpoint and another for the from(jbi:).
>>>
>>> If you just want to log the message that is going to/from the bean
>>> endpoint, you can alter the route just before that
>>> from("jbi:endpoint:urn:org:apache:servicemix:example:bean:jms:consumer")
>>> .to("log:before-bean)
>>> .to("jbi:endpoint:org:apache:servicemix:example:bean:bean:endpoint")
>>> .to("log:after-bean);
>>>
>>> If, on the other hand, you want to start a new MessageExchange from
>>> within the bean and send that to the Camel route with the log:
>>> endpoint, you have to make sure the name of that endpoint is different
>>> than the name of your bean endpoint itself. Upon sending the exchange
>>> to the log route, you can set the target service to be that you
>>> specified in the from("jbi:...") for the log route.
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>> Blog: http://gertvanthienen.blogspot.com/
>>>
>>>
>>>
>>> 2009/11/26 Michael-P. <Michael.Preuss@ses-astra.com>:
>>>>
>>>> Hello
>>>>
>>>> Many thanks for your tips. For me all attached files are available when
>>>> I
>>>> click on the links. :confused:
>>>>
>>>> I deleted all entries in the data directory and added the if ACTIVE
>>>> check,
>>>> but that solved not the problem.
>>>>
>>>> I found that the error occurs when try to configure a route in the Camel
>>>> RouteBuilder from the servicemix-bean to the log:XXX service.
>>>>
>>>> public void configure() {
>>>>
>>>> from("timer://tutorial?fixedRate=true&delay=3000&period=10000")
>>>> .setBody(constant("<message>SRQ</message>"))
>>>>
>>>> .to("jbi:endpoint:urn:org:apache:servicemix:example:bean:jms:provider");
>>>>
>>>>
>>>> from("jbi:endpoint:urn:org:apache:servicemix:example:bean:jms:consumer")
>>>>
>>>> .to("jbi:endpoint:org:apache:servicemix:example:bean:bean:endpoint");
>>>>
>>>>
>>>> from("jbi:endpoint:org:apache:servicemix:example:bean:bean:endpoint")
>>>> .to("log:beanExample");
>>>> }
>>>>
>>>> Did I here a mistake? I'm wondering to use an endpoint in the from
>>>> definition but I find no example to configure something more in the
>>>> servicemix-bean xbean.xml file.
>>>>
>>>> Again, many thanks in advance!
>>>>
>>>>
>>>> Best regards
>>>>
>>>> Michael Preuß
>>>>
>>>>
>>>> Gert Vanthienen wrote:
>>>>>
>>>>> L.S.,
>>>>>
>>>>> The exception you posted in the mailing list indicates that two
>>>>> endpoints are being configured with the same name. I haven't found
>>>>> the duplicate name in you own configuration at first glance (some of
>>>>> the links you posted seem to be no longer available), so it might just
>>>>> be a consequence of a failed deployment. Could you try stopping
>>>>> servicemix, deleting the entire data directory and then restart the
>>>>> ESB to see if you get a clean deploy then?
>>>>>
>>>>> Now, at runtime, there's a problem with your ListenerBean. The
>>>>> onMessageExchange method will be used to handle the first incoming
>>>>> exchange, but it will also get invoked whenever the DONE
>>>>> MessageExchange you're sending comes back. Your code will set the
>>>>> DONE status on that exchange again, which will cause exceptions. You
>>>>> probably want to add a check for if (exchange.getStatus() ==
>>>>> ExchangeStatus.ACTIVE) before handling the exchange.
>>>>>
>>>>> Another option could be to add the bean to the Camel SU. Since you're
>>>>> already using Camel in your route, it might be easier to use Camel's
>>>>> excellent http://camel.apache.org/bean-integration.html instead of
>>>>> dealing with the JBI MessageExchanges directory from a
>>>>> servicemix-bean.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Gert Vanthienen
>>>>> ------------------------
>>>>> Open Source SOA: http://fusesource.com
>>>>> Blog: http://gertvanthienen.blogspot.com/
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Servicemix-bean-send-messages-tp26525328p26531243.html
>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>> -----
>>> ---
>>> Gert Vanthienen
>>> http://gertvanthienen.blogspot.com
>>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Servicemix-bean-send-messages-tp26525328p26628850.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>

-----
---
Gert Vanthienen
http://gertvanthienen.blogspot.com

Re: Migrating from SMX3 to SMX4

2009-12-06T10:22:18Z

Lukasz,

We have a installation of SMX3.3.1 with CXF BC, CXF SE, SA's, We want to move to SMX 4 by deploying these existing SA's in SMX4 and then move the SA's to OSGi Bundles, If we start migrating to OSGi bundles as our starting step, it is going to take significant time before our system is ready to test.

So I am looking to how to migrate quickly and then move to OSGi bundles. I looked at SMX 4 documentation for migrating but all that says is deploy the SA's in deploy directory. We have stand alone jars that are not part of SA's and deployed in the lib folder. I am wondering how do I move all this configuration(servicemix.conf) to SMX 4.

cxf.xml was used by the CXF BC and CXF SE to initiliaze the port for the whole bus(CXFBusImp)l, I see that CXF BC is still on 2009.01 version in SMX 4, so where do I deploy the cxf.xml bus configuration.

thanks for your help
-gopal

Hello,
Changes that ServiceMix team made in SMX 4 is really big.
1) It depends, because SMX 4 is built on OSGi. In OSGi world class loading are very strict. In SMX 3 the conf directory was classpath element. In SMX4 configuration is no longer classpath element so you have to enable it in own bundle.
2) In SMX 4 the JBI is only one feature from set of provided. If you had defined beans in servicemix.xml you should enable it as services in OSGi bundle. SMX4 offers support for JBI 1.0 but preffered programming is based on OSGi bundles. First of all it allows you to define many different endpoints in one bundle (Maven project) - CXF BC, CXF SE or event embedded Camel.
3) The default broker is on deploy directory.
4) You can add own keystore using -Djavax.net.ssl.keyStore parameter.

Best regards,
Lukasz Dywicki

GNarra wrote:

Hi All,

We are evaluating on making the move from SMX3.3.1 to SMX4 and have a few questions.

1) In SMX 3.3.1, we deployed servicemix/conf/cxf.xml which has the <httpj:engine-factory><httpj:engine port="0000">, where do you deploy cxf.xml in SMX4 configuration?
2) what is the equivalent of servicemix.xml "jbi" container configuration?
3) Where is the DefaultBroker class in smx4?
4) In SMX4 there is no keystore.jks file,

any help is greatly appreciated

thanks
-gopal

Re: Migrating from SMX3 to SMX4

2009-12-06T06:23:22Z

Hello,
Changes that ServiceMix team made in SMX 4 is really big.
1) It depends, because SMX 4 is built on OSGi. In OSGi world class loading are very strict. In SMX 3 the conf directory was classpath element. In SMX4 configuration is no longer classpath element so you have to enable it in own bundle.
2) In SMX 4 the JBI is only one feature from set of provided. If you had defined beans in servicemix.xml you should enable it as services in OSGi bundle. SMX4 offers support for JBI 1.0 but preffered programming is based on OSGi bundles. First of all it allows you to define many different endpoints in one bundle (Maven project) - CXF BC, CXF SE or event embedded Camel.
3) The default broker is on deploy directory.
4) You can add own keystore using -Djavax.net.ssl.keyStore parameter.

Best regards,
Lukasz Dywicki

GNarra wrote:

Hi All,

We are evaluating on making the move from SMX3.3.1 to SMX4 and have a few questions.

1) In SMX 3.3.1, we deployed servicemix/conf/cxf.xml which has the <httpj:engine-factory><httpj:engine port="0000">, where do you deploy cxf.xml in SMX4 configuration?
2) what is the equivalent of servicemix.xml "jbi" container configuration?
3) Where is the DefaultBroker class in smx4?
4) In SMX4 there is no keystore.jks file,

any help is greatly appreciated

thanks
-gopal

Deploying a configured MINA socket endpoint

2009-12-05T08:59:42Z

Hi all,

I tried to deploy a configured MINA endpoint using the following bean description in the Camel configuration file.

.....



<bean id="myMinaFactory" class="org.apache.camel.component.mina.MinaComponent">
<constructor-arg index="0" ref="camelContext" />
</bean>
<bean id="myMinaEndpoint" factory-bean="myMinaFactory" factory-method="createEndpoint">
<constructor-arg index="0" ref="myMinaConfig" />
</bean>
<bean id="myMinaConfig" class="org.apache.camel.component.mina.MinaConfiguration">
<property name="protocol" value="tcp" />
<property name="host" value="localhost" />
<property name="port" value="10023" />
<property name="sync" value="true" />
<property name="minaLogger" value="true" />
</bean>



<camelContext id="camelContext"
xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="bean:myMinaEndpoint" />
<to uri="bean:myBean?methodName=doSomething" />
<to uri="file:/home/paul/Desktop/output.txt" />
</route>
</camelContext>

This configuration file is actually provided in one of the Camel tutorials and it seems to work if used outside ServiceMix.

However when I deploy it in ServiceMix I get the following error message in my log:

WARN - ScheduledPollConsumer - An exception occured while polling: Endpoint[bean:myMinaEndpoint]: endpointUri is not specified and org.apache.camel.component.mina.MinaEndpoint does not implement createEndpointUri() to create a default value

Any help would be greatly appreciated.

Thanks and regards,
Paul

Migrating from SMX3 to SMX4

2009-12-04T15:15:27Z

Hi All,

We are evaluating on making the move from SMX3.3.1 to SMX4 and have a few questions.

1) In SMX 3.3.1, we deployed servicemix/conf/cxf.xml which has the <httpj:engine-factory><httpj:engine port="0000">, where do you deploy cxf.xml in SMX4 configuration?
2) what is the equivalent of servicemix.xml "jbi" container configuration?
3) Where is the DefaultBroker class in smx4?
4) In SMX4 there is no keystore.jks file,

any help is greatly appreciated

thanks
-gopal

CXF 2.3/Camel 2.0/OSGi: As anyone ever get a sample to work with these versions?

2009-12-04T03:02:35Z

I have seen samples that came with Servicemix 4.x, I upgraded camel to version 2.0 (Which I needed to do) and I have not been able to get the cxf-camel-nmr sample to work.

The problems comes mostly as a result of dependency error, the last one being not able to upgrade CXF SE/BC because servicemix-common will not upgrade because it has dependency issues with org.osgi.framework
[org.osgi.framework.BundleException: Unresolved constraint in bundle 185: package; (&(package=org.osgi.framework)(version>=1.5.0))]