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

Similar Messages

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

PROBLEMS JAXB and XML-schema

Hello,
I think my problem is not directly related to JAXB but to my understanding of schema-files.
I defined a schema like that:
<xsd:complexType name="BSR">
<xsd:sequence>
<xsd:element name="VERB" type="VERB"/>
<xsd:element name="NOUN" type="NOUN"/>
<xsd:element name="REVISION" type="REVISION"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="VERB">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="value" fixed="ACKNOWLEDGE"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="NOUN">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="value" fixed="PO"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="REVISION">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="value" fixed="003"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
When I tried to compile that schema via JAXB I got the following error:
[ERROR] A property with the same name "value" is generated from more than one schema component line 31 of ACKNOWLEDGE_PO_003.xsd
[ERROR] (Relevant to above error) another one is generated from this schema component. line 14 of datatypes.xsd
[...] and so on!
How do I manage to use that attribute "value" in several elements???
Is there a possibility to declare the attribute once an refer to it, like to an type?
Please help, I could not find anythig in docu.
thanX chris

hallo again,
i tried that, but the point is, if i remove the declaration of the attribute called "value" it works fine.
<xsd:element name="BSR">
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="VERB"/>
                    <xsd:element ref="NOUN"/>
                    <xsd:element ref="REVISION"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="VERB">
          <xsd:complexType>
               <xsd:simpleContent>
                    <xsd:extension base="xsd:string">
                    </xsd:extension>
               </xsd:simpleContent>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="NOUN">
          <xsd:complexType>
               <xsd:simpleContent>
                    <xsd:extension base="xsd:string">
                    </xsd:extension>
               </xsd:simpleContent>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="REVISION">
          <xsd:complexType>
               <xsd:simpleContent>
                    <xsd:extension base="xsd:string">
                    </xsd:extension>
               </xsd:simpleContent>
          </xsd:complexType>
     </xsd:element>
I can compile it that way! but i need these attributes called "value" as you see them above....
so i think i worked out, that the problem is not in the "BSR"-tag, but the 3-times occurrence of the attribute "value".

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

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>

JAXB & the W3C schema for schemas

When I try and run JAXB over the W3C schema for schemas I get loads of error messages during the parsing concerning the simple type definitions which restrict the xs:whiteSpace property of xs:simpleType.
Has anybody else tried to run JAXB over the schema for schemas?
Has anyone been successful?
Cheers,
Simon

I also tried to compile Schema for Schemas (normative)
from http://www.w3.org/TR/xmlschema-1/#normative-schemaSchema
This one in definition of schema in fact, but I can't compile it with JAXB. The error messages are :
[ERROR] rcase-Recurse.2: There is not a complete functional mapping between the particles.
line 776 of schema.xsd
[ERROR] derivation-ok-restriction.5.3: Error for type 'all'. The particle of the type is not a valid restriction of the particle of the base.
line 776 of schema.xsd
[ERROR] rcase-Recurse.2: There is not a complete functional mapping between the particles.
line 478 of schema.xsd
[ERROR] derivation-ok-restriction.5.3: Error for type 'simpleRestrictionType'. The particle of the type is not a valid restriction of the particle of the base.
line 478 of schema.xsd
[ERROR] rcase-Recurse.2: There is not a complete functional mapping between the particles.
line 432 of schema.xsd
[ERROR] derivation-ok-restriction.5.3: Error for type 'complexRestrictionType'. The particle of the type is not a valid restriction of the particle of the base.
line 432 of schema.xsd
Failed to parse a schema.
One can see that all messages about the same problem.
It looks like a bug in JAXB because normative schema must be compiled , I guess...
Is anyone has any idea how to solve the problem?
WBR Slava

Does JaxB support inported schemas?

hi i'm trying to compile the CD_DataBase.xsd schema (using the JaxB that I got from the JWSDP found at Sun's site) which references to an Album element in Album.xsd
For some reason, my xjc task falls when trying to read the imported schema.
here are the schemas':
Album.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.bll.co.il"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
jaxb:extensionBindingPrefixes="xjc"
jaxb:version="1.0"
elementFormDefault="qualified">
<xsd:annotation>
<xsd:appinfo>
<jaxb:globalBindings>
<xjc:serializable/>
</jaxb:globalBindings>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="album">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="description" type="xsd:string"/>
<xsd:element name="producer" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
CD_DataBase.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.bll.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
xmlns:alb="http://www.bll.co.il"
xmlns:cd="http://www.bll.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
jaxb:extensionBindingPrefixes="xjc"
jaxb:version="1.0"
elementFormDefault="qualified">
<xsd:import namespace="http://www.bll.co.il" schemaLocation="Album.xsd"/>
<xsd:annotation>
<xsd:appinfo>
<jaxb:globalBindings>
<xjc:serializable/>
</jaxb:globalBindings>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="CD">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="artist" type="xsd:string"/>
<xsd:element ref="alb:album"/>
</xsd:sequence>
<xsd:attribute name="title" type="xsd:string" use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
can any one help?
even if it works, will jaxb compile the referenced schema (album.xsd) to java classes every time i use it (in other schemas' that are using it)?
Thank's,
Regards,
Yair Ogen

Does any body know if I can configure Jaxb so it won't
compile the imported schema every time I have a schema
that uses it?It would be nice to be able to do this but I haven't seen how. You can't have two schemas that both import another common schema and have them both share the base schema types. One way I have gotten around this is to make a single common document with all the types we use but I'm not very happy with that.
The other way is to first generate the types for album.xsd and then add lines to album.xsd telling it to use those types instead of generating them each time. It solves your issue but is less than perfect, I'll admit.

Adadmin Compile APPS schema never complete & it running for infinite time

Hi,
When I am trying to compile apps schema from adadmin --> compile apps schema, It never complete & it is not compiling invalid objects, I tried to manually run the adutlrcmp.sql through SQL, also the same problem the scripts is stuck (hang) in the UTL_RECOMP.RECOMP_PARALLEL proceure.
Please note the following:
1- That I am able to compile invalid objects manually through Toad Or through alter package.
2- The compile apps schema was running successfully & very fast in the past.
What should I do? how can I resolve this issue ?
Your quick feed back is very much appreciated.
Marwan

Hi Hussein,
The following is the adadmin log for the compile apps schema:
AD code level : [B.1]
Connecting to SYSTEM......Connected successfully.
Connecting to APPS......Connected successfully.
sqlplus -s APPS/***** @/u03/applprod/prod/apps/apps_st/appl/ad/12.0.0/sql/adutlrcmp.sql APPLSYS ***** APPS ***
** ***** 0 0 NONE FALSE
Arguments are:
AOL_schema = APPLSYS, AOL_password = *****,
Schema_to_compile = APPS, Schema_to_compile_pw = *****,
SYSTEM_password = *****, Total_workers = 0, Logical_worker_num = 0
Object_type_to_not_compile = NONE
Use_stored_dependencies = FALSE
Connected.
Running utl_recomp.recomp_parallel(0), if it exists
no rows selected
Elapsed: 00:00:00.17
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.00
STATUS_MESSAGE
Running UTL_RECOMP.RECOMP_PARALLEL...
declare
ERROR at line 1:
ORA-01013: user requested cancel of current operation
An error occurred while running a SQL*Plus script.
As you can see the :
STATUS_MESSAGE
Running UTL_RECOMP.RECOMP_PARALLEL...
Is stucking & you wait for a long long time & it never ends So I canceled it manually.
And when checking the database locks the following appears:
OWNER OBJECT_NAME
APPLSYS FND_CONCURRENT_QUEUES
APPLSYS FND_CONCURRENT_REQUESTS
Regards,
Marwan

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 ...

Compile Apps Schema took sooooo long

Hi Friends,
EBS R12.1
OEL 5.4
I am compiling apps schema due to some invalid object when applying patch. but the program is running forever like 24hrs + now :(
Have you encountered similar problem yet? Can you help me troubleshoot this kind of issue?
adadmin
       Compile/Reload Applications Database Entities
   1.    Compile APPS schema
   2.    Compile menu information
   3.    Compile flexfields
   4.    Reload JAR files to database
   5.    Return to Main Menu
Enter your choice [5] : 1
sqlplus -s APPS/***** @/u01/applprod/PROD/apps/apps_st/appl/ad/12.0.0/sql/adutlrcmp.sql APPLSYS ***** APPS ***** ***** 16 0 NONE FALSEThe above program is running forever and its has activity when you check OS status "top""
top - 14:27:49 up 63 days, 4:59, 6 users, load average: 2.12, 2.17, 2.23
Tasks: 432 total,   2 running, 430 sleeping,   0 stopped,   0 zombie
Cpu(s): 12.5%us, 0.2%sy, 0.0%ni, 86.9%id, 0.4%wa, 0.0%hi, 0.0%si, 0.0%st
Mem:   8171552k total, 8121216k used,    50336k free,    34908k buffers
Swap: 8388600k total, 1101216k used, 7287384k free, 5796552k cached
PID USER      PR NI VIRT RES SHR S %CPU %MEM    TIME+ COMMAND
23133 oraprod   25   0 1227m 116m 109m R 100.0 1.5   1144:00 oracle
27215 root      16   0 13004 1364 820 S 0.7 0.0   0:04.44 top
18303 root      15   0 13004 1360 816 R 0.3 0.0   0:00.03 top
23346 oradev1   15   0 1215m 41m 41m S 0.3 0.5   3:48.11 oracle
24746 appldev1 17   0 821m 246m 6244 S 0.3 3.1   8:25.78 javaPlease help....
Thanks a lot
MsK

Hi,
I tried to abort the program (ctrl+c) and this is the result in the adadmin.log
sqlplus -s APPS/***** @/u01/applprod/PROD/apps/apps_st/appl/ad/12.0.0/sql/adutlrcmp.sql APPLSYS ***** APPS ***** ***** 16 0 NONE FALSE
Arguments are:
AOL_schema = APPLSYS, AOL_password = *****,
Schema_to_compile = APPS, Schema_to_compile_pw = *****,
SYSTEM_password = *****, Total_workers = 16, Logical_worker_num = 0
Object_type_to_not_compile = NONE
Use_stored_dependencies = FALSE
Connected.
Running utl_recomp.recomp_parallel(16), if it exists
OWNER                          NUM_INVALID
APPS                                    87
Elapsed: 00:00:00.09
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.00
STATUS_MESSAGE
Running UTL_RECOMP.RECOMP_PARALLEL...
declare
ERROR at line 1:
ORA-01013: user requested cancel of current operation
An error occurred while running a SQL*Plus script.
Continue as if it were successful [No] : No
AD Administration error:
Error running adutlrcmp.sql in adprdcAdUtilrcmp()
An error occurred while compiling invalids using the SYS.UTL_RECOMP() package.
Time is: Tue Sep 28 2010 14:29:09
Backing up restart files, if any......Done.

Color Scheme Problems in Ultiboard

Hi, I've been having trouble with the color scheme problems in Ultiboard ever since I upgraded form 10.0 to 10.1. The color schemes will not save in Ultiboard 10.1, even with the new patch 10.1.0.1, this problem is persistant.
Here's the problem in detail:
In global Preferences, I click on "Colors", and then New Scheme, give it a name, and I define my colors. However, when I open a new file, the colors are reverted to the default. When I check the preferences again, the name that I have given to my color scheme is labeled as "User settings", and they are the same as the default colors.
This is really annoying as every time I open a file, I have to change the color schemes. It seems like these settings are not being saved in the user-configuration file for some reason or another.
I have tried deleting my user-config file in the user directories, and started new user-config files, but to no avail, the problem is persistent. The color just will not stay.
How do I get around this problem?
-J

Hello,
Thanks for reporting this. I was able to reproduce the issue and created a defect report, ID: 112869.
Fernando D.
National Instruments

I want to compile apps schema in oracle applications production.

Hi,
Is there any care that must be taken to compile apps schema using adadmin in production.
With Regards
GNVMK

Hi,
Is there any care that must be taken to compile apps schema using adadmin in production.No, you can simply run adadmin and compile apps schema from adadmin while the application is up and running. Just make sure you login as applmgr and source the application env file before doing so.
Regards,
Hussein

Scheduling compile apps schema , flexfields and menu information

Hi,
Version: 11.5.10.2
we have requirement like can we put compile apps schema, flexfields and menu to be schedule once in a month.
1) If this is practical how we can achieve.
2)what is the recommended way to do it manually from adadmin or schedule..
Regards

Hi,
we have requirement like can we put compile apps schema, flexfields and menu to be schedule once in a month.
1) If this is practical how we can achieve.If you have frequent changes at the database level and customization is involved, then you need to consider compiling apps schema on regular basis (daily basis). This can be done from adadmin or using utlrp.sql script, or manually.
2)what is the recommended way to do it manually from adadmin or schedule..I would recommend running it from adadmin. However, for compiling flexfileds and menus I would not recommend doing so unless you are instructed to do so (for example, after applying application patches).
Regards,
Hussein

Compile apps schema, flexfield and menu

Hi,
i would like to ask question related to adadmin utility,
can we execute the task like
1)compile Apps Schema
2)compile menu information
3)complie flexfields
4)relink application programs
when the application is up and running parallely users are working on it.
Regards

Hi,
can we execute the task like
1)compile Apps Schema
2)compile menu information
3)complie flexfields You can compile the above while the application is up and the users are connected.
4)relink application programsIt is possible to relink application programs (not for all programs). If the executable file is in use, relinking mail fail and the executable file will not be generated unless you stop the application services first.
Regards,
Hussein

Compile apps schema

Dear Hussein,
Do we need to shutdown the application services before compiling apps schema

Hi,
To compile APPS schema, issue adadmin and select:
3. Compile/Reload Applications Database Entities menu
1. Compile APPS schema
You cannot select specific schema to compile.
For generating forms, select:
1. Generate Applications Files menu -- Here, it is possible to select the module.
This is all documented in Oracle Applications Maintenance Utilities/Procedures manuals.
Release 12.0.4 Documentation Library
http://download.oracle.com/docs/cd/B40089_09/current/html/docset.html
Regards,
Hussein

JAXB, Compiling a schema problem

Similar Messages

Maybe you are looking for