Wscompile error documentation

Dear all,
searching the web for documentation about the wscompile tool results in (roughly) the same information as displayed when typing "wscompile -help" on the command line.
Does there happen to be any documentation about the meaning and (possible) cause of the various error message thrown from wscompile?
Thanks in advance.
Regards,
Jonatan Samoocha

Hi!
Is there any solution for this problem?
Thanks in advance
Eddy

Similar Messages

  • JWSDP1.5: wscompile error: "(should not happen): tie.generator.002

    Hi all,
    I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
    error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
    Cheers,
    --Tim West
    Full output (from wscompile Ant task) - added linebreaks for readability
    Buildfile: C:\common\eclipse-projects\thp\build.xml
    wscompile-init:
    ANEW-generate-server-binding:
    [wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
    -features:documentliteral,wsi -g -gen:server -keep -verbose \
    C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
    [wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: userDefinedBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdHeader]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestAckHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyResponseChoiceHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusQueryHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: statusStructure]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseHdr]
    [wscompile] error: generator error: internal error (should not happen): tie.generator.002
    BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
    Total time: 2 seconds

    Hi again,
    The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
    Thanks again,
    -Tim West
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
        name="TentativeHold"
        targetNamespace="http://www.w3.org/2001/08/thp/definitions"
        xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
        xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns="http://schemas.xmlsoap.org/wsdl/">
      <types>
        <schema xmlns="http://www.w3.org/2001/XMLSchema"
            xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
            targetNamespace="http://www.w3.org/2001/08/thp/schemas">
          <!-- =================================================================== -->
          <!-- Item - holdHeader -->
          <!-- Note - This information is required in all the Tentative Hold Protocol
                      communications. -->
          <!-- Fields- holdID - UUID. -->
          <!--             customerID - account number or other identifier -->
          <!--             replyTo - could be a unique locator such as a URI or an
                              email address depending on the communication protocol
                              to be used. -->
          <!-- comment - space for trading partner defined info. -->
          <!-- =================================================================== -->
          <complexType name="holdHeader">
            <sequence>
              <element name="holdID" type="int"/>
              <element name="customerID" type="string"/>
              <element name="replyTo" type="string"/>
              <element name="comment" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - userDefinedBody -->
          <!-- Note - This will carry any domain-specific information  (e.g., product
                ID and quantity). An implementation shall probably have many
                different userDefinedBody's (one for holdRequest, holdRequestAck,
                ...). This body is used in all messages. -->
          <!-- Fields - Trading partner to trading partner specific or an agreed
             - standard (e.g., RosettaNet PIP). -->
          <!-- =================================================================== -->
            <!-- TIM: Just junk here for now, must fix later -->
          <complexType name="userDefinedBody">
            <sequence>
              <element name="someRequestField" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestHdr -->
          <!-- Note - Specifies the Tentative Hold Protocol header for messages
             - requesting a tentative hold. -->
          <!-- Fields - Same as holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdRequestHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestAckHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + timeUntilResponse - a indication of the time it
             - will take the resource provider to process the request. -->
          <!-- =================================================================== -->
          <complexType name="holdRequestAckHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="timeUntilResponse" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdGrantHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdDuration" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the
             - denial. The implementation may choose to use reason codes or just
             - textual descriptions. -->
          <!-- =================================================================== -->
          <complexType name="holdDenialHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="reason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdModifyRequestHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdModifyGrantHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the denial.
             - The implementation may choose to use reason codes or just textual
             - descriptions.-->
          <!-- =================================================================== -->
          <complexType name="holdModifyDenialHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyResponseChoiceHdr -->
          <!-- Note - The use of a single type for this response was to facilitate a
             - synchronous request/response for the modify request without preventing
             - asynchronous.-->
          <!-- Fields - Either holdModifyGrantHdr or holdModifyDenialHdr -->
          <!-- =================================================================== -->
          <!-- TIM: JWSDP does not support xsd:choice, so I'm turning this into a sequence.
             -      The implementor is now responsible for ensuring exactly one of these
                    is present.
            -->
          <complexType name="holdModifyResponseChoiceHdr">
            <sequence>
              <element name="grant" type="holdSchema:holdModifyGrantHdr"/>
              <element name="deny" type="holdSchema:holdModifyDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + customerReason - a description of or a code for
             - the reason why the hold is being cancelled. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationRequestHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="customerReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationResponseHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationNotificationHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + cancellationReason - a description of or a code
             -for the reason the vendor is cancelling the hold. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationNotificationHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="cancellationReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusQueryHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusQueryHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - statusStructure -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdState - a description of the state of the hold.
             - Possible values currently defined are: responding, in process, active,
             - and inactive. The definition is left open (not restricted) for future or
             - user refinement of the useful values. -->
          <!-- =================================================================== -->
          <complexType name="statusStructure">
            <sequence>
              <element name="itemHeader" type="holdSchema:holdHeader"/>
              <element name="holdState" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseBody -->
          <!-- Note - -->
          <!-- Fields - holdItemsCount - the number of holds matching the holdStatusQuery. -->
          <!--             itemList - The header and state of the holds that match the query. -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseBody">
            <sequence>
              <element name="holdItemsCount" type="int"/>
              <element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdErrorHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <!-- TIM: Combined old "holdErrorHdr" and "holdErrorBody" as a fault must
             - have only a single part (see WSDL sec 3.6).
            -->
          <complexType name="holdError">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdErrorType" type="int"/>
              <element name="holdErrorDesc" type="string"/>
            </sequence>
          </complexType>
          <!-- TIM: To use doc/lit, we need <element> tags here to reference from WSDL -->
          <element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
          <element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
          <element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
          <element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
          <element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
          <element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
          <element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
          <element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
          <element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
          <element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
          <element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
          <element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
          <element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
          <element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
          <element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
          <element name="holdError" type="holdSchema:holdError"/>
        </schema>
      </types>
      <message name="HoldRequest">
        <part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
        <part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldRequestAck">
        <part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
        <part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldGrantResponse">
        <part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
        <part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldDenialResponse">
        <part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
        <part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyRequest">
        <part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
        <part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyResponse">
        <part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
        <part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationRequest">
        <part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
        <part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationResponse">
        <part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
        <part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationNotification">
        <part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
        <part name="body" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusQueryRequest">
        <part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
        <part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusResponse">
        <part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
        <part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
      </message>
      <message name="HoldErrorResponse">
        <!-- TIM: altered to be consistent with updated schema - the
           - fault body must have only one part
          -->
        <part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
      </message>
      <portType name="TentativeHoldServicePortType">
        <operation name="InitiateHold">
          <input message="tns:HoldRequest"/>
          <output message="tns:HoldRequestAck"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldModify">
          <input message="tns:HoldModifyRequest"/>
          <output message="tns:HoldModifyResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldCancellation">
          <input message="tns:HoldCancellationRequest"/>
          <output message="tns:HoldCancellationResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateStatusQuery">
          <input message="tns:HoldStatusQueryRequest"/>
          <output message="tns:HoldStatusResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
      </portType>
      <portType name="TentativeHoldNotificationServicePortType">
        <operation name="NotifyHoldGranted">
          <output message="tns:HoldGrantResponse"/>
        </operation>
        <operation name="NotifyHoldDenied">
          <output message="tns:HoldDenialResponse"/>
        </operation>
        <operation name="NotifyServerHoldCancellation">
          <output message="tns:HoldCancellationNotification"/>
        </operation>
      </portType>
      <binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
          <operation name="InitiateHold">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldModify">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldCancellation">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateStatusQuery">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
      </binding>
      <service name="TentativeHoldService">
        <documentation> Mythical Tentative Hold Web service</documentation>
        <port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHold/"/>
        </port>
      </service>
      <service name="TentativeHoldNotificationService">
        <port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHoldNotification"/>
        </port>
      </service>
    </definitions>

  • ORA-01801 does not exist in Oracle Errors Documentation

    Hi,
    <br>
    RMAN issed to me the following error: <br>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 06/18/2007 09:55:57
    RMAN-03999: Oracle error occurred while while converting a date: <b>ORA-01801</b>: date
    format is too long for internal buffer<br>
    Regardless of the error reason, when I looked up the ORA-01801 error in the following reference, I did not see the error number there:<br>
    Oracle Database Error Messages 10g Release 2 (10.2) A14219-01
    <br>
    <br>
    However, I saw it in Oracle 9i error documentation.
    <br>
    <br>
    Are there any obsolete errors? Why I don't see the error in 10g doc?
    Thanks in advance.

    You should report such thing into Documentation
    Nicolas.

  • OVM 3.0.x Error documentation?

    Hi,
    I was wondering if there is any OVM-related errors documentations that I could use. With Oracle database products, I can quickly diagnose errors by using the oerr tool:
    eg. oerr ora 12540 for an ORA-12540 error...
    However, even just a document explaining the most common OVM- OVMRU_ etc error types would be most helpful, instead of having to search for each error individually.
    Thanks in advance,
    T.

    Wait for some time. Sometimes the VM Manager takes some time to do actions if you are doing too many actions through VM Manager. If after 5-10 mins of deleting the VM is not deleted, try the following:
    - logout and login to VM Manager and try again
    If that does not work reset the VM and after it is reset to original status, try deleting it.
    If you have any probs, check the Vm logs in VM Manager.
    Regards
    CP

  • WSCompile error

    Hello,
    I'm very new to webservices. I am using tomcat as the container and got jwsdp installed in it.
    While trying to build one of the examples provided I am getting a build error. It seems that WSCompile isn't working fine. Find below the extracts of build output and some excerpts of build.xml file too.
    build output
    C:\tomcat50-jwsdp\xws-security\samples\simple>ant run-sample
    Buildfile: build.xml
    clean:
       [delete] Deleting directory C:\tomcat50-jwsdp\xws-security\samples\simple\build
       [delete] Deleting directory C:\tomcat50-jwsdp\xws-security\samples\simple\dist
    as8-check:
    ws-check:
    tc-check:
        [mkdir] Created dir: C:\tomcat50-jwsdp\xws-security\samples\simple\build\client\classes
        [mkdir] Created dir: C:\tomcat50-jwsdp\xws-security\samples\simple\build\server\WEB-INF\classes
        [mkdir] Created dir: C:\tomcat50-jwsdp\xws-security\samples\simple\dist
    compile-handler-code:
         [echo] Compiling the handler source code
        [javac] Compiling 1 source file to C:\tomcat50-jwsdp\xws-security\samples\simple\build\server\WE
    B-INF\classes
        [javac] Compiling 1 source file to C:\tomcat50-jwsdp\xws-security\samples\simple\build\client\cl
    asses
    create-handler-jar:
          [jar] Building jar: C:\tomcat50-jwsdp\xws-security\samples\simple\build\client\secenv-handler.
    jar
    prepare:
    gen-server:
         [echo] Running wscompile....
    BUILD FAILED
    file:C:/tomcat50-jwsdp/xws-security/samples/simple/build.xml:135: Could not create task or type of t
    ype: wscompile.
    Ant could not find the task or a class this task relies upon.
    This is common and has a number of causes; the usual
    solutions are to read the manual pages then download and
    install needed JAR files, or fix the build file:
    - You have misspelt 'wscompile'.
       Fix: check your spelling.
    - The task needs an external JAR file to execute
       and this is not found at the right place in the classpath.
       Fix: check the documentation for dependencies.
       Fix: declare the task.
    - The task is an Ant optional task and optional.jar is absent
       Fix: look for optional.jar in ANT_HOME/lib, download if needed
    - The task was not built into optional.jar as dependent
       libraries were not found at build time.
       Fix: look in the JAR to verify, then rebuild with the needed
       libraries, or download a release version from apache.org
    - The build file was written for a later version of Ant
       Fix: upgrade to at least the latest release version of Ant
    - The task is not an Ant core or optional task
       and needs to be declared using <taskdef>.
    Remember that for JAR files to be visible to Ant tasks implemented
    in ANT_HOME/lib, the files must be in the same directory or on the
    classpath
    Please neither file bug reports on this problem, nor email the
    Ant mailing lists, until all of these causes have been explored,
    as this is not an Ant bug.
    Total time: 2 seconds
    Excerpts from the build.xml
    <!--
    Copyright 2004 Sun Microsystems, Inc. All rights reserved.
    SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
    -->
    <!DOCTYPE project [
          <!ENTITY tomcat SYSTEM "file:../buildconfig/tomcat-config.xml">
          <!ENTITY sjsas SYSTEM "file:../buildconfig/sjsas-config.xml">
          <!ENTITY sjsws SYSTEM  "file:../buildconfig/sjsws-config.xml">
    ]>
    <project name="simple" default="usage" basedir=".">
      <!-- Values in build.properties (if any) override the values in this file -->
      <property file="build.properties"/>
      <property file="../build.properties"/>
      <property name="context-path" value="securesimple"/> 
      <property name="client-class" value="${ant.project.name}.TestClient"/>
      <property name="url" value="http://${endpoint.host}:${endpoint.port}/manager/"/>
      <property name="username" value="${username}"/>
      <property name="password" value="${password}"/>
      <property name="build.home" value="build"/>
      <property name="dist.home" value="dist"/>
      <property name="portable-war" value="${ant.project.name}-portable.war"/>
      <property name="deployable-war" value="${context-path}.war"/>
      <property name="war-path" value="${dist.home}/${deployable-war}"/>
      <property name="config.rpcenc.file" value="${basedir}/etc/config.xml"/>
      <property name="client.config.rpcenc.file" value="${basedir}/etc/client-config.xml"/>
      <property name="model.rpcenc.file" value="model.xml.gz"/>
      <property name="webapp.webxml" value="${basedir}/etc/web.xml"/>
      <property name="jaxrpc.tool.verbose" value="true"/>
      <target name="as8-check" if="sjsas.home">
        <mkdir dir="${build.home}/client/classes"/>
        <mkdir dir="${build.home}/server/WEB-INF/classes"/>
        <mkdir dir="${dist.home}"/>
        &sjsas;
      </target>
      <target name="ws-check" if="sjsws.home">
        <mkdir dir="${build.home}/client/classes"/>
        <mkdir dir="${build.home}/server/WEB-INF/classes"/>
        <mkdir dir="${dist.home}"/>
        &sjsws;
      </target>
      <target name="tc-check" if="tomcat.home">
        <mkdir dir="${build.home}/client/classes"/>
        <mkdir dir="${build.home}/server/WEB-INF/classes"/>
        <mkdir dir="${dist.home}"/>
        <!--&tomcat;--><!--Added by Sourabh: Its commented to fix compilation issues-->
      </target>
      <target name="prepare" depends="as8-check, ws-check, tc-check, compile-handler-code, create-handler-jar">
          <mkdir dir="${build.home}"/>
          <mkdir dir="${build.home}/server"/>
          <mkdir dir="${build.home}/server/WEB-INF"/>
          <mkdir dir="${build.home}/server/WEB-INF/classes"/>
          <mkdir dir="${dist.home}"/>
      </target>
      <target name="compile-handler-code"
              description="Compiles the handler">
        <echo message="Compiling the handler source code "/>
         <path id="app.classpath">
         <!--Added by Sourabh:Start -->
              <fileset dir="${build.home}/../../../../xws-security/lib">
                   <include name="**/*.jar"/>
              </fileset>
              <fileset dir="${build.home}/../../../../jwsdp-shared/lib">
                   <include name="**/*.jar"/>
              </fileset>
         <!--Added by Sourabh: End-->
         </path>
        <javac debug="true"
               srcdir="src"
               destdir="${build.home}/server/WEB-INF/classes"
               includes="**/*.java">
        <classpath>
            <path refid="app.classpath"/>
        </classpath>
        </javac>
        <javac debug="true"
               srcdir="src"
               destdir="${build.home}/client/classes"
               includes="**/*.java">
        <classpath>
            <path refid="app.classpath"/>
        </classpath>
        </javac>
      </target>
      <target name="create-handler-jar"
              description="Creating jar file">
        <jar jarfile="${build.home}/client/secenv-handler.jar">
          <fileset dir="${build.home}/client/classes">
            <include name="**/*.class"/>
          </fileset>
        </jar>
      </target>
      <target name="compile-server" depends="gen-server"
              description="Compiles the server-side source code">
        <echo message="Compiling the server-side source code...."/>
        <javac debug="true"
               srcdir="server/src"
               destdir="${build.home}/server/WEB-INF/classes"
               includes="**/*.java">
        <classpath>
            <path refid="app.classpath"/>
         </classpath>
        </javac>
      </target>
      <target name="gen-server" depends="prepare"
              description="Runs wscompile to generate server artifacts">
        <echo message="Running wscompile...."/>
        <wscompile verbose="${jaxrpc.tool.verbose}"
                   xPrintStackTrace="true"   
                   jvmargs="-Djava.endorsed.dirs=${java.endorsed.dir}"
                   keep="true" fork="true"
                   security="${server.security.config}"
                   import="true"
                   model="${build.home}/server/WEB-INF/${model.rpcenc.file}"
                   base="${build.home}/server/WEB-INF/classes"
                   classpath="${app.classpath}"
                   config="${config.rpcenc.file}">
          <classpath>
            <pathelement location="${build.home}/server/WEB-INF/classes"/>
            <path refid="app.classpath"/>
          </classpath>
        </wscompile>
      </target>
        <target name="setup-web-inf" depends="prepare">
            <echo message="Setting up ${build.home}/server/WEB-INF..."/>
            <copy file="./etc/web.xml" todir="${build.home}/server/WEB-INF"/>
            <copy file="./etc/jaxrpc-ri.xml" todir="${build.home}/server/WEB-INF"/>
            <copy file="./etc/PingService.wsdl" todir="${build.home}/server/WEB-INF"/>
        </target>
      <target name="raw-war" depends="setup-web-inf"
              description="Creates a 'raw' WAR file">
        <echo message="Packaging to ${dist.home}/${portable-war}...."/>
        <delete file="${dist.home}/${portable-war}" />
        <jar jarfile="${dist.home}/${portable-war}">
          <fileset dir="${build.home}/server">
            <include name="WEB-INF/**"/>
            <include name="index.html"/>
          </fileset>
        </jar>
      </target>
      <target name="process-war" depends="raw-war"
              description="Runs wsdeploy to create a deployable or 'cooked' WAR file">
        <echo message="Running wsdeploy..."/>
        <delete file="${dist.home}/${deployable-war}"/>
        <wsdeploy fork="true" verbose="${jaxrpc-tool-verbose}" keep="true"
                  jvmargs="-Djava.endorsed.dirs=${java.endorsed.dir}"
                  tmpdir="${build.home}/server"
                  outwarfile="${dist.home}/${deployable-war}"
                  inwarfile="${dist.home}/${portable-war}">
          <classpath>
            <path refid="app.classpath"/>
          </classpath>
        </wsdeploy>
      </target>
      <target name="build-server"
              depends="compile-server, gen-server, raw-war, process-war">
      </target>
      <!-- Appserver -->
      <target name="check-if-deployed-as" if="sjsas.home">
        <echo message="Checking for deployed webapp at context path /${context-path}"/>
        <condition property="as.webapp.deployed">
          <http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
        </condition>
      </target>
      <target name="deploy-sjsas"
              depends="prepare, check-if-deployed-as, undeploy-sjsas"
              if="sjsas.home">
        <echo message="Deploying war for ${ant.project.name} to sjsas"/>
        <appserv-deploy file="${war-path}" password="${password}" sunonehome="${sjsas.home}" />
      </target>
      <target name="undeploy-sjsas" if="as.webapp.deployed">
        <echo message="Undeploying existing webapp at ${context-path}"/>
        <echo message="appclasspath ${app.classpath}"/>
        <appserv-undeploy name="${context-path}" password="${password}" sunonehome="${sjsas.home}" />
      </target>
      <!-- end of Appserver -->
      <!-- Webserver -->
      <target name="check-if-deployed-ws" if="sjsws.home">
        <echo message="Checking for deployed webapp at context path /${context-path}"/>
        <condition property="ws.webapp.deployed">
          <http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
        </condition>
      </target>
      <target name="deploy-ws">
          <echo message="deploying ${war-path} at ${context-path}" />
          <exec executable="${SJSWS_DEPLOY}" vmlauncher="false">
          <arg value="deploy" />
          <arg value="-u" />
          <arg value="/${context-path}" />
          <arg value="-i" />
          <arg value="${VS.DIR}" />
          <arg value="-v" />
          <arg value="${VS.DIR}" />
          <arg value="${war-path}" />
          </exec>
      </target>
      <target name="undeploy-ws" >
        <echo message="undeploying ${context-path}" />
        <exec executable="${SJSWS_DEPLOY}" vmlauncher="false">
            <arg value="delete" />
            <arg value="deploy" />
            <arg value="-u" />
            <arg value="/${context-path}" />
            <arg value="-i" />
            <arg value="${VS.DIR}" />
            <arg value="-v" />
            <arg value="${VS.DIR}" />
            <arg value="hard" />
         </exec>
      </target>
      <target name="deploy-sjsws"
              depends="prepare, check-if-deployed-ws, undeploy-sjsws"
              if="sjsws.home" >
        <echo message="Deploying war for ${ant.project.name} to sjsws"/>
        <antcall target="deploy-ws" />
      </target>
      <target name="undeploy-sjsws" if="ws.webapp.deployed">
        <echo message="Undeploying existing webapp at ${context-path}"/>
        <echo message="appclasspath ${app.classpath}"/>
        <antcall target="undeploy-ws" />
      </target>
      <!--End of Webserver -->
      <!--Tomcat -->
      <target name="check-if-deployed-tom" if="tomcat.home">
        <echo message="Checking for deployed webapp at context path /${context-path}"/>
        <condition property="tom.webapp.deployed">
          <http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
        </condition>
      </target>
      <target name="deploy-tomcat"
              depends="prepare, check-if-deployed-tom, undeploy-tomcat"
              if="tomcat.home" >
        <echo message="Deploying war for ${ant.project.name} to tomcat"/>
        <deploy-catalina url="${url}" username="${username}" password="${password}"
                path="/${context-path}" war="file:${war-path}"/>
      </target>
    <target name="undeploy-tomcat-proper" if="webapp.deployed">
          <echo message="Undeploying existing webapp at ${context-path}"/>
          <undeploy-catalina url="${url}" username="${username}" password="${password}" path="/${context-path}"/>
      </target>
      <target name="undeploy-tomcat-war-present" if="war.present">
          <echo message="Undeploying existing webapp at ${context-path}"/>
          <undeploy-catalina url="${url}" username="${username}" password="${password}" path="/${context-path}"/>
      </target>
      <target name="undeploy-tomcat" if="tomcat.home">
        <echo message="Undeploying existing webapp at ${context-path}"/>
        <condition  property="war.present">
            <available file="${tomcat.home}/webapps/${deployable-war}" />
        </condition>
        <antcall target="undeploy-tomcat-war-present" />
        <condition property="webapp.deployed">
          <http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
        </condition>
        <antcall target="undeploy-tomcat-proper" />
    </target>
      <!--End of Tomcat -->
      <target name="deploy-forced" depends= "deploy-sjsas, deploy-sjsws, deploy-tomcat"/>
      <target name="internal-undeploy" depends= "undeploy-sjsas, undeploy-sjsws, undeploy-tomcat"/>
      <target name="redeploy" depends="prepare"
          description="Undeploys and deploys a Web aplication">
          <antcall target="undeploy" />
          <antcall target="deploy" />
      </target>
      <target name="gen-client" depends="prepare"
              description="Runs wscompile to generate client side artifacts">
        <echo message="Running wscompile...."/>
        <wscompile fork="true" verbose="${jaxrpc.tool.verbose}" keep="true"
                   jvmargs="-Djava.endorsed.dirs=${java.endorsed.dir}"
                   client="true"
                   security="${client.security.config}"
                   base="${build.home}/client"
                   features=""
                   config="${client.config.rpcenc.file}">
          <classpath>
            <fileset dir="${build.home}/client">
                <include name="secenv-handler.jar"/>
            </fileset>
            <path refid="app.classpath"/>
          </classpath>
        </wscompile>
      </target>
      <target name="compile-client" depends="prepare"
              description="Compiles the client-side source code">
        <echo message="Compiling the client source code...."/>
        <javac srcdir="client/src"
               debug="true"
               destdir="${build.home}/client"
               includes="**/*.java">
          <classpath>
            <path refid="app.classpath"/>
            <fileset dir="${build.home}/client">
                <include name="secenv-handler.jar"/>
            </fileset>
          </classpath>
        </javac>
      </target>
      <target name="build-client" depends="gen-client, compile-client"
              description="Executes the targets needed to build a stub client.">
      </target>
      <target name="run-sample"
              depends="clean, prepare, build-server, deploy-forced, build-client"
              description="Runs the example client">
        <echo message="Running the ${client-class} program...."/>
        <java fork="on" classname="${client-class}">
          <sysproperty key="java.endorsed.dirs" value="${java.endorsed.dir}"/>
          <sysproperty key="endpoint.host" value="${endpoint.host}"/>
          <sysproperty key="endpoint.port" value="${endpoint.port}"/>
          <sysproperty key="service.url" value="${service.url}"/>
          <sysproperty key="jwsdp.home" value="${jwsdp.home}"/>
          <classpath>
            <pathelement location="${build.home}/client"/>
            <fileset dir="${build.home}/client">
                <include name="secenv-handler.jar"/>
            </fileset>
            <path refid="app.classpath"/>
          </classpath>
        </java>
      </target>
      <target name="run-remote-sample"
              depends="clean, prepare, build-client"
              description="Runs the example client">
        <echo message="Running the ${client-class} program...."/>
        <java fork="on" classname="${client-class}">
          <sysproperty key="java.endorsed.dirs" value="${java.endorsed.dir}"/>
          <sysproperty key="http.proxyHost" value="${http.proxyHost}"/>
          <sysproperty key="http.proxyPort" value="${http.proxyPort}"/>
          <sysproperty key="endpoint.host" value="${endpoint.host}"/>
          <sysproperty key="endpoint.port" value="${endpoint.port}"/>
          <sysproperty key="service.url" value="${service.url}"/>
          <sysproperty key="jwsdp.home" value="${jwsdp.home}"/>
          <classpath>
            <pathelement location="${build.home}/client"/>
            <fileset dir="${build.home}/client">
                <include name="secenv-handler.jar"/>
            </fileset>
            <path refid="app.classpath"/>
          </classpath>
        </java>
      </target>
      <target name="clean-server"
              description="Removes server side build directories">
        <delete dir="${build.home}/server"/>
      </target>
      <target name="clean-client"
              description="Removes client side build directories">
        <delete dir="${build.home}/client"/>
      </target>
      <target name="clean"
              description="Removes all build and dist directories">
        <delete dir="${build.home}"/>
        <delete dir="${dist.home}"/>
      </target>
      <target name="usage" depends="prepare">
        <echo message="Please see README.txt for more info."/>
        <echo message="Useful targets:"/>
        <echo message="  clean = remove both server and client objects"/>
        <echo message="  clean-server = remove only server objects"/>
        <echo message="  clean-client = remove only client objects"/>
        <echo message="  build-server = build server side code"/>
        <echo message="  deploy-forced = force deploy built server code to Container"/>
        <echo message="  build-client = build client app code"/>
        <echo message="  run-sample = run the sample"/>
        <echo message="  run-remote-sample = run the sample against a remote server containing the deployed endpoint"/>
      </target>
      <target name="help" depends="usage"/>
    </project>any help would be highly appreciated.
    regards,
    Sourav

    407 Proxy Authentication Required
    The compiler is trying to reference a document on the web, but can't use your proxy because it doesn't have the proxy id and password to use.
    If it isn't possible to pas the proxy info to the compiler, download the doc to a local server and reference it there.

  • BW Authorization Error documentation Question

    Hi,
    I have a question, may be you can help in this:
    Q: In BW Analyzer if we get the following authorization error for some reason:
    ->Authorization Check
    You do not have authorization for Add or Create
    There is a Details tab to see the authorization error details. I need to add documentation for the naming conventions the Users need to use so that it's easy for Users to see what is the reason for the error and what naming convention do they need to use to prevent the error.
    Right now, details tab shows "No Documentation Available". How can I add documentation here? Where do I add this documentation and how do I link it to the Authorization Error Message's Details tab?
    I tried running RSRTRACE to see which function modules/programs get called but that does not help. It gives me the following two function modules which are being called when I get the error message and when I click the details tab:
    RZX0_MESSAGES_GET
    RZX0_MESSAGE_H_GET
    and surprisingly when I try to look them up in SE37 they do not exist … What can be the reason for this?
    Is there a system transaction, like .. SM02, in BW where we can define or create authorization error message documentation for BEx Analyzer? How do I link it to the Authorization Error message?
    Your help or advise will be very much appreciated.
    Thank You,
    Regards,
    Mandeep Virk

    It can be done via SE91.
    Message Class is R9 and message number is 108
    We have to define the Long Text and save it under the RSZ class.
    It works for me now.
    Thanks,
    Mandeep

  • Consolidation Error Documentation (CSD)

    Hi all,
    I have recently ended upon a consolidation engine error (CSD-070, CSD-080). Searching in the forum I have see some threads talking about some documentation about these errors. Could anyone please send that documentation?
    About the CSD-070 (No Time available) & CSD-080 (No Group Available) errors, does anybody know what they can be related to?
    Kind Regards,
    Rafael
    Edited by: Rafael Moreno on Oct 2, 2008 2:00 PM

    Please find below a list of all errorcodes per stored procedure.
    Alwin
    MSG     SPRUNCONVERSION
    FX-000     ERROR FX-000 Application not Available !
         Appset maintenance in progress
    FX-010     ERROR FX-010 Wrong Application, check your logic
         You may have hardcoded a wrong application in your logic.
    FX-020     ERROR FX-020 No Currency in your Appset ! You must have a Dimension with dimension type = u2018Ru2019 in your Application. !
         You must have at least one member with CURRENCY_TYPE = R In your currency dimension.
    FX-030     Warning : Application without INTCO dimension
         No INTCO Dimension IN your Application.(Dimtype = I)
    FX-040     Warning : Application without Flow Dimension
         No FLOW Dimension IN your Application.(Dimtype = S)
    FX-050     Warning : Application without Datasrc Dimension
         No DATASRC Dimension IN your Application.(Dimtype = D)
    FX-060     ERROR FX-060 No Local currency, You must have a currency with CURRENCY_TYPE Equal to L
         You must have one member with CURRENCY_TYPE = L (Local currency) In your currency dimension.
    FX-070     ERROR FX-070 No Entity available in your Application
         You have to select a parameter which is not a parent.
    FX-080     ERROR FX-080 No Time available in your Application
         Check if in the TIME Dimension, you have the property "MONTHNUM"
         Check if in the TIME Dimension, you have filled properly the property "MONTHNUM". The first Period of the Fiscal year must be 1, and then the second 2u2026.
    FX-090     ERROR FX-090 Problem IN Category Dimension check properties. 
         Your parameter CATEGORY is not valid.
    FX-100     ERROR FX-100 Problem IN Category OR Ratedim Dimension check properties. 
         Your parameter CATEGORY is not valid OR
         You don' t have the Property FX-SOURCE_CATEGORY In your Exchange Rate Dimension (For Simulation) OR
         The Exchange Rate id you chose doesn't exist.
    FX-110     ERROR FX-110 Problem IN Category Or Categhory_for_ope check properties. 
         Your parameter CATEGORY is not valid OR
         You don' t have the Property CATEGORY_FOR_OPE In your CATEGORY Dimension OR
         You don' t have the Property RATE_CATEGORY In your CATEGORY Dimension OR
         You don' t have the Property FX-DIFFERENCE_ONLY In your CATEGORY Dimension
    FX-120     ERROR FX-120 Problem IN Category Or TIME. 
    FX-130     ERROR FX-130 No Group available.
         Check if the selected group has the property CURRENCY_TYPE = "G".
    FX-140     ERROR FX-140 No Currency avalaible
    FX-150     ERROR FX-150 Problem IN Ownership
         Check if you have a base member equal to "METHOD" in the account dimension of the OWNERSHIP cube.
         Check If you have valid information in the OWNERSHIP cube for the selected Category  Time.
    FX-160     ERROR FX-160 No Entity available
    FX-170     ERROR FX-170 No Entity Available
    FX-180     ERROR FX-180 No Datasrc to be converted
    FX-190     ERROR FX-190 No Rate Application
    FX-200     ERROR FX-200 No Rate Extract From FactRate
         No Rate found for the selected category and time.
         Check If the Rateentiy you enter in the parameter is the Same as the one in the Rateentity Dimension
         Check If the Rates in the Rate Cube are in the RATE Dimension with Property Ratetype equal to "FX" OR "FX Rate".
    FX-210     Warning : No Rates found in the opening period
    FX-220     ERROR FX-220 No Rate for reference currency
         Check If you Pivot currency (The base currency to enter the rate, Rate = 1) is filled.
    FX-230     ERROR FX-230 Problem in your Entity Dimension id from your Rate application 
         The Rateentity (Dimension from the Rate cube with Evdimtype = E) you chose does not exist
    FX-240     ERROR FX-240 : No Rate Extract From MbrRate
         No Rate in the RATE Dimension with Property Ratetype equal to "FX" OR "FX Rate".
    FX-250     ERROR FX-250  No Rates found
    FX-260     ERROR FX-260 No Rate in Fact corresponding with Rate dimension
         Check If the Rates in the Rate Cube are in the RATE Dimension with Property Ratetype equal to "FX" OR "FX Rate".
    FX-270     ERROR FX-270 No Formulas extract from FXTRANS
         No Rate formulas in your Fxtrans Table.
         Check if the application name in the Logic.
    FX-280     ERROR FX-280 No values found (T_FIN)
         No values found for the selected Entities . Check if you have values in LC for the selected Entities OR
         Check if the LC values are fro DATASRC with Property IS_CONVERTED not equal to "N"
    FX-290     ERROR FX-290 No values found (Entity  - T_FINANCETMP)
    FX-300     ERROR FX-300 No values found (CLCFXTRANS  - T_FINANCE)
         No values found from FACT table for Account / Flow. Check if you have values in LC for the selected Account / Flow OR
         Check our Fxtrans Table.
    FX-310     ERROR FX-310 No values found (RATE  - T_DATA)
         No account extracted have a corresponding Rate_formula in the Fxtrans table.
    FX-320     ERROR FX-320 No values found (ENTITY - GROUPS - T_FINAL2)
         Check your Ownership and your group_currency values.
         SPRUNCONSO
    CSD-000     ERROR CSD-000 Application not Available !
         Appset maintenance in progress
    CSD-010     ERROR CSD-010 No Subtables. Verify properties FLOW_TYPE, IS_INPUT, SEGNOINV, SUBTABLES_ORIG  
         No Flow available, check the flow dimension, you must have the property "FLOW_TYPE"
    CSD-011     ERROR CSD-011 No instruction retreived from the ELIM table
         No instruction retreived from ELIM Table.
         Check If the Elim id in ELIM table Exist in the ELIMH Table.
         Check if the Account in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACCOUNT Dimension)
    CSD-012     ERROR CSD-012 No instruction retreived from the ELIM Table : GROUP_ACC Problem
         No instruction retreived from ELIM Table. GROUP_ACC Problem
         Check if the GROUP_ACC in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
    CSD-013     ERROR CSD-013 No instruction retreived from the ELIM Table : MINO_ACC Problem
         No instruction retreived from ELIM Table. MINO_ACC Problem
         Check if the MINO_ACC in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
    CSD-014     ERROR CSD-014 No instruction retreived from the ELIM Table : EQUITY_ACC Problem
         No instruction retreived from ELIM Table. EQUITY_ACC Problem
         Check if the EQUITY_ACC in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
    CSD-015     ERROR CSD-015 No instruction retreived from the ELIM Table with FLOW Dimension
         Check if the SUBTABLE_ORIG in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST in the FLOW Dimension)
    CSD-020     ERROR CSD-020 No Currency in your Appset ! You must have a Dimension with dimension type = u2018Ru2019 in your Application. !
         No Account extracted from CLCELIM Table, please check the Account from CLCELIM.
         Check if the ACCOUNT in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
    CSD-030     ERROR CSD-030 No Entity Available 
         No Entity extracted. Check if you have the Property INTCO and the property CURRENCY in your ENTITY Dimension
    CSD-040     ERROR CSD-040 No Account
         No Account Extract from Account Dimension
    CSD-050     ERROR CSD-050 No datasrc. Verify Properties DATASRC_TYPE,DATASRC_ORIG, IS_CONSOL
         No Datasrc extracted.
         Check if you have the Property "DATASRC_TYPE" and the property "IS_CONSOL" in your DATASRC Dimension
    CSD-060     ERROR CSD-060 No Rules
         No rules in your CLCRULES Table
         Make sure the METHOD from the CLCRULES is not blank.
         Make sure the I_METHOD from the CLCRULES is not blank.
    CSD-070     ERROR CSD-070 No Time available
         Check if in the TIME Dimension, you have the property "MONTHNUM"
         Check if in the TIME Dimension, you have filled properly the property "MONTHNUM". The first Period of the Fiscal year must be 1, and then the second 2u2026.
    CSD-080     ERROR CSD-080 No Group Available
         Check if the selected group has the property CURRENCY_TYPE = "G".
    CSD-090     ERROR CSD-090 Nothing Extracted From Ownership 
         Check if You have the property "IS_INPUT" in the Account dimension of the OWNESHIP Cube
         Check if You have some base member from the Account dimension of the OWNESHIP Cube with IS_INPUT = "Y"
         Check If you have valid information in the OWNERSHIP cube for the selected Category  Time.
    CSD-100     Warning : Nothing Extract From Ownership for OPENING Period 
         Nothing extracted from Opening period in the Ownership cube.
    CSD-110     ERROR CSD-110 No AccountOwn available
         Check if You have the property "IS_INPUT" in the Account dimension of the OWNESHIP Cube
         Check if You have the property "RATETPE" in the Account dimension of the OWNESHIP Cube
         Check if You have some base member from the Account dimension of the OWNESHIP Cube with IS_INPUT = "Y"
    CSD-120     ERROR CSD-120 No Entity - Method available
         No data found in OWNERSHIP Cube for this method.
         Check if you have METHOD in your ownership cube for the selected CATEGORY - TIME - GROUP
    CSD-125     ERROR CSD-125 No Entity - Method available 
         No data found in OWNERSHIP Cube for this method.
         Check if you have METHOD in your ownership cube for the selected CATEGORY - TIME - GROUP
    CSD-130     ERROR CSD-130 Problem Extracting data from the Fact Table
         No Values found
         Check if You have Some Account from the ELIM Table.
         Check if You have some DATASRC with IS_CONSOL = "Y"
    CSD-135     ERROR CSD-135 Problem Extracting data - C_FINANCE
         No Values found
         Check the Account in the FACT Tables
    CSD-140     ERROR CSD-140 Problem Extracting data  - C_DATA
         No Values found
         Check the Entity in the FACT Tables
         Check the INTCO in the FACT Tables
    CSD-145     ERROR CSD-145 Problem Extracting data  - C_DATA_ALL
         No Values found for those Account And/Or Flow.
         Check the DATASRC in the FACT Linked to the DATASRC_ORIG in the ELIMH Table.
    CSD-150     ERROR CSD-150 Problem Extracting data  - C_REPART
         No Values found for those rules.
         Check the method between METHOD Table and your ownership Cube.
         Check your Rules between the RULES Table and The ELIM Table.
         Check The INTCO.
    CSD-160     ERROR CSD-160 Problem Extracting data  - C_CONSO
         SPRUNCALC
    CALC-000     ERROR CALC-000 Application not Available !
         Appset maintenance in progress
    CALC-010     ERROR CALC-010 Nothing Extract from CALCACCOUNT TABLE  
         Nothing Extracted from CALCACCOUNT Table, check the account, The account must be a as Base Member or an Agregat or a Value in property DIMLIST or a value from property TYPELIM in the ACOUNT Dimension)
    CALC-020     ERROR CALC-020 Nothing Extract from CALCACCOUNT TABLE   (FLOWS)
         Nothing Extracted from CALCACCOUNT Table, check the Subtables, The Subtables must be a as Base Member or an Agregat or a Value in property DIMLIST in the FLOW Dimension)
    CALC-030     ERROR CALC-030 NoTime extract.
         Check your TIME Dimension
    CALC-040     ERROR CALC-040 NoTime extract for YTD
         Check your TIME Dimension.
         Check if in the TIME Dimension, you have the property "MONTHNUM"
         Check if in the TIME Dimension, you have filled properly the property "MONTHNUM". The first Period of the Fiscal year must be 1, and then the second 2u2026.
    CALC-050     ERROR CALC-050 NoEntity extract
         Check your Parameter Entity, it must be an base member (Or a list of base member)  from the ENTITY Dimension
    CALC-060     ERROR CALC-060 NoEntity extract
         Check your Parameter Currency, it must be a base member (Or a list of base member)  from CURRENCY Dimension
    CALC-070     ERROR CALC-070 NoEntity extract
         No values found, check if you have something to calculate for the selected CATEGORY - TIME - CURRENCY
         Check your CALCACCOUNT Table.
         Check : The account must be a as Base Member or an Agregat or a Value in property DIMLIST or a value from property TYPELIM in the ACOUNT Dimension)
    CALC-080     ERROR CALC-080 NoEntity extract
         No Values found.
         Check your CALCACCOUNT Table.
         Check : The SUBTABLES must be a as Base Member or an Agregat or a Value in property DIMLIST in the FLOW Dimension)
         SPCOPYCATEGORY
    CCAT-000     ERROR CCAT-000 Application not Available !
         Appset maintenance in progress
    CCAT-010     ERROR CCAT-010 No Time available in your Application
         Check your Parameter "Time".
    CCAT-020     ERROR CCAT-020 Nothing extracted from the Account Dimension
         Check the property in the parameter.
         Check that this property is in the ACCOUNT Dimension
    CCAT-030     ERROR CCAT-030 No Entities available
         Check your Parameter "Entity".
    CCAT-040     ERROR CCAT-040 No Currency available
         Check your Parameter "Currency".
    CCAT-050     ERROR CCAT-050 No data found
         No data found, check if you have data for the selected CATEGORY - TIME - CURRENCY
         SPCOPYOPENING
    COPYO-000     ERROR COPYO-000 Application not Available !
         Appset maintenance in progress
    COPYO-010     ERROR COPYO-010 No Datasrc Available
         Check if you have Datasrc with DATASRC_TYPE different from "A"
         Check if COPYOPENING Property is equal to Y
    COPYO-020     ERROR COPYO-020 Nothing extracted from COPYOPENING TABLE
         Check your COPYOPENING TABLE
    COPYO-030     ERROR COPYO-030 No Time available
         Check your Parameter "Time".
    COPYO-040     ERROR COPYO-040 No category available
         Your parameter CATEGORY is not valid OR
         You don' t have the Property CATEGORY_FOR_OPE In your CATEGORY Dimension OR
         You don' t have the Property OPENING_YEAR In your CATEGORY Dimension OR
         You don' t have the Property OPENING_PERIOD In your CATEGORY Dimension
    COPYO-045     ERROR COPYO-045 No category available
         Your parameter CATEGORY is not valid
    COPYO-050     ERROR COPYO-050 Problem in COPYOPENING Properties
         Check Opening_year and / Or  Opening period properties in CATEGORY Dimension.
    COPYO-060     ERROR COPYO-060 No Entities available
         Check your Parameter "Entity".
    COPYO-070     ERROR COPYO-070 No Currency available
         Check your Parameter "Currency".
    COPYO-080     ERROR COPYO-080 No Account available
         Check your COPYOPENING Table
         Check if the Account in the COPYOPENING Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACCOUNT Dimension)
    COPYO-090     ERROR COPYO-090 No Data found
         Check if you have data for the selected CATEGORY - TIME - GROUP
         SPRUNVALID
    VALID-000     ERROR VALID-000 Application not Available !
         Appset maintenance in progress
    VALID-010     ERROR VALID-020 Nothing extracted from VALIDATION TABLE
         Check your VALIDATION TABLE
    VALID-020     ERROR VALID-020 Nothing extracted from VALIDATION_H TABLE
         Check your VALIDATION_H TABLE
    VALID-030     ERROR VALID-030 Wrong Application, check your logic
         You may have hardcoded a wrong application in your logic.
    VALID-040     ERROR VALID-040 No Datasrc available
         Check your Parameter "DATASRC".
    VALID-050     ERROR VALID-050 No Time available
         Check your Parameter "Time".
    VALID-060     ERROR VALID-060 Nothing extracted from VALIDATION - VALIDATION_H Table
         Check your VALIDATION TABLE
         Check your VALIDATION_H TABLE
         Check the validation iD in VALIDATION and VALIDATION_H Table.
    VALID-070     ERROR VALID-070 No Data found
         Check if you have data for the selected CATEGORY - TIME - GROUP
    VALID-080     ERROR VALID-080 No Data found for the selected period
         Check your PERIOD Property in the VALIDATION_H Table

  • [wscompile] error: invalid remote interface

    I have an interface I want to publish as a web service. This interface extends java.rmi.Remote and each of its methods throws a RemoteException. But when I run wscompile (via ant) against this interface in order to have the wsdl file generated it gives me:
    error: invalid remote interface; class manplan.j2ee.service.project.ProjectManager is not an interfacee
    I have searched the forum and the internet yet could not find an answer. Any hints are most welcome. Below you will find excerpts from the relevant files.
    Cheers,
    Olaf
    [interface]
    public interface ProjectManager extends java.rmi.Remote
         void createProject(final Project project) throws DuplicateProjectException,
                   ProjectManagementRuntimeException, RemoteException;
    [ant]
    <wscompile
         keep="true"
         define="true"
         base="${ws.build.classes.dir}"
         xPrintStackTrace="true"
         verbose="true"
         model="${ws.build.dir}/${ws.model.rpcenc.file}"
         config="${ws.conf.rpcenc.file}">
         <classpath>
              <path refid="ws.class.path"/>
         </classpath>
    </wscompile>
    [interface-config.xml]
    <configuration
    xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
    <service
    name="ProjectManagementService"
    targetNamespace="urn:manplan:Services"
    typeNamespace="urn:manplan:Types"
    packageName="manplan.j2ee.webservice">
    <interface name="manplan.j2ee.service.project.ProjectManager"/>
    </service>
    </configuration>

    OK. Found it: unlike Axis' java2wsdl does wscompile not support JavaBeans and so it gets confused by all those Project params and return types. So I guess wscompile is not the right tool for me in this situation?
    Cheers,
    Olaf

  • Wscompile - error: in message "SystemSupportException", part "fault" ...

    Hey,
    did anybody ever face this problem? I am working on it since hours, but cannot find any solution. my wsdl was generated from websphere studio
    application developer 5.1.2. and now I run wscompile and get these error
    messages.
    when I compile my wsdl to get the client side artifacts like stub, etc and I get the following error message:
    error: in message "SystemSupportException", part "fault" must specify a "element" attribute
    the whole stack looks like this:
    in message "SystemSupportException", part "fault" must specify a "element" attri
    bute
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.handleLiteralS
    OAPFault(WSDLModelerBase.java:1893)
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOpe
    rationRPCLiteralStyle(WSDLModelerBase.java:1764)
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOpe
    ration(WSDLModelerBase.java:663)
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processPort(WS
    DLModelerBase.java:548)
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processService
    (WSDLModelerBase.java:385)
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.internalBuildM
    odel(WSDLModelerBase.java:238)
    at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSD
    LModelerBase.java:146)
    at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:
    85)
    at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
    at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:571)
    at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
    at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22)
    error: in message "SystemSupportException", part "fault" must specify a "element
    " attribute
    my wsdl:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://core.rbac.csap2" xmlns:impl="http://core.rbac.csap2" xmlns:intf="http://core.rbac.csap2" xmlns:tns2="http://exceptions.csap2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
      <schema targetNamespace="http://core.rbac.csap2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:impl="http://core.rbac.csap2" xmlns:intf="http://core.rbac.csap2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
       <element name="sessionId" nillable="true" type="xsd:string"/>
       <element name="name" nillable="true" type="xsd:string"/>
       <element name="password" nillable="true" type="xsd:string"/>
       <element name="loginAndCreateSessionReturn" nillable="true" type="xsd:string"/>
      </schema>
      <schema targetNamespace="http://exceptions.csap2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:impl="http://core.rbac.csap2" xmlns:intf="http://core.rbac.csap2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
       <complexType name="SystemSupportException">
        <complexContent>
         <extension base="tns2:CSAP2Exception">
          <sequence/>
         </extension>
        </complexContent>
       </complexType>
       <complexType name="CSAP2Exception">
        <sequence>
         <element name="message" nillable="true" type="xsd:string"/>
        </sequence>
       </complexType>
       <element name="SystemSupportException" nillable="true" type="tns2:SystemSupportException"/>
      </schema>
    </wsdl:types>
       <wsdl:message name="SystemSupportException">
          <wsdl:part name="fault" type="tns2:SystemSupportException"/>
       </wsdl:message>
       <wsdl:message name="logoutResponse">
       </wsdl:message>
       <wsdl:message name="logoutRequest">
          <wsdl:part name="sessionId" type="xsd:string"/>
       </wsdl:message>
       <wsdl:message name="loginAndCreateSessionResponse">
          <wsdl:part name="loginAndCreateSessionReturn" type="xsd:string"/>
       </wsdl:message>
       <wsdl:message name="loginAndCreateSessionRequest">
          <wsdl:part name="name" type="xsd:string"/>
          <wsdl:part name="password" type="xsd:string"/>
       </wsdl:message>
       <wsdl:portType name="SystemSupport">
          <wsdl:operation name="logout" parameterOrder="sessionId">
             <wsdl:input message="intf:logoutRequest" name="logoutRequest"/>
             <wsdl:output message="intf:logoutResponse" name="logoutResponse"/>
             <wsdl:fault message="intf:SystemSupportException" name="SystemSupportException"/>
          </wsdl:operation>
          <wsdl:operation name="loginAndCreateSession" parameterOrder="name password">
             <wsdl:input message="intf:loginAndCreateSessionRequest" name="loginAndCreateSessionRequest"/>
             <wsdl:output message="intf:loginAndCreateSessionResponse" name="loginAndCreateSessionResponse"/>
             <wsdl:fault message="intf:SystemSupportException" name="SystemSupportException"/>
          </wsdl:operation>
       </wsdl:portType>
       <wsdl:binding name="SystemSupportSoapBinding" type="intf:SystemSupport">
          <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="logout">
             <wsdlsoap:operation soapAction=""/>
             <wsdl:input name="logoutRequest">
                <wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
             </wsdl:input>
             <wsdl:output name="logoutResponse">
                <wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
             </wsdl:output>
             <wsdl:fault name="SystemSupportException">
                <wsdlsoap:fault name="SystemSupportException" use="literal"/>
             </wsdl:fault>
          </wsdl:operation>
          <wsdl:operation name="loginAndCreateSession">
             <wsdlsoap:operation soapAction=""/>
             <wsdl:input name="loginAndCreateSessionRequest">
                <wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
             </wsdl:input>
             <wsdl:output name="loginAndCreateSessionResponse">
                <wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
             </wsdl:output>
             <wsdl:fault name="SystemSupportException">
                <wsdlsoap:fault name="SystemSupportException" use="literal"/>
             </wsdl:fault>
          </wsdl:operation>
       </wsdl:binding>
       <wsdl:service name="SystemSupportService">
          <wsdl:port binding="intf:SystemSupportSoapBinding" name="SystemSupport">
             <wsdlsoap:address location="http://localhost:9080/CSAP2SysSupRouter/services/SystemSupport"/>
          </wsdl:port>
       </wsdl:service>
    </wsdl:definitions>I would be glad to get a response to this topic. I am really on my personal limits!
    thanks and regards,
    simon

    hi,
    first of all your service user : SID_PIRWBUSR
    has a wrong name it sould be PIRWBUSR
    so check where did you define this SID_PIRWBUSR
    Regards,
    michal

  • Error documented goods movements

    Hello PP experts
    I have done the good issue of the components of a process order.
    If I ckeck it in the order in Lits-> documented goods movement, sytem showe me an error  'There is no data for the selection'
    What is wrong? why does not show me the movements of good issue?
    Thanks in advance

    Dear
    Order type dependent parameters- Implementation tab - Documentation of goods movements - Make tick mark for all.

  • Wscompile, error: the following naming conflicts...

    Hi,
    I am stuck with a naming conflict in some wsdl that I cannot change.
    The issue is apparently related to the names of types that differ
    only by the case of the first letter, one is upper, the other is lower.
    wscompile apparently tries to fix that with the generation of a Xxxx_Type
    but fails.
    I have investigated the <typeMappingRegistry> thing in the config.xml
    for xml but there are very little info about that and so far, no success.
    Any clue ? Thanks.

    Nota: The error occurs in wsi mode, i.e. document/literal mode.
    One of the involved types, the simple one, is actually generated
    from the operation name, this may be relevant.
    Cheers.
    JeanHuguesRobert

  • Form Error Documentation

    Can someone tell me why oracle has removed all documentation about oracle errors from this website? I have a FRM-40735 error in forms builder 9i, and there are no resources to find out what this means. Pretty stupid if you ask me
    adam

    What version of Forms is it ? In 9.0.4.1.0 all FRMs all back.

  • Wscompile error : duplicate

    environment: JAX-RPC Standard Implementation (1.1.2_01, build R40)
    Server: Sun Application Server 8.0
    Problem Statement:
    We have two schemas suppose abc.xsd and cde.xsd which refer to one another i.e. abc.xsd imports cde.xsd and vice-versa (circular referencing).
    There is a WSDL that imports in the type definition another schema say A.xsd which in turn imports abc.xsd. config-wsdl.xml refers to this WSDL.
    On running the following command to generate server side artifacts:
    wscompile -gen:server -d build -classpath build -mapping mapping.xml config-wsdl.xml
    we get the following error:
    error: modeler error: duplicate "element" entity
    Is there any mechanism (like setting a flag/using some option )by which wscompile should include definitions of the schemas only once or some other solution to overcome this duplicate element entity error. Since there is no control over xsd's, we cannot modify the schema.
    Thanks in advance
    Regards
    anjali

    Hi,
    I have a duplicate error of another reason. I try to generate client stubs on a WSDL which has many identical type names but in different namespaces.
    - Is there any way to tell wscompile to map the different namspaces automatically to different packagenames?
    There will be more and more such webservices with identical types in different namespaces in it. I have to use them and I wan't have the possibility to write for each single webservice explicit namspace / packagename mappings in the config files.
    - Does somebody know a solution?

  • Wscompile error : exclusive attributes: "type", "substitutionGroup"

    Hi All,
    I'm trying to use wscompile with a WSDL file and a set of XSDs. It keeps failing with the following error
    error: modeler error: model error: exclusive attributes: "type", "substitutionGroup"
    all the XSDs are standard files available in "http://www.starstandards.org/STAR"
    wscompile version is "JAX-RPC Standard Implementation (1.1.3, build R1)" and I am able to deploy services/access them using our own XSDs and the same approach.
    Appreciate if anyone could help me figure out a solution for this.
    Thanks,
    Nilantha

    I'm getting the exact same problem when I compile my wsdl - hopefully someone will come up with a solution or at least a lead!!
    Russ

  • Wscompile error with PayPalSvc.wsdl

    Hi,
    I am trying to use wscompile to generate the client artifacts for the PaypalSvc.wsdl file.
    The error is: error: modeler error: duplicate "complexType" entity: "AmountType"
    The link to the wsdl file is: http://www.sandbox.paypal.com/wsdl/PayPalSvc.wsdl
    My version of wscompile is: JAX-RPC Standard Implementation (1.1.2_04, build R45)
    Thanks,
    Jim

    We are having the same problem with the case changes in WSDL generation, preventing us from upgrading, too.  Haven't heard a peep from Adobe on it.
    - http://forums.adobe.com/message/1053957
    Wish I could help more.
    Fred

Maybe you are looking for

  • Performance issue-Report

    Hi, I have developed FI report which is having 18 laks records, the time taken is more than 45 hrs,please any one can help me in the performance wise. SELECT ZBUKR          RZAWE          LIFNR          KUNNR          ZNME1          VBLNR          RW

  • Error while creating SC: Message E COM_PRODUCT_SETTINGS 001

    Hi Experts, When try to create a SC the error message is through: Message E COM_PRODUCT_SETTINGS 001 cannot be processed in plug mode HTTP. I am configuring the SRM7.0 for the first time and system throws the error message. Kindly help to resolve thi

  • My imac is frozen with the following notice:  USB over current notice.  have tried powered hub, no help.  have tried unplug and restart, no help.  any suggestions?

    my imac is frozen with the pop up notice of "usb over current notice, a usb device is currently drawing too much power.  the hub it is attached to will be deactivated".  have tried unplug and restart, no help.  have tried power hub, no help.  my wire

  • Html tags br and hr in JEditorPane

    I have a JEditorPane that is used to display html data. The data is obtained from an xml file, transformed to html using a stylesheet and rendered in the JEditorPane using setContentType("text/html") and setText() methods. However the <br/> and <hr/>

  • My iPod will not charge.

    When i went to plug my ipod into the charger, the battery came up saying it needed awhile to recharge. So i left it for 4 hours. And when i came back it said the same thing. It has been stuck on this low battery and wont even let me onto my lock scre