JAXB Compiler Interface generation problem

I have a schema where two different elements extend the same base type. The JAXB compiler throws the following error. How do I fix this?
parsing a schema...
An interface with the same name "generated.FooType" is generated from more than one schema component.
line 10 of sample.xsd
(Relevant to above error) another one is generated from this schema component.
line 23 of sample.xsd
Failed to parse a schema.
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" >     <xsd:element name="Sample" type="Sample_Type"/>
     <xsd:complexType name="Sample_Type">
          <xsd:sequence>
                    <xsd:element     ref="Foo"/>
                    <xsd:element     ref="Bar"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="Foo">
          <xsd:complexType>
               <xsd:complexContent>
                    <xsd:extension base="Foo_Type"/>
          </xsd:complexContent>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="Bar">
          <xsd:complexType>
               <xsd:complexContent>
                    <xsd:extension base="Foo_Type"/>
               </xsd:complexContent>
          </xsd:complexType>
     </xsd:element>
     <xsd:complexType name="Foo_Type">
               <xsd:sequence>
                         <xsd:element ref="FooBar"/>
                    </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="FooBar" type="FooBar_Type"/>
     <xsd:simpleType name="FooBar_Type">
          <xsd:restriction base="xsd:long"/>
     </xsd:simpleType>
</xsd:schema>

The problem is because of you have a complex type Foo_Type
Solution:
=============
Replace all occurences of Foo_Type with something else say "Some_Type"
It should work
Explaination:
=============
Basically you were getting FooType generated from 2 cases. You have an element "Foo" inside which you have an anonymous complex type. So the java class for the anonymous complex type would be "FooType"
Then you had a named complex type Foo_Type and the java class would be "FooType" again because "_" is removed when generating classes
Hence the compiler reported the error
For more explaination see Section 5.7.2 of the spec Also Table 3.2 of the spec
Also you seem to be using xjc <schemafile>
Hence the code by default gets generated in package "generated"
Recommendation
=============
Use xjc -p com.something <schemafile>
to get the package com.something

Similar Messages

  • JAXB XJC class generation problem

    Hi!, I�m trying to generate the classes for the IMS-LearningDesign schema:
    xjc -d src_temp -p edu.eci.ims.ld IMS_LD_Level_A.xsd
    parsing a schema...
    [ERROR] Attempt to create a property having the same name as the reserved word "Class".
    line 177 of IMS_LD_Level_A.xsd
    The problem is that schema has a 'class' attribute, and that`s a reserved word for JAXB.
    When the schema is modified (add a character to the attribute name - oclass) it works fine, but I need to keep the standard specification (to parse standard XML - LD files). What can I do to solve this problem without modifying the schema?

    I'd suggest you repost this to the JAXB users mailing list at Java.Net. That list is monitored by the JAXB implementation team.
    Check http://jaxb.dev.java.net/

  • JAXB, Compiling a schema problem

    Hi,
    I�m trying to test the examples from the JWSDP tutorial (section "Using JAXB") and I get the following error when executing:
    C:\tutoriales\jwstutorial13\examples\jaxb\unmarshal-read>%JWSDP_HOME%\jaxb\bin\xjc.bat po.xsd -p primer.po
    parsing a schema...
    compiling a schema...
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: java.lang.NullPointerException
    at com.sun.tools.xjc.generator.SkeletonGenerator.generateStaticRuntime(SkeletonGenerator.java:233)
    at com.sun.tools.xjc.generator.SkeletonGenerator.<init>(SkeletonGenerator.java:128)
    at com.sun.tools.xjc.generator.SkeletonGenerator.generate(SkeletonGenerator.java:108)
    at com.sun.tools.xjc.Driver.generateCode(Driver.java:366)
    at com.sun.tools.xjc.Driver.run(Driver.java:215)
    at com.sun.tools.xjc.Driver._main(Driver.java:80)
    at com.sun.tools.xjc.Driver.access$000(Driver.java:46)
    at com.sun.tools.xjc.Driver$1.run(Driver.java:60)
    I suppose could be configuration issues or path issues but I can�t get over it.
    Thanks

    http://forum.java.sun.com/thread.jsp?forum=34&thread=484038&tstart=0&trange=15

  • JAXB compiler error : Complex Type Definition Representation Error

    Hi,
    I have a problem when I try to generate Java classes for the XML Digital Signature schema along with the XAdES extension. Apparently, we got an XML validation issue when the XAdES schema is parsed.
    Here is the xjc tool ouput :
    [ERROR] src-ct.1: Complex Type Definition Representation Error for type 'IdentifierType'.  When complexContent is used, the base type must be a complexType.
      line 33 of XAdES.xsd
    [ERROR] src-ct.1: Complex Type Definition Representation Error for type 'EncapsulatedPKIDataType'.  When complexContent is used, the base type must be a complexType.
      line 57 of XAdES.xsdNow these are the schema lines from XAdES.xsd that cause the problem :
    <xsd:complexType name="IdentifierType">
      <xsd:complexContent>
        <xsd:extension base="xsd:anyURI">
          <xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
        </xsd:extension>
      </xsd:complexContent>
    </xsd:complexType>
    <xsd:complexType name="EncapsulatedPKIDataType">
      <xsd:complexContent>
        <xsd:extension base="xsd:base64Binary">
          <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
        </xsd:extension>
      </xsd:complexContent>
    </xsd:complexType>The most disturbing thing is that those two schemas I used (e.g. xmldsig-core-schema.xsd and XAdES.xsd) come directly from the W3C, so they should be fully compliant to the XML schema spec, shouldn't they ?
    Moreover, I tried to validate these two schemas with XML Spy 4.3 and the problem occurs in slightly different way. In fact, the <xsd:complexContent> tags are replaced silently by XML Spy with <xsd:simpleContent> tags in order to validate the schema. So XML Spy seems to have a problem too with these complex type definitions. Besides, if I replace the <xsd:complexContent> tags the same way as XML Spy does, and if I run again the JAXB compiler, it works fine...
    Does anyone have any knowledge about this issue ? I'd like very much to hear about anyone who has experienced or better solved the same kind of issue.
    By the way, here is the version of JAXB that I use :
    xjc version "1.0.2-b15-fcs"
    JavaTM Architecture for XML Binding(JAXB) Reference Implementation, (build 1.0.2-b15-fcs)Any help appreciated.
    Thanks,
    Gregory

    <xsd:extension base="xsd:anyURI">
    <xsd:extension base="xsd:base64Binary">
    The base attribute of the xs:extension elements shoule refer to a complexType.
    For example,
    <xs:complexType name="complexTypeA">
    </xs:complexType>
    <xsd:complexType name="IdentifierType">
    <xsd:complexContent>
    <xsd:extension base="complexTypeA">
    <xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>

  • IMAQdx External Compiler Interface

    Hello,
    I wish to use the IMAQdx and NI-Vision External Compiler Interfaces with Cygwin gcc/g++ compilers.
    I am already doing this sort of game without any problem with the NI-VISA and NI-DAQmx External Interfaces (g++ appears to be happy with the dll files in C:\WINDOWS\system32 for NI-VISA, NI-488.2 and NI-DAQmx).
    I have written a simple C test code that calls IMAQdx symbols.
    I compile it from Cygwin terminal with the command :
    gcc -I/cygdrive/c/PROGRA~1/NATION~1/Shared/EXTERN~1/C/include TestIMAQdx.c -L/cygdrive/c/WINDOWS/system32 -lniimaqdx -lnivision
    It apparently compiles and links fine, but I get unreliable behavior and segmentation faults.
    (But the camera is found and I get some informations from it, so the symbols are somehow found. But there seems to be some problems with memory alignments)
    If I compile the very same C test code with MSVC from the Microsoft Visual Studio command line:
    cl -IC:\PROGRA~1\NATION~1\Vision\Include -IC:\PROGRA~1\NATION~1\NI-IMA~1\include TestIMAQdx.c /link C:\PROGRA~1\NATION~1\Vision\Lib\MSVC\nivision.lib C:\PROGRA~1\NATION~1\NI-IMA~1\lib\msvc\niimaqdx.lib
    Then, everything works fine. So, I guess it is not a bug in my C source file, but rather some incompatibilities between the library and the compiler. But since it is a C interface (and not, eg. a C++ interface, with ABI problems), I see no reason why it shouldn't work.
    However, I cannot use MSVC for my application because I require linking with several Cygwin C++ libraries that are not compatible with MSVC (for ABI reasons). Since IMAQdx are C interfaces, it SHOULD work.
    So:
    Is there a compatible interface library available somewhere ? Could NI possibly provide a standard external interface ?
    What could I possibly do to have g++ link properly ?
    Why does it work like a charm with VISA and DAQmx, and not with IMAQdx and Vision ?
    Thank you for your help.
    Attachments:
    TestIMAQdx.c ‏4 KB

    Hi jsalort,
    I have reproduced this issue with the code you provided. Specifically, I noted that some of the calls were corrupting the stack. This appears to be due to a mismatched calling convention. Looking at NIIMAQdx.h, it appears that the calling convention (stdcall for most functions) is NOT declared when __GNUC__ is defined (presumably under the assumption that GCC platforms were non-Windows and did not deal with multiple calling conventions).
    I think you can work around this on your own by putting the following before including NIIMAQdx.h:
    #define _NI_FUNC_DEFINED
    #define NI_FUNC         __stdcall
    #define NI_FUNCC       __cdecl
    I have also filed this issue as CAR #410920 so that it can be addressed in the header file itself.
    Eric

  • Ivette manzur : Interface errors problems on cisco 3560

    Hello,
    I have a problem on one of the interfaces on a cisco 3560 switch. In fact, I set up a monitoring network recently (cacti), and I have a significant number of errors on the interfaces. the problem is that when I do a sh interface I see no errors, and even by making a clear counters it does not solve my problem .. I also changed the wiring with cat 6 cables but nothing has changed ..
    What are the main causes of errors on an interface of a switch? what should I do in this case?
    Thank you for your help in advance
    ivette manzur

    Hello,
    I've a e61i and I experience a similar problem. My phone work very well on WiFi network with no encryption as well as 64-bit wep.
    At home I've 2 wireless routers, both encrypted at 128 bits, one with WEP and the other with WPA. On both of them I can correctly obtain an IP thru DHCP, but the traffic do not go thru.
    By using IfInfo I think I discovered the reason of the problem (unless IfInfo is not working properly...) and it seems a bug related to the netmask, broadcast and gateway settings. The router is 192.168.15.1 and this is what I get:
    1) DHCP case -- I get two IP adresses: the 169.254.x.x and the one assigned to the router. DNS is also set properly, but both gateway, broadcast and netmask are set to 0.0.0.0 for both IPs.
    IP Addr: 169.254.162.106
    Netmask: 0.0.0.0
    Broadcast: 0.0.0.0
    Gateway: 0.0.0.0
    DNS1: 192.168.15.1
    IP Addr: 192.168.15.100
    Netmask: 0.0.0.0
    Broadcast: 0.0.0.0
    Gateway: 0.0.0.0
    DNS1: 192.168.15.1
    2) Static IP 192.168.15.64, netmask set to 255.255.255.0 and gateway and DNS set to 192.168.15.1. The 169.254.x.x disappears and I get only one IP which is set to:
    IP Addr: 192.168.15.64
    Netmask: 0.0.0.0
    Broadcast:192.168.15.255
    Gateway: 192.168.15.1
    DNS1: 192.168.15.1
    So in conclusion, it seems that with 128bit encryption, in the DHCP case gateway, broadcast and netmask are not assigned correctly! While in the Static IP case the netmask is still not assigned correctly!!!
    Hope this can help...
    --AP

  • How to use schemas in MDS with the JDeveloper JAXB compiler ?

    Hello,
    I would like to use the JAXB2 compiler to generate a content model from an XSD in MDS. I don't find any way to do it because in order to select the source schema I only can browse my project and application directory but not the MDS. I configured JDeveloper such that to connect to MDS and I'm able to browse the MDS, to open artifacts. But I cannot extract/export/download them from MDS to the JDeveloper project such that to use the JAXB compiler against it. I tried the Add to project function once that the artifact is opned but nothing seems to happen. How could I do that ?
    Many thanks in advance,
    Nicolas

    hi Henrique Pinto!
    but you'll need to import all the wsdl's,,,
    this mean that i will have to request another wsdl which is general wsdl contained object and operation and soap action?
    or i can use only this wsdl and then need to do something in external definition with this wsdl?
    thanks & regards
    dennis
    Message was edited by:
            ogawa Dennis

  • Compiler Code Generation API

    I would like to ask if you guys could make a Compiler Code Generation API.  This would allow developers who would like to fine-tune details you guys probably don't have time to do, for projects we think its important on.  Specifically with [Bindable] and {} code generation.
    I would like to be able, and many others I'm sure, to turn Binding on/off (conditional binding), and add more complicated expressions, but that's currently impossible, unless I rewrote the core UIComponent and everything.  Or unless I had access to the generated code through a nice API which shouldn't take you guys long at all: you already are generating lots of code and have templates for it, I would just like to ask for easy access to those templates.
    Please let me know what you think.  Thanks a lot for your time.
    Lance

    It's something we've thought about but it's not a high enough priority right now.  Certainly a feature that folks could think about implementing on their own and contributing back though.  It tends to be more complicated than you'd think though
    Matt

  • JAXB compilation error

    I got this error when executing a jaxb compilation against my xml schema
    JAXB Compilation Exception: java.lang.Exception: Un problème est survenu parce que des fonctions de schéma XML non prises en charge sont utilisées dans le schéma. La définition de contraintes d'identité (identity-constraint), à savoir "key", "keyref" et "unique", n'est pas prise en charge. Utilisez le paramètre -extension.
    Here is my xml schema :
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:element name="classification">
              <xs:annotation>
                   <xs:documentation source="../classification-reference-fr.doc" xml:lang="fr">Documentation de référence en français</xs:documentation>
                   <xs:documentation source="../classification-reference-de.doc" xml:lang="de">Deutsche Referez Beschreibungen des Schema</xs:documentation>
                   <xs:documentation source="../classification-reference-it.doc" xml:lang="it"/>
                   <xs:documentation source="../classification-reference-en.doc" xml:lang="en"/>
              </xs:annotation>
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="classification-name" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation xml:lang="fr">Dénomination de la classification gérée dans le document</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:simpleContent>
                                       <xs:restriction base="classification-nameType"/>
                                  </xs:simpleContent>
                             </xs:complexType>
                        </xs:element>
                        <xs:element ref="classification-version" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation xml:lang="fr">Liste des versions de la classification gérée dans le document. Les entrées originales sont maintenus si elles sont modifiées. Chaque modification est associée à une version. Les états antérieurs ou la liste des changements intervenus à chaque nouvelle version peuvent être obtenus en tout temps.</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="classification-language">
                             <xs:complexType>
                                  <xs:sequence>
                                       <xs:element name="classification-language-code" type="xs:language">
                                            <xs:annotation>
                                                 <xs:documentation xml:lang="fr">Code de la angue dans laquelle la classification peut être publiée</xs:documentation>
                                            </xs:annotation>
                                            <xs:unique name="classification-language-code-unique">
                                                 <xs:selector xpath="classification-language-code"/>
                                                 <xs:field xpath="."/>
                                            </xs:unique>
                                       </xs:element>
                                       <xs:element name="classification-language-label" type="xs:string">
                                            <xs:annotation>
                                                 <xs:documentation xml:lang="fr">Libellé de la angue dans laquelle la classification peut être publiée</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="classification-entry" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation xml:lang="fr">Entrées de premier niveau de la classification. Les entrées dépendantes sont répertoriées dans l'élément classification-entry-child qui met en oeuvre le même type que le présent élément. La hierarchie est donc récursive jusqu'au niveau de détail souhaité.</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:complexContent>
                                       <xs:extension base="classification-entryType"/>
                                  </xs:complexContent>
                             </xs:complexType>
                        </xs:element>
                   </xs:sequence>
                   <xs:attribute name="schema-version" type="xs:string" use="required" fixed="1.0"/>
              </xs:complexType>
         </xs:element>
         <xs:complexType name="classification-nameType" mixed="true">
              <xs:simpleContent>
                   <xs:extension base="classification-titleType"/>
              </xs:simpleContent>
         </xs:complexType>
         <xs:element name="classification-version">
              <xs:complexType>
                   <xs:simpleContent>
                        <xs:extension base="xs:string">
                             <xs:attribute name="validity-from-date" type="xs:date" use="required"/>
                             <xs:attribute name="validity-to-date" type="xs:date" use="optional"/>
                             <xs:attribute name="publication-date" type="xs:date" use="optional"/>
                        </xs:extension>
                   </xs:simpleContent>
              </xs:complexType>
              <xs:unique name="classification-version-unique">
                   <xs:selector xpath="classification-version"/>
                   <xs:field xpath="."/>
              </xs:unique>
         </xs:element>
         <xs:complexType name="classification-entryType">
              <xs:sequence>
                   <xs:element name="classification-entry-identification" type="xs:string">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Code d'identification interne unique. Il est librement déterminé par les personnes chargées de la gestion de la classification. Chaque entrée est identifiée de manière unique au moyen de ce code.</xs:documentation>
                        </xs:annotation>
                        <xs:unique name="classification-id-unique">
                             <xs:selector xpath="classification-entry-identification"/>
                             <xs:field xpath="."/>
                        </xs:unique>
                   </xs:element>
                   <xs:element name="classification-entry-code" type="xs:string">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Code de la classification pour ce niveau d'entrée. La classification est organisée sous la forme d'une hierarchie. Les niveaux précédents ne sont pas contenus dans le présent code, ils découlent du code du précédent niveau dans lequel l'entrée a été introduite.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="classification-entry-code-fullPath" type="xs:string">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Code complet de la classification comprenant tous les codes des niveaux précédents et le code du présent niveau. Le code complet est généré, il ne devrait a priori ne pas être modifié manuellement. Il représente une clé utilisée pour les références utilisées lorsque des liens entre les entrées autre que hierarchiques sont déclarés.</xs:documentation>
                        </xs:annotation>
                        <xs:unique name="classification-entry-code-fullPath">
                             <xs:selector xpath="classification-entry-code-fullPath"/>
                             <xs:field xpath="."/>
                        </xs:unique>
                   </xs:element>
                   <xs:element name="classification-entry-status">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Statut qui active ou desactive l'entrée. Le statut permet de gérer des entrées à titre historique, notamment des codes qui n'ont plus court mais qui ont existé dans des versions précédentes.</xs:documentation>
                        </xs:annotation>
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:enumeration value="enable"/>
                                  <xs:enumeration value="disable"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="classification-entry-title" type="classification-entry-titleType">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Ensemble de titres pour l'entrée de la classification</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="classification-entry" type="classification-entryType" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Classification dépendante de la l'entrée de la classification</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="classification-id-ref" refer="classification-id-unique">
                             <xs:selector xpath="classification-entry-reference"/>
                             <xs:field xpath="."/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="classification-entry-update" type="classification-entry-updateType" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Gestion des modification et des versions des entrées de la classification</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="classification-entry-link" type="classification-entry-linkType" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Liens non hierarchiques entre les entrées de la classification. Ces liens sont utilisésen particulier pour gérer les inclusions ou exclusions.</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="classification-entry-link-keyref" refer="classification-entry-code-fullPath">
                             <xs:selector xpath="classification-entry-link"/>
                             <xs:field xpath="."/>
                        </xs:keyref>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="classification-entry-titleType">
              <xs:sequence>
                   <xs:element name="classification-entry-main-title" type="classification-main-titleType" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Titre principal de l'entrée de la classification. Les différents type de titres sont publiés de manière distinctes. Plusieurs titres principaux peuvent être introduits pour une même langue. Ils seront publiés dans l'ordre dans lesquels ils sont placés dans le document.</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="classification-entry-main-title-language-keyref" refer="classification-language-code-unique">
                             <xs:selector xpath="classifcation-entry-main-title"/>
                             <xs:field xpath="@language"/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="classification-entry-complementary-title" type="classification-complementary-titleType" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Titre complémentaire de l'entrée de la classification. Les différents type de titres sont publiés de manière distinctes. Plusieurs titres comolémentaire peuvent être introduits pour une même langue. Ils seront publiés dans l'ordre dans lesquels ils sont placés dans le document.</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="classification-entry-complementary-title-language-keyref" refer="classification-language-code-unique">
                             <xs:selector xpath="classifcation-entry-complementary-title"/>
                             <xs:field xpath="@language"/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="classificatin-entry-index-title" type="classification-index-titleType" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Titre utilisé pour les entrées dans les différents index lorsqu'ils sont différents du texte prévu dans l'index principal ou les entrées complémentaires.</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="classification-entry-index-title-language-keyref" refer="classification-language-code-unique">
                             <xs:selector xpath="classifcation-entry-index-title"/>
                             <xs:field xpath="@language"/>
                        </xs:keyref>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="classification-main-titleType">
              <xs:simpleContent>
                   <xs:extension base="classification-titleType"/>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="classification-complementary-titleType">
              <xs:simpleContent>
                   <xs:extension base="classification-titleType"/>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="classification-index-titleType">
              <xs:simpleContent>
                   <xs:extension base="classification-titleType"/>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="classification-entry-updateType">
              <xs:sequence>
                   <xs:element name="classification-update-version">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Version pour laquelle la modification a été apportée</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="update-version-keyref" refer="classification-version-unique">
                             <xs:selector xpath="update-version"/>
                             <xs:field xpath="."/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="classification-update-date">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Date à laquelle le changement a été apporté</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="classification-update-author">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Auteur de la modification. L'auteur de la modification est une personne autorisée déclarée dans le document xml correspondant.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="classification-update-category">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Type de modification apportée à la classification</xs:documentation>
                        </xs:annotation>
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:enumeration value="new entry"/>
                                  <xs:enumeration value="updated entry"/>
                                  <xs:enumeration value="suppressed entry"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="classification-update-description" type="update-descriptionType" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation xml:lang="fr">Description textuelle de la modification apportée. Cette description fera l'objet d'une entrée dans le journal des modifications apportées pour la version</xs:documentation>
                        </xs:annotation>
                        <xs:keyref name="classification-update-description-language-keyref" refer="classification-language-code-unique">
                             <xs:selector xpath="classifcation-update-description"/>
                             <xs:field xpath="@language"/>
                        </xs:keyref>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="update-descriptionType">
              <xs:attribute name="language" type="xs:language" use="required"/>
         </xs:complexType>
         <xs:complexType name="classification-titleType" mixed="true">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="language" type="xs:language" use="required"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="classification-entry-linkType">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="link-type" use="required">
                             <xs:simpleType>
                                  <xs:restriction base="xs:string">
                                       <xs:enumeration value="excluding"/>
                                       <xs:enumeration value="including"/>
                                       <xs:enumeration value="seeAlso"/>
                                       <xs:enumeration value="completeAlso"/>
                                  </xs:restriction>
                             </xs:simpleType>
                        </xs:attribute>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
    </xs:schema>

    The same xml schema compile sucessfully in top link workbench ...

  • JAXB compiler problem in handling xsd:any and nillble = "true"

    Dear all,
    i am using jdeveloper 10.1.3.1 production release version.
    i am designing a xml schema that contain element of attribute nillable="true", for extensible, contain tag <xsd:any>.
    but i encounter 2 problem:
    1. for xml schema element with attribute nillable="true", no corresponding isNil(), setNil
    method is generated (refer to jaxb 1.0 spec. 5.7.1)
    2. cannot handle tag <xs:any> that generate incorrect java source code (cannot compile) [refer to jaxb 1.0 spec 5.9.5)
    *** i have add jaxb customization tag inside the <xs:any> tag
    ***   <xs:annotation><xs:appinfo>
    ***               <jaxb:property name="Extension"/>
    ***</xs:appinfo></xs:annotation>
    Does oracle's JAXB implementation conform to the JAXB 1.0 spec?
    Is it a known bug?
    Could anybody help me?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Refer to section
    E.2 Not Required XML Schema
    concepts
    "A JAXB implementation is not required to support the following XML Schema
    concepts for this version of the specification. A JAXB implementation may
    choose to support these features in an implementation dependent manner."
    E.2.2 Not supported while manipulating the XML
    content
    Schema component: wildcard
    (any)
    how can i know if an xml element with xsi:nil="true" (unmarshal)
    and set xsi:nil="true" for an element (marshal) ?
    According to the JAXB 1.0 specification:
    If {nillable} is "true", the methods setNil() and isNil() are
    generated.

  • Upgrading to JAXB/JWSDP1.3 from JAXB/JWSDP 1.2 -- problems

    I am seeing 2 problems after upgrading to the JAXB found in WSDP 1.3 (from 1.2)
    We are using JAXB in a client/server style app where the server is accessed via a web interface and the client is delivered via Java Web Start (JWS). Both the server and client use JAXB-generated classes.
    We have an ant build.xml file that invokes xjc and this was working for us as expected.
    For the JWS piece, we need to sign the jars we use and for testing purposes we were self-signing them, including the jar files needed for JAXB also self-signed. This is also coordinated through an ant task.
    After replacing the jar files in our lib area with the ones from my recent download of the 1.3 version of JAXB the following happens.
    1. I am seeing compiler deprecation warnings for the generated code -- this did not happen in our use of JAXB from 1.2. For example:
    [javac] /Users/jjs/Projects/SGS-Install-Fixed/sgs/src/com/gestalt/sgs/uobdif/impl/runtime/SAXMarshaller.java:259: warning: ERR_MISSING_OBJECT in com.sun.xml.bind.marshaller.Messages has been deprecated
    [javac] Messages.format(Messages.ERR_MISSING_OBJECT), null,
    [javac] ^
    I am using Java 1.4.1 on Max OS X (I know... not supported but this doesn't seem like a platform dependency) and these warnings go away if I revert back to the JAXB jars from the 1.2 release of WSDP.
    2. These are only warnings, so my build proceeds with ant. But, when I get to the jar signing step I see:
    [signjar] Signing Jar : /Users/jjs/Projects/SGS-Install-Fixed/sgs/lib/jaxb-libs.jar
    [signjar] jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 63854 but got 19845 bytes)
    I looked at the jar file using the jar command and there are entries there:
    4038 Wed Dec 03 22:16:20 EST 2003 META-INF/MANIFEST.MF
    3303 Wed Dec 03 22:16:20 EST 2003 META-INF/SUN_MICR.RSA
    3780 Wed Dec 03 22:16:20 EST 2003 META-INF/SUN_MICR.SF
    0 Wed Dec 03 22:16:20 EST 2003 META-INF/pack.properties
    that suggest to me that perhaps the jar is now sigend by Sun and therefore can't be signed again. If I look at the corresponding jar from the JAXB/1.2, these SUN_MICR entries do not appear.
    Is this assumption correct? Can I deliver my app through web start with my apps own jars self-signed and the JAXB jars signed by Sun? I suppose I can un-jar the JAXB jars, remove the manifest material and then re-jar the files and sign those. I expect this might work.
    I am looking to share migration experiences (1.2 to 1.3) and to see what work-arounds there might be.
    Thanks
    Jim

    Replying to my own post.
    It seems that with the JWSDP 1.3 release, most (if not all) of the included jars are signed by Sun. You can NOT include jars with different signatures in the same web start application -- that's the error I get when I tried to do this.
    This means that if I want to package my jars using a self-signed certificate, I have to first un-jar all of the JAXB lib jars I want to include, get rid of the parts of the manifest that deal with signing, re-jar them and then sign all of the jars in my web start app using my own cert. More work for me, but not a show-stopper.
    I still am not sure why I am getting deprecated warnings from javac though.
    Jim

  • Jaxb strange (de)serialization problem

    Hi!
    I have strange a problem in which deserialization of xml to an object generated by jaxb in some cases results in a classcastexception.
    Please bare with me...
    The problem occurs when I generate code for two schema's which both have an imported common schema which contain common data types and elements. Now I use 2 ant xjc task to generate the sources (to the same target folder). Whichever schema is created LAST works. That is, the sample xml for that schema can be deserialized. Now if I swap the order of generation the service for which the deserialization worked now fails and the other one works.
    If I add both schema's into a single call to xjc then it works but then I have a problem that I can't add any custom serialization because the additional of multiple binding files result in "not part of the compilation.." errors.
    This problem has been bugging me for days now and I wonder if anyone had the same problem? Or better, has a solution....
    Cheers,
    Robin

    sorry for the question already asked here. Actually I found the answer here
    http://forum.java.sun.com/thread.jspa?forumID=62&threadID=793180
    the problem was in the header, each time appended to the file. Anyhow, thanks to arnaud63 and ejp.

  • Error during distribution for compiled code generation-Reply

    Hi,
    Looking at your error messages, it looks as though your build is failing during the code generation phase of an autocompilation. To determine why the code generator crashed, either look in the $FORTE_ROOT/log/forte_ex*.log files or don't use autocompilation and use fcompile.
    There are many reasons why the code generator could crash. Some of the things I've come across are running out of memory and trying to find invalid classes.
    If its the invalid class problem you'll find a message like:
    Generating code for partition BLTCustomWindow_cl0_Part1.
    ERROR: Exiting due to following exception:
    SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated by escaped
    exception. See the remainder of the error stack for more information.
    Class: qqsp_ResourceException
    Error #: [1001, 3]
    Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    Error Time: Tue Aug 18 17:52:44
    Exception occurred (locally) on partition "Forte_Executor", (partitionId =
    9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1, taskId =
    [9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1.6]) in application
    "FTCompile_cl0", pid 28331 on node stardev in environment <unknown>.
    FATAL ERROR: Invalid class ProductBMServices.ProductSecurityMgrProxy
    (0x4ecd,0x19a)
    Class: qqsp_ImplementationException
    Detected at: qqcg_TRclass::SetClass at 2
    Last TOOL statement: method ForteCompiler.ProcessPGF
    Error Time: Tue Aug 18 17:52:44
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId = 9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1, taskId =
    [9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1.6]) in application
    "FTCompile_cl0", pid 28331 on node stardev in environment <unknown>.
    The solution for this instance is to clean up the invalid classes using the c4tstdrv utility.
    c4tstdrv > setrepos star8
    c4tstdrv > setwork dmcompiledbuild
    c4tstdrv > open
    Type Service Flags Level
    err sh * 255
    trc rp 1 4
    c4tstdrv > findproj productbmservices
    c4tstdrv > cleanuprtclasses
    Removing extraneous RTclass ProductShootingLocationMgrProxy
    Removing extraneous RTclass PRTerritoryBaseMgrProxy
    Removing extraneous RTclass PRTerritoryMgrProxy
    Removing extraneous RTclass TalentBaseMgrProxy
    Removing extraneous RTclass TalentTypeMgrProxy
    Removing extraneous RTclass TitleTypeBaseMgrProxy
    Removing extraneous RTclass TitleTypeMgrProxy
    Removing extraneous RTclass ProductSecurityBaseClass
    Removing extraneous RTclass ProductSecurityBaseQuery
    Removing extraneous RTclass ProductSecurityQuery
    Removing extraneous RTclass ProductSecurityMgrProxy
    c4tstdrv > commit
    c4tstdrv > exit
    Integrate the changes to the workspace, start the build again and this should have cured the problem.
    However, its hard to know what the cause of your problem is without seeing the output in the log files.
    Good luck.
    Mark Carruthers
    20th Century Fox
    "Forte Consultants" <[email protected]> 01/22/99 08:35am >>>
    Hi,
    I'm doing application distribution for my application using a fscript
    script and am forcing compilation on 2 of my partitions.
    This I have been doing from quite sometime successfully. Recently I
    developed a new service and plugged it into my application for
    deployment.
    I'm successfully able to distribute & deploy the interpreted code. But
    I'm getting a long list of system errors when I try doing distribution
    for compiled code. And I see only one of the .exe generated instead of
    two because of which I'm unable to go ahead with installaion. I would
    appreciate if anybody let me know why this's happening ?. The following
    is the main chunk of this error list.
    Thanks in advance.
    --Anand Ramaswamy
    SYSTEM ERROR: Cannot resolve the distributed reference for an object of
    class
    (qqlo_Object) named (<Unknown>) for the reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 144]
    Detected at: qqdo_ProxyMgr::ResolveOutGoingProxy at 10
    Error Time: Fri Jan 22 10:44:22
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Can not initially communicate with the object named
    (Unnamed),
    which is supposed to be in partition
    (32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x616:0x1).
    Class: qqsp_DistAccessException
    Error #: [601, 140]
    Detected at: qqdo_ProxyMgr::CheckAccess at 1
    Error Time: Fri Jan 22 10:44:22
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Attempt to send to unknown destination partition
    (32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x616:0x1).
    Class: qqsp_DistAccessException
    Error #: [601, 102]
    Detected at: qqdo_PartitionMgr::SendMsg at 1
    Error Time: Fri Jan 22 10:44:22
    Distributed method called: qqdo_InternalMessage.<Message> (object
    name
    Unnamed) from partition "CodeGenerationSvc_cl0_Part1-router",
    (partitionId
    = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.2]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Partition (32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x616:0x1)
    no
    longer exists. The process associated with the partition probably
    terminated.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::CheckStarted at 1
    Error Time: Fri Jan 22 10:44:22
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: This method invocation is being retried because the
    failures
    shown below and the fact that the dialog duration is MESSAGE. This is
    try #2.
    Class: qqsp_DistAccessException
    Error #: [601, 54]
    Detected at: qqdo_Message::Failed at 1
    Error Time: Fri Jan 22 10:44:19
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: The load balanced router is disabled or has no members.
    This
    can happen if all of the members terminated or failed.
    Class: qqsp_DistAccessException
    Error #: [601, 161]
    Detected at: qqdo_LbRouter::Route at 1
    Error Time: Fri Jan 22 10:44:19
    Distributed method called: GenerationMgrProxy.GeneratePartitionCode
    (object name
    site/codegenerationsvc_cl0/codegenerationsvc_cl0-codegensvc)
    from partition "Fscript_cl9_Client", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614.2]) in application
    "fscript",
    pid 4b81 on node MOOSUP in environment IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: This method invocation is being retried because the
    failures
    shown below and the fact that the dialog duration is MESSAGE. This is
    try #1.
    Class: qqsp_DistAccessException
    Error #: [601, 54]
    Detected at: qqdo_Message::Failed at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Access to a load balanced router member (which is a
    service
    object) failed for the reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 162]
    Detected at: qqdo_LbRouter::Route at 2
    Error Time: Fri Jan 22 10:44:15
    Distributed method called: GenerationMgrProxy.GeneratePartitionCode
    (object name
    site/codegenerationsvc_cl0/codegenerationsvc_cl0-codegensvc)
    from partition "Fscript_cl9_Client", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614.3]) in application
    "fscript",
    pid 4b81 on node MOOSUP in environment IGTSDENV
    Distributed method called: qqlo_Object.<Message> (object name
    Unnamed)
    from partition "Forte_Executor", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.12]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: Cannot resolve the distributed reference for an object of
    class
    (qqlo_Object) named (<Unknown>) for the reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 144]
    Detected at: qqdo_ProxyMgr::ResolveOutGoingProxy at 10
    Error Time: Fri Jan 22 10:44:15
    Distributed method called: qqlo_Object.<Message> (object name
    Unnamed)
    from partition "Forte_Executor", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.12]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: This distributed reference was previously invalidated due
    to the
    reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 132]
    Detected at: qqdo_ProxyMgr::ResolveOutGoingProxy at 3
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Asynchronous Failure: Recieved a close from the network
    partner:
    Internet Location - Host: moosup.iroquois.com Port Number: 2504 Dot:
    193.1.11.26 %LINKDISCON, network partner disconnected logical link
    Event 4
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: This method invocation is being retried because the
    failures
    shown below and the fact that the dialog duration is MESSAGE. This is
    try #1.
    Class: qqsp_DistAccessException
    Error #: [601, 54]
    Detected at: qqdo_Message::Failed at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Fri Jan 22 10:44:15
    Distributed method called: qqlo_Object.<Message> (object name
    Unnamed)
    from partition "Forte_Executor", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.12]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Asynchronous Failure: Recieved a close from the network
    partner:
    Internet Location - Host: moosup.iroquois.com Port Number: 2504 Dot:
    193.1.11.26 %LINKDISCON, network partner disconnected logical link
    Event 4
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    If this INCLUDE is in a function group go the MAIN program and activate from there.
    Can you list out the include name?

  • SOAP wdsl generation problem j developer

    hi im having a problem with wsdl file generated from jdeveloper.
    I expose a pl/sql function as a web service. I can then conect to the soap url with a web browser and sucessfull publish data to the db from this , but if i take the wsdl file from jdeveloper in to a soap test client (magoo) i get an error, on anything that trys to post data back to the DB ???
    the error is
    No Deserializer found to deserialize a ':emp' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
    im not using BPEL (which i know has some soap problems)
    THIS IS THE SOAP MESSAGE THE WSDL FILE GENERATES
    <?xml version='1.0' encoding='UTF-8'?>
    <soapenv:Envelope xmlns:m='MyWebService-v9' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:ns1='http://oadev11/Company.xsd' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'>
    <soapenv:Body soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
    <m:addemp>
    <emp>
    <eid xsi:type='xsd:int'>7</eid>
    <efirstname xsi:type='xsd:string'>mr</efirstname>
    <elastname xsi:type='xsd:string'>magoo</elastname>
    <addr>
    <street xsi:type='xsd:string'>granby grove</street>
    <city xsi:type='xsd:string'>southampton</city>
    <state xsi:type='xsd:string'>uk</state>
    <zip xsi:type='xsd:string'>so</zip>
    </addr>
    <salary xsi:type='xsd:double'>1000</salary>
    </emp>
    </m:addemp>
    </soapenv:Body>
    </soapenv:Envelope>
    this returns an error,
    No Deserializer found to deserialize a ':emp' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
    ive tested the client with the googlesearchapi wsdl file, so the client is working ok, I think there might be a problem with the wsdl file generation. can anyone sugest what this might be?
    conecting directly to the soap service url and submitting xml suggested by the interface, adds the entry to the databse and works fine
    <emp xmlns:ns1="http://oadev11/Company.xsd"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:type="ns1:oadev11_EmployeeUser">
    <eid xsi:type="xsd:int">7</eid>
    <efirstname xsi:type="xsd:string">MR</efirstname>
    <elastname xsi:type="xsd:string">MAGGO</elastname>
    <addr xsi:type="ns1:oadev11_AddressUser">
    <street xsi:type="xsd:string">Granby grove</street>
    <city xsi:type="xsd:string">southampton</city>
    <state xsi:type="xsd:string">uk</state>
    <zip xsi:type="xsd:string">SO</zip>
    </addr>
    <salary xsi:type="xsd:double">1000</salary>
    </emp>
    This sucessfuly ads the entry to the databse any ideas please?

    Hi,
    Action parameter is always under Opertaion tag of your wsdl. In your case it is
    Action = rpc/http://siebel.com/CustomUI:ATDDQMatchWS
    <operation name="ATDDQMatchWS">
    <soap:operation soapAction="rpc/http://siebel.com/CustomUI:ATDDQMatchWS"/>
    <input>
    <soap:body use="literal" namespace="http://siebel.com/CustomUI"/>
    </input>
    <output>
    <soap:body use="literal" namespace="http://siebel.com/CustomUI"/>
    </output>
    </operation>
    It looks to me you are trying to invoke RC encoded webservice which is not supported in XI.
    Reward points if find useful
    Thanks
    Amit

  • Stub generation problem with the wsdl file

    Hi all
    I'm trying to write a simle webservice client based on JAX. My webservice is working fine I've tested it with a standalone app. In my webservice I'm using complex type. Problem is that i can't generate properly stubs. This is a msg I'm getting during the generation
    warning: ignoring operation "getEmployee": message part does not refer to a schema element declaration
    warning: Port "EmployeeIFPort" does not contain any usable operationsBecause of that my method to get the Object from the webservice is not generated.
    This is the wsdl file.
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="EmployeeService" targetNamespace="urn:Foo" xmlns:tns="urn:Foo" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
      <types>
        <schema targetNamespace="urn:Foo" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:Foo" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
          <complexType name="Employee">
            <sequence>         
              <element name="name" type="xsd:string"/>
              <element name="surname" type="xsd:string"/>
           <element name="age" type="xsd:int"/>
         </sequence>
         </complexType>
        </schema>
       </types>
      <message name="EmployeeIF_getEmployee">
        <part name="String_1" type="xsd:string"/>
        <part name="String_2" type="xsd:string"/>
        <part name="int_3" type="xsd:int"/>
      </message>
      <message name="EmployeeIF_getEmployeeResponse">
        <part name="result" type="tns:Employee"/>
      </message>
      <portType name="EmployeeIF">
        <operation name="getEmployee" parameterOrder="String_1 String_2 int_3">
          <input message="tns:EmployeeIF_getEmployee"/>
          <output message="tns:EmployeeIF_getEmployeeResponse"/>
        </operation>
      </portType>
      <binding name="EmployeeIFBinding" type="tns:EmployeeIF">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <operation name="getEmployee">
          <soap:operation soapAction=""/>
          <input>
            <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="literal"/>
          </input>
          <output>
            <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="literal"/>
          </output>
        </operation>
      </binding>
      <service name="EmployeeService">
        <port name="EmployeeIFPort" binding="tns:EmployeeIFBinding">
          <soap:address location="http://localhost:8080/EmployeeService/getEmployee"/>
        </port>
      </service>
    </definitions>However the complex type class Employee is generated properly as well as other stub classes like the interface EmployeeIF, EmployeeIF_getEmployee_RequestStruct and EmployeeIF_getEmployee_ResponseStruct (I mean i think they are generated properly). As I said befor the problem is that the webservice method from the EmployeeIF.getEmployee() is not generated in the EmployeeIF_Stub. Any ideas why? I'm using WTK 2.5
    thx in advance :)

    Here i Followed  Url &sap-user=XXX&sap-password=YYY to the WSDL-URL with XXX and YYY being your username and password and you will be authenticated.
    Later i Struck. Actual my requirement is I have two views i want to take a value from the first view and then return value displayed in the second view. All input/output parameters are the taken from the WSDL file. Can you please Help me.

Maybe you are looking for

  • My itunes won't open... read?

    "Apple application support was not found. Apple application support is required to run itunes. Please uninstall itunes and reinstall again. Error 2. (windows error 2)" that error comes up everytime i try to open up itunes. I've un-installed itunes se

  • Unordered List Problem

    I'm trying to create a bulleted (unordered) list in Dreamweaver MX. For example: List Title * First Bulleted list @ Lower Level List : Lower Level List I don't see anyway to do this without having a space (hard return) between each line, which I don'

  • Safari version 8.0

    is there any new version to safari 8.0 released recently as today while logging on to apple site / apple support communities,  I got a message that "this version of safari is not supported any longer"

  • FUNCTION EXIT_SAPMM07M_001. para la transaccion MB1A

    Gracias amigos por su ayuda, si fuera posible, los invitaria a todos a un asado... necesito buscar un user exit para la transaccion MB1A, ya que al grabar, necesito validar un campo, la funcion que uso es FUNCTION EXIT_SAPMM07M_001. INCLUDE ZXMBCU02.

  • Schedule dunning (sm36)transaction f150, prog. sapf150v (dunning)

    Hi, We are running 4.7 R/3 Enterprise transaction f150, prog. sapf150v (dunning) I'm wondering if anybody has scheduled dunning to run daily? I have attempted in sm36 with the following error message. I suspect I would be looking at a modification to