WSDL generated from service that references XMLBean is invalid

Env: Weblogic Workshop 9.2.0
Build id: 783464
When I validate a WSDL generated from a service that imports XMLBean classes (auto-generated by the XMLBeans Builder) it shows numerous errors including src-resolve.4.2. and ?The part ?parameters? has an invalid value ?hello? ??. All my schemas validate without error in both Workshop and XMLSpy. This happens for both the WSDL generated from the right click menu and from the auto generated WSDL located in the build sub-directory.
Related to this problem, when I deploy the web service (for some reason I can deploy it if I don?t deploy the WSDL) sometimes I either can reach the web service and sometimes I receive a failure related to the parse of the WSDL stating java.util.NoSuchElementException as the reason.
Has anyone else seen these kinds of problems?

I'm going to open a support case but here are the XSDs
There are four in total ... I have marked the top and bottom of each so you can clearly identify them.
---AddressData.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:addr="http://www.test.org/address" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.org/address" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:complexType name="AddressType">
          <xs:sequence>
               <xs:element name="LineOne" type="addr:LineOneType"/>
               <xs:element name="LineTwo" type="addr:StreetAddressType" minOccurs="0"/>
               <xs:element name="City" type="addr:CityType"/>
               <xs:element name="State" type="addr:StateType"/>
               <xs:element name="Zip" type="addr:ZipType"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="LineOneType">
          <xs:choice>
               <xs:element name="StreetAddress" type="addr:StreetAddressType"/>
               <xs:element name="POBoxAddress" type="addr:POBoxAddressType"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="StreetAddressType">
          <xs:sequence>
               <xs:element name="StreetAddress" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="POBoxAddressType">
          <xs:sequence>
               <xs:element name="POBoxAddress" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="CityType">
          <xs:sequence>
               <xs:element name="City" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="StateType">
          <xs:sequence>
               <xs:element name="State" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="ZipType">
          <xs:sequence>
               <xs:element name="Zip" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
</xs:schema>
---AddressData.xsd Stop---
---CustomerData.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:cust="http://www.test.org/customerdata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:addr="http://www.test.org/address" xmlns:pri="http://www.test.org/priority" xmlns:ndata="http://www.test.org/ndata" targetNamespace="http://www.test.org/customerdata" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:import namespace="http://www.test.org/priority" schemaLocation="CustomerPriority.xsd"/>
     <xs:import namespace="http://www.test.org/address" schemaLocation="AddressData.xsd"/>
     <xs:import namespace="http://www.test.org/ndata"
          schemaLocation="DataType.xsd" />
     <xs:element name="CustomerData">
          <xs:annotation>
               <xs:documentation>
                    Comment describing your root element
               </xs:documentation>
          </xs:annotation>
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="Customer" type="cust:CustomerType" />
                    <xs:element name="otherData1" type="ndata:newDataType" />
                    <xs:element name="secondaryAddress"
                         type="addr:AddressType" />
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="CustomerType">
          <xs:sequence>
               <xs:element name="name" type="cust:CustomerNameType"/>
               <xs:element name="address" type="addr:AddressType"/>
               <xs:element name="priority" type="pri:PriorityLevelType"/>
               <xs:element name="data" type="cust:moreData"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="CustomerNameType">
          <xs:sequence>
               <xs:element name="lastname" type="xs:string"/>
               <xs:element name="firstname" type="xs:string"/>
               <xs:element name="title" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="anotherBitOfData" type="xs:gMonthDay"/>
     <xs:complexType name="moreData">
          <xs:sequence>
               <xs:element name="data1" type="xs:string"/>
               <xs:element name="data2" type="xs:long"/>
          </xs:sequence>
     </xs:complexType>
</xs:schema>
---CustomerData.xsd Stop---
---CustomerPriority.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:pri="http://www.test.org/priority" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.org/priority" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:element name="CustomerPriority">
          <xs:annotation>
               <xs:documentation>Comment describing your root element</xs:documentation>
          </xs:annotation>
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="priority" type="pri:PriorityLevelType"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="PriorityLevelType">
          <xs:choice>
               <xs:element name="Level1Value" type="xs:string"/>
               <xs:element name="Level2Value" type="xs:string"/>
               <xs:element name="Level3Value" type="xs:string"/>
          </xs:choice>
     </xs:complexType>
</xs:schema>
---CustomerPriority.xsd Stop---
---DataType.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ndata="http://www.test.org/ndata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pri="http://www.test.org/priority" targetNamespace="http://www.test.org/ndata" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:import namespace="http://www.test.org/priority"
          schemaLocation="CustomerPriority.xsd" />
     <xs:complexType name="newDataType">
          <xs:sequence>
               <xs:element name="pri" type="xs:string" />
          </xs:sequence>
     </xs:complexType>
</xs:schema>
---DataType.xsd Stop---

Similar Messages

  • Full qualified host name not appearing in url within WSDL generated from PI

    Hi
       We are on PI711  ( AIX OS ) and are stuck with an issue of the fully qualifed hostname not appearing within WSDL file  generated in PI71 for a webservice it exposes using the Integration builder
    We changed the host name in exchange profile ( all locations ) from hostname to hostname.companyname.intra and also in the ABAP stack as recommended in all OSS notes.
    We use the Integration Directory --> Sender Agreement --> Display WSDL option to generate the WSDL.
    Its to be noted that all locations ( including url for WSDL ) have the fully qualified hostname except the url within the WSDL.
    Dioes anyone come across this issue/ know which parameters to be updated on the PI server to make the url within the WSDL for the PI webservice to have the fully qualified host name ?

    HI Karthik,
    As Mentioned by Baskar donu2019t use proposed URL .. while creating WSDL in Id.. but instead provide URL in following format and use it in that place and create WSDL.. details about URL format..
    the URL format is fix. and it is simple.
    http://host:HTTPPort/XISOAPAdapter/MessagingServlet?channel=party:sendersystem:CC_sender
    in above URL provide your sender service component name instead of sender system.
    and provide SOAP sender communication channel name in place of CC_sender
    provide your PI system host and http name in place of host and https and use this..
    for more details about URL..
    Propose URL when Configuring Sender SOAP Adpater
    soap url
    Thanks,
    Bhupesh

  • Soap Action missing in the WSDL generated for Service Interface

    Hi All,
    I have modelled an interface in the ESR and have created the proxy in the back-end ECC6 system. It is basically an outside-in approach. I have generated a WSDL using the Wizard in the SPROXY transaction. But the WSDL does not have any SOAP Action. I tried to create a web-service for an existing BAPI. That WSDL also did not have any SOAP Action. Can you please let me know why the SOAP Action is missing? Is there any other way of generating the WSDL?
    Regards,
    Geetha

    Hi Geetha,
    Please try configuring the entire scenario in PI.
    If you are using PI 7.1, You can see the WSDL by right clicking on Sender agreement. Please use SENDER SOAP Channel. In PI 7.0 you will have to generate WSDL manually.
    Regards,
    Vikas

  • WSDL generated from java class - how to include headers?

    I am using the servicegen ant task and generating a web service based on a java class. I would like to include a username and password in the soap header and read that info using a handler. I am able to get that working, but how do I get the auto-generated WSDL to include the username/password header information? Is there something that I have to do in the handler so that this information is included in the WSDL?
    Thanks,
    Mike

    I did do this and I got the following error when deploying to the Stand-alone OC4j:
    Operation failed with error:
    Error compiling
    :D:\h\cots\Oracle\JDeveloper10g10.1.3\j2ee\home\applications\DBOperationsWSApp-DBData-WS\WebServices: Error instantiating compiler: webservice artifact generation failed :oracle.j2ee.ws.common.tools.api.ValidationException : Exception declaration mismatch between Implementation: dbdatapackage.DBDataOperations and Interface: dbdatapackage.DBDataWS. Impl class Method: getData declares exceptions not declared by the interface (java.lang.Exception)
    I am quite sure what it is saying. It generated the code for the Interface: dbdatapackage.DVDataWS. Impl class. Why would it not do it right? What expection is it complaining about? java.lang.Exception?

  • Suppress authentication for a WSDL generated from SA

    Hi ,
    I have a SOAP communication channel and generated a wsdl from the sender agreement.
    The WSDL requires authentication information both in design time and run time.
    I would like to suppress(or default) it in both these cases. Is there any way to do this ?
    Thanks for the help.
    Regards
    Bharath

    Hello Bharathwaj ,
                There are two authentication mechanisams available for Web Services, one is the Basic, where we provide login details at design time and runtime in Visual Admin. There is another technique which is by enabling Client Certificates (i.e. X.508 Client certificate).  You can use Client Certificate mechanisam  and suppress the authorization details at design time and runtime.
    Refer this blog for further information
    [Consuming Web Service|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0647127850DB00972051598695383049End?blog=/pub/wlg/1012]
    [Consuming Via Certificates|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a9419c0d-0301-0010-bd84-93978e7ef13a&overridelayout=true]
    Regards,
    Prasanna

  • WAS 6.20: Why does WSDL generated from BAPI includes the data type BCD3.0?

    Hello,
    I'm trying to invoke a BAPI (specifically BAPI_REQUISITION_GETDETAIL) via WAS 6.20 however the WSDL that's returned from the Web Service Browser contains the following Schema:
    <xsd:element name="GR_PR_TIME" minOccurs="0" type="xsd:bcd3.0"/>
    The xsd namespace prefix is defined as follows:
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    .NET is complaining about this data type with the following parser error:
    Schema parsing error Type 'http://www.w3.org/2001/XMLSchema:bcd3.0' is not declared.
    and as far as I can tell binary coded decimal (bcd) isn't part of the Schema specification.
    Can anyone shed any insight as to why serialization is occurring this way and if there's anyway to correct or work around it?
    Thanks,
    Jay
    Where

    your noise margin increasing from 6 to 9 after you previously had it reset is a good indication there is a problem
    did you try thr quiet line test?
    are you connected directly to the master or test socket?   do you have other sockets apart from the master?
    you can try this post for other ideas 
    http://community.bt.com/t5/BB-in-Home/Poor-Broadband-speed/m-p/14217#M8397
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • STO generated from TLB without reference of Purchase Requisition

    Dear SAP Gurus,
    We are using TLB to generate STO from confirmed Purchase Requisition from Deployment execution and the Stock Transfer Orders are generated in the ECC side without reference to the purchase requisition.
    Do you know how to solve this issue?
    Thanks and BR
    Mauricio

    Hi,
    Did something similar on a 4.0a system years ago, maybe this will help.
    My notes say:
    PO create, stock transfer order
    enter order type (ours was customized version - probably so that the copy rules from PR - PO were set correctly)
    Create with reference to P.Req.
    on the pop-up box remove the 'U' (think that was the key bit)
    continue
    select item, copy +details
    Save, STO created
    Regards,

  • PReq not generated from Service Order SM03 using Control Key SM02

    Hi,
    The PReq is not getting generated for Control Key SM02 for service order SM03. I am using PReq generation as "Immediately". The issue is I am filling all the required fileds in the External Processing Operation Popup Screen & saving my Service Order. After that when i check the Document flow - there is no Preq number & in Actual Data for External opration, i find the fileds i have filled in the Preq popup screen as blank (such as Material group, Purc. grp, cost element, vendor etc). I have checked the config also, but cant find any clue.
    Thanks.

    did you check the control key settings for sm02?
    is it happening for this control key with other order types nd sm03 order type with sm03 ( external services ) control key?
    is it possible to replicate it? it is also possible tht the order didnt get saved as the user didnt see some warning info in the bottom bar

  • Error while selecting from view that references external table

    Can someone explain why the error near the bottom of the code below is occuring? If USER1 grants SELECT on the external table to USER2, then USER2 can select from the view without any problems; however, I want to avoid giving USER2 access to all of the columns in the external table. (I only want to give USER2 access to two of the four columns.)
    SQL> CONNECT sys AS SYSDBA
    Connected as SYS@ as sysdba
    SQL> CREATE USER user1 IDENTIFIED BY user1
    User created.
    SQL> CREATE USER user2 IDENTIFIED BY user2
    User created.
    SQL> GRANT CONNECT, CREATE TABLE, CREATE VIEW TO user1
    Grant complete.
    SQL> GRANT CONNECT TO user2
    Grant complete.
    SQL> GRANT READ, WRITE ON DIRECTORY EXT_DATA_DIR TO user1, user2
    Grant complete.
    SQL> CONNECT user1/user1
    Connected as USER1@
    SQL> CREATE TABLE emp_xt
      emp_id     NUMBER,
      first_name VARCHAR2(30),
      last_name  VARCHAR2(30),
      phone      VARCHAR2(15)
    ORGANIZATION EXTERNAL
      TYPE ORACLE_LOADER
      DEFAULT DIRECTORY EXT_DATA_DIR
      ACCESS PARAMETERS
        RECORDS DELIMITED BY NEWLINE
        FIELDS TERMINATED BY ','
        OPTIONALLY ENCLOSED BY '"'           
      LOCATION ('emp.txt')
    REJECT LIMIT 0
    Table created.
    SQL> SELECT COUNT(1) FROM emp_xt
      COUNT(1)
             4
    1 row selected.
    SQL> CREATE OR REPLACE VIEW emp_xt_view AS SELECT first_name, last_name FROM emp_xt;
    View created.
    SQL> SELECT COUNT(1) FROM emp_xt_view
      COUNT(1)
             4
    1 row selected.
    SQL> GRANT SELECT ON emp_xt_view TO user2
    Grant complete.
    SQL> CONNECT user2/user2
    Connected as USER2@
    SQL> SELECT COUNT(1) from user1.emp_xt_view
    SELECT COUNT(1) from user1.emp_xt_view
    Error at line 0
    ORA-29913: error in executing ODCIEXTTABLEOPEN callout
    ORA-29400: data cartridge error
    ORA-04043: object "USER1"."EMP_XT" does not exist
    SQL> CONNECT user1/user1
    Connected as USER1@
    SQL> GRANT SELECT ON user1.emp_xt TO user2
    Grant complete.
    SQL> CONNECT user2/user2
    Connected as USER2@
    SQL> SELECT COUNT(1) from user1.emp_xt_view
      COUNT(1)
             4
    1 row selected.
    {code}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    user503699 wrote:
    user1983440 wrote:
    Can someone explain why the error near the bottom of the code below is occuring? If USER1 grants SELECT on the external table to USER2, then USER2 can select from the view without any problems; however, I want to avoid giving USER2 access to all of the columns in the external table. (I only want to give USER2 access to two of the four columns.)As you have demonstrated, I guess the view approach only works for database tables. External tables are actually files on the file system. Even through OS, it is not possible to grant READ/WRITE access to only part of the file. The access is for entire file. An "External Table" is just a "wrapper" provided by oracle (using data cartridge) to allow user to be able to access the file as a "table". So it can definitely not do something that underlying OS can not do.
    p.s. In fact, oracle does not even allow to edit data in external tables using SQL.Why not just make a second external table (only including the 2 columns you need) and grant select directly on that to the user. I know you say "views only" but there's an exception to every rule ... just because it's called a table doesn't make it so. You could argue an external table is nothing more than a fancy view.
    Worst case, make a view on top of the second external table.
    CREATE TABLE emp_xt_less_information
      first_name VARCHAR2(30),
      last_name  VARCHAR2(30)
    ORGANIZATION EXTERNAL
      TYPE ORACLE_LOADER
      DEFAULT DIRECTORY EXT_DATA_DIR
      ACCESS PARAMETERS
        RECORDS DELIMITED BY NEWLINE
        FIELDS TERMINATED BY ','
        OPTIONALLY ENCLOSED BY '"'   
             emp_id      number,
             first_name  char,
             last_name   char,
             phone       char
      LOCATION ('emp.txt')
    REJECT LIMIT 0
    {code}
    Should do it, but my syntax may be off a touch ....                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Failure to generate WSDL from web service when use xmlbean

    Hi, I have a web service that uses xmlbean generated by schema. The schema from 3rd party is in a separate project since it's used by another web app and ejb project. In wlw103 I have included the schema project in this web service project's Java Build Path. The web service compiles, but when I tried to generate WSDL a Error window shows and says "The WSDL cannot be generated from the web service due to unexpected runtime errors".
    The following is the detail. What do I need to do to make the xmlbean available for my web service? Thanks
    com.bea.workshop.webservices.core.gen.WebServicesException: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
         at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:335)
         at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.accessCompiler(WebServiceCompilerImpl.java:390)
         at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile0(WebServiceCompilerImpl.java:330)
         at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile(WebServiceCompilerImpl.java:275)
         at com.bea.workshop.webservices.ui.actions.GenerateWsdlFromJwsAction.run(GenerateWsdlFromJwsAction.java:169)
         at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
    Caused by: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
         at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:526)
         at weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:483)
         at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:333)
         ... 46 more
    Caused by: weblogic.wsee.tools.WsBuildException: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
         at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:227)
         at weblogic.wsee.tools.jws.wsdl.WsdlBuilder.processImpl(WsdlBuilder.java:43)
         at weblogic.wsee.tools.jws.jaxrpc.JAXRPCProcessor.process(JAXRPCProcessor.java:27)
         at weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProcessor.java:47)
         at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:522)
         ... 48 more
    Caused by: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
         at weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplodedTylar(SoapAwareJava2Schema.java:1414)
         at weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.createBuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:216)
         at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:223)
         ... 52 more

    HI,
    I hope this issue can resolved by adding this patch CR349256
    Try to contact weblogic support to get more details about this patch.
    Regards,
    Kal.

  • Invocation of Netweaver generated Web Service from XI

    Hi,
    I have defined a webservice for a stateless session bean using the developer studio. From the wsdl I have imported the message interface as external definition. I have defined mappings on the respective message type. Now I would like to call my service using the SOAP receiver adapter.
    Could anybody tell me which URL has to be quoted there. I retrieve the wsdl from the following address:
    http://myhost:50000/AddressService/AddressConfig?wsdl
    Since the webservice is RPC like, is it valid to invoke it using the SOAP receiver adapter?
    Kind regards,
    Heiko

    Hi Naveen,
               Do you have an answer for this ....
    Hi Friends,
    I have a question regarding publishing a WSDL created via XI (Integration Directory) to a UDDI Server of SAP WAS JAVA 640. Can I publish the WSDL generated from XI in the UDDI Server provided as a part of SAP WAS 640 ? I know that the WSDL will be specific for a client( sender) but I feel that its better than emailing the WSDL to the client after generating it in the integration directory. Any relevant documents, links explaining how to do that will be appreciated.
    The above question was asked by Siva Maranani before. His question was as below .
    "I know that whenever a webservice is developed using NDS it can be deployed in WebAs and the same can be registered in UDDI ( webAs acting as UDDI registry).
    Now my requirement is to register a WSDL file (which describes) for an external webservice. Can WebAs be used as a UDDI registry..?
    I like to know if this is possible or not..? if yes.. how..?"
    Waiting for the reply...
    Thanks & Regards,
    Mathew

  • Externalize wsdl url from

    Hello
    Can we externalize wsdl url ( get wsdl url from property in runtime) from wsimport generated stub though changing server handle by changing location from property file.
    Regards
    Haroon Idrees

    Yes, you can use WSDL generated from ICO. ICO simply represents combination of RD,ID and agreement objects.

  • Parameter names change when generating web service from WSDL

    Hi,
    I have a problem with BEAs web services that I'm hoping someone can help me with.
    I have a
    WSDL file, and from that I want to generate a web service implementation and a
    web service
    client. In the WSDL file, I have a message defined like this:
    <message name="someRequest">
    <part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
    name="data"/>
    </message>
    I generate the server using the server using the wsdl2service Ant task, I implement
    the necessary classes, and I deploy it. When I access the deployed web service,
    the parameter name has changed, from "data" to "bytes". If I access the WSDL file
    of the deployed web service, it says:
    <message name="someRequest">
    <part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
    name="bytes"/>
    </message>
    This happens for all parameters, string parameters are renamed to "string", base64Binary
    parameters are renamed to "bytes", etc...
    This poses a problem to me, because if I generate a web service client from the
    original WSDL file, it will not be able to talk to my web service. Is there any
    way of forcing a web service generated from a WSDL file to keep the parameter
    names of the original WSDL file?
    Any help in this is greatly appreciated.
    Regards,
    Petter

    From a quick look of your WSDL, it seams that you are mixing document-literal-bare and document-literal-wrapped flavor of web services. WSA may be able to do a better job at working around this mixed flavors than JDeveloper.
    If you have hand crafted this WSDL, I would recomend that you spend some time looking at the way WSDL are generated, with the java-first mode (or bottom-up), then author the WSDL you need for the final service.
    Here are sample of bare-style :
    <xsd:element name="getPupilAddressResponse" type="xsd:string"/>
    <xsd:element name="getPupilAddressRequest" type="xsd:int"/>
    Wrapped will looks like that:
    <xsd:element name="getSENLevelResponse">
    <xsd:complexType>
    <xsd:sequence maxOccurs="1" minOccurs="1">
    <xsd:element name="LevelDetails" type="tns:SENLevelRecord"/>
    <xsd:element name="RecordCount" type="xsd:int">
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    Hope this helps,
    Eric

  • Problem using WSDL from SAP in IBM's RAD for generating web service client

    When importing a WSDL from the ABAP stack on a SAP 6.40 system into IBM's RAD tool for generating a web service client there are errors with the soap fault classes that get generated.  The WSDL declares the types for the faults with WebServiceName.RfcException and these have elements of name, text, and message.  When the tools see this in the WSDL they generate classes that extend the Java exeception class and this causes an error because the "message" name conflicts with the standard java exception message.  Has anyone else ran into this problem?  It seems like a basic problem many java tools for generating web service client proxies would have because the soap faults get turned into java exceptions.  This name conflict of the java exception with the WSDL fault definition means that code always needs to be adjusted and cannot simply use the classes that are generated from the WSDL.  Anyone run across this or a similar problem in the java environment using the SAP WSDL?
    Aaron

    Hi,
    Hello again .
    Have you tried your service using soapui ?
    You can use your WSDL as input .
    In order to eliminate eclipse problem try this service:(I just did)
    http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
    Regards.
    package main;
    import java.io.FileInputStream;
    import java.rmi.RemoteException;
    import java.util.Properties;
    import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapType;
    import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapTypeProxy;
    import org.oorsprong.www.websamples_countryinfo.TCountryCodeAndName;
    public class Main {
    public static void main(String[] args) {
      try {
       final Properties properties = new Properties();
       properties.load(new FileInputStream("properties.ini"));
       System.getProperties().putAll(properties);
      } catch (final Exception exception) {
       exception.printStackTrace();
      new Main();
    public Main() {
      try {
       final CountryInfoServiceSoapType infoServiceSoapType = new CountryInfoServiceSoapTypeProxy();
       final TCountryCodeAndName[] tCountryCodeAndNames = infoServiceSoapType.listOfCountryNamesByName();
       for (final TCountryCodeAndName tCountryCodeAndName : tCountryCodeAndNames) {
        System.out.println(tCountryCodeAndName.getSName());
      } catch (final RemoteException exception) {
       exception.printStackTrace();

  • The difference of jar files that were generated from wsdl

    hello there:
    I used maven's jaxws plugin to generate jar files from two wsdl links. The links are pretty much the same except for one line:
    <wsdlsoap:address location="http://<env>.XXXXXX"the <env> indicate the environment is a prod or uat. Other than that, the wsdl is the same.
    The question is, can the jars generated from respective wsdl be used interchangably? I did notice there a few bytes different from the resultant two jars, and the test shows they CAN'T be used interchangably.
    Can anyone explain why?
    Thanks,
    Johnny

    You may use them interchangeably if the code that uses the classes in the jar(s) does not depend on the default address of the web service but instead always passes the URL during initialization of such stub classes.

Maybe you are looking for

  • Payload not Serializable

    Hi everyone, I have implemented an asynchronous web service based on a MDB EJB. Here is the part of the web-services.xml that describes this web service : <web-service name="MOCBean" targetNamespace="moc" uri="/MOCBean"> <components> <jms-send-destin

  • Rob Papen is not showing up in my plugins

    I installed rob papen blue,blade and punch to my mac and when i open logic and look for my plugins none of them are showing up.

  • Question about safari status bar

    Hi All, I have a web application , mainpage contained an iframe . the Page in iframe will set data to status bar . And mainpage will scan status bar by a timer to get the update info . All the flow was controlled by JavaScript . It works fine with IE

  • Wt taxed at supplemental rate and other wt at regular rate

    How do we define a wage type for supplemental tax rate and regular tax rate? Thanks Charlene

  • Best way to implement a docking container

    Hi everyone, I need to create a docking container that behaves the same way the draggable panel system works in Flex Builder (Eclipse): - Dock other containers to the edges - Automatically layout other containers when the dragged container is docked