XMLBean generation from WSDL file

I have used workshop for weblogic 9.2 to generate web service from wsdl files. The problem is however, that the (XmlBean) code generated from the <wsdl:fault name="..... /> does not genetate a "Throwable" object. The resulting methods produced by the Web Services -> Generate Web Service... menu option produces code that cannot be compiled, because the (generated) throws clause uses an object that is not derived from Throwable.
Has anyone else had these symptoms? is there a fix?
Thanks
Alan

Have you tried pulling the schema out of the wsdl and putting it in a xsd file and see if it validates?
Otherwise, have you tried removing the xmlns:"" from <WL5G3N0:definitions xmlns:"".
Edited by: C.Stodden on Oct 11, 2012 8:52 AM

Similar Messages

  • Problem in client generation from wsdl file

    Hi i am trying to generate client from a wsdl file through apache cxf framework, but it throws WSDLRefValidator error.
    Here is the error statment:
    Oct 11, 2012 11:51:33 AM org.apache.cxf.tools.validator.internal.WSDLRefValidator collectValidationPoints
    WARNING: WSDL document file:/D:/latestWS20120925/WebServiceTest26092012/WebContent/wsdl/PlmWebserviceImportGcas.wsdl does not define any services
    WSDLToJava Error:
    line 5 column 646 of file:/D:/latestWS20120925/WebServiceTest26092012/WebContent/wsdl/PlmWebserviceImportGcas.wsdl: cvc-complex-type.2.4.a: Invalid content was found starting with element 'WL5G3N0:definitions'. One of '{"http://www.w3.org/2001/XMLSchema":include, "http://www.w3.org/2001/XMLSchema":import, "http://www.w3.org/2001/XMLSchema":redefine, "http://www.w3.org/2001/XMLSchema":annotation, "http://www.w3.org/2001/XMLSchema":simpleType, "http://www.w3.org/2001/XMLSchema":complexType, "http://www.w3.org/2001/XMLSchema":group, "http://www.w3.org/2001/XMLSchema":attributeGroup, "http://www.w3.org/2001/XMLSchema":element, "http://www.w3.org/2001/XMLSchema":attribute, "http://www.w3.org/2001/XMLSchema":notation}' is expected.
    org.apache.cxf.tools.common.ToolException:
    line 5 column 646 of file:/D:/latestWS20120925/WebServiceTest26092012/WebContent/wsdl/PlmWebserviceImportGcas.wsdl: cvc-complex-type.2.4.a: Invalid content was found starting with element 'WL5G3N0:definitions'. One of '{"http://www.w3.org/2001/XMLSchema":include, "http://www.w3.org/2001/XMLSchema":import, "http://www.w3.org/2001/XMLSchema":redefine, "http://www.w3.org/2001/XMLSchema":annotation, "http://www.w3.org/2001/XMLSchema":simpleType, "http://www.w3.org/2001/XMLSchema":complexType, "http://www.w3.org/2001/XMLSchema":group, "http://www.w3.org/2001/XMLSchema":attributeGroup, "http://www.w3.org/2001/XMLSchema":element, "http://www.w3.org/2001/XMLSchema":attribute, "http://www.w3.org/2001/XMLSchema":notation}' is expected.
         at org.apache.cxf.tools.validator.internal.SchemaValidator.validate(SchemaValidator.java:203)
         at org.apache.cxf.tools.validator.internal.SchemaValidator.validate(SchemaValidator.java:119)
         at org.apache.cxf.tools.validator.internal.SchemaValidator.isValid(SchemaValidator.java:103)
         at org.apache.cxf.tools.validator.internal.WSDL11Validator.isValid(WSDL11Validator.java:157)
         at org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.validate(JAXWSDefinitionBuilder.java:204)
         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:182)
         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:142)
         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:300)
    The excerpt from wsdl file is provided below:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="PlmWebserviceImportGcas.wsdl" targetNamespace="D:/webservice">
    <wsdl:types>
    <xsd:schema xmlns="http://www.pg.com/css/webservice" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.pg.com/css/webservice">
    *<WL5G3N0:definitions xmlns="" xmlns:WL5G3N0="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N1="http://www.pg.com/Inputs/HubPollForTSStatusInput" xmlns:WL5G3N2="http://www.pg.com/Outputs/HubPollForTSStatusOutput" xmlns:WL5G3N3="http:/www.pg.com/productNet/HubSubmitForumlatoCSSInput" xmlns:WL5G3N4="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput" xmlns:WL5G3N5="http://www.pg.com/Inputs/HubDeleteTSRequestInput" xmlns:WL5G3N6="http://www.pg.com/Outputs/HubDeleteTSRequestOutput" xmlns:WL5G3N7="http://www.pg.com/WS/FormulaHubWS" xmlns:WL5G3N8="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://www.pg.com/WS/FormulaHubWS">*
    <WL5G3N0:types>
    <xsd:schema xmlns="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput" xmlns:CSS_SubmitFormulaOutput.xsd="http://pg.com/Inputs/CSS_SubmitFormulaOutput" xmlns:ns2="http://www.pg.com/Inputs/HubPollForTSStatusInput" xmlns:ns3="http://www.pg.com/Outputs/HubPollForTSStatusOutput" xmlns:ns4="http:/www.pg.com/productNet/HubSubmitForumlatoCSSInput" xmlns:ns5="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput" xmlns:ns6="http://www.pg.com/Inputs/HubDeleteTSRequestInput" xmlns:ns7="http://www.pg.com/Outputs/HubDeleteTSRequestOutput" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.pg.com/WS/FormulaHubWS" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput">
                                  <xsd:import namespace="http://pg.com/Inputs/CSS_SubmitFormulaOutput"/>
                                  <xsd:element name="SubmitFormulatoCSSOutput">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element ref="CSS_SubmitFormulaOutput.xsd:SubmitFormulatoCSS_Output"/>
    It seems to be problem with tag WL5G3NO declaration.
    Can anyone suggest how to rectify this?
    Thanks

    Have you tried pulling the schema out of the wsdl and putting it in a xsd file and see if it validates?
    Otherwise, have you tried removing the xmlns:"" from <WL5G3N0:definitions xmlns:"".
    Edited by: C.Stodden on Oct 11, 2012 8:52 AM

  • Error while generating java client code from wsdl file

    I am trying to generate a java client code from WSDL file um_workflowSaveCreateProfile.wsdl which includes um_workflowSaveCreateProfile_interface.wsdl file, so I am keeping both the files in the same folder and trying to generate the client code but it is showing me the below error highlighted .
    um_workflowSaveCreateProfile.wsdl
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="E:/DIPPWF/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:obinterface="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile">
         <import namespace="D:/DIPP/WSDL/um_workflowSaveCreateProfile_interface" location="um_workflowSaveCreateProfile_interface.wsdl"/>
         <service name="OblixIDXML_um_workflowSaveCreateProfile_Service">
              <port name="OblixIDXML_um_workflowSaveCreateProfile_Port" binding="obinterface:OblixIDXML_um_workflowSaveCreateProfile_Binding">
                   <soap:address location="http://localhost:7777/identity/oblix/apps/userservcenter/bin/userservcenter.cgi"/>
              </port>
         </service>
    </definitions>
    um_workflowSaveCreateProfile_interface.wsdl
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:oblixxmllocalschema="http://www.oblix.com/OblixXMLLocalSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface">
         <types>
              <xsd:schema targetNamespace="http://www.oblix.com/" elementFormDefault="qualified"
                   xmlns="http://www.oblix.com/"
                   xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                        <xsd:include schemaLocation="../XMLSchema/common_parameters.xsd" />
                        <xsd:include schemaLocation="../XMLSchema/common_authentication.xsd" />
                        <xsd:include schemaLocation="../XMLSchema/workflowSaveCreateProfile.xsd" />
              </xsd:schema>
              <xsd:schema targetNamespace="http://www.oblix.com/OblixXMLLocalSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                   <xsd:element name="request">
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="params">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element ref="oblix:ObWorkflowName"/>
                                                 <xsd:element ref="oblix:ObDomainName"/>
                                                 <xsd:element ref="oblix:ObWfComment" minOccurs="0"/>
                                                 <xsd:element ref="oblix:noOfFields"/>
                                                 <xsd:element ref="oblix:AttributeParams"/>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                             <xsd:attribute name="version" type="xsd:string" use="optional"/>
                             <xsd:attribute name="application" type="xsd:string" use="required" />
                             <xsd:attribute name="function" type="xsd:string" use="required" />
                             <xsd:attribute name="mode" type="xsd:string" use="optional"/>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:schema>
         </types>
         <message name="OblixIDXMLInput">
              <part name="authentication" element="oblix:authentication"/>
              <part name="request" element="oblixxmllocalschema:request"/>
         </message>
         <message name="OblixIDXMLOutput">
              <part name="body" element="oblix:Oblix"/>
         </message>
         <portType name="OblixIDXMLPortType">
              <operation name="OblixIDXML_um_workflowSaveCreateProfile">
                   <input message="tns:OblixIDXMLInput"/>
                   <output message="tns:OblixIDXMLOutput"/>
              </operation>
         </portType>
         <binding name="OblixIDXML_um_workflowSaveCreateProfile_Binding" type="tns:OblixIDXMLPortType">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="OblixIDXML_um_workflowSaveCreateProfile">
                   <soap:operation soapAction="http://www.oblix.com/"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
         </binding>
    </definitions>
    I am using WSDL2 Java for generating the client code .
    Please suggest where am I wrong .
    E:\axis2-1.4\bin>WSDL2Java -uri E:\DIPPWF\um_workflowSaveCreateProfile.wsdl -p R
    ND -d adb -s -o build\client--http-proxy-host 10.74.93.35 --http-proxy-port 80
    Using AXIS2_HOME: E:\axis2-1.4
    Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0_02
    Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
    Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
    ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
    ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
    owSaveCreateProfile.xsd'.
    Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
    rkflowSaveCreateProfile.xsd'.
    Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
    ma/workflowSaveCreateProfile.xsd'.
    Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
    omponent_basic.xsd'.
    Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
    nt_basic.xsd'.
    Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
    F/XMLSchema/workflowSaveCreateProfile.xsd'.
    Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
    Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
    ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
    ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
    owSaveCreateProfile.xsd'.
    Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
    rkflowSaveCreateProfile.xsd'.
    Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
    ma/workflowSaveCreateProfile.xsd'.
    Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
    omponent_basic.xsd'.
    Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
    nt_basic.xsd'.
    Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
    F/XMLSchema/workflowSaveCreateProfile.xsd'.
    *[ERROR] More than one part for message OblixIDXMLInput*
    org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
    More than one part for message OblixIDXMLInput
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1162)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1085)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
    ng(WSDL11ToAxisServiceBuilder.java:686)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    int(WSDL11ToAxisServiceBuilder.java:538)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    ints(WSDL11ToAxisServiceBuilder.java:489)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
    ce(WSDL11ToAxisServiceBuilder.java:363)
    at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
    llServices(WSDL11ToAllAxisServicesBuilder.java:107)
    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
    ionEngine.java:147)
    at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
    at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
    Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
    : Error parsing WSDL
    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
    ionEngine.java:153)
    at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
    at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
    Caused by: org.apache.axis2.AxisFault: More than one part for message OblixIDXML
    Input
    at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
    ce(WSDL11ToAxisServiceBuilder.java:397)
    at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
    llServices(WSDL11ToAllAxisServicesBuilder.java:107)
    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
    ionEngine.java:147)
    ... 2 more
    Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
    gException: More than one part for message OblixIDXMLInput
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1162)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1085)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
    ng(WSDL11ToAxisServiceBuilder.java:686)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    int(WSDL11ToAxisServiceBuilder.java:538)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    ints(WSDL11ToAxisServiceBuilder.java:489)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
    ce(WSDL11ToAxisServiceBuilder.java:363).
    Thanks in advance.
    akshay

    Hello,
    Were you able to resolve this issue ?
    I am seeing the same issue and at my wits end.
    regards
    Amit

  • How to generate java file from WSDL file

    Hi friends,
    I am new to this thing, so that's why I need some guidence .
    I need to generate java file programatically from existing wsdl file.
    I thought the ways - to use xmlbeans apache library or jaxb.
    Can you suggest what will be better way to generate java file from wsdl? can you please be more descriptive and can you direct me to appropriate link?
    Thanks.
    Harshit

    xmlbeans apache provides easiest way to create java file from wsdl there is very good link for that
    http://www.ibm.com/developerworks/webservices/library/ws-soa-clientxmlbeans.html
    If you want more programmatic approach then Jaxb will be a better option

  • Error in generating adobe interactive form created from WSDL file

    Hi,
    I have created a form in SFP from a WSDL file.Copy paste the below program and when i run the program it gives me error message
    "_Adobe reader could not open ..Because it is either not supported file type or has been damaged (...)"_. I am not sure whether i am doing right.If this is not the right one, then how can i generate a interactive PDF from WSDL.
    DATA: ie_outputparams TYPE sfpoutputparams.
    DATA: i_name TYPE fpname,
    i_funcname TYPE funcname.
    DATA: fp_docparams TYPE sfpdocparams.
    DATA: fp_formoutput TYPE fpformoutput.
    DATA: data_tab TYPE solix_tab.
    ie_outputparams-getpdf = 'X'.
    ie_outputparams-nodialog = 'X'. " suppress printer dialog popup
    CALL FUNCTION 'FP_JOB_OPEN'
      CHANGING
        ie_outputparams = ie_outputparams.
    TRY.
       i_name = 'ZSPADOBE01'. "your form name
      i_name = 'Z....'. "your form name
        CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
          EXPORTING
            i_name     = i_name
          IMPORTING
            e_funcname = i_funcname.
      CATCH cx_fp_api_repository.
      CATCH cx_fp_api_usage.
      CATCH cx_fp_api_internal.
    ENDTRY.
    fp_docparams-langu = 'E'.
    fp_docparams-country = 'US'.
    fp_docparams-fillable = 'X'.
    CALL FUNCTION i_funcname
      EXPORTING
        /1bcdwb/docparams  = fp_docparams
      IMPORTING
        /1bcdwb/formoutput = fp_formoutput
      EXCEPTIONS
        usage_error        = 1
        system_error       = 2
        internal_error     = 3.
    CALL FUNCTION 'FP_JOB_CLOSE'
      EXCEPTIONS
        usage_error    = 1
        system_error   = 2
        internal_error = 3
        OTHERS         = 4.
    DATA: filename TYPE string,
    path TYPE string,
    fullpath TYPE string,
    default_extension TYPE string VALUE 'PDF'.
    cl_gui_frontend_services=>file_save_dialog(
    EXPORTING
    default_extension = default_extension
    CHANGING
    filename = filename
    path = path
    fullpath = fullpath ).
    CHECK fullpath IS NOT INITIAL.
    CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
      EXPORTING
        buffer     = fp_formoutput-pdf
      TABLES
        binary_tab = data_tab.
    cl_gui_frontend_services=>gui_download(
    EXPORTING
    filename = filename
    filetype = 'BIN'
    CHANGING
    data_tab = data_tab ).
    cl_gui_frontend_services=>execute(
    EXPORTING
    document = filename ).

    Hi Sanu,
    Hope this link help you.
    [CALLING WEB SERVICES IN INTERACTIVE ADOBE FORMS|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20280d13-7b93-2e10-51a0-ba05fd26355a]
    Regards,
    Shaira

  • Java implementation from WSDL file

    Hello All
    I am working on my thesis and have to deal with web services. I have a WSDL file where I have to create the Java implementation for and deploy it to TomCat which is comming with JWSDP1.3.
    The steps I do are as follow:
    1. Get the WSDL file
    2. Create the config.xml file
    3. run wscompile with "-import" option
    4. implement service implementation (provider interface)
    5. run wsdeploy tool
    All tools are running successfully without exception. When I try to access the webservice I receive the following message from tomcat:
    "No JAX-RPC context information available."
    and I cannot access the webservice from my client program. The "hello" example works with my setup.
    Below, please find my WSDL file and my config file as well as my provider interface implementation.
    Thanks for your help.
    ===========
    calculatesqrt1.wsdl:
    <definitions xmlns:tns="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1.wsdl" name="Calculatesqrt1">
         <types/>
         <message name="CalculatesqrtProvider1_sqrt">
              <part name="double_1" type="xsd:double"/>
         </message>
         <message name="CalculatesqrtProvider1_sqrtResponse">
              <part name="result" type="xsd:double"/>
         </message>
         <portType name="CalculatesqrtProvider1">
              <operation name="sqrt" parameterOrder="double_1">
                   <input message="tns:CalculatesqrtProvider1_sqrt"/>
                   <output message="tns:CalculatesqrtProvider1_sqrtResponse"/>
              </operation>
         </portType>
         <binding name="CalculatesqrtProvider1Binding" type="tns:CalculatesqrtProvider1">
              <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="sqrt">
                   <input>
                        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calculatesqrt1.wsdl"/>
                   </input>
                   <output>
                        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calculatesqrt1.wsdl"/>
                   </output>
                   <soap:operation/>
              </operation>
         </binding>
         <service name="Calculatesqrt1">
              <port name="CalculatesqrtProvider1Port" binding="tns:CalculatesqrtProvider1Binding">
                   <soap:address location="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1"/>
              </port>
         </service>
    </definitions>
    ===========
    config.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
         <wsdl location="Calculatesqrt1.wsdl" packageName="calcusqrt1">
         </wsdl>
    </configuration>
    ============
    CalculatesqrtServiceImpl1.java:
    package calcusqrt1;
    public class CalculatesqrtServiceImpl1 implements calcusqrt1.CalculatesqrtProvider1 {
      public double sqrt(double double0) {
        return Math.sqrt(double0);

    Please post future JAXRPC related questions to [email protected]
    Sounds like it did not get deployed properly on the web server. You should be able to hit the URL for the
    web service in a web browser to get an information.
    The client will use the address stored in the WSDL to access the webservice, please make sure that it is correct. If you download the WSDL from the deployed service the address should be fixed up for you.

  • Server Proxy generation from WSDL in ABAP

    Hi ,
    I have  a WSDL file. Using transaction SPROXY i am abe to generate Cient proxy in ECC 6.0.
    Can i generate a erver Proxy also from the WSDL?
    Ifyes , then what is the approach , transaction etc to so, Any refeence document would be helpful.
    If no , then what should i use , to generate the Server Proxy.
    My scenario is that I have designing an Enterprise Service via Top - Down Approach . I have designed the Interface with operations and generated the Wsdl . now i need to generate the Server proxy  in ABAP SDL , so that i can write the implementation of the service in ABAP.
    Any help would be appriciated
    Thank You
    I

    Hoping to resurrect this thread. I have the exact same requirement. Anyone figured out how to do this?

  • Client API generation from WSDL.

    Hi,
    Could any one guide as how to generate the client from WSDL? I am using RAD7/Eclipse.
    When i try to generate it gives below error.
    Errors occurred during wsimport.
      warning: src-resolve.4.2: Error resolving component 'ns1:pagedata'. It was detected that 'ns1:pagedata' is in namespace 'urn:SCenter-Data-Svc-SubmissionWorkflowSvc:CreateSubmissionWorkItemRequest', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'. If this is the incorrect namespace, perhaps the prefix of 'ns1:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8
    warning: src-resolve.4.2: Error resolving component 'ns2:pagedata'. It was detected that 'ns2:pagedata' is in namespace 'urn:SCenter-Data-Svc-SubmissionWorkflowSvc:CreateSubmissionWorkItemResponse', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'. If this is the incorrect namespace, perhaps the prefix of 'ns2:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8
    warning: src-resolve.4.2: Error resolving component 'ns3:pagedata'. It was detected that 'ns3:pagedata' is in namespace 'urn:SCenter-Data-Svc-BrokerInfo:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns3:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns4:pagedata'. It was detected that 'ns4:pagedata' is in namespace 'urn:SCenter-Data-Svc-ClientInfo:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns4:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns5:pagedata'. It was detected that 'ns5:pagedata' is in namespace 'urn:SCenter-Data-Svc-State:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns5:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns6:pagedata'. It was detected that 'ns6:pagedata' is in namespace 'urn:SCenter-Data-Svc-SubmissionInfo:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns6:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns7:pagedata'. It was detected that 'ns7:pagedata' is in namespace 'urn:SCenter-Data-Svc-Exception:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema2'. If this is the incorrect namespace, perhaps the prefix of 'ns7:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema2'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema2
    error: Invalid header "ServiceInvoker" of binding operation "CreateSubmissionWorkItem": not literal
      Invalid header "ServiceInvoker" of binding operation "CreateSubmissionWorkItem": not literalCan any one tell us what is happening?

    just like the error message says, you are using some namespaces in your wsdl, e.g. "urn:SCenter-Data-Svc-SubmissionWorkflowSvc:CreateSubmissionWorkItemRequest" for which there is no relevant schema import. thus, the code generator cannot find the definition of the types in those namespaces.

  • How to Create Service Interface from WSDL file

    Dear Experts,
    Required your help in below scenario resolution.
    I have a WSDL file , from that WSDL file can I create a service interface.
    If yes than what are the steps for creating the same.
    Thanks & Regards,
    Rathan.

    Rathan,
    PLz chk the below link (PDF file)
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79?quicklink=index&overridelayout=true
    Mutti

  • SSIS Not Detecting Input Service or Method from WSDL File

    I have a WSDL file saved locally (first downloaded from a developer kit, which instructs to save it locally and NOT download it from a public URL), and I'm trying to use it in a Web Service Task in SSIS (2008 R2 Enterprise Edition). I'm pointing to the local
    file in the Web Service Task Editor (General tab). The HTTP Connection is pointing to a URL that has had a successful test connection in the HTTP Connection Manager.
    However, the Input tab dropdown menus for selecting Service and Method are blank. I'm not getting any errors about the WSDL file itself. It looks to be well-formed and valid. I'm not sure why SSIS isn't detecting the services and methods from the WSDL document.
    I tried saving a different WSDL document locally from
    http://graphical.weather.gov, and that worked in a different Web Service Task. I'm guessing there's something wrong with the structure of the WSDL. I saw this
    similar post that makes me think this is indeed the case. 
    The WSDL was accessed with account credentials, so I've redacted identifying information in the code below:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="Service" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:error="http://www.[redacted].com/error" xmlns:co="http://www.[redacted].com/co" xmlns:srv="http://www.[redacted].com/srv" xmlns:tns="http://www.[redacted].com/tns" targetNamespace="http://www.[redacted].com/tns">
    <wsdl:types>
    <xsd:schema>
    <xsd:import namespace="http://www.[redacted].com/XMLSchema/1" schemaLocation="1.xsd"/>
    <xsd:import namespace="http://www.[redacted].com/XMLSchema/2" schemaLocation="2.xsd"/>
    <xsd:import namespace="http://www.[redacted].com/XMLSchema/3" schemaLocation="3.xsd"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="ServiceRequestMessage">
    <wsdl:part name="Body" element="srv:ServiceRequest"/>
    <wsdl:part name="security" element="co:security"/>
    </wsdl:message>
    <wsdl:message name="ServiceResponseMessage">
    <wsdl:part name="Body" element="srv:ServiceResponse"/>
    </wsdl:message>
    <wsdl:message name="ServiceErrorMessage">
    <wsdl:part name="ServiceError" element="error:Errors"/>
    </wsdl:message>
    <wsdl:portType name="ServicePortType">
    <wsdl:operation name="ProcessService">
    <wsdl:input name="ServiceRequest" message="tns:ServiceRequestMessage"/>
    <wsdl:output name="ServiceResponse" message="tns:ServiceResponseMessage"/>
    <wsdl:fault name="ServiceError" message="tns:ServiceErrorMessage"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="ServiceBinding" type="tns:ServicePortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="ProcessService">
    <soap:operation soapAction="http://soap.[redacted].com/binding" style="document"/>
    <wsdl:input name="ServiceRequest">
    <soap:body parts="Body" use="literal"/>
    <soap:header message="tns:ServiceRequestMessage" part="security" use="literal">
    <soap:headerfault message="tns:ServiceErrorMessage" part="ServiceError" use="literal"/>
    </soap:header>
    </wsdl:input>
    <wsdl:output name="ServiceResponse">
    <soap:body parts="Body" use="literal"/>
    </wsdl:output>
    <wsdl:fault name="ServiceError">
    <soap:fault name="ServiceError" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="ServiceService">
    <wsdl:port name="ServicePort" binding="tns:ServiceBinding">
    <soap:address location="https://ws.[redacted].com/service"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Is there anything in this WSDL that SSIS does not support? Or am I just missing something simple? Thanks.

    Hi, you may want to walk through the following threads:
    http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/01/28/consuming-web-services-in-ssis-script-task.aspx
    http://stackoverflow.com/questions/21596429/using-https-wsdl-in-visual-studio-ssis
    http://www.bidn.com/blogs/BillBrannen/bidn-blog/619/ssis-web-service-task-step-by-step
    Regards, Leo

  • Web Services from WSDL file

    Hi there. I am new for Java Web Services.
    I'm trying to generate a web service from a .wsdl file. This file includes a references to other .xsd files
    and that's the problem.
    First I've tried with JBuilder 9 but it gave me some problems with some element definitions from xsd file (such as those elements defined as 'choice'): there were generated some classes with repeated elements (such as variables and methods), some classes with strange names (it was added a 'TypeN' label to the name of the class), etc.
    Then I've tried with Sun One Studio 5. It didn't support 'include' tags in the wsdl file.
    Later I've tried with Weblogic Workshop but an error with an internal class of Weblogic was generated.
    Can anyone tell me what editor could I use to generate the Java Web Services?
    Thanks!

    https://jax-rpc.dev.java.net/whitepaper/1.1/index-part2.html explains in detail how to develop, deploy and invoke a web service starting from a WSDL.
    Let me know if you have any specific questions.
    Thanks,
    -Arun

  • Getting a Java class from WSDL file

    Hello,
    I have a WSDL file at http://gis13.exp.sis.pitt.edu:8080/axis/services/BufferProcessorService?wsdlI would like to know how to get a java class file from the WSDL posted here.
    For instance, I have a class entitled InsightPoint. How do I get this from the WSDL to a java class in order to use it in my web service?
    Cheers,
    Chris

    Setareh,
    Here is an excerpt from the javadoc for ExceptionInInitializer:
    Signals that an unexpected exception has occurred in a static initializer
    or the initializer for a static variable.
    Before running your function in SQL*Plus, do the following:
    set serveroutput on size 1000000
    exec DBMS_JAVA.SET_OUTPUT(1000000)Then you may get more information. If you don't then you may find more details in the Oracle log files in the "bdump" destination. The following query will tell you where that is:
    select VALUE
      from V$PARAMETER
    where NAME = 'background_dump_dest'Then, if you are still having trouble, post the entire error message and stack trace, as well as your java code.
    Good Luck,
    Avi.

  • Workshop IDE can not create CTRL from WSDL file

    Hi everybody,
    For the evualtion of the Workshop IDE that comes with WLS 7.0 beta, I'm developing
    a web service (via this IDE) which must interoperate with another web service
    implemented with the help of another tool. I got the corresponding WSDL of this
    "outside" web service (see attachement), and when I want to generate the corresponding
    CTRL (via Add Service Control), I get the following error:
    Error: Could not find operation 'sayHello' in portType ''
    Prescription: The operation you are trying to bind was not found among the declared
    operations. Please check your <portType> sections.
    I do not have a lot of experience with WSDL files and its specification, but I
    compared this file with another WSDL files that work with WORKSHOP IDE, and I
    do not see difference between these files and the file that does not work. Moreover
    the IDE error says that my service 'sayHello' can not be find inside the 'portType'
    tags, but if you have a look at the WSDL file, you will see that is not true ?!?!?
    Can somebody help me please?
    Have a nice day
    Vincent

    Vincent,
    What is happening is that the type attribute on the binding tag must match
    both the targetnamespace and the name of the portType name attribute. Yours
    do match in basename only. When parsing the WSDL file what we do is put the
    name attributes of the portType, service and binding tags into the
    targetNamespace of the WSDL and then we expect the references to these names
    to also be resolved to that namespace.
    In the case of your WSDL, your targetNamespace is
    http://localhost:8000/HelloWorldApp/servlet/rpcrouter and the type attribute
    on the binding attribute just references HelloWorldServicePort which means
    it will use the default namespace of http://schemas.xmlsoap.org/wsdl which
    is, of course, different than the targetNamespace.
    To fixup the WSDL I would recommend you just define a new namespace at the
    top of the WSDL file that matches the targetNamespace attribute and then use
    that prefix in the text value of the attribute used to reference that name.
    Yes, we do need to do some better parser/error messages to help identify
    this :)
    Here is one way that I have done to fixup your WSDL and Workshop does pull
    it in and expose the methods correctly:
    <?xml version='1.0'?>
    <definitions name='HelloWorldService'
    xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
    xmlns:xsd='http://www.w3.org/2001/XMLSchema'
    xmlns='http://schemas.xmlsoap.org/wsdl/'
    xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
    targetNamespace='http://localhost:8000/HelloWorldApp/servlet/rpcrouter'
    xmlns:test='http://localhost:8000/HelloWorldApp/servlet/rpcrouter'
    xmlns:xsd1='http://localhost:8000/HelloWorldApp/servlet/rpcrouter/schema'>
    <types>
    <xsd:schema
    targetNamespace='http://localhost:8000/HelloWorldApp/servlet/rpcrouter/schem
    a'>
    <xsd:simpleType name="java.lang.Integer"><xsd:restriction
    base="xsd:int"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.Short"><xsd:restriction
    base="xsd:short"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.Long"><xsd:restriction base="xsd:long"
    /></xsd:simpleType>
    <xsd:simpleType name="java.lang.Double"><xsd:restriction
    base="xsd:double"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.Float"><xsd:restriction
    base="xsd:float"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.Boolean"><xsd:restriction
    base="xsd:boolean"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.Character"><xsd:restriction
    base="xsd:string"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.String"><xsd:restriction
    base="xsd:string"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.StringBuffer"><xsd:restriction
    base="xsd:string"/></xsd:simpleType>
    <xsd:simpleType name="java.lang.Byte"><xsd:restriction
    base="xsd:byte"/></xsd:simpleType>
    <xsd:simpleType name="char_lb_rb"><xsd:restriction
    base="xsd:string"/></xsd:simpleType>
    <xsd:simpleType name="char"><xsd:restriction
    base="xsd:string"/></xsd:simpleType>
    </xsd:schema>
    </types>
    <message name='sayHelloInput'>
    <part name='message' type='xsd:string'/>
    </message>
    <message name='sayHelloOutput'>
    <part name='result' type='xsd:string'/>
    </message>
    <portType name='HelloWorldServicePort'>
    <operation name='sayHello'>
    <input message='test:sayHelloInput'/>
    <output message='test:sayHelloOutput'/>
    </operation>
    </portType>
    <binding name='HelloWorldServiceBinding'
    type='test:HelloWorldServicePort'>
    <soap:binding style='rpc'
    transport='http://schemas.xmlsoap.org/soap/http'/>
    <operation name='sayHello'>
    <soap:operation
    soapAction='http://localhost:8000/HelloWorldApp/servlet/rpcrouter/sayHello'/
    >
    <input>
    <soap:body use='encoded' namespace='urn:HelloWorldService'
    encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'/>
    </input>
    <output>
    <soap:body use='encoded' namespace='urn:HelloWorldService'
    encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'/>
    </output>
    </operation>
    </binding>
    <service name='HelloWorldService'>
    <port name='HelloWorldServicePort'
    binding='test:HelloWorldServiceBinding'>
    <soap:address
    location='http://localhost:8000/HelloWorldApp/servlet/rpcrouter'/>
    </port>
    </service>
    </definitions>
    Thanks,
    Art
    "Vincent Ducret" <[email protected]> wrote in message
    news:[email protected]...
    >
    Thanks for your answer, but I do not understand it, and also yoursuggestion.
    >
    According to WSDL specification, the 'type' attribute of a 'binding' tagmust
    reference (bind to) an exisiting 'portType' tag. And it's the case here,no? I.e.
    we have a 'portType' tag called HelloWorldServicePort, which is referencedby
    the 'binding' tag named HelloWorldServiceBinding via its 'type' attribute:'HelloWorldServicePort'.
    >
    Where is the problem ?
    Thanks a lot
    Thanks for your help

  • PDF Layer Generation from DWG file

    I am able to generate a PDF with layer controls (visible and invisible) when opening a DWG file from Acobat X.   I however with same file can not generate the same layer controls by using Adobe.pc3 or DWGtoPDF.pc3 from AutoCAD.   I either get the layer in the list or don't.   I find that I can not generate the layer but have it non-visible at the same time.  

    I did find the .arx files and attempted to load to try run, but they won't.   I'm sure this is because we are running 2012.     As you pointed out they are not on the compatable list.    Looks like it isn't going to happen.   I do appeaciate your suggestion.
    I realize it is asking a lot to get two application to pass information properly for each other.  I had previously posted on the AutoDesk forum, too, with no solution.

  • Generatin client stubs from wsdl file

    i user wsimport to generate the client stubs
    look like i am missing some files
    like the service port/stub..
    please help

    i user wsimport to generate the client stubs
    look like i am missing some files
    like the service port/stub..wsimport is run on a WSDL and it generates all required stubs for you. What is the exact nature of your problem ? more details please

Maybe you are looking for

  • Change a string into a different format

    How do I convert this CN=zeeeComputerName,OU=cars,OU=sales,OU=employees,OU=Desktop,DC=carplace,DC=com to this carplace.com/desktop/employees/sales/cars/zeeeComputerName

  • Deleted Music in iTunes and now iPhone and iPad do not match up.

    I recently I did a purge of all old music in my iTunes library to also make space on my iPhone and iPad. My iPad has numerous songs which I have kept not being able to play. It is grey'ed out and have the circle with a stop button next to it. On my i

  • Missing filters after exporting from lightroom

    I am currently moving my photo editing from a 32-bit WinXP machine to a 64-bit Win7 machine.  For the time being, both computers have CS4 Design Premium and Lightroom 2.5 installed.  All apps on both machines are currently up-to-date. The issue, and

  • Attaching pll library

    Hello everybody I attached a pll library with my form module,I selected the Attached libraries node in the object navigator and I clicked on the create button, and when arrived in the alert message stating that the attached library is in a non portab

  • Show part of the document

    For example, I have the following document: <url> http://www.abc.com </url> <headline> A headline for this article </headline> <pub_date> 20001208 </pub_date> <text> This is a document content </text> I know that I can use session (field) for the tag