Unfortunately, the attached java and composite files are removed by the mailing 
list. The best way is to attach them in a JIRA. I appreciate your patience. 

Thanks,
Raymond


From: Sandeep Raman 
Sent: Wednesday, March 26, 2008 1:57 AM
To: [email protected] 
Subject: Fw: Error while Invoking Service



----- Forwarded by Sandeep Raman/BLR/TCS on 03/26/2008 02:27 PM ----- 
      Sandeep Raman/BLR/TCS 
      03/26/2008 02:24 PM 
     To Raymond Feng" <[EMAIL PROTECTED]>  
            cc  
            Subject Re: Error while Invoking Service 

            

     


Hi, 

My wsdl is as follows: 

  <?xml version="1.0" encoding="UTF-8" ?> 
- <wsdl:definitions targetNamespace="http://eai"; 
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:ns0="http://eai"; 
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; 
xmlns:ns1="http://org.apache.axis2/xsd"; 
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> 
- <wsdl:types> 
- <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" 
targetNamespace="http://eai"; xmlns:ns="http://eai";> 
- <xs:element name="Compose"> 
- <xs:complexType> 
- <xs:sequence> 
  <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string" /> 
  </xs:sequence> 
  </xs:complexType> 
  </xs:element> 
- <xs:element name="ComposeResponse"> 
- <xs:complexType> 
- <xs:sequence> 
  <xs:element minOccurs="0" name="return" nillable="true" type="xs:string" /> 
  </xs:sequence> 
  </xs:complexType> 
  </xs:element> 
  </xs:schema> 
  </wsdl:types> 
- <wsdl:message name="ComposeResponse"> 
  <wsdl:part name="parameters" element="ns0:ComposeResponse" /> 
  </wsdl:message> 
- <wsdl:message name="ComposeRequest"> 
  <wsdl:part name="parameters" element="ns0:Compose" /> 
  </wsdl:message> 
- <wsdl:portType name="ComposerPortType"> 
- <wsdl:operation name="Compose"> 
  <wsdl:input message="ns0:ComposeRequest" wsaw:Action="urn:Compose" /> 
  <wsdl:output message="ns0:ComposeResponse" wsaw:Action="urn:ComposeResponse" 
/> 
  </wsdl:operation> 
  </wsdl:portType> 
- <wsdl:binding name="ComposerSOAP11Binding" type="ns0:ComposerPortType"> 
  <soap:binding style="document" 
transport="http://schemas.xmlsoap.org/soap/http"; /> 
- <wsdl:operation name="Compose"> 
  <soap:operation soapAction="urn:Compose" style="document" /> 
- <wsdl:input> 
  <soap:body use="literal" /> 
  </wsdl:input> 
- <wsdl:output> 
  <soap:body use="literal" /> 
  </wsdl:output> 
  </wsdl:operation> 
  </wsdl:binding> 
- <wsdl:binding name="ComposerHttpBinding" type="ns0:ComposerPortType"> 
  <http:binding verb="POST" /> 
- <wsdl:operation name="Compose"> 
  <http:operation location="Composer/Compose" /> 
- <wsdl:input> 
  <mime:content part="Compose" type="text/xml" /> 
  </wsdl:input> 
- <wsdl:output> 
  <mime:content part="Compose" type="text/xml" /> 
  </wsdl:output> 
  </wsdl:operation> 
  </wsdl:binding> 
- <wsdl:service name="Composer"> 
- <wsdl:port name="ComposerSOAP11port_http" 
binding="ns0:ComposerSOAP11Binding"> 
  <soap:address location="http://172.19.103.213:8080/ComposerService"; /> 
  </wsdl:port> 
- <wsdl:port name="ComposerHttpport" binding="ns0:ComposerHttpBinding"> 
  <http:address location="http://172.19.103.213:8080/ComposerService"; /> 
  </wsdl:port> 
  </wsdl:service> 
  </wsdl:definitions> 


The composite files: 




The java code: 



Can you have a look 
Meanwhile ,I wil raise a JIRA. 

Regards 
Sandeep. 


Hi, Sandeep.

Thank you for reporting the problem. But we need more information such as 
the WSDL, the composite file and the java code to diagnose. Would you please 
open a JIRA at http://issues.apache.org/jira/browse/TUSCANY? It would be 
very helpful if you can attach your test case in the JIRA so that we can 
troubleshoot the issue.

Thanks,
Raymond
--------------------------------------------------
From: "Sandeep Raman" <[EMAIL PROTECTED]>
Sent: Monday, March 24, 2008 9:31 PM
To: <[email protected]>
Subject: Error while Invoking Service

> I have a service running accepting a string as input , it has
> implementation in a java class. When i invoke the wsdl with a SOAP message
> i get error as following, what may be the reason for this:
>
> Mar 25, 2008 9:50:43 AM
> org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
> problem
> WARNING: Duplicate service name: ComposerComponent/Composer
> Mar 25, 2008 9:50:56 AM org.apache.tuscany.sca.http.jetty.JettyServer
> addServletMapping
> INFO: Added Servlet mapping:
> http://01hw113905:8080/LOSComposite/LOSComposerService
> Mar 25, 2008 9:55:40 AM
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver
> invokeBusinessLogic
> SEVERE: java.lang.ClassCastException: java.lang.String
> org.osoa.sca.ServiceRuntimeException: java.lang.ClassCastException:
> java.lang.String
>        at
> org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(
> RuntimeWireInvoker.java:122)
>        at
> org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(
> RuntimeWireInvoker.java:88)
>        at
> org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(
> RuntimeWireInvoker.java:82)
>        at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(
> RuntimeWireImpl.java:126)
>        at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(
> Axis2ServiceProvider.java:589)
>        at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(
> Axis2ServiceInOutSyncMessageReceiver.java:59)
>        at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(
> AbstractInOutSyncMessageReceiver.java:42)
>        at org.apache.axis2.receivers.AbstractMessageReceiver.receive(
> AbstractMessageReceiver.java:96)
>        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
>        at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
> HTTPTransportUtils.java:275)
>        at org.apache.axis2.transport.http.AxisServlet.doPost(
> AxisServlet.java:120)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>        at org.mortbay.jetty.servlet.ServletHolder.handle(
> ServletHolder.java:487)
>        at org.mortbay.jetty.servlet.ServletHandler.handle(
> ServletHandler.java:367)
>        at org.mortbay.jetty.servlet.SessionHandler.handle(
> SessionHandler.java:181)
>        at org.mortbay.jetty.handler.ContextHandler.handle(
> ContextHandler.java:712)
>        at org.mortbay.jetty.handler.HandlerWrapper.handle(
> HandlerWrapper.java:139)
>        at org.mortbay.jetty.Server.handle(Server.java:285)
>        at org.mortbay.jetty.HttpConnection.handleRequest(
> HttpConnection.java:502)
>        at org.mortbay.jetty.HttpConnection$RequestHandler.content(
> HttpConnection.java:835)
>        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:723)
>        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208
> )
>        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378
> )
>        at org.mortbay.io.nio.SelectChannelEndPoint.run(
> SelectChannelEndPoint.java:368)
>        at org.apache.tuscany.sca.core.work.Jsr237Work.run(
> Jsr237Work.java:61)
>        at
> org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(
> ThreadPoolWorkManager.java:205)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> ThreadPoolExecutor.java:650)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:675)
>        at java.lang.Thread.run(Thread.java:595)
>
>
> Regards,
> Sandeep
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




ForwardSourceID:NT00009762  


ForwardSourceID:NT00009902    
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you




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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to