Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2431C10898 for ; Thu, 12 Sep 2013 06:30:28 +0000 (UTC) Received: (qmail 91844 invoked by uid 500); 12 Sep 2013 06:30:27 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 91818 invoked by uid 500); 12 Sep 2013 06:30:27 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Delivered-To: moderator for users@camel.apache.org Received: (qmail 95487 invoked by uid 99); 12 Sep 2013 02:01:06 -0000 X-ASF-Spam-Status: No, hits=4.5 required=5.0 tests=HTML_MESSAGE,SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of contactreji@gmail.com does not designate 216.139.236.26 as permitted sender) Date: Wed, 11 Sep 2013 19:00:39 -0700 (PDT) From: contactreji To: users@camel.apache.org Message-ID: In-Reply-To: References: <1378902475266-5739142.post@n5.nabble.com> Subject: Re: CFX to Queue : io.serializationException MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_268527_18540310.1378951239124" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_268527_18540310.1378951239124 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Christian Thank you so much. Could you help me with configuring the marshaller. The class is something called DTPowerconsumption which has the schema for the pojo. I see in Camel jaxb component that there are parameters called contextPath and namespaces. What should I enter for those values? Reji On Thursday, September 12, 2013, Christian Mueller [via Camel] < ml-node+s465427n5739188h7@n5.nabble.com> wrote: > Yes, use the camel-jaxb dataformat to marshal your payload into a > byte[]/String before sending it to the queue. After dequeuing it, unmarshal > it to your Java pojo. > > Best, > Christian > ----------------- > > Software Integration Specialist > > Apache Camel committer: https://camel.apache.org/team > V.P. Apache Camel: https://www.apache.org/foundation/ > Apache Member: https://www.apache.org/foundation/members.html > > https://www.linkedin.com/pub/christian-mueller/11/551/642 > > > On Wed, Sep 11, 2013 at 2:27 PM, contactreji <[hidden email]> wrote: > >> Hi Guys >> >> I have a problem in the following route. >> >> * >> >> >> <bean >> ref="myBean"/> >> >> >> >> * >> >> The data from cxf:bean:PowerConsumptionEndpoint is not able to queue up in >> the message broker. It gives io.serialization exception. >> >> I tried modifying as cxf:bean:PowerConsumptionEndpoint?dataFormat=MESSAGE >> which indeed solved the issue. >> >> But I have another route picking the same data from the queue as >> >> * >> >> >> >> >> <bean >> ref="myBean"/> >> >> >> * >> >> Here the SAPClientInvoker is a Java class which makes a webservice call to >> SAP PI system. We have followed the WSDL approach and we have a schema >> class >> DTPowerConsumption whose object is used to invoke Webservice call to SAP >> PI. >> * >> This is part of SAPClientInvoker Class >> DTPowerConsumption PC=exchng.getIn().getBody(DTPowerConsumption.class); >> LOGGER.info("\n Data received for Energy Consumption from >> MES \n"); >> LOGGER.info("\n Sending Request from MES to PI for Energy >> Consumption >> \n"); >> >> try { >> LOGGER.info("before invoking"); >> sapService.siID59PowerconsumptionAsyncOut(PC); >> LOGGER.info("Response from PI for Energy >> Consumption"); >> exchng.getOut().setBody("Response from PI Energy >> for consumption"); >> >> * >> Now i assume that dataFormat=MESSAGE parameter is fiddling with the >> original >> compatible data coming to fuse endpoint and hencethe SAPClientInvoker >> webservice call is not able to maintain the perfect call to SAP PI. and SAP >> PI ends up sending HTTP 500 error code . >> >> >> Can anyone suggest me how to store the data on route 1 without really >> fiddling with the message formats without serialization exceptions? >> >> Or can I use a marshaller before storing it into the Queue and unmarshaller >> after fetching it from the queue before calling SAPClinetInvoker? >> >> If so can I use Camel component >> >> * >> > contextPath="org.apache.camel.example" >> partClass="org.apache.camel.example.PurchaseOrder" >> fragment="true" >> partNamespace="{http://example.camel.org/apache}po" /> >> >> >> >> > contextPath="org.apache.camel.example" >> partClass="org.apache.camel.example.Partial" /> >> >> * >> What is the value to be entered for contextPath and partNamespace?? I am >> confused with that. >> If there is a alternate way to handle this, please help me with it.. >> >> Reji >> >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/CFX-to-Queue-io-serializationException-tp5739142.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > > ________________________________ > If you reply to this email, your message will be added to the discussion below: > http://camel.465427.n5.nabble.com/CXF-to-Apache-ActiveMQ-Queue-io-serializationException-tp5739142p5739188.html > To unsubscribe from CXF to Apache ActiveMQ Queue : io.serializationException, click here. > NAML -- View this message in context: http://camel.465427.n5.nabble.com/CXF-to-Apache-ActiveMQ-Queue-io-serializationException-tp5739142p5739195.html Sent from the Camel - Users mailing list archive at Nabble.com. ------=_Part_268527_18540310.1378951239124--