Problems with creating model in Email Web Service tutorial

Hello!
In the moment, I'm trying to follow the tutorial "Using an Email Web Service in Web Dynpro". I followed all the steps in the chapter "Generating a Model from the WSDL Description", but after typing in the mentioned WSDL description "http://webservices.matlus.com/scripts/emailwebservice.dll/wsdl/IemailService" in the "New Model" wizard, I'm getting the error message, that the WSDL file is not found or not valid and no new model can be created.
So I'm quite stuck. What am I doing wrong? Did anyone encounter the same problems?
Greeting
Bärbel

Hello Baerbel,
I could not reproduce this error and never had this before. What you could do in the meantime is taking the wsdl description from the url and copy and paste it into a notepade file. Then please save it under emailwebservice.xml onto your hard disc and select it from "local file system or url" and take it from the path of your local file system.
Hope that helps!
Best regards,
Karin

Similar Messages

  • Error in using email  Web Service tutorial

    Hi ,
    I downloaded the email web service tutorial from
    sdn and tried to executeit.
    But it is throwing error,.
    I also  tried to bypass proxy settimg but still the same error is coming
    Can anyone guide me as what i should do?
    The error stack trace -
    The initial exception that caused the request to fail, was:
       java.io.IOException: Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl: www.abysal.com
        at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:161)
        at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1018)
        at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1125)
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
        at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:146)
    Detailed Error -
    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 'null'
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:421)
         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:325)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:198)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1029)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:247)
         at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
         at emailadwsmodel.EmailAdWSModel.<init>(EmailAdWSModel.java:45)
         at com.sap.tc.wd.adws.comp.app.EmaiFormView.wdDoInit(EmaiFormView.java:107)
         at com.sap.tc.wd.adws.comp.app.wdp.InternalEmaiFormView.wdDoInit(InternalEmaiFormView.java:156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         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.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.<init>(DGenericServiceImpl.java:49)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:91)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:419)
         ... 45 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:146)
         ... 49 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl: www.abysal.com -> java.io.IOException: Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl: www.abysal.com
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1038)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1125)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
         ... 50 more
    Caused by: java.io.IOException: Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl: www.abysal.com
         at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:161)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1018)
         ... 52 more

    Hi Vivek,
    This problem occurs when Web Service provider is not reachable , it means the server which provides services to the WSDL is temporally down or not reachable . To check whether the services is reachable , you could paste the WSDL URL in your internet browser , if it opens then problem is with NWDS configuration of proxy else sever is not reachable .
    In your case problem is not with NWDS but with server as it looks that it is temprorarly down. To avoid such problem in future you could also store the WSDL file locally on your system and then can import ( obvioulsy you requires at least once to get the WSDL ) . This will help only while modelling the application to run you will require the service provider to be up and runnning
    You could use other tutorials to try AWS Model in Web Dynpro .
    regards
    Dhawal

  • Problem with datetime data type in Web Service

    Hi,
      I created local ABAP proxy based on a WSDL and some of the fields for the SOAP methods has data type datetime:
    name="MsgEndTimeStamp" type="s:dateTime" />
    name="MsgStatus" type="s:string"/>
    Since ABAP stack doesnt support dataTime data type it has created the proxy method with data type STRING.  Now when I call the proxy method (consuming the service) I get an error:
    <CODE>SoapFaultCode:4</CODE>
    <ERRORTEXT>Server was unable to read request. --> There is an error in XML document (1, 626). --> String was not recognized as a valid DateTime.</ERRORTEXT>
    I am sure others have faced the same issue.  Can someone help?
    Thanks

    Thanks but I dont think that link is much relevant to the problems I am facing, because I cannot change the web service definition as it is used by many others.  Also the target application runs on oracle so thats why some of the fields are datetime and I dont want to change that, even if I could.
    I am just stuck in creating the wrapper program to call the service since the SAP converts datetime data type to string and when the messages gets to the application it cannot convert string -> datetime.
    thanks anyway

  • Problem with file receiving through abap web service

    Hi experts,
    I need to created web service for import file from .NET application into SAP.
    ABAP function expect hexadecimal string (same as GUI_UPLOAD / GUI_DOWNLOAD) but hexadecimal string from C# is too long (double longer), and I have no idea how to convert it. Also there is a problem with code page...
    Is there some better way to do this? Any idea is welcome!

    Hi Nemanja,
    Please bear in mind that your SAP system is based on UTF-8 encoding. Since you have the xstring length doubled, most probably your sender system uses UTF-16 encoding. So what you need to do is change the encoding used by your .NET application when sending the data to SAP.
    Alternatively, you can try using XSL Transformations in ABAP to have the input data converted from UTF-16-encoded xstring to ABAP structures. You can find a little example in this thread: ABAP data to XML conv with UTF-8 encoding and custom namespace. The point is to start your XSLT with the following: <?xml version="1.0" encoding="utf-16"?>.
    Hope this helps,
    Greg

  • Problems with UTL_DBWS calling out a web service.

    I´m using ORACLE 10G 10.2.0 and i ´ve downloaded the dbws-callout-utility-10R2.zip utility l´ve unziped it and launched it .
    the command loadjava -u SCOTT/passwd -r -v -f -genmissing dbwsclientws.jar dbwsclientdb102.jar ended without errors.
    then I gave grant access using the following commands
    the environment variable is
    $TMPCLASSPATH=$ORACLE_HOME/sqlj/lib/dbwsa.jar:$ORACLE_HOME/jdk/lib/dt.jar:$ORACLE_HOME/jdk/lib/tools.jar:$ORACLE_HOME/sqlj/lib/runtime12.jar:$ORACLE_HOME/sqlj/lib/translator.jar:$ORACLE_HOME/javavm/lib/aurora.zip:$ORACLE_HOME/rdbms/jlib/xdb.jar:$ORACLE_HOME/lib/xsu12.jar:$ORACLE_HOME/jlib/jndi.jar:$ORACLE_HOME/rdbms/jlib/aqapi.jar:$ORACLE_HOME/rdbms/jlib/jmscommon.jar:$ORACLE_HOME/lib/xmlparserv2.jar:$ORACLE_HOME/jlib/orai18n.jar:$ORACLE_HOME/jdbc/lib/ojdbc14.jar
    call dbms_java.grant_permission( 'SCOTT','SYS:java.lang.RuntimePermission', 'shutdownHooks', '' );
    COMMIT;
    call dbms_java.grant_permission( 'SCOTT', 'SYS:java.util.logging.LoggingPermission', 'control', '' );
    COMMIT;
    call dbms_java.grant_permission( 'SCOTT', 'SYS:java.lang.RuntimePermission', 'setFactory', '' );
    COMMIT;
    then I created the package running UTL_DBWS .SQL scripts
    when I run a test for calling out the web service I got the next error.
    ORA-29532: UNCAUGHT JAVA EXCEPTION : Java.Lang.IllegalAccessException: java.lang.ExceptionLnLn
    at line
    " function create_service_proxy(wsdl_Document_Location VARCHAR2, service_Name VARCHAR2) return SERVICE
    as language java 'oracle.jpub.runtime.dbws.DbwsProxy.createService(java.lang.String,java.lang.String) return long' "
    name 'oracle.jpub.runtime.dbws.DbwsProxy.createService(java.lang.String,java.lang.String) return long';
    Is necessary to install the jpublisher in addition for a sucessfully web service calling out?
    what goes wrong?
    Thanks for the soon answer.

    I have exactly the same problem.
    All possible grants are made.
    Running as SYS is not functioning as well.
    The same installation (the same jar's, the same utl_dbws version, the same database version) does function on two other (developers team's) servers .
    The differences are:
    Where it functions: Oracle database Enterprise edition on Windows (Windows 7, Vista)
    Where it does not function: Oracle database Stadard edition on Unix
    I have gone though a decent number of forums and other on-line resources with no success. Solutions available are to grant missing permissions. However these solutions are based on the assumption that under SYS user everything functions properly.
    In my case, this does not function even under SYS as SYSDBA.
    I will highly appreciate any recommendations!
    Best Regards,
    Michail
    P.S.
    Database: Oracle 10.2.0.1 Standard edition installed on Unix

  • Problems with deep request structure in web service

    I'm having problems when trying to consume an Enterprise Service-like web service in my Web Dynpro application. The web service FindXByElements has a request-structure as follows:
    XByElementsQuery
    -ProcessingConditions
    -QueryHitsMaximumNumberValue
    -QueryHitsUnlimitedIndicator
    -XSelectionByElements
    -ID
    -Year
    Regarding the structures on level two, the structure ProcessingConditions are of the global data type "WITHOUT_LASTRETURNED_QueryProcessingConditions" and are therefore typed. The structure XSelectionByElements on the other hand are just a "level" in the request structure and are therefore not typed. Both structures have occurrence 1 so they have to be filled with input data.
    The code in wdDoInit in the Component Controller looks like this:
    QueryXInModel model = new QueryXInModel();
    wdContext.nodeRequest_FindXByElements().bind(wdContext.createRequest_FindXByElementsElement(new Request_FindXByElements(model)));
    wdContext.currentRequest_FindXByElementsElement().modelObject().setXByElementsQuery(new XByElementsQuery_Sync(model));
    //Processing structure
    wdContext.currentXByElementsQueryElement().modelObject().setProcessingConditions(new WITHOUT_LASTRETURNED_QueryProcessingConditions(model));
    //Selection structure
    wdContext.currentXByElementsQueryElement().modelObject().setXSelectionByElements(new XSelectionByElements(model));
    The last row generates the following exception:
    java.lang.IllegalArgumentException: Cannot perform write operation 'setRelatedModelObject' on target role: Class 'XSelectionByElements' is not compatible to class '$002fWsdlDefinitions$002fWsdlTypes$002fXsdSchema$002fXsdComplexType$005b3$005d$002fXsdSequence$002fXsdElement$005b2$005d$002fXsdComplexType' of target role 'XSelectionByElements' in model class 'XByElementsQuery_Sync'
    There seems to be a problem to bind a non-typed structure element to a context node since the processing structure is working fine but the selection structure are not.
    What am I doing wrong, anyone got any clues?
    /Oskar

    Hi
    QueryXInModel model = new QueryXInModel();
    wdContext.nodeRequest_FindXByElements().bind(wdContext.createRequest_FindXByElementsElement(new Request_FindXByElements(model)));
    wdContext.currentRequest_FindXByElementsElement().modelObject().setXByElementsQuery(new XByElementsQuery_Sync(model));
    //Processing structure
    wdContext.currentXByElementsQueryElement().modelObject().setProcessingConditions(new WITHOUT_LASTRETURNED_QueryProcessingConditions(model));
    //Selection structure
    wdContext.currentXByElementsQueryElement().modelObject().setXSelectionByElements(new XSelectionByElements(model));
    XByElementsQuery
    ProcessingConditions
    QueryHitsMaximumNumberValue
    QueryHitsUnlimitedIndicator
    XSelectionByElements
    ID
    Year
    as
              QueryXInModel model = new QueryXInModel();
               Request_FindXByElement  request = new Requst_FindXByElement();
                ProcessCondition   processCond  = new  ProcessCondition(model);
                QueryHitsMaximumNumberValue  qhMaxNumValues = QueryHitsMaximumNumberValue(model);
          QueryHitsUnlimitedIndicator  qhUnLimind = new QueryHitsUnlimitedIndicator(model);
            XSelectionByElements  selecByEle = new XSelectionByElements(model);
                     processCond.set....();                         
                     qhMaxNumValues .set...();
               and so on
                    request.set....();
    wdcontext.nodeReqestFindX..bind(request);
      in the above during the values you will automatically get the set values .

  • Problem with signed SAML assertion and Web Services Manager

    Folks,
    I’m having some issues trying to generate a proper signed SAML assertion using JDeveloper 10.1.3. I am securing a java proxy class using the wizard as described in http://www.oracle.com/technology/products/jdev/howtos/1013/wssecure/10gwssecurity_howto.html .
    On the OWSM side, I have a service that I am securing with SAML - Verify WSS 1.0 Token. If I set the "Allow signed assertions only" property to false I can complete the service call. However, when it is set to true I am receiving the following fault: javax.xml.rpc.soap.SOAPFaultException: SAML token verification failed.
    When I examine the message going to OWSM in a packet analyzer, it is missing the signature in the SAML assertion. The <saml:Assertion> tags looks like:
          <saml:Assertion MajorVersion="1" MinorVersion="1"
                          xmlns="urn:oasis:names:tc:SAML:1.0:assertion"
                          xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
                          AssertionID="yM0oqZgF0N1a1td6yzKgOQ22"
                          IssueInstant="2007-01-23T17:15:27Z"
                          Issuer="HealthMarkets_s3">
            <saml:Conditions NotBefore="2007-01-23T17:15:27Z"
                             NotOnOrAfter="2007-01-24T17:15:27Z"/>
            <saml:AuthenticationStatement AuthenticationInstant="2007-01-23T17:15:27Z"
                                          AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password">
              <saml:Subject>
                <saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">client_s3</saml:NameIdentifier>
                <saml:SubjectConfirmation>
                  <saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
                </saml:SubjectConfirmation>
              </saml:Subject>
            </saml:AuthenticationStatement>
          </saml:AssertionI have selected the Sign Outbound Messages in step 3 of the Secure Web Proxy Wizard. This step uses the DSA-SHA1 algorithm.
    Any help is greatly appreciated.
    Thanks in advance,
    Joseph

    Thanks for the response. I am not using any pages for this application yet... just calling the web service from SOAP UI or any Web Service testing tool causes the problem.
    All that has to be done to replicate it is to build a simple EJB 3.0 JPA bean using the entities from tables wizard and then add named query as follows:
    @NamedQuery(name = "BomHeader.findByDesc", query = "select o from BomHeader o where o.bomDesc like :p_bomDesc")
    then build a session bean with the wizard that includes the JPA persistence unit and the entity and subsequently use the wizard to wrap the session bean in a web service.
    The whole replication process should take 5 minutes if you have some database tables to work with. It breaks when the web service is called.
    Thanks in advance

  • Problems with permissions to execute a web service in a drop down list ...

    Hello:
    I have created several iView with VC and I integrated it into guided procedures process. In some of that VC iViews I have drop down list that are filled with data retrieved from web services created by us that doesnu2019t require any authentication.
    When I execute my VC iViews with the Administrator user everything works ok, but when I execute it with a different user the drop down list doesnu2019t retrieve any value, as if the corresponding web services where not executed. 
    If I assign the "super_administrator" portal role to those users everythingu2019s goes OK. But I don't want that users to have that permission. Can anyone help me to identify which granular permission do I have to assign to that users in order to get the iView working as they are working for the "super_administrator" role?
    Thank you in advance.
    Ricardo Zengin.
    Edited by: Ricardo Zengin on Jul 6, 2009 6:35 PM

    I solved this issue giving administrator read and end user permision in te portal systems creadted for the web services to a group to which all my users belongs.

  • Problems with Community Bridge (MS REST-Web-Service)

    Hello,
    few days ago I started experiencing problems while connecting to Microsoft TechNet Forums
    by using Community Bridge 3 (MSDN/Social/Partner) and "Forté
    Agent" client. I get the error below from bridge debugger while retrieving headers from Windows Server General Forums
    I subscribed:
    Update threads since (null)
    CreateRequest: https://forumsapi.contentservices.msdn.microsoft.com/threads/?forumId=0b3d1d0b-dfd6-4df9-a87a-80d34d658a5f&sort=createdDate&order=desc&page=1
    WebException: JSON: {
    "errors": [
    "No results found."
    RequestTime: 8348 ms
    Note: The error also appears from any other forum. 
    So I sent bridge debugger collected information to Jochen Kalmbach (the developer).
    The error seems to come from the MS REST-Web-Service.
    Could you confirm the problem ?
    Bye,
    Luca
    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

    You might also check on that over here.
    http://communitybridge.codeplex.com/discussions
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Problem with special characters when calling web services via ISG

    Hi all,
    I have a problem when trying to send or retrieve strings containing some special characters via Integrated SOA Gateway.
    For example, when I call a PL/SQL function via ISG that returns a string containing curling single and double quote characters, these are not represented by valid XML character entity references. So when trying to open the response XML (returned by ISG) in a browser, I get a parser error...
    Has anybody had a similar experience with ISG? How can I resolve that - is it an ISG bug?
    Thanks
    Carolin

    XML Parsing Error: not well-formed
    Location: file:///C:/Users/sanders/Desktop/Text3.xml
    Line Number 4734, Column 54: <DESCRIPTION>Overhead Track Lighting 4?</DESCRIPTION>Do you get the same error if you change the description from "Overhead Track Lighting 4?" to "Overhead Track Lighting 4"?
    Do you have any invalid characters?
    BI Publisher Reports End With Error When There Is An Ampersand Character ( & ) On The Xml Data File [ID 1081175.1]
    Journal Entries Report Doesn'T Yield Output: Java Heap Error [ID 1115663.1]
    Thanks,
    Hussein

  • Problem with email web service

    I'm trying to implement the email web service tutorial.  When I run the application I get the initial page but when I try to send mail I get the following error:
    Service call exception; nested exception is: java.net.UnknownHostException: proxy
    We don't use a proxy server so I'm not sure why this error appears. 
    I tried to disable http proxy server in the Systems Administration. 
    Any ideas would be greatly appreciated.
    Ross

    Hi Michael,
    This exception is thrown if at runtime for service exceution the host ip address could not be resolved. It could happen if service provider server is down, not responding or out of network . Another cause could be if you have not configured the proxies in Visual admin to go out of network .
    regards
    dhawal

  • Email web service example as an Adaptive Web Service Model

    Hi All,
    I am using email web service example as an Adaptive Web Service Model in my Web DynPro application (The WSDL of the application that I use is:
    http://www.abysal.com/soap/AbysalEmail.wsdl).  While loading the WSDL file I am getting following error in log file. Could someone please help me what would be the problem?
    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.<init>(DGenericServiceImpl.java:49)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:411)
         ... 53 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:146)
         ... 56 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl, passing via http proxy: :80: Connection refused: connect -> java.io.IOException: Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl, passing via http proxy: :80: Connection refused: connect
         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.io.IOException: Cannot connect to http://www.abysal.com/soap/AbysalEmail.wsdl, passing via http proxy: :80: Connection refused: connect
         at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:161)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1008)
         ... 59 more
    Thanks,
    Naresh

    Hi Naresh,
    See if any of the following threads help, all are related to the same wsdl:
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=54635">https://www.sdn.sap.com/irj/sdn/thread?threadID=54635</a>
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=95335">https://www.sdn.sap.com/irj/sdn/thread?threadID=95335</a>
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=58137">https://www.sdn.sap.com/irj/sdn/thread?threadID=58137</a>
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=36756">https://www.sdn.sap.com/irj/sdn/thread?threadID=36756</a>
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=204762">https://www.sdn.sap.com/irj/sdn/thread?threadID=204762</a>
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=37640">https://www.sdn.sap.com/irj/sdn/thread?threadID=37640</a>
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=80384">https://www.sdn.sap.com/irj/sdn/thread?threadID=80384</a>
    In most of these threads, the suggestion given has been to try using the following wsdl:
    <a href="http://www.mindreef.net/tide/scopeit/start.do?referer=xmethods&url=http://www.abysal.com/soap/AbysalEmail.wsdl">http://www.mindreef.net/tide/scopeit/start.do?referer=xmethods&url=http://www.abysal.com/soap/AbysalEmail.wsdl</a>
    Tutorial related to this web service is:
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8c6e81e5-0601-0010-e8b0-8d5c74a21cd1">https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8c6e81e5-0601-0010-e8b0-8d5c74a21cd1</a>
    (page 181)
    Bye
    Ankur
    Reward points if it helps!!

  • Problem with creating email account on E72

    I have bought E72 and want to use mine company email - but there is a problem with creating email account in mail program.
    Restoring to fabric settings doesn't works.
    When I'm creating Gmail account it's OK, but phone doesnt want to cooperate with other accouns:/

    Try again without using WLAN. I had same problem, but solved it using GPRS.

  • WSDL description for email Web service

    hi
    while creating an application for sending and receiving emails, i created an <b>Import Web Service Model</b> and selected WSDL source as <b>UDDI/URL</b>. Then i entered <b>http://www,abysal.com/soap/AbysalEmail.wsdl</b>
    but it can not be saved and gives the error  " <i>Invalid WSSDL or WSDl not found, please spcify different WSDL or check WSDL location entered on previous wizard page</i>"
    please help.
    Thanks in advance.

    Hi,
    Try creating a web service of your own(out of a simple Java class or ejb) and check if it is working fine.
    If yes, then it might be the problem with the internet connection that you might be using. There might be some restriction in your connection that is preventing your system from creating the proxies related to the wsdl.
    If no, please let me know what the error is.
    Regards,
    Noufal

  • How do I create a "document-centric" Web Service?

    By document-centric I'm talking about receiving a SOAP message on the server-side, where the initial parsing and security processing (this aspect is very important) is performed but then allowing the developer to access the delivered "payload", i.e. the XML, and perform whatever mapping/processing that is required without automatically mapping to the "standard" auto-generated Java objects.
    It is important that the client receives the "full" complex WSDL and can therefore generate their proxy classes with whatever tool (or language) that is appropriate.
    On the server side we do not want to create hundreds (if not thousands) of Java Bean clases as we already have the legacy code to map XML to Java. The idea is that JAX-RPC only instantiates the SOAPElements that represent the "raw" message, or, if possible, doesn't instantiate any objects whatsoever.
    I've spent many days now trying to find a single well-worked example for this type of Web Service without success - many, many references of the style "..and you can then create a document style web service.." but without the all important "how".
    From what I've read a custom type-mapping and/or serializer/deserializer could be the answer but again no good, solid examples are forthcoming.
    Another alternative seems to be to create the server side stub-classes using a "dummy" WSDL with the elements set to "anyType" but then distribute the "genuine" WSDL to the clients - we've got a simple example of the kind working but I don't like the idea of "tricking" the system in this way.
    I'm working with WASD 5.1, which in theory conforms with JAX-RPC so any ideas offered here should also apply in that environment.
    Has ANYONE successfully created a service of this type?
    Any help with this issue would be very much appreciated and rewarded (with Duke Dollars of course).
    Chris.

    Chris,
    I too noticed that most vendors take the RPC centric approach. Its because most of the industry examples of how WSs were used were simple enough to implement using RPC and anything more (document literal) would add to the complexity of implementation. This is something that is feared by many developers, especialy the .Net crowd who seem to want everything done through a wizard menu interface and don't care about other WS implementations at all.
    This is sort of changing. J2EE 1.4 is WS-I compliant, so when you compile server side ties from WSDL you can specify a document literal option and WS-I compliance. This gives you access to the SOAPElement objects. There's still issues with going between W3C DOM and SOAP elements but that's just API inconvenience, not a show stopper. As the inudustry develops more complex WSs we will see the vendors change their tools to better support this...
    Anyway, some more help...
    I use the the following wscompile options to build from WSDL for document literal WSs.
    wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -import config.xml
    wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -gen:server config.xml
    My "wrapper" elements look like this...
    <xs:element name="AComplexXMLResponse">
         <xs:complexType>
              <xs:sequence>
                   <xs:element ref="myNS:MYComplexXMLType"/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    If I do this:
    <xs:element name="ASimpleXMLResponse">
         <xs:complexType>
              <xs:sequence>
                   <xs:element name="AName" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    I still get the JAXRPC language bindings to a string, but in my case I don't really care. This may well be different for you.
    What I do to manage these elements is to split up the WSDL, WS wrapper element definitions and actual data XML schema definitions into separate documents. This means I have a WSDL which IMPORTS my message schema (this is where I define wrappers for in and out XML) which INCLUDES the actual DATA XML schema that I have.
    The WSDL import looks like this:
    <types>
         <xs:schema>
              <xs:import namespace="http://schemaURI" schemaLocation="./relativePath/WrapperElementSchema.xsd"/>
         </xs:schema>
    </types>
    The wrapper element schema has:
    <xs:include schemaLocation="./ActualDataSchema.xsd"/>
    This way I can easily replace the wrapper documents with just anyType references if something doesn want to play nice. The data schema file and the WSDL stay the same. This minimises the impact on what you have to change in your distribution. This is important as the WSDL is often generated on the fly by your WS environment and so can not be easily changed once you build your WSs, but the schema files it references are easily changed without affecting your code.
    Another reason for the wrapper elements was a JWSDP 1.2 issue (I don't know if this has been fixed in 1.3), where if you had the same method parameter signature in a web service (the parameters it took were the same XML types, for instance if you have an add and update methods for the same document input) JWSDP would get confused at runtime. It did not take account of the SOAP action that came along with the request to determine which operation to call. It just took the incoming XML, saw that it was of a certain type and it passed it to the first operation that took this element, which is VERY wrong. By using the wrapper elements, I could give all my input and output elements for each method different names (I used a naming stragegy that appended a 'request' or 'response' string to the method name to form a method parameter element name. This is a pain in the ass, but works and does wonders for interoperability with other WS vendors. Like I said before, I've got this working with JWSDP, BEA and .Net servers and clients.
    Hope this helps,
    If you think there is a real need for a public HOWTO on this, I could write one with a full step by step guideline that shows where I broke my legs getting this stuff to work. But this would eat into my sleep time :-/ TO JUDGE INTEREST I call on all people interested in a tutorial to respond to this thread (esp people involved with the JWSDP WS tutorial documentation). If I get 5 or more different people responding I will loose some sleep for the good of this community. Otherwise, I will just try to help you when I have time to read the forums.
    Kuba

Maybe you are looking for