Exception whilst consuming a Webservice!

Hi,
I am new to webservices. I consume a webservice and while testing the created proxy i am getting an excpetion like this.
SoapFaultCode:1 JAXB unmarshalling exception: Unable to create an instance of de.te****************blw.v2.MeldungType; neste
d exception is javax.xml.bind.UnmarshalException: Unable to create an instance of de.te****************blw.v2.MeldungType-
+with linked exception: [java.lang.InstantiationException]+
The type meldung type was of type abstract="true" in the xsd as shown below.
{color:#ff0000}<xsd:complexType name="MeldungType" abstract="true">
<xsd:annotation>
<xsd:documentation>
Abstrakter Basistyp f&uuml;r alle Meldungen. Jeder Meldungstyp ist in einer eigenen Ableitung definiert.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Meldungsnummer" type="bt:MeldungsnummerType">
<xsd:annotation>
</xsd:sequence>
</xsd:complexType>
{color}{color:#000000}In the service call i used a type derived from it ie. one which extends from the MeldungType.
Could this be a problem in getting the above exception.
Comments requested.
Regards
Sandeep{color}

I think you had hitted a bug here.
In order to address the issue apply patch from Bug 17246737.Steps to download and apply the patch are listed below:
Go to MOS and search for the bug 17246737
1) Log onto My Oracle Support.
2) Click on the "Patches & Updates" tab.
3) Click on "Patch Name, Number (the default).
4) For the "Patch Name or Number" type in the patch number (for example: 17246737).
5) Choose the "Platform" or (Select the default which is "Select up to 5" for any platforms)
6) Hit Search.
Thanks
Ranjan

Similar Messages

  • Getting error while consuming google webservice in jspDynpage

    Hi All,
    I am consuming google webservices in my JspDyn page
    i am getting following error
    An exception occurred while processing a request for :
    iView : GoogleSer.google
    Component Name : GoogleSer.google
    Could not find portal application <b>com.company.global.enterprise.portal.wsdl.webservices.service.</b>
    Please help me to resolve this issue
    code ::
    MyGoogle googleService =
    (MyGoogle) PortalRuntime.getRuntimeResources().getService("com.company.global.enterprise.portal.wsdl.webservices.service.MyGoogle");
    GoogleSearchResult result = googleService.doGoogleSearch("google", "SAP", 0, 10, false, "", false, "", "", "");
    Thanks & Regards
    Rudra

    Hi,
    I am still having the same problem, however the scenario in which I am getting varies.
    I am getting this exception:
    "com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: IOError while working with the message."
    Some users when trying to login into the portal are getting blank screen and for some the portal launcher page is loading fine and could go to the Home Page.
    When I view the logs I am seeing the Nested Soap Exception.
    Any Ideas??? Starting the J2EE engine also did'nt help.
    Thanks in advance.
    Madhavi

  • Getting error in consuming google webservices from JspDynPage

    Hi All,
    Getting following error while consuming google webservices from JspDynPage
    An exception occurred while processing a request for :
    iView : GoogleSer.google
    Component Name : GoogleSer.google
    Could not find portal application com.company.global.enterprise.portal.wsdl.webservices.service.
    Code :
    MyGoogle googleService =
    (MyGoogle) PortalRuntime.getRuntimeResources().getService("com.company.global.enterprise.portal.wsdl.webservices.service.MyGoogle");
    GoogleSearchResult result = googleService.doGoogleSearch("google", "SAP", 0, 10, false, "", false, "", "", "");
    ResultElement[] results = result.getResultElements();          
    if(results != null) {
    response.write("<br> Search Result Size " +results.length );
    for (int i = 0; i < results.length; i++) {
    response.write((i + 1) + ": " + results);
    Thanks
    Rudra

    Hi,
    I am still having the same problem, however the scenario in which I am getting varies.
    I am getting this exception:
    "com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: IOError while working with the message."
    Some users when trying to login into the portal are getting blank screen and for some the portal launcher page is loading fine and could go to the Home Page.
    When I view the logs I am seeing the Nested Soap Exception.
    Any Ideas??? Starting the J2EE engine also did'nt help.
    Thanks in advance.
    Madhavi

  • Consuming a Webservice on WAS 6.40

    Hello,
    i try to consume a Webservice created with the Webservice Creation Wizard. I have configured the logical port and i created the client proxy. But when i run the test program with the crated proxy i retrieve the following error:
    (id=SOAP:111): Unallowed RFC-XML Tag (SOAP_EINVALDOC)
    In the RFC-Trace the following log is displayed:
    INFO 16:34:40: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT <
    XRFC> ->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message <
    XRFC> <
    XRFC> INFO 16:34:49: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE <
    XRFC> STATUSCODE() Received return code 500 ( Internal Server Error ) <
    XRFC> <
    XRFC> ERROR 16:34:49: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE <
    XRFC> PART~INITFOR_DESERIALIZE() A SOAP Runtime Core Exception <
    XRFC> occurred in method XP_READ_TAG of class CL_SOAP_XP at position id <
    XRFC> 1 with internal error id 111 and error text Unallowed RFC-XML Tag <
    XRFC> (SOAP_EINVALDOC) (fault location is 1 ).
    What's wrong here? Someone can help me?
    Thanks for your help!

    Hi Adriano,
    Here is the link I think you're looking for:
    http://help.sap.com/saphelp_nw04/helpdata/en/4f/2e6a52c3cdc44d83169b181a9c62ba/frameset.htm
    Hope it helps.
    Thanks,
    Marty

  • Consuming MII WebService in Java WebDynpro

    Hello,
    We are facing a strange situation...
    We define a transaction in MII to be consumed as WebService in Java WebDynpro. This transaction is a simple query on a DB returning 4 fields :
    Shift code : SHIFT
    Shift description : DESCRIPTION
    Start time : START_TIME
    End time : END_TIME
    It works fine, we use the import adaptative web service wizzard in netweaver developper studio to use this WS...
    But if we to an update on the webservice, changing a field name for example (SHIFT -> SHIFTCODE), we start to have trouble...
    We got then the very helpful error message :
    Exception on execution of web service with WSDL URL '<sever>/WebServices/GetShift' with operation 'Xacute' in interface 'XacuteWSSoap'
    If I display the model info using wdContext.currentRequest_XacuteElement().modelObject().associatedModelClassInfo().getModelInfo().toString()
    I got the following (extract) :
    <ModelClassPropertyInfo name="SHIFT" dataType="com.sap.tc.webdynpro.model.webservice.types.string(java.lang.String)" readOnly="false" qName="SHIFT" required="true" backendType="null"/>
    As you can see, the model definition is NOT updated and we still have SHIFT as name instead of SHIFTCODE...
    If someboby has an idea, it will save us our life ;o)
    Thank you
    PS:it the same behaviour if we add a field...

    Oliver -
    Did you try to reimport the WS model ..? If yes and still doesn't work...Try  to delete the old proxy in webdynpro ( adoptive ws) and import again.
    To avoid code changes,you can give same old name while fresh import.
    Adoptive WS in webdynpro  is not really like Adoptive RFC .It has some limitations.
    Thanks
    Hari

  • Error in consuming RFC Webservice in webdynpro

    Hi,
         I am trying to consume RFC Webservices in webdynpro.For that i created Z- functional module for availability check.But once i am deploying this application ,all the input fields of the corresponding application are disabled.
    The error is like
    Exception on execution of web service on destination 'DEFAULT_WS_EXECUTION_DEST' for operation 'ZwrMaterialAvailability' in interface 'ZWebService'
    Can someone help me to resolve this error?
    Thanks,
    Kundan

    Hi Saravanan ,
                             Thanks for your replay.
    Once i am testing the WSDL URL in netweaver webservice navigator,it showing an error like like
    Cannot download WSDL from http://host name.sap.com:8000/sap/bc/srt/wsdl/sdef_ZWEBSERVICE/wsdl11/ws_policy/document?sap-client=800: It is not allowed to access this service.
    But same URL is working fine in browser.It's displaying the XML file.
    Can you provide the solution to resolve this error?
    Thanks,
    Kundan

  • Consuming ABAP Webservice in Webdynpro app

    Hi,
    I have wrote a webdynpro app for consuming ABAP webservice. I used the procedure in the link below
    http://wiki.sdn.sap.com/wiki/display/WDJava/ConsumingABAPWebServiceinJavaWD
    Everything seemed to be went well, I created model and Webservice destinations. I have written the code for calling the webservice, which does not return data as part of response. I mean though the RFC returns data at the backend,its not showing the returned records in the webdynpro table.
    I have also tried checking the same by setting external break point. when the webservice is executed from my webdynpro app,it goes to the ABAP debugger and i could clearly see the records in the export parameters of RFC,but the same is not returned in the reponse object.
    Could any one let me know what could be missing. Any help is greatly appreciated?
    I have used the following code in Init method of my View
    Request_ZMYRFC input=new Request_ZMYRFC (model);
    wdContext.nodeRequest_ZMYRFC ().bind(input);
    ZMYRFC  req= new ZMYRFC (model);
    req.setPUserid("EDLAS00C");
    req.setPLtc("E");
    input.setMYRFC (req);
    IWDMessageManager manager = wdComponentAPI.getMessageManager();
        try
        wdContext.currentRequest_ZMYRFCElement().modelObject().execute();
          wdContext.nodeResponse().invalidate();
          wdContext.nodeZMYRFCResponse().invalidate();
          wdContext.nodeReturn_res().invalidate();
         wdContext.nodeItem_res_ret().invalidate();
          wdContext.nodeILtcg_res().invalidate();
          wdContext.nodeItem_res_ltcg().invalidate();
        catch(Exception e)
          manager.reportException(e.getMessage(), false);
    Thanks
    Santhosh

    santosh,
    Check provider system defination in nwa for webservice.After this mapp the provider system and service group after wd app deployed.This is mandatory while consuming webservice in webdynpro for latest versions of CE7.11 or later.for reference check this article/document. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50d70a19-45a3-2b10-bba0-807d819daf46
    Thanks,
    Murthy.
    Edited by: Murthy Karaka on Mar 22, 2010 12:59 PM

  • Error in Consuming Portal Webservice

    Hi ,
    I created a portal web service(RetrieveAndValidateUserService) and then consumed this portal service in an AbstractPortal Component application(RetrieveValidateUserComp).
    On deploying that application on portal I get the following error -
    #1.5#001372247F6F00640000001C000011600004542B1E4EA3FD#1218444075594#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#34878##PUNITP84649D.ad_SYN_3160950#Administrator#2b7b0eb0678111ddb00a001372247f6f#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#/System/Server#Java###Exception ID:02:11_11/08/08_0002_3160950
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : RetrieveAndVAlidateUser.RetrieveValidateUserComp
          at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
          at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
          at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
          at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
          at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
          at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
          at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
          at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
          at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
          at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
          at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
          at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
          at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
          at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
          at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.pseg.test.webservice.RetrieveValidateUserComp of Portal Component RetrieveAndVAlidateUser.RetrieveValidateUserComp because: Could not instantiate implementation class
          at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
          at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
          at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
          at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
          at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
          ... 26 more
    Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application RetrieveAndValidateUserService
          at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:415)
          at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
          at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
          at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
          at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
          at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
          at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
          ... 30 more
    1. I added a Private Sharing Reference Property in portalapps.xml of the application -
    <application-config>
        <property name="PrivateSharingReference" value="com.pseg.webservice.RetrieveAndValidateUser"/>
      </application-config>
    2. I modified the Java-Build Path to include the Portal Service Application.
    3. I deployed the Webservice par on the portal. I can see the service listed under Applications in
    System Administration->System configuration->Service Configuration.
    Is there anything i am missing or doing incorrectly?
    Points will be promptly awarded for helpful answers.

    Hi Lokesh
    I created a Portal Service consuming a webservice.
    It turns out the Private Sharing Reference that i gave had some fault. That's corrected now.
    Now on deploying the Portal Application I created for accessing the service, i am getting the following error -
    java.lang.Exception: The parameter Accounts is null before the serialization but in WSDL definition this field cannot be null
    Here, we need to pass this parameter "Accounts" as NULL only, for test purpose.
    Points will be awarded generously in case of helpful answer.

  • Consume Axis2 webservice in a JSP using Tomcat

    Hey,
    I desperately try to consume a Netbeans created Axis2 web service in a jsp.
    i am able to consume the web service in a Java test class as well as in j2me using the created stubs from WTK.
    But now I would like to consume the webservice in a jsp.
    First i tried to use the netbeans client generator (which does work out in a regular test class), As soon as i try to invoke the webservice in the jsp, i get an exception (i currently don't have access to the exact message, i will append that asap) . It stated, my part tag needed a type value (currently there's an element attribute included as i am using document style). I tried the same using a hello world class generated by netbeans using netbeans stubs...same error.
    Then I switched to java2wsdl, when using those stubs, i got another exception "axis2 webservice could not be generated".
    Then i tried using a soap call with the axis service class for preventing auto generated stubs. all of the 3 ways did work out in a java test class.
    But now i get the following exception:
    org.apache.jasper.JasperException: javax.servlet.ServletException: java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory
    org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:522)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:398)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    root cause
    javax.servlet.ServletException: java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory
    org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:850)
    org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779)
    org.apache.jsp.test_jsp._jspService(test_jsp.java:102)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803).
    The thing is: i did include the common-logging.jar in the project lib and it seems to work out smoothly when compiling. but at runtime i always get the same exception.
    i also put the library in the tomcat lib folder (after that in the lib/common folder) - same result. i tried downloading a new jar. still no changes (all of those folder arse included in my classpath).
    then i included the logging jar in my java/lib/ext folder.
    After that a new jar was missing (mail.jar). but my axis2 engine doesn't run anymore (apparently some conflict with other libraries).
    Now i dunno what to do anymore. even the simpelst hrllo world web service doesn't work in jsp.
    If i tried to invoke non axis2 webservices in a jsp - it does work out. but that's not an option for me

    There is a folder for shared packages
    tomcat_root\lib; or
    tomcat_root\common
    also most versions have a lib or common folder for each webapp for packages that are not to be shared.
    tomcat_root\webapps\appname\web-inf\lib
    Agreed that it is strange to allow servlets to import from the classes foler but not JSPs. It should make no difference but it is convension to place single classes in the same folder as the app's directory and packages (especially jar's) in the lib directory.

  • Consuming https: webservices

    Hi
    We consumed a WebService successfully and in the routings section we observed that the Primary URL starts with https:// rather than http://. When I try to access the webservice from PeopleCode i am getting the following error
    Integration Gateway - HttpTargetConnector:ExternalApplicationException. Http status code HttpStatusCode returned : 500. (158,10623) SAMPLE_TST_CON_WS.SUBMIT_PB.FieldChange PCPC:4499 Statement:46
    HttpTargetConnector:ExternalApplicationException. External System responded with an Error status. For Http Status Code explanation please check Http protocol Specifications.
    Do we any kind of setup in Peoplesoft to handle this kind of Web Services. Also we need to set implicit SOAP header values. Is there anyway that we can do that using Peoplecode.
    Any help is appreciated.

    I had the same problem in webdynpro. I created a webdynpro app for consuming a adative Webservices and I alse get the following exception on deploy and run.
    (Exception on execution of web service with WSDL URL http://vsrmi71.sap.dev.local:50100/WS_CAF_Ume_Service/Caf_Ume_Service?wsdl&mode=ws_policy with operation getAllUmeUsers in interface Caf_Ume_Service)
    - My webdynpro has only one webservice model with no homonymous classes.
    - The Service delivers a ArrayList of my own type of UME-Users (DataTypes).
    - The Service was create with caf and works fine with the visual composer and the wsnavigator.
    If someone has a solution for this problem please let me know! Thanks!

  • Getting exception while accessing External WebServices from Portal Componen

    Hi,
    We are using one external Temperature WebService and calling it from the proxy which is called by a Portal Component. My proxy name is TempService and portal component name is TempComponent.While calling the web service from portal component we are getting the exception. When I checked with log file, I got that invokeMethod() is failing and following exception is occuring :
    Caused by: com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: IOError while working with the message. Check the nested Exception.
         at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:197)
         at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:209)
         at com.sap.portal.tutorial.translation.TempService.getTemp(TempService.java:158)
         at com.sap.portal.tutorial.TempComponent.TempComponent.doContent(TempComponent.java:18)
    Can some one help us to resolve it.
    Thanks in advance,
    ajay

    As far as I know, webservices are working pretty well from SP2 Patch4. On patch3 hf2 I've had problems creating the proxy classes (especially for consuming .net webservices) and also gotten some runtime exception (cannot remember what they were).
    Suggest you open an OSS against SAP with your specific problem.

  • Consume a webservice developed in other than coldfusion  in WS-Security mode

    1. What are the prerequisites (any software installation, configuration) to be considered ?
    Requirement : To consume a Webservice developed in other than coldfusion in WS-Secuirty mode .
    Environment used : Windows 2003, IIS 6, Coldfusion 8, SQl server 2005
    2. While trying to consume a public webservice through coldfusion , We received unable to read WSDL file and Unknown host exception error.Can you please advise. why we are receiving this error and solution ?

    Thanks Dan Bracuk, for your reply.
    What I could understand from Sivakarthikeyan post is that
    Point 1)
    It is mentioned that they are going to consume external webservices for which he would like to know whether any software/configuration is required to implement WS-Security (In IIS or coldfusion administrator)?
    Point 2)
    It could be a correct URL that he is using, from his description (2nd step) he gets a error message as "Unable to read WSDL file". If it of incorrect URL then he would have received file not found or other error message.
    Can you please or anyone clarify?
    Thanks,
    Satheesh

  • How to consume REST WebService using Axis2 in Adobe CQ5.5

    Hi All,
        How to consume REST WebService using Axis2 in Adobe CQ5.5 ?
    Please help me with this.Thanks very much for your help.
    Thanks & Regards,
    Kumar

    We had enough trouble getting the "osgi compliant" Axis2 library to run in OSGI without spooky failures that we ended up re-writing everything utilizng JAX-WS. JAX-WS is present in the underlying JDK, you just need to create an OSGI fragment bundle that exposes these classes from the JDK. So basically a bundle that just exports:
    com.sun.xml.ws,
                                    com.sun.xml.ws.addressing,
                                    com.sun.xml.ws.addressing.model,
                                    com.sun.xml.ws.addressing.v200408,
                                    com.sun.xml.ws.api,
                                    com.sun.xml.ws.api.addressing,
                                    com.sun.xml.ws.api.client,
                                    com.sun.xml.ws.api.fastinfoset,
                                    com.sun.xml.ws.api.handler,
                                    com.sun.xml.ws.api.message,
                                    com.sun.xml.ws.api.message.stream,
                                    com.sun.xml.ws.api.model,
                                    com.sun.xml.ws.api.model.soap,
                                    com.sun.xml.ws.api.model.wsdl,
                                    com.sun.xml.ws.api.pipe,
                                    com.sun.xml.ws.api.pipe.helper,
                                    com.sun.xml.ws.api.server,
                                    com.sun.xml.ws.api.streaming,
                                    com.sun.xml.ws.api.wsdl.parser,
                                    com.sun.xml.ws.api.wsdl.writer,
                                    com.sun.xml.ws.binding,
                                    com.sun.xml.ws.client,
                                    com.sun.xml.ws.client.dispatch,
                                    com.sun.xml.ws.client.sei,
                                    com.sun.xml.ws.developer,
                                    com.sun.xml.ws.developer.servlet,
                                    com.sun.xml.ws.encoding,
                                    com.sun.xml.ws.encoding.fastinfoset,
                                    com.sun.xml.ws.encoding.soap,
                                    com.sun.xml.ws.encoding.soap.streaming,
                                    com.sun.xml.ws.encoding.xml,
                                    com.sun.xml.ws.fault,
                                    com.sun.xml.ws.handler,
                                    com.sun.xml.ws.message,
                                    com.sun.xml.ws.message.jaxb,
                                    com.sun.xml.ws.message.saaj,
                                    com.sun.xml.ws.message.source,
                                    com.sun.xml.ws.message.stream,
                                    com.sun.xml.ws.model,
                                    com.sun.xml.ws.model.soap,
                                    com.sun.xml.ws.model.wsdl,
                                    com.sun.xml.ws.org.objectweb.asm,
                                    com.sun.xml.ws.protocol.soap,
                                    com.sun.xml.ws.protocol.xml,
                                    com.sun.xml.ws.resources,
                                    com.sun.xml.ws.server,
                                    com.sun.xml.ws.server.provider,
                                    com.sun.xml.ws.server.sei,
                                    com.sun.xml.ws.server.servlet,
                                    com.sun.xml.ws.spi,
                                    com.sun.xml.ws.streaming,
                                    com.sun.xml.ws.transport,
                                    com.sun.xml.ws.transport.http,
                                    com.sun.xml.ws.transport.http.client,
                                    com.sun.xml.ws.transport.http.server,
                                    com.sun.xml.ws.transport.http.servlet,
                                    com.sun.xml.ws.util,
                                    com.sun.xml.ws.util.exception,
                                    com.sun.xml.ws.util.localization,
                                    com.sun.xml.ws.util.pipe,
                                    com.sun.xml.ws.util.xml,
                                    com.sun.xml.ws.wsdl.parser,
                                    com.sun.xml.ws.wsdl.writer,
                                    com.sun.xml.ws.wsdl.writer.document,
                                    com.sun.xml.ws.wsdl.writer.document.http,
                                    com.sun.xml.ws.wsdl.writer.document.soap,
                                    com.sun.xml.ws.wsdl.writer.document.soap12,
                                    com.sun.xml.ws.wsdl.writer.document.xsd,
                                    com.sun.xml.internal.bind,
                                    com.sun.xml.internal.bind.v2,
                                    com.sun.xml.internal.ws,
                                    com.sun.xml.internal.ws.addressing,
                                    com.sun.xml.internal.ws.addressing.model,
                                    com.sun.xml.internal.ws.addressing.v200408,
                                    com.sun.xml.internal.ws.api,
                                    com.sun.xml.internal.ws.api.addressing,
                                    com.sun.xml.internal.ws.api.client,
                                    com.sun.xml.internal.ws.api.fastinfoset,
                                    com.sun.xml.internal.ws.api.handler,
                                    com.sun.xml.internal.ws.api.message,
                                    com.sun.xml.internal.ws.api.message.stream,
                                    com.sun.xml.internal.ws.api.model,
                                    com.sun.xml.internal.ws.api.model.soap,
                                    com.sun.xml.internal.ws.api.model.wsdl,
                                    com.sun.xml.internal.ws.api.pipe,
                                    com.sun.xml.internal.ws.api.pipe.helper,
                                    com.sun.xml.internal.ws.api.server,
                                    com.sun.xml.internal.ws.api.streaming,
                                    com.sun.xml.internal.ws.api.wsdl.parser,
                                    com.sun.xml.internal.ws.api.wsdl.writer,
                                    com.sun.xml.internal.ws.binding,
                                    com.sun.xml.internal.ws.client,
                                    com.sun.xml.internal.ws.client.dispatch,
                                    com.sun.xml.internal.ws.client.sei,
                                    com.sun.xml.internal.ws.developer,
                                    com.sun.xml.internal.ws.encoding,
                                    com.sun.xml.internal.ws.encoding.fastinfoset,
                                    com.sun.xml.internal.ws.encoding.soap,
                                    com.sun.xml.internal.ws.encoding.soap.streaming,
                                    com.sun.xml.internal.ws.encoding.xml,
                                    com.sun.xml.internal.ws.fault,
                                    com.sun.xml.internal.ws.handler,
                                    com.sun.xml.internal.ws.message,
                                    com.sun.xml.internal.ws.message.jaxb,
                                    com.sun.xml.internal.ws.message.saaj,
                                    com.sun.xml.internal.ws.message.source,
                                    com.sun.xml.internal.ws.message.stream,
                                    com.sun.xml.internal.ws.model,
                                    com.sun.xml.internal.ws.model.soap,
                                    com.sun.xml.internal.ws.model.wsdl,
                                    com.sun.xml.internal.ws.org.objectweb.asm,
                                    com.sun.xml.internal.ws.protocol.soap,
                                    com.sun.xml.internal.ws.protocol.xml,
                                    com.sun.xml.internal.ws.resources,
                                    com.sun.xml.internal.ws.server,
                                    com.sun.xml.internal.ws.server.provider,
                                    com.sun.xml.internal.ws.server.sei,
                                    com.sun.xml.internal.ws.spi,
                                    com.sun.xml.internal.ws.streaming,
                                    com.sun.xml.internal.ws.transport,
                                    com.sun.xml.internal.ws.transport.http,
                                    com.sun.xml.internal.ws.transport.http.client,
                                    com.sun.xml.internal.ws.transport.http.server,
                                    com.sun.xml.internal.ws.util,
                                    com.sun.xml.internal.ws.util.exception,
                                    com.sun.xml.internal.ws.util.localization,
                                    com.sun.xml.internal.ws.util.pipe,
                                    com.sun.xml.internal.ws.util.xml,
                                    com.sun.xml.internal.ws.wsdl.parser,
                                    com.sun.xml.internal.ws.wsdl.writer,
                                    com.sun.xml.internal.ws.wsdl.writer.document,
                                    com.sun.xml.internal.ws.wsdl.writer.document.http,
                                    com.sun.xml.internal.ws.wsdl.writer.document,
                                    com.sun.xml.internal.ws.wsdl.writer.document.soap,
                                    com.sun.xml.internal.ws.wsdl.writer.document.soap12,
                                    com.sun.xml.internal.ws.wsdl.writer.document.xsd,
                                    com.sun.xml.internal.messaging.saaj.soap

  • Consuming a webservice in ABAP ECC 6.0 without using XI/ PI

    Hi Experts,
    I wanted to consume an external webservice without using XI / PI.After doing my homework and search on sdn I came to know that we can consume webservices in ABAP using proxies using SE80(Enterprise Services).
    I am trying to create a client proxy with the URL of webservice.It asks me the option to choose between URL or HTTP.
    I am selecting URL and in the second screen it asks about the package details and after that it finishes.Later I get an error message stating "NO VENDOR SPECIFIED".Its not allowing me to create a proxy.
    So, here are my questions.
    Does anyone faced the same kind of problem?
    Can we really consume a webservice without using XI / PI or any other middleware?
    Is it possible to consume the webservice only with URL or WSDL file ?
    Please let me know the exact process.
    Thanks in Advance.
    Shanker Pandey.

    Hi Martin,
      Please check these following links. Though you have reported already, these may help
    Proxy Object generation error using Wizard for Web Service Consumption
    Also, please have a look @ /people/thomas.jung/blog/2006/03/13/develop-a-web-service-that-sends-an-email--in-abap-netweaver-04s
    Hope this helps,
    Karthik

  • Error While Consuming the webservice in ABAP

    Hi,
      I am trying to consume a webservice in ECC. I have imported the WSDL and generated the proxy. Did the configuration in the SOAMANAGER. While calling the webservice from the program I am getting the following error message. "SRT: Unsupported xstream found: ("HTTP Code 400  : Bad Request")"
       Any help is appreciated.
    Thanks
    Raghavendra Kuamr

    Hi,
    Check ST11 to find detailed log of issue, most likely you are passing "WS-A" message id along with request (check settings in SOAMANAGER Logical Port).
    Try calling service after suppressing "Message Id transfer". See SAP Note: 1361688 and related notes in 0001292171
    Regards,
    Gourav
    PS: please search forum before posting questions.

Maybe you are looking for

  • Iphone 5 not restoring my back up data from itunes? Iphone 5 began freezing and turning off by itself after ios7 updates. How can i recover my data?

    I began having problems with my iphone 5 after I updated to ios7. It began having several issues e.g. freezing, turning on and off by itself and the home button was not responding. It is a long story because I had to talk to apple reps etc. to make a

  • CFCHART - multiple series problem

    Hello, I am using CFCHART to plot a line graph with 2 series of data (percentage for a date). The problem I'm having is that if one of the series is missing data for a particular date, the line breaks so I have one complete line graph, and the second

  • Searching Eclipse-Plugin for EL

    Hi @all! I wanna try to write an application with EL. Actually I'm using Eclipse 2.1.1. and I'm using the Lomboz-Plugin for creating JSP-pages by Java-Code. But I've noticed this Plugin is not able to know EL. In kind of errors, no corrections will b

  • Setup Error

    Hi All, I just upgraded to Win 7 Pro 64 bit, I am trying to install the Photoshop Cs4 Demo that I downloaded from here and when I run setup it goes thru a "Checking System Profile" then it comes up with a Setup Error the reads "Setup has encountered

  • Updating existing gallery

    I was wondering if it is possible to update an existing gallery without having to recreate the whole gallery again.  I'm guessing there is some way to save a gallery some how but I have no idea how to.  This problem makes it kind of tedious if I just