Topic
  • 3 replies
  • Latest Post - ‏2013-12-19T06:56:30Z by PengFeiYu
kennetheld
kennetheld
38 Posts

Pinned topic WSDL Issue

‏2013-12-18T04:22:18Z |

I am having trouble with a WSDL file.  I am getting an error on trying to parse the lines below when I try to run the jsp on the server (TOMCAT).  I can use the "Test with Web Services Explorer" and the web service call works correctly.  No one will be able to verify what I am saying since this web service requires specific IP mapping to reach.  I have attached the whole WSDL.  I can certainly reach out to the provider.  I am wondering if I am missing something in the structure of my project.  I basically imported the WSDL, created the EGL Service Skeleton, setup both the Deployment, Bindings and client.  Any help would be GREATLY appreciated.  Since the canned client works I have got to be doing something wrong with my setup.  

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd0" namespace="http://tempuri.org/"/>

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/PushWcfService.Models"/>

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd3" namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/>

 

The last three receive an error that states

 

"Multiple annotations found at this line:

                - XSD: There is no xmlns declaration for namespace 'http://schemas.microsoft.com/2003/10/Serialization/'

                - XSD: The location 'http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd1' has not been resolved because the

                 import is unused"

 

This is the complete XML tag.

 

<xsd:schematargetNamespace="http://tempuri.org/Imports">

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd0" namespace="http://tempuri.org/"/>

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/PushWcfService.Models"/>

<xsd:importschemaLocation="http://qawebservicesv2.cooltrax.com/Service.svc?xsd=xsd3" namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/>

</xsd:schema>

 

Let me know if you have any thoughts.  I can certainly follow-up with Susan or even the contact at Cool Trax if that is OK.  I think it may have something to do with the way I have files stored in the project but unsure.  Let me know your thoughts.  Thanks.

Attachments

  • canutri
    canutri
    354 Posts

    Re: WSDL Issue

    ‏2013-12-18T21:33:34Z  

    Are you trying to call a method in the web service to be used in your EGL logic?  Is so, I believe you would want to use the "Create EGL Client Interface" from the "EGL Services" context menu.

    I have had trouble in the past consuming a rather large wsdl provided from Oracle for their CRM On-Demand offering.

    Daron

  • kennetheld
    kennetheld
    38 Posts

    Re: WSDL Issue

    ‏2013-12-18T22:02:48Z  
    • canutri
    • ‏2013-12-18T21:33:34Z

    Are you trying to call a method in the web service to be used in your EGL logic?  Is so, I believe you would want to use the "Create EGL Client Interface" from the "EGL Services" context menu.

    I have had trouble in the past consuming a rather large wsdl provided from Oracle for their CRM On-Demand offering.

    Daron

    Daron,

    Thanks for the reply.  I have actually created the client using the Create EGL Client Interface.  What I showed was calling the function created within that creation on the jsfhandler associated with the JSP screen.  I have verified that CustomerID has a value.  I am unsure where to go from there.  I guess I can try to run trace and see if that shows something.  If you can think of anything else let me know.  Thanks.

  • PengFeiYu
    PengFeiYu
    29 Posts

    Re: WSDL Issue

    ‏2013-12-19T06:56:30Z  

    Daron,

    Thanks for the reply.  I have actually created the client using the Create EGL Client Interface.  What I showed was calling the function created within that creation on the jsfhandler associated with the JSP screen.  I have verified that CustomerID has a value.  I am unsure where to go from there.  I guess I can try to run trace and see if that shows something.  If you can think of anything else let me know.  Thanks.

    Hi,

    When I was trying to recreate the issue in my environment, I got the error dialog as attached, maybe it's caused by the special IP mapping rules so I got HTTP 403 forbidden.

    This issue looks like similar to APAR "PI06175: WSDLException faultCode=PARSER_ERROR consuming service" which has already been delivered to RBD 9.0.1, can you please try 901?
     If the problem still exists in 901, then I suggest to open PRM against this.

    Thanks & Regards

    Attachments