Problem Importing MOSS Search Service WSDL to ALSB 2.6

I am trying to import the MOSS Search Service WSDL to ALSB 2.6. Facing issues while creating the WSDL resource in ALSB.
Exception.
"An error occurred creating the resource : The WSDL is not semantically valid: error: src-resolve: element 'schema@http://www.w3.org/2001/XMLSchema' not found"
Please let me know the next steps on how to resolve this. I am also not clear whether the ALSB2.6 supports the MOSS SharePoint service WSDL.
The SharePoint Search service is secured using NTLM authentication. Please also let me know , how to handle the NTLM authentication on ALSB 2.6 for invoking the MOSS Search WebService.
Any information, forums, links or documentation for the above issue is greatly appreciated.

A possible workaround:
1) import into ALSB XMLSchema.xsd e namespace.xsd from w3c
2) add to msft wsdl <xs:import namespace="http://www.w3.org/2001/XMLSchema" schemaLocation="http://www.w3.org/2001/XMLSchema.xsd"/>
I tried it with alsb 3.0 and works fine.

Similar Messages

  • Import Direct Binding Service WSDL in OSB

    I was wondering how to import direct binding service wsdl in OEPL. I tried the below but getting an error. Any help is greatly appreciated.
    File - Import - File System. .... After importing the WSDL, I'm getting an error. So I was not sure if I'm on the right track or not.
    Thanks
    NC

    If you have brought in the whole directory structure then you can simply drag the WSDL into the corrct directory that relates to your imports.
    Then you can delete the unwanted directories using the delete key.
    If you don't want the directory structory to import you need to be conscience every time that you need to uncheck a check box that is checked by default. Can't remember the exact name but basiclly something like import directory structure.
    Once the WSDL in correct folder and still having issues, open up and view the source. Make sure all references are correct for the project directory structure.
    cheers
    James

  • Asynchronouus Service WSDL requires namespace in its (XSD)

    his post is to ask, if it is possible to add a namespace to PeopleSoft (PSoft) schemas and if you have encountered any problems with PSoft asynchronous service WSDL’s being invoked from JDeveloper BPEL. Further is it possible to automatically add the namespace into the schema?
    The issue that we are seeing is as follows. We have developed an asynchronours PSoft service. No problems there.
    When our developers use the generated WSDL . JDeveloper gives compilation problems. The error is "Global Type declaration/definition of names" error. Their BPEL service invokes a our asynchronous service.
    We investigated the problem and found that the asynchronous services use two schemas, a request and response schema. The schemas do not have a namespaces defined. The BPEL service needs a namespace to be defined in both the request and response schema to resolve the issue.
    How can we add the namespace into the schema, we do not want to do this manually?

    I have the same problem.Jboss+Wscompile, and I in the Sopa response elements are not qualified. could you fix this issue? I need to use type substitution and I can not ahve unqualified as default.

  • ALSB 3.0: Problem with Nested Policies in Proxy Service WSDL

    Hello,
    I'm trying to implement client applications that consume Web Services.
    In ALSB, i imported the WSDLs of the services, created business and proxy Services.
    Creating web references in .NET and Netbeans is working well, as long as there is no security policy attached to the WSDLs of the proxy services.
    When attaching a policy, ALSB nests it inside the WSDL:
    <s0:Policy s1:Id="signMessage">
    <wssp:Integrity SignToken="false">
    <wssp:SignatureAlgorithm URI="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
    <wssp:CanonicalizationAlgorithm URI="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    <wssp:Target>
    and references it, where i want it to have. in this case it's in the request of the service:
    <s2:input>
    <s4:body use="literal"/>
    <wsp:Policy>
    <wsp:PolicyReference URI="#signMessage"/>
    </wsp:Policy>
    </s2:input>
    The problem is, that neither .Net (C#) nor Netbeans (Java) correctly import and handle these policies. .Net even mentions in the generated code that the "Policy" element was not handled. So when running my applications, i logically get exceptions that no credentials/tokens or else were delivered from the client side. In general the mentioned IDEs that i'm using support the configuration of those security issues. But when not correctly parsing the WSDL from the Service Bus, they don't work.
    I tried many ways to dodge this problem, but without success.
    Manually writing policy Statements into the WSDL files is not what i'm searching for as a solution. I want it dynamically.
    I hope i could describe my problem clear enough and to get a possible solution.
    Thanks

    Sorry, found the answer but forgot to update this thread.
    The ?WSDL mechanism fails if Enforce WS-I Interoperability is true for the Proxy Service.
    While BEA support (and the docs relating to this flag) say this is by design (Only POST not GET is supported by WS-I) personally it seems to me that this rule should apply to operation invocation not a metadata inquiry but there you go...

  • Problem importing two service interfaces using the same data types

    Hi,
    I've been playing around with BPM for a while. Now I wanted to add a custom service interface to my starting event. I created the interface in ESR of CE 7.11. After importing I get this error message and I can't use the interface:
    Cannot change XsdSimpleTypeDefinition AcademicTitleCodeContent by importing the document http://sap.com/xi/APPL/SE/Global::src/wsdl/TestInterface.wsdl, because it is already defined in the document http://sap.com/xi/APPL/SE/Global::src/wsdl/rootwsdl_CustomerERPByIDQueryResponse_InService.wsdl in this project. Importing into another project might be possible.
    Of course the problem is clear, but how can I achieve importing two service interfaces that use the same data type without changing the xsd source?
    Thanks in advance,
    Mane

    Sorry for the late answer, but I am really busy at the moment.
    Unfortunately I can't the Interface and data types are already changed.
    But this happened various times. Each time I already had imported a SAP Enterprise Service into NW BPM that contains a bunch of inline data types. While creating my own interface I referenced one of those data types that are stored in a SAP namespace. After import the error message appeared.
    In the wsdl of the created interface there is a import statement for the namespace where the referenced data types origin from. Additionally there is a namespace definition xmlns:p1="SAPnamespace". In the element the type is "p1:ReferencedType". Could this maybe cause the error, because one time it is with this leading p1 in my created wsdl and once without in the SAP Service wsdl?
    Thanks and I am looking forward to next EhP of NW BPM,
    Mane

  • Search Service Application problems after upgrading from Foundation to Enterprise edition of SharePoint 2013

    Hi all. I have been searching for days for a solution to a problem I am having with SP2013 Enterprise edition.
    We recently upgraded from SP2013 Foundation to SP2013 Enterprise. After the upgrade, the search services are no longer working and we are receiving many application log entries indicating the following:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
    Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    Technical Support Details:
    System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    as well as:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
    Reason: The object you are trying to create already exists. Try again using a different name.  
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.  
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    I have tried to remove the search service application and recreate it, and even though the SharePoint Central Administration states that it was created successfully, I am still getting the same errors in the log. If I go to the Search Service Application
    Search Administration page, the "System Status" shows the following message:
    The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '0359af35-0982-4ede-8838-b1d390e915bf' in search application 'Search Service Application' is in a good state and
    try again
    Additionally, under the "Search Application Topology" section, it states "Unable to retrieve topology component health states. This may be because the admin component is not up and running" which I assume is normal if the admin is not
    running.
    Does anyone know how I can resolve this problem? 
    Thanks!

    Hi Joaquin,
    According to your description, the error occurred when you re-created the Search Service Application.
    Based on the error message, I recommend to verify the things below:
       1. Check if the association between the Search Service Application proxy and the web application is configured.
    Please go to Central Administration > Application Management > Configured service application associations > Click Default to see if the Search Service application is checked.
       2. Change the app pool for the Search Service Application to SharePoint Web Services Default in the properties of the Search Service Application.
    Please go to Central Administration > Application Management > Manage service applications > Highlight the Search Service Application > Click Properties in the ribbon > Change
    the two app pool to SharePoint Web Services Default: App Pool For Search Admin Web Service and Application Pool for Search Query and Site Settings Web Service.
        3. Run PS command to check if the search admin timer job is enabled: Get-SPTimerJob
    job-application-server-admin-service | fl. If it is not enabled, use PS command to enabled it and then reset Internet Information Services: Enable-SPTimerJob job-application-server-admin-service.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Problem rename sharepoint 2010 search service application admin database

    Hi all,
    i have a problem that hopefully someone has an answer to.  i am not too familiar with sharepoint so please excuse my ignorance.
    we have sharepoint 2010 on a windows 2008r2 server.  everything seems to work fine.  but as you know, the default database names are horrendous.  i have managed to rename all of them, except for the "search service application" admin
    database.
    the default is: Search_Service_Application_DB_<guid>
    the other 2 databases (crawl and property) were renamed without a problem.
    we are following the article from technet on how to rename the search service admin db (http://technet.microsoft.com/en-nz/library/ff851878%28en-us%29.aspx).  it says to enter the following command:
    $searchapp | Set-SPEnterpriseSearchServiceApplication -DatabaseName "new database name" -DatabaseServer "dbserver"
    however, i get an error about identity being null.  no big deal, i add the -Identity switch and the name of my search service application.  but the real problem comes the error it throws:
    Set-SPEnterpriseSearchServiceApplication : The requested database move was aborted as the associated search application is not paused.
    At line:1 char:54
    + $searchapp | Set-SPEnterpriseSearchServiceApplication <<<<  -Identity "Search Service Application" -DatabaseName "SharePoint2010_Search_Service_Application_DB" -DatabaseServer "dbserver"
        + CategoryInfo          : InvalidData: (Microsoft.Offic...viceApplication:
       SetSearchServiceApplication) [Set-SPEnterpriseSearchServiceApplication], I
      nvalidOperationException
        + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchS
       erviceApplication
    when i look at the crawling content sources, i see "Local SharePoint Sites" and it's status is Idle.  i even looked at this article on how to pause the search to no avail.  (http://technet.microsoft.com/en-us/library/ee808864.aspx)
    does someone know how i can rename my Search Service Applcation Admin database properly?  or at least "pause" that service so i can rename it?
    thank you all in advanced

    If you want to have no guids for your search admin db, i recommend you check out this script :)
    just delete your search service application (assuming you have just started)
    Alpesh Nakar's Blog
    Alpesh
    Just SharePoint Just SharePoint Updates
    SharePoint Conference Southeast Asia
    Oct 26-27 2010 Contributing Author
    SharePoint 2010 Unleashed
    MCTS: SharePoint 2010 Configuration
    MCITP: SharePoint 2010 Administrator

  • Problem while importing a web service model.

    Hi
    I am building a simple send email application using a web service.
    While creating a new model i am using following options.
    step 1 - Select "Import Adaptive web service model"
    step 2 - Select Wsdl Source
    2.1 - Local file system or URL
    Step 3 - No logical destination
    step 4 - choose wsdl file from file system.
    Process successfully done and model created.
    BUT
    when i am trying to run this application it is throwing file not found exception. i.e. not able to locate wsdl file.
    java.io.FileNotFoundException: C:\AbysalEmail.wsdl (The system cannot find the file specified)
    I am using remote network connection to access NWDS. and in remote drive C: itself i have saned my file.
    Then Why it is not able to locate my file.
    Please Help me out.
    Thanks.

    Hi
    I have provided in J2EE Engine visual administrator under
    Web Services Security -> Dynamic web services proxies
    following configuration.
    I have created a new Dynamic web service proxie.
    And in it under connection settings -> URL i have specified
    http://<host>:<port>/
    Above is host name and potr from where my WebDynpro application runs.
    But my file is located in C:\
    I think i am unable to set mapping configuration
    from
    http://<host>:<port>/
    to
    C:\
    Where shall i ten keep my WSDL file.!!!
    Thanks.
    Edited by: Saurabh Agarwal on Jul 30, 2008 1:34 PM

  • After my iphone4S update to 7.0.6, it have a problem that keep searching network then no service show on display. Can't call. I have try check sim card, reset network settings, and restore my iphone. Still not working at all. Need help please.

    After my iphone4S update to 7.0.6, it have a problem that keep searching network then no service show on display. Can't call. I have try check sim card, reset network settings, and restore my iphone. Still not working at all. Need help please.Urgent.TQ

    Izit software or hardware? Confuse:(
    Only can use wifi now.
    Any way thanks guys for ur suggestion:) amishcake and simes

  • ALSB 3.0 - Form of URL to obtain Proxy Service WSDL changed?

    A quick 'technical' question that seems too dumb to raise as a support call, but cant find any discussion or details in docs, release notes etc.
    There might be some subtle default which has changed or I've done some thing different and I just can't find it - likely:).
    QUESTION: Has the way in which the WSDL is requested from a (Proxy) Web Service changed.
    IN ALSB 2.6 and earlier:
    http://localhost:7501/service/EchoStringService?WSDL
    would return WSDL
    IN ALSB 3.0
    the same (or similar form after recreating the above service in ALSB 3.0 ) returns:
    Error 405--Method Not Allowed
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.6 405 Method Not Allowed
    The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
    Any advice would be appreciated
    Thanks
    Jim Nicolson

    Sorry, found the answer but forgot to update this thread.
    The ?WSDL mechanism fails if Enforce WS-I Interoperability is true for the Proxy Service.
    While BEA support (and the docs relating to this flag) say this is by design (Only POST not GET is supported by WS-I) personally it seems to me that this rule should apply to operation invocation not a metadata inquiry but there you go...

  • Problem in web services wsdl file with tomcat 5

    Hi to all JGurus,
    I am sunil, i have one problem with simple web service, i made a simple web service and deployed on my tomcat 5, my tomcat showing the web service but when i click on the wsdl link it throws the exception:
    javax.servlet.ServletException: JAXRPCSERVLET35: failed to create a template object
         com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGetDefault(JAXRPCServletDelegate.java:351)
         com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGet(JAXRPCServletDelegate.java:157)
         com.sun.xml.rpc.server.http.JAXRPCServlet.doGet(JAXRPCServlet.java:111)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    please help me, thanks in advance.

    Hi Rama,
    I used JAX-RPC with WSDp 2.0 first i created my interface then implemented class then i have used the wscompile to generate wsdl. then i packed with jaxrpc-ri and web.xml in a war file, this raw war file i used to generate my original final war with the help of wsdeploy command.
    I deployed this file on tomcat its showing the service but while clicking on wsdl link it throws the above exception.
    Please let me know any thing else u want to know i can fwd my sample war file also to u.
    Thanks in advance.
    Sunil

  • Error while importing Adaptive Web Service Model in WDJ

    Hello,
    We are getting following error while trying to import any web service using Adaptive WS model in WDJ.
    Error in loading WSDL file.Check the error log for more details.
    Log file shows following error message.
    !ENTRY com.tssap.util 4 0 Mar 05, 2014 10:51:54.307
    !MESSAGE Mar 5, 2014 10:51:54 AM          com.sap.ide.webdynpro.ui.service.ServicesUI          [Thread[main,5,main]] Error: Internal error
       Plugin name: Web Dynpro Model Editor
       Plugin ID  : com.sap.ide.webdynpro.modeleditor
       Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
       Method     : loadNameSpacesAndModelClasses
       Message    : Cannot load NameSpaces and ModelClasses
    Class Path: C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;
    java.home: C:\j2sdk1.4.2_10
    proxyHost:
    proxyPort:
    nonProxyHosts: |
    Temporary Directory: C:\DOCUME~1\721398\LOCALS~1\Temp\
    WSDL URL: http://1XXXXXXXX:50000/<WS>?wsdl
       Exception  : com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL http://ip address>:50000/<WS>?wsdl and service factory configuration {DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=* DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\j2sdk1.4.2_10, DynamicProxy.TempDir=C:\DOCUME~1\721398\LOCALS~1\Temp\, DynamicProxy.INetProxy.Host=}
    !STACK 0
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://<IP address>:50000/<WS>?wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\j2sdk1.4.2_10, DynamicProxy.TempDir=C:\DOCUME~1\721398\LOCALS~1\Temp\, DynamicProxy.INetProxy.Host=}'
      at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:414)
      at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
      at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
      at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:306)
      at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:316)
      at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
      at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
      at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
      at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
      at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
      at org.eclipse.jface.window.Window.open(Window.java:563)
      at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
      at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
      at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
      at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
      at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
      at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
      at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
      at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
      at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
      at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
      at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
      at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
      at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
      at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
      at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
      at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
      at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
      at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
      at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
      at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
      at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
      at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
      at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
      at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
      at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
      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:324)
      at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
      at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
      at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
      at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
      at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
      at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
      at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
      ... 53 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception.
      at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:284)
      at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
      ... 56 more
    Caused by: java.io.IOException: CreateProcess: javac "@C:\Documents and Settings\721398\Local Settings\Temp\DGenService1393996912479\javac_args1.cfg" error=2
      at java.lang.Win32Process.create(Native Method)
      at java.lang.Win32Process.<init>(Win32Process.java:66)
      at java.lang.Runtime.execInternal(Native Method)
      at java.lang.Runtime.exec(Runtime.java:566)
      at java.lang.Runtime.exec(Runtime.java:491)
      at java.lang.Runtime.exec(Runtime.java:457)
      at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:386)
      at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traversThrough(PackageBuilder.java:291)
      at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:485)
      at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compilePackage(PackageBuilder.java:215)
      at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:271)
      ... 57 more
    Any inputs would be helpful.
    Thanks,
    Balaram

    Hello Balaram,
    I think the issue is related to NWDS Plug in- Web Dynpro Model Editor.Please check following thread.
    Can't create model in Web Dynpro
    Thanks & Regards,
    Patralekha

  • Error import Adaptive Web Service Modal

    Hi, i´m doing an tutorial of import Adaptive Web Service Modal, but when i create the model and write the link: http://www.abysal.com/soap/AbysalEmail.wsdl in the top appear "Error in loading the WSDL file. Check the error log for more details".
    I see the log, but appear:
    Error Mon Sep 24 13:54:37 CEST 2007 Sep 24, 2007 1:54:37 PM          com.sap.ide.webdynpro.ui.service.ServicesUI          [Thread[main,5,main]] Error: Internal error
       Plugin name: Web Dynpro Model Editor
       Plugin ID  : com.sap.ide.webdynpro.modeleditor
       Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
       Method     : loadNameSpacesAndModelClasses
       Message    : Cannot load NameSpaces and ModelClasses
    Class Path: C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi/_cmi_api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception/lib/exception.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime/lib/SapDictionaryTypesRuntime.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services/lib/SapDictionaryTypeServices.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/logging.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/loggingStandard.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/jARM.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;
    java.home: C:j2sdk1.4.2_09
    proxyHost:
    proxyPort:
    nonProxyHosts:
    Temporary Directory: C:DOCUME1vcapillaCONFIG1Temp
    WSDL URL: http://www.abysal.com/soap/AbysalEmail.wsdl
       Exception  : com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL http://www.abysal.com/soap/AbysalEmail.wsdl and service factory configuration {DynamicProxy.ClassPath=C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi/_cmi_api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception/lib/exception.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime/lib/SapDictionaryTypesRuntime.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services/lib/SapDictionaryTypeServices.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/logging.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/loggingStandard.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/jARM.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:j2sdk1.4.2_09, DynamicProxy.TempDir=C:DOCUME1vcapillaCONFIG1Temp, DynamicProxy.INetProxy.Host=}
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://www.abysal.com/soap/AbysalEmail.wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi/_cmi_api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception/lib/exception.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime/lib/SapDictionaryTypesRuntime.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services/lib/SapDictionaryTypeServices.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/logging.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/loggingStandard.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging/lib/jARM.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Archivos de programa/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:j2sdk1.4.2_09, DynamicProxy.TempDir=C:DOCUME1vcapillaCONFIG1Temp, DynamicProxy.INetProxy.Host=}'
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:413)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:371)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:341)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:305)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:315)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
         at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
         at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
         at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         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:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:149)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl. java.net.SocketException: Connection reset
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1028)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1115)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
         ... 57 more
    Caused by: java.net.SocketException: Connection reset
         at java.net.SocketInputStream.read(SocketInputStream.java:168)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
         at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:165)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1008)
         ... 59 more
    What happend?
    Thanks,

    Thanks,

  • Problem calling a web Service from BI Publisher (10.1.3.2 )

    We have published a PL/SQL Web Service (from Jdeveloper 10.1.3 ) into a SOA Suite server.
    As requirements from BI Publisher , we chose Document/Literal, SOAP 1.1.
    The Program Unit accept an input parameter (we tried NUMBER & STRING)
    The result is an XML formatted (PL/SQL functions returns a CLOB then converted as a String).
    When testing the Service call from the SOA Suite console, no problems.
    We declined a page with APEX to test this Web Service too : Test is OK
    We added this web service as a data source in BI Publisher :
    After typing WSDL URL, Method, Parameter
    After testing , we do not get the XML result but an error message, coming from Apache AXIS (seems to be the DynamicInvoker) :
    not know how to convert '50740' into org.apache.axis.client.Call@cd7fdb
    Our demo is very near to this example : http://blogs.oracle.com/xmlpublisher/2006/11/01#a123
    and the one from the BI Publisher documentation

    I can't say I know the answer but I wanted to share a thought on debugging the issue. Like you I am seeing an axis error for a parameter on a web service I know works. I can call it using BPEL, SoapUI, etc... I suspect that perhaps BI pub is having trouble interpreting the WSDL for the web service. Specifically, I suspect that since I have imported schemas in the WSDL and nested imports in the supporting XSD files, the process is getting confused. The request message is fairly simple with three optional parameters but the WSDL does use an import via the WSDL. I wanted to share this since this problem often comes up with various tooling and I am lacking time to work out a test case to prove this theory out any time soon. I will try to post once I find some time to test this theory but it may be a while. Reading the results of someone else's test would be just as good!

  • Problem invoking RPC web service (Unbalanced ELEMENT)

    Hi folks!
    I am trying to create an RPC web service for an existing (and working) EJB using
    WebLogic 6.1 SP2, but I keep getting the following error message each time I invoke
    any of the available methods from the stateless session bean using a (static)
    test client:
    Exception in thread "main" java.lang.reflect.UndeclaredThrowableException: Error
    at Line:12, token:[SPACE]     (
    )Unbalanced ELEMENT got:head expected:meta
         at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseException(SAXElementFactory.java:67)
         at weblogic.xml.babel.parsers.StreamParser.streamParseSome(StreamParser.java:136)
         at weblogic.xml.babel.parsers.BabelXMLEventStream.parseSome(BabelXMLEventStream.java:46)
         at weblogicx.xml.stream.XMLEventStreamBase.hasNext(XMLEventStreamBase.java:135)
         at weblogicx.xml.stream.XMLEventStreamBase.hasStartElement(XMLEventStreamBase.java:241)
         at weblogicx.xml.stream.XMLEventStreamBase.hasStartElement(XMLEventStreamBase.java:171)
         at weblogicx.xml.stream.XMLEventStreamBase.startElement(XMLEventStreamBase.java:164)
         at weblogic.soap.codec.SoapMessage.read(SoapMessage.java:86)
         at weblogic.soap.WebServiceProxy.receive(WebServiceProxy.java:480)
         at weblogic.soap.WebServiceProxy.invoke(WebServiceProxy.java:431)
         at weblogic.soap.SoapMethod.invoke(SoapMethod.java:186)
         at weblogic.soap.wsdl.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:27)
         at $Proxy0.testmethod(Unknown Source)
         at Client.main(Client.java:58)
    Does anybody have an idea what might be causing this problem? A search in the
    newsgroup archive suggests that this problem might be related to the WSDL interface
    file, although it is not clear to me how I can change that .wsdl file directly
    as I am using the wsdl.jsp file created using the Remote2WSDL function. Any help
    would be greatly appreciated!
    regards,
    Ekim

    Sorry, have no solution for you, but I can agree we with your observations, that only document literal style services work in a predictable fashion. (In 10.1.3.1.0)
    Message was edited by:
    taylor_tails

Maybe you are looking for