Nabble - java.net - jaxb users

Having Namespace for every attribute

2009-12-02T10:02:25Z

Hi All,

We would like to use annotations and take advantage of jaxb for marshalling ang unmarshalling the Java Objects.
These Objects are legacy code and hence we would like to add annotations only at class level i.e @XmlRootElement(name = "Title" , namespace="com.company.referencedata")

For ex

@XmlRootElement(name = "Title" , namespace="com.company.referencedata")
public class Title {
private int id;
...
}

What we have observed was the xml generated on marshalling had namespace included only for rootNode

ex:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:Title xmlns:ns2="com.company.referencedata">
<description>description</description>
<id>1</id>
</ns2:Title>

We expected it to add even for elements

ex :

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:Title xmlns:ns2="com.company.referencedata">
<ns2:description>description</ns2:description>
<ns2:id>1</ns2:id>
</ns2:Title>

One solution is add @XMLElement for all the attributes, but is there any other way where we could include namespace ??

I am new to JAXB, Any help is highly appreciated.

Thanks In Advance

Re: Unmarshalling ignores value of anyType element

2009-12-02T07:49:58Z

Thanks Wolfgang,

I used the solution below and I could access the content of the tag.

Cheers,
Fabrice

Wolfgang Laun-2 wrote:

The second case uses this schema definition:

<xs:complexType name="MyTypeThree">
<xs:complexContent mixed="1">
<xs:extension base="xs:anyType"/>
</xs:complexContent>
</xs:complexType>

Class MyTypeThree now has List content, in order to
collect text content chunks and child elements, as they appear
in the element. Full blown processing after unmarshalling would
have to instanceof-test the list elements, and process accordingly.
For simple text content, you can expect a String object, which
can also be put during marshalling.

Re: Unmarshalling ignores value of anyType element

2009-12-02T01:05:12Z

Similar questions crop up every now and then. That's why I'll
answer this in some detail.

xs:anyType is the "ur-type" (W3C) of all complex schema types. There is a
restriction, xs:anySimpleType, the union of all simple types (and their xs:list
derivations).

This means that a binding of xs:anyType is not restricted in any way.
XML representations may have to add the type to the element, using, e.g.
<wild xsi:type="xs:string"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Wild</wild>

Here is the corresponding schema using xs:anyType for an element type:
<xs:element name="docOne" type="DocTypeOne"/>
<xs:complexType name="DocTypeOne">
    <xs:sequence>
      <xs:element name="text" type="xs:string"/>
      <xs:element name="wild" type="xs:anyType"/>
    </xs:sequence>
</xs:complexType>

To marshal/unmarshal, simply use setWild( "..." )/getWild()

An explicit complex type definition such as, e.g.,

<xs:element name="docTwo" type="DocTypeTwo"/>
<xs:complexType name="DocTypeTwo">
    <xs:sequence>
      <xs:element name="text" type="xs:string"/>
      <xs:element name="wild" type="MyTypeTwo"/>
    </xs:sequence>
</xs:complexType>
<xs:complexType name="MyTypeTwo">
    <xs:complexContent>
      <xs:extension base="xs:anyType"/>
    </xs:complexContent>
</xs:complexType>

Results in a Java class MyTypeTwo, which (similar to your type "Varies")
contains field List<Element> any (for all the element(!) children) and
field Map<QName,String> otherAttributes (which might be there even
if not declared in the schema).

But an XML element instance
   <wild>xyz</wild>
doesn't have a child element - it has text content.

At this point, you'll have to decide: Would you prefer to wrap this data
in a subelement for <wild>, or do you modify the schema, defining
the complexType to be mixed?

In the first case, marshalling and unmarshalling becomes complex,
since you must create a org.w3c.dom.Element, from a JAXBElement
defining some tag, and insert this by calling getAny().add( domEl );
and you must use getAny().getTextContent() to retrieve the
subelement's content.

The second case uses this schema definition:

<xs:complexType name="MyTypeThree">
    <xs:complexContent mixed="1">
      <xs:extension base="xs:anyType"/>
    </xs:complexContent>
</xs:complexType>

Class MyTypeThree now has List<Object> content, in order to
collect text content chunks and child elements, as they appear
in the element. Full blown processing after unmarshalling would
have to instanceof-test the list elements, and process accordingly.
For simple text content, you can expect a String object, which
can also be put during marshalling.

-W

On Tue, Dec 1, 2009 at 6:55 PM, fcamous <fabrice.camous@...> wrote:

Hi all,

I'm having problem accessing a value contained in an anyType element:

I have this data type called "varies" in my schema:
<xsd:complexType name="varies">
<xsd:complexContent>
<xsd:extension base="xsd:anyType"/>
</xsd:complexContent>
</xsd:complexType>

xjc generates Varies.java and I have an getter to access the value:
public List<Element> getAny() {
if (any == null) {
any = new ArrayList<Element>();
}
return this.any;
}

I'm unmarshalling an xml document and this is the part I am interested in:
<OBX.5>
6.4
</OBX.5>

"OBX.5" is an extension of "varies" type.
xjc generates OBX5CONTENT.java which inherits the getAny() method. However,
after unmarshalling, when I use the method in my code, the list of
org.w3c.dom.Element objects it returns is always empty. Note that I have
access to other fields of the OBX5CONTENT object without a problem.
Any idea?
Thanks in advance.

Here's the OBX.5 schema definition if it's needed:
<xsd:attributeGroup name="OBX.5.ATTRIBUTES">
<xsd:attribute name="Item" type="xsd:string" fixed="573"/>
<xsd:attribute name="Type" type="xsd:string" fixed="varies"/>
<xsd:attribute name="LongName" type="xsd:string" fixed="Observation Value"/>
</xsd:attributeGroup>
<xsd:complexType name="OBX.5.CONTENT">
<xsd:annotation>
<xsd:documentation xml:lang="en">Observation Value</xsd:documentation>
<xsd:appinfo>
<hl7:Item>573</hl7:Item>
<hl7:Type>varies</hl7:Type>
<hl7:LongName>Observation Value</hl7:LongName>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="varies">
<xsd:attributeGroup ref="OBX.5.ATTRIBUTES"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="OBX.5" type="OBX.5.CONTENT"/>
--
View this message in context: http://old.nabble.com/Unmarshalling-ignores-value-of-anyType-element-tp26595595p26595595.html
Sent from the java.net - jaxb users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Unmarshalling ignores value of anyType element

2009-12-01T09:55:16Z

Hi all,

I'm having problem accessing a value contained in an anyType element:

I have this data type called "varies" in my schema:
<xsd:complexType name="varies">
<xsd:complexContent>
<xsd:extension base="xsd:anyType"/>
</xsd:complexContent>
</xsd:complexType>

xjc generates Varies.java and I have an getter to access the value:
public List<Element> getAny() {
if (any == null) {
any = new ArrayList<Element>();
}
return this.any;
}

I'm unmarshalling an xml document and this is the part I am interested in:
<OBX.5>
6.4
</OBX.5>

"OBX.5" is an extension of "varies" type.
xjc generates OBX5CONTENT.java which inherits the getAny() method. However, after unmarshalling, when I use the method in my code, the list of org.w3c.dom.Element objects it returns is always empty. Note that I have access to other fields of the OBX5CONTENT object without a problem.
Any idea?
Thanks in advance.

Here's the OBX.5 schema definition if it's needed:
<xsd:attributeGroup name="OBX.5.ATTRIBUTES">
<xsd:attribute name="Item" type="xsd:string" fixed="573"/>
<xsd:attribute name="Type" type="xsd:string" fixed="varies"/>
<xsd:attribute name="LongName" type="xsd:string" fixed="Observation Value"/>
</xsd:attributeGroup>
<xsd:complexType name="OBX.5.CONTENT">
<xsd:annotation>
<xsd:documentation xml:lang="en">Observation Value</xsd:documentation>
<xsd:appinfo>
<hl7:Item>573</hl7:Item>
<hl7:Type>varies</hl7:Type>
<hl7:LongName>Observation Value</hl7:LongName>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="varies">
<xsd:attributeGroup ref="OBX.5.ATTRIBUTES"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="OBX.5" type="OBX.5.CONTENT"/>

Re: how to get the annotations with the methods in stead of with the fields?

2009-11-30T10:38:24Z

On Mon, Nov 30, 2009 at 3:45 PM, xtien <christine@...> wrote:
>
> There is an annotation @XmlAccessorType(XmlAccessType.FIELD) in the xml files
> that the Jaxb plugin has generated. According to Jaxb documentation,
> @XmlAccessorType(XmlAccessType.PUBLIC_MEMBER) is default. So my question
> boils down to how to I get the plugin to follow the default behavior for
> @XmlAccessorType?
>

This is controlled by xjc, the JAXB schema compiler, which has a definite code
model, according to which Java code is generated.

> Again, this would save me time.

All right, and it would save the time of the volunteers on this list if you
would post the data describing the problem you have, as I have urged you
to do. Either do this, or, please, stop wasting your and our time.

-W

> The getter names I have are standard camel
> case, but the field names use upper case and lower case more or less at
> random because they were generated from a system in which I can't control
> field names. There should be a configuration file for jaxb, but I can't find
> one.
> --
> View this message in context: http://old.nabble.com/how-to-get-the-annotations-with-the-methods-in-stead-of-with-the-fields--tp26529506p26575846.html
> Sent from the java.net - jaxb users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: how to get the annotations with the methods in stead of with the fields?

2009-11-30T06:45:08Z

There is an annotation @XmlAccessorType(XmlAccessType.FIELD) in the xml files that the Jaxb plugin has generated. According to Jaxb documentation, @XmlAccessorType(XmlAccessType.PUBLIC_MEMBER) is default. So my question boils down to how to I get the plugin to follow the default behavior for @XmlAccessorType?

Again, this would save me time. The getter names I have are standard camel case, but the field names use upper case and lower case more or less at random because they were generated from a system in which I can't control field names. There should be a configuration file for jaxb, but I can't find one.

Re: XJC: get the Annotation-Information of a field

2009-11-27T02:40:22Z

Hey Aleksei and Wolfgang!
Thanks a million! (:

regards Flori

On 27.11.2009, at 10:20, Aleksei Valikov wrote:

> Hi,
>
>> Dear XJC-Users,
>> how I can find out, how an field is annotated?
>>
>> Suppose I have a class with two fields:
>> SupposedClass {
>> @XmlElement(name = "AnElement")
>> protected AnElement anElement;
>> @XmlAttribute(name = "attribute")
>> protected AnAttribute attribute;
>> }
>>
>> How can I find out, if an field is an XmlElement or an XmlAttribute and which name it uses?
>
> https://jaxb2-reflection.dev.java.net/users-guide.html
>
> Bye.
> /lexi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

--
Florian Bachmann, Softwareentwicklung
Micromata GmbH
Hauptsitz: Marie-Calm Str. 1-5, D-34131 Kassel
Niederlassung Bonn: Menuhinstr. 8, 53113 Bonn
Tel: +49 561 / 31 67 93 - 0
Fax: +49 561 / 31 67 93 - 11
mailto: f.bachmann@...
http://www.micromata.com
AG Kassel HRB 7370
Geschäftsführung:
Dipl.-Ing. Thomas Landgraf
Dipl.-Phys. Kai Reinhard

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: XJC: get the Annotation-Information of a field

2009-11-27T01:20:46Z

Hi,

> Dear XJC-Users,
> how I can find out, how an field is annotated?
>
> Suppose I have a class with two fields:
> SupposedClass {
> @XmlElement(name = "AnElement")
> protected AnElement anElement;
> @XmlAttribute(name = "attribute")
> protected AnAttribute attribute;
> }
>
> How can I find out, if an field is an XmlElement or an XmlAttribute and which name it uses?

https://jaxb2-reflection.dev.java.net/users-guide.html

Bye.
/lexi

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: XJC: get the Annotation-Information of a field

2009-11-27T01:11:33Z

On Fri, Nov 27, 2009 at 8:25 AM, Florian Bachmann <f.bachmann@...> wrote:

Dear XJC-Users,
how I can find out, how an field is annotated?

Suppose I have a class with two fields:
SupposedClass {
@XmlElement(name = "AnElement")
protected AnElement anElement;
@XmlAttribute(name = "attribute")
protected AnAttribute attribute;
}

How can I find out, if an field is an XmlElement or an XmlAttribute and which name it uses?

See the code below. - You may want to catch the "##default" and replace it with the field's own name.
-W

import java.util.*;
import java.lang.reflect.*;
import java.lang.annotation.*;
import javax.xml.bind.annotation.*;

public class AnnotationReader {

    private final Class clazz;

    public AnnotationReader( Class clazz ){
        this.clazz = clazz;
    }

    private List<Field> getFieldsWith( Class annotation ){
        Field[] fields = clazz.getDeclaredFields();
        List<Field> fList = new ArrayList<Field>();
        for( Field f: fields ){
            Annotation[] annos = f.getDeclaredAnnotations();
            for( Annotation a: annos ){
                if( annotation.isInstance( a ) ){
                    fList.add( f );
                    break;
                }
            }
        }
        return fList;
    }

    public List<Field> getElementFields(){
        return getFieldsWith( XmlElement.class );
    }

    public List<Field> getAttributeFields(){
        return getFieldsWith( XmlAttribute.class );
    }

    public Map<String,String> getSchemaNames() throws Exception {
        Field[] fields = clazz.getDeclaredFields();
        Map<String,String> field2tag = new HashMap<String,String>();
        for( Field f: fields ){
            Annotation[] annos = f.getDeclaredAnnotations();
            for( Annotation a: annos ){
                if( a instanceof XmlElement ||
                    a instanceof XmlAttribute ){
                    Class annoClass = a.annotationType();
                    String tName = (String)annoClass.getMethod( "name" ).invoke( a );
                    field2tag.put( f.getName(), tName );
                }
            }
        }
        return field2tag;
    }
}

XJC: get the Annotation-Information of a field

2009-11-26T23:25:18Z

Dear XJC-Users,
how I can find out, how an field is annotated?

Suppose I have a class with two fields:
SupposedClass {
@XmlElement(name = "AnElement")
protected AnElement anElement;
@XmlAttribute(name = "attribute")
protected AnAttribute attribute;
}

How can I find out, if an field is an XmlElement or an XmlAttribute and which name it uses?

regards Flori

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: how to get the annotations with the methods in stead of with the fields?

2009-11-26T08:27:26Z

Wolfgang Laun-2 wrote:

On Thu, Nov 26, 2009 at 4:21 PM, xtien <christine@christine.nl> wrote:
Anyway, assuming you get the @XmlElement annotation, what's in there that
is so desirable to have in an application? (I admit, I'm *very* curious ;-)

My app converts from and to an api that uses weird names. Jaxb creates decent getters and setters from the xsd that I created from the api, but as the api uses uppercase and lowercase more or less at random, it's easier to use the original element names than to try to create them from the getter name.

Re: Marshal to unqualified form?

2009-11-26T08:11:28Z

On Thu, 26 Nov 2009, Wolfgang Laun wrote:

> On Thu, Nov 26, 2009 at 3:15 PM, <david@...> wrote:
>
> Do I have to write a NamespacePrefixFormatter to get them unqialified? I
>> cannot seem to find any options for the Marshaller to get this OOTB.
>>
>> The other alternative of course, is to change the elementQualification in
>> the schema - but as these are external I'd rather try to avoid that ( and it
>> would be nice to control it at runtime - to be able to support both forms if
>> neccessary).
>>
>> Does this change really remove the NS prefixes from the marshalled XML?
>
> If not, please post the <xs:schema> element in full.
> -W

I was a little short-thought about this.
The jaxbmarshaller was defined with several contexts, hence it knew
several namespaces, and they were all included in the root element and all
the elemes were marshalled with a namespaceprefix.

i split it up in one context pr. schema and the one namespace is then
defined as targetdefault on the root node, and all the children are
defined without prefixes.

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

http://www.davidkarlsen.com

Re: how to get the annotations with the methods in stead of with the fields?

2009-11-26T07:51:46Z

On Thu, Nov 26, 2009 at 4:21 PM, xtien <christine@...> wrote:

Wolfgang Laun-2 wrote:
>
> On Thu, Nov 26, 2009 at 2:34 PM, xtien <christine@...> wrote:
>>
>> The Jaxb Eclipse plugin generates @XmlElement annotations with the field
>> names. In my app, it would be more convenient to have the annotations
>> with
>> the getter.
>
> Why? Perhaps you post what you want to achieve.
>

Does it matter?

There might be another way of getting what you want, from the XmlElement
annotation.

In my code at some point I have a getter method. The code invokes the method
on a class. With this invocation, the code needs the name of the element
that's in the information from the XmlElement. If the naming of methods and
fields were standard, I could simply get the annotation from the field by
creating the field name from the getter name and get the fields annotation.

The JAXB plugin just uses xjc to generate classes from an XML schema, and this
produces, for a field called fooBar, a getter getFooBar (or isFooBar for boolean).
Weird names might muddle the issue, but basically it's quite simple.

However, the classes are genereated based on xml from a system that does not
conform to standard field names. I am not in control of that system. It's
hard to create a field name from a getter name, so that's why it would be
convenient to have the annotation with the getter.
Actually, all I want to do is retrieve the original element name in a piece
of code where I have the getter method but not the field that it goes with.

Anyway, assuming you get the @XmlElement annotation, what's in there that
is so desirable to have in an application? (I admit, I'm very curious ;-)

-W

--
View this message in context: http://old.nabble.com/how-to-get-the-annotations-with-the-methods-in-stead-of-with-the-fields--tp26529506p26530937.html
Sent from the java.net - jaxb users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Marshal to unqualified form?

2009-11-26T07:24:56Z

On Thu, Nov 26, 2009 at 3:15 PM, <david@...> wrote:

Hi!

I have a schema (a SEPA PACS002 one) which is defined as elementFormDefault="qualified"

Hence when I marshal and object instance to XML all the elements are qualified with a namespace prefix.

Do I have to write a NamespacePrefixFormatter to get them unqialified? I cannot seem to find any options for the Marshaller to get this OOTB.

The other alternative of course, is to change the elementQualification in the schema - but as these are external I'd rather try to avoid that ( and it would be nice to control it at runtime - to be able to support both forms if neccessary).

Does this change really remove the NS prefixes from the marshalled XML?

If not, please post the <xs:schema> element in full.
-W

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: how to get the annotations with the methods in stead of with the fields?

2009-11-26T07:21:31Z

Wolfgang Laun-2 wrote:

On Thu, Nov 26, 2009 at 2:34 PM, xtien <christine@christine.nl> wrote:
>
> The Jaxb Eclipse plugin generates @XmlElement annotations with the field
> names. In my app, it would be more convenient to have the annotations with
> the getter.

Why? Perhaps you post what you want to achieve.

Does it matter?

In my code at some point I have a getter method. The code invokes the method on a class. With this invocation, the code needs the name of the element that's in the information from the XmlElement. If the naming of methods and fields were standard, I could simply get the annotation from the field by creating the field name from the getter name and get the fields annotation. However, the classes are genereated based on xml from a system that does not conform to standard field names. I am not in control of that system. It's hard to create a field name from a getter name, so that's why it would be convenient to have the annotation with the getter.
Actually, all I want to do is retrieve the original element name in a piece of code where I have the getter method but not the field that it goes with.

Re: Mixing schema-derived and own annotation defined types in a JaxbContext

2009-11-26T06:58:13Z

On Thu, Nov 26, 2009 at 3:10 PM, <david@...> wrote:

On Thu, 26 Nov 2009, Wolfgang Laun wrote:

Probably with the message "...doesnt contain ObjectFactory.class or
jaxb.index" (which you might have told us). See the JAXB Tutorial section on
JAXBContext<https://jaxb.dev.java.net/tutorial/section_3_5-The-JAXB-Context.html#The%20JAXB%20Context>
.

OK - so this confirms my suspicion.
Would it be possible to enhance JAXB with a new signature, giving both context paths (for schema derived classes (which are also annotated by th eway), as well as a vararg classes argument for the homemade ones?

You can always request an enhancement.

But, given that it is so simple to write a jaxb.index file, you might as well do that, and specify two (or more) package names.

-W

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: how to get the annotations with the methods in stead of with the fields?

2009-11-26T06:54:54Z

On Thu, Nov 26, 2009 at 2:34 PM, xtien <christine@...> wrote:

The Jaxb Eclipse plugin generates @XmlElement annotations with the field
names. In my app, it would be more convenient to have the annotations with
the getter.

Why? Perhaps you post what you want to achieve.

I have seen an example where the annotation is with the getter.

This was probably coded by hand.
-W

How do I make Jaxb put annotations with getters rather than with fields?

Thanks :-)

--
View this message in context: http://old.nabble.com/how-to-get-the-annotations-with-the-methods-in-stead-of-with-the-fields--tp26529506p26529506.html
Sent from the java.net - jaxb users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Marshal to unqualified form?

2009-11-26T06:15:07Z

Hi!

I have a schema (a SEPA PACS002 one) which is defined as
elementFormDefault="qualified"

Hence when I marshal and object instance to XML all the elements are
qualified with a namespace prefix.
Do I have to write a NamespacePrefixFormatter to get them unqialified? I
cannot seem to find any options for the Marshaller to get this OOTB.

The other alternative of course, is to change the
elementQualification in the schema - but as these are external I'd rather
try to avoid that ( and it would be nice to control it at runtime - to be
able to support both forms if neccessary).

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

http://www.davidkarlsen.com

Re: Mixing schema-derived and own annotation defined types in a JaxbContext

2009-11-26T06:10:56Z

On Thu, 26 Nov 2009, Wolfgang Laun wrote:

> Probably with the message "...doesnt contain ObjectFactory.class or
> jaxb.index" (which you might have told us). See the JAXB Tutorial section on
> JAXBContext<https://jaxb.dev.java.net/tutorial/section_3_5-The-JAXB-Context.html#The%20JAXB%20Context>
> .

OK - so this confirms my suspicion.
Would it be possible to enhance JAXB with a new signature, giving both
context paths (for schema derived classes (which are also annotated by th
eway), as well as a vararg classes argument for the homemade ones?

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

http://www.davidkarlsen.com

how to get the annotations with the methods in stead of with the fields?

2009-11-26T05:34:41Z

The Jaxb Eclipse plugin generates @XmlElement annotations with the field names. In my app, it would be more convenient to have the annotations with the getter. I have seen an example where the annotation is with the getter. How do I make Jaxb put annotations with getters rather than with fields?

Thanks :-)

Re: Changing access modifiers of generated classes

2009-11-26T00:41:37Z

On Wed, Nov 25, 2009 at 11:11 PM, jurgen quipere <jquipere@...> wrote:

Hi,

Is it possible to change the access modifier of a generated class from public to none? Can't find out how to do this in a plugin.

Perhaps a simple sed script would be adequate, e.g., for modifying just the setters:

sed -e '/ public void set/s/public //' SomeClass.Java

Plus a little shell glue to handle file copying.

-W

Re: Mixing schema-derived and own annotation defined types in a JaxbContext

2009-11-26T00:33:59Z

Probably with the message "...doesnt contain ObjectFactory.class or jaxb.index" (which you might have told us). See the JAXB Tutorial section on JAXBContext.

-W

On Thu, Nov 26, 2009 at 1:40 AM, David J. M. Karlsen <david@...> wrote:
> Hi!
>
> I have classes which were generated by XJC from and XSD, as well as a few
> homebrew classes/types, which were defined with annotations, like this:
>
> package jaxbPoc.client;
>
> import javax.xml.bind.annotation.XmlAccessType;
> import javax.xml.bind.annotation.XmlAccessorType;
> import javax.xml.bind.annotation.XmlElement;
> import javax.xml.bind.annotation.XmlRootElement;
> import javax.xml.bind.annotation.XmlType;
>
>
> @XmlRootElement( name="someElementName", namespace="" )
> @XmlAccessorType( XmlAccessType.FIELD )
> @XmlType
> public class SomeHomeBrewStructure
> {
> @XmlElement( name="TheElementName" )
> private String someVar = "theElementValue";
>
> }
>
> The generated ones are in jaxbCode.generated
>
> This works:
> jc = JAXBContext.newInstance("jaxbPoc.generatedCode");
>
> and this works:
> jc = JAXBContext.newInstance(jaxbPoc.client.SomeHomeBrewStructure.class);
>
> but this will not work:
> JAXBContext.newInstance("jaxbPoc.generatedCode:jaxbPoc.client");
>
> which is very un-handy.
>
> Is there no way to define them both in the one context together?
>
> --
> --
> David J. M. Karlsen - +47 90 68 22 43
> http://www.davidkarlsen.com
> http://mp3.davidkarlsen.com
> Sent from my bog-standard SMTP client
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

Re: XJC and "choice" element.

2009-11-26T00:12:57Z

On Wed, Nov 25, 2009 at 2:36 PM, Wolfgang Laun <wolfgang.laun@...> wrote:
> On Wed, Nov 25, 2009 at 2:26 PM, Pavel Bucek <Pavel.Bucek@...> wrote:
>>
>> reason: you are using jaxb-api v2.1 from jdk 1.6
>> needed action: copy jaxb-api.jar (v2.2!) to jdk's endorsed dir
>
> Which, to save you the bother of googling, is
> $JAVA_HOME/jre/lib/endorsed/, needing to be created.

And copy jaxb-impl.jar as well, or else execution fails with
java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory

-W

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Mixing schema-derived and own annotation defined types in a JaxbContext

2009-11-25T16:40:41Z

Hi!

I have classes which were generated by XJC from and XSD, as well as a
few homebrew classes/types, which were defined with annotations, like this:

package jaxbPoc.client;

import javax.xml.bind.annotation.XmlAccessType;
import javax.xml.bind.annotation.XmlAccessorType;
import javax.xml.bind.annotation.XmlElement;
import javax.xml.bind.annotation.XmlRootElement;
import javax.xml.bind.annotation.XmlType;

@XmlRootElement( name="someElementName", namespace="" )
@XmlAccessorType( XmlAccessType.FIELD )
@XmlType
public class SomeHomeBrewStructure
{
@XmlElement( name="TheElementName" )
private String someVar = "theElementValue";

}

The generated ones are in jaxbCode.generated

This works:
jc = JAXBContext.newInstance("jaxbPoc.generatedCode");

and this works:
jc = JAXBContext.newInstance(jaxbPoc.client.SomeHomeBrewStructure.class);

but this will not work:
JAXBContext.newInstance("jaxbPoc.generatedCode:jaxbPoc.client");

which is very un-handy.

Is there no way to define them both in the one context together?

--
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

http://www.davidkarlsen.com

Changing access modifiers of generated classes

2009-11-25T14:11:46Z

Hi,

Is it possible to change the access modifier of a generated class from public to none? Can't find out how to do this in a plugin.

Express yourself instantly with MSN Messenger! MSN Messenger

Re: XJC and "choice" element.

2009-11-25T05:36:09Z

On Wed, Nov 25, 2009 at 2:26 PM, Pavel Bucek <Pavel.Bucek@...> wrote:
>
> Hello,
>
> already explained in the issue comment.. see
> https://jaxb.dev.java.net/issues/show_bug.cgi?id=721.
>
> there is a simple reason

Ha!

> and a simple way how to get this working:
>
> reason: you are using jaxb-api v2.1 from jdk 1.6
> needed action: copy jaxb-api.jar (v2.2!) to jdk's endorsed dir

Which, to save you the bother of googling, is
$JAVA_HOME/jre/lib/endorsed/, needing to be created.

FYI, I have also urged for clarifying info in JAXB's docs/ReleaseNotes.html

-W

>
> regards,
> Pavel
>
>
> Wolfgang Laun wrote:
>>
>> John,
>>
>> the schema with 0/unboudned compiles without a hitch with any regular
>> xjc from JAXB v 2.1.8 up to 2.1.11 and the one distributed with JDK
>> "1.6.0_0". It fails with xjc JAXB 2.2 "Early Access". I'll submit an
>> issue.
>>
>> -W
>>
>>
>> On Tue, Nov 24, 2009 at 7:45 PM, John Leonard <jleonard.20081@...>
>> wrote:
>>
>>>
>>> Wolfgang Laun wrote:
>>>
>>>>
>>>> This does not depend on <choice...> alone. Can you post a full .xsd
>>>> producing the exception?
>>>> -W
>>>>
>>>> On 11/22/09, John Leonard <jleonard.20081@...> wrote:
>>>>
>>>>
>>>>>
>>>>> Does JAXB understand the following use of the "choice" element?
>>>>>
>>>>> <choice minOccurs="0" maxOccurs="unbounded">
>>>>> <element...
>>>>> <element...
>>>>> ...
>>>>> </choice>
>>>>>
>>>>> Here is the output of XJC when I run it from the command line on a file
>>>>> containing such code:
>>>>> parsing a schema...
>>>>> compiling a schema...
>>>>> [INFO] generating code
>>>>> unknown location
>>>>>
>>>>> Exception in thread "main"
>>>>> java.lang.reflect.UndeclaredThrowableException
>>>>> at $Proxy7.required(Unknown Source)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotateReferenc
>>>>> e(AbstractField.java:197)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotate(Abstrac
>>>>> tField.java:156)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.field.AbstractListField.generate(Abs
>>>>> tractListField.java:124)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.field.UntypedListField.<init>(Untype
>>>>> dListField.java:107)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.field.UntypedListFieldRenderer.gener
>>>>> ate(UntypedListFieldRenderer.java:72)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.field.DefaultFieldRenderer.generate(
>>>>> DefaultFieldRenderer.java:79)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(Bean
>>>>> Generator.java:747)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(Bean
>>>>> Generator.java:535)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.j
>>>>> ava:235)
>>>>> at
>>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator
>>>>> .java:175)
>>>>> at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)
>>>>> at com.sun.tools.xjc.Driver.run(Driver.java:343)
>>>>> at com.sun.tools.xjc.Driver.run(Driver.java:191)
>>>>> at com.sun.tools.xjc.Driver._main(Driver.java:116)
>>>>> at com.sun.tools.xjc.Driver.access$000(Driver.java:74)
>>>>> at com.sun.tools.xjc.Driver$1.run(Driver.java:96)
>>>>> Caused by: java.lang.NoSuchMethodException:
>>>>> javax.xml.bind.annotation.XmlElement
>>>>> Ref.required()
>>>>> at java.lang.Class.getDeclaredMethod(Unknown Source)
>>>>> at
>>>>> com.sun.codemodel.TypedAnnotationWriter.invoke(TypedAnnotationWriter.
>>>>> java:107)
>>>>> ... 17 more
>>>>>
>>>>> Thanks,
>>>>> John L.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>>> For additional commands, e-mail: users-help@...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>> For additional commands, e-mail: users-help@...
>>>>
>>>>
>>>
>>> File "xjc_compiles.xsd":
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <schema
>>> xmlns="http://www.w3.org/2001/XMLSchema"
>>> targetNamespace="http://www.sudokucaptain.com/CommandString111609"
>>> xmlns:cs="http://www.sudokucaptain.com/CommandString111609">
>>>
>>> <element name="TestElement">
>>> <complexType>
>>> <choice>
>>> <element name="element1" />
>>> <element name="element2" />
>>> </choice>
>>> </complexType>
>>> </element>
>>>
>>> </schema>
>>>
>>> File "xjc_doesnt_compile.xsd":
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <schema
>>> xmlns="http://www.w3.org/2001/XMLSchema"
>>> targetNamespace="http://www.sudokucaptain.com/CommandString111609"
>>> xmlns:cs="http://www.sudokucaptain.com/CommandString111609">
>>>
>>> <element name="TestElement">
>>> <complexType>
>>> <choice minOccurs="0" maxOccurs="unbounded">
>>> <element name="element1" />
>>> <element name="element2" />
>>> </choice>
>>> </complexType>
>>> </element>
>>>
>>> </schema>
>>>
>>> The only difference between these two files is this line:
>>> <choice minOccurs="0" maxOccurs="unbounded">
>>>
>>> I think JAXB would have a hard time working with a List containing
>>> unrelated
>>> types. Their only common ancestor would be "Object". It would still be
>>> nice,
>>> however, if this could be done as it would offer an alternative to
>>> creating
>>> large groups of related types and substitution groups.
>>>
>>> John L.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: XJC and "choice" element.

2009-11-25T05:26:49Z

Hello,

already explained in the issue comment.. see
https://jaxb.dev.java.net/issues/show_bug.cgi?id=721.

there is a simple reason and a simple way how to get this working:

reason: you are using jaxb-api v2.1 from jdk 1.6
needed action: copy jaxb-api.jar (v2.2!) to jdk's endorsed dir

regards,
Pavel

Wolfgang Laun wrote:

> John,
>
> the schema with 0/unboudned compiles without a hitch with any regular
> xjc from JAXB v 2.1.8 up to 2.1.11 and the one distributed with JDK
> "1.6.0_0". It fails with xjc JAXB 2.2 "Early Access". I'll submit an
> issue.
>
> -W
>
>
> On Tue, Nov 24, 2009 at 7:45 PM, John Leonard <jleonard.20081@...> wrote:
>
>> Wolfgang Laun wrote:
>>
>>> This does not depend on <choice...> alone. Can you post a full .xsd
>>> producing the exception?
>>> -W
>>>
>>> On 11/22/09, John Leonard <jleonard.20081@...> wrote:
>>>
>>>
>>>> Does JAXB understand the following use of the "choice" element?
>>>>
>>>> <choice minOccurs="0" maxOccurs="unbounded">
>>>> <element...
>>>> <element...
>>>> ...
>>>> </choice>
>>>>
>>>> Here is the output of XJC when I run it from the command line on a file
>>>> containing such code:
>>>> parsing a schema...
>>>> compiling a schema...
>>>> [INFO] generating code
>>>> unknown location
>>>>
>>>> Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
>>>> at $Proxy7.required(Unknown Source)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotateReferenc
>>>> e(AbstractField.java:197)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotate(Abstrac
>>>> tField.java:156)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.field.AbstractListField.generate(Abs
>>>> tractListField.java:124)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.field.UntypedListField.<init>(Untype
>>>> dListField.java:107)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.field.UntypedListFieldRenderer.gener
>>>> ate(UntypedListFieldRenderer.java:72)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.field.DefaultFieldRenderer.generate(
>>>> DefaultFieldRenderer.java:79)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(Bean
>>>> Generator.java:747)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(Bean
>>>> Generator.java:535)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.j
>>>> ava:235)
>>>> at
>>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator
>>>> .java:175)
>>>> at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)
>>>> at com.sun.tools.xjc.Driver.run(Driver.java:343)
>>>> at com.sun.tools.xjc.Driver.run(Driver.java:191)
>>>> at com.sun.tools.xjc.Driver._main(Driver.java:116)
>>>> at com.sun.tools.xjc.Driver.access$000(Driver.java:74)
>>>> at com.sun.tools.xjc.Driver$1.run(Driver.java:96)
>>>> Caused by: java.lang.NoSuchMethodException:
>>>> javax.xml.bind.annotation.XmlElement
>>>> Ref.required()
>>>> at java.lang.Class.getDeclaredMethod(Unknown Source)
>>>> at
>>>> com.sun.codemodel.TypedAnnotationWriter.invoke(TypedAnnotationWriter.
>>>> java:107)
>>>> ... 17 more
>>>>
>>>> Thanks,
>>>> John L.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>> For additional commands, e-mail: users-help@...
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>> File "xjc_compiles.xsd":
>> <?xml version="1.0" encoding="UTF-8"?>
>> <schema
>> xmlns="http://www.w3.org/2001/XMLSchema"
>> targetNamespace="http://www.sudokucaptain.com/CommandString111609"
>> xmlns:cs="http://www.sudokucaptain.com/CommandString111609">
>>
>> <element name="TestElement">
>> <complexType>
>> <choice>
>> <element name="element1" />
>> <element name="element2" />
>> </choice>
>> </complexType>
>> </element>
>>
>> </schema>
>>
>> File "xjc_doesnt_compile.xsd":
>> <?xml version="1.0" encoding="UTF-8"?>
>> <schema
>> xmlns="http://www.w3.org/2001/XMLSchema"
>> targetNamespace="http://www.sudokucaptain.com/CommandString111609"
>> xmlns:cs="http://www.sudokucaptain.com/CommandString111609">
>>
>> <element name="TestElement">
>> <complexType>
>> <choice minOccurs="0" maxOccurs="unbounded">
>> <element name="element1" />
>> <element name="element2" />
>> </choice>
>> </complexType>
>> </element>
>>
>> </schema>
>>
>> The only difference between these two files is this line:
>> <choice minOccurs="0" maxOccurs="unbounded">
>>
>> I think JAXB would have a hard time working with a List containing unrelated
>> types. Their only common ancestor would be "Object". It would still be nice,
>> however, if this could be done as it would offer an alternative to creating
>> large groups of related types and substitution groups.
>>
>> John L.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: XJC and "choice" element.

2009-11-25T00:03:32Z

John,

the schema with 0/unboudned compiles without a hitch with any regular
xjc from JAXB v 2.1.8 up to 2.1.11 and the one distributed with JDK
"1.6.0_0". It fails with xjc JAXB 2.2 "Early Access". I'll submit an
issue.

-W

On Tue, Nov 24, 2009 at 7:45 PM, John Leonard <jleonard.20081@...> wrote:

> Wolfgang Laun wrote:
>>
>> This does not depend on <choice...> alone. Can you post a full .xsd
>> producing the exception?
>> -W
>>
>> On 11/22/09, John Leonard <jleonard.20081@...> wrote:
>>
>>>
>>> Does JAXB understand the following use of the "choice" element?
>>>
>>> <choice minOccurs="0" maxOccurs="unbounded">
>>> <element...
>>> <element...
>>> ...
>>> </choice>
>>>
>>> Here is the output of XJC when I run it from the command line on a file
>>> containing such code:
>>> parsing a schema...
>>> compiling a schema...
>>> [INFO] generating code
>>> unknown location
>>>
>>> Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
>>> at $Proxy7.required(Unknown Source)
>>> at
>>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotateReferenc
>>> e(AbstractField.java:197)
>>> at
>>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotate(Abstrac
>>> tField.java:156)
>>> at
>>> com.sun.tools.xjc.generator.bean.field.AbstractListField.generate(Abs
>>> tractListField.java:124)
>>> at
>>> com.sun.tools.xjc.generator.bean.field.UntypedListField.<init>(Untype
>>> dListField.java:107)
>>> at
>>> com.sun.tools.xjc.generator.bean.field.UntypedListFieldRenderer.gener
>>> ate(UntypedListFieldRenderer.java:72)
>>> at
>>> com.sun.tools.xjc.generator.bean.field.DefaultFieldRenderer.generate(
>>> DefaultFieldRenderer.java:79)
>>> at
>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(Bean
>>> Generator.java:747)
>>> at
>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(Bean
>>> Generator.java:535)
>>> at
>>> com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.j
>>> ava:235)
>>> at
>>> com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator
>>> .java:175)
>>> at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)
>>> at com.sun.tools.xjc.Driver.run(Driver.java:343)
>>> at com.sun.tools.xjc.Driver.run(Driver.java:191)
>>> at com.sun.tools.xjc.Driver._main(Driver.java:116)
>>> at com.sun.tools.xjc.Driver.access$000(Driver.java:74)
>>> at com.sun.tools.xjc.Driver$1.run(Driver.java:96)
>>> Caused by: java.lang.NoSuchMethodException:
>>> javax.xml.bind.annotation.XmlElement
>>> Ref.required()
>>> at java.lang.Class.getDeclaredMethod(Unknown Source)
>>> at
>>> com.sun.codemodel.TypedAnnotationWriter.invoke(TypedAnnotationWriter.
>>> java:107)
>>> ... 17 more
>>>
>>> Thanks,
>>> John L.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>
> File "xjc_compiles.xsd":
> <?xml version="1.0" encoding="UTF-8"?>
> <schema
> xmlns="http://www.w3.org/2001/XMLSchema"
> targetNamespace="http://www.sudokucaptain.com/CommandString111609"
> xmlns:cs="http://www.sudokucaptain.com/CommandString111609">
>
> <element name="TestElement">
> <complexType>
> <choice>
> <element name="element1" />
> <element name="element2" />
> </choice>
> </complexType>
> </element>
>
> </schema>
>
> File "xjc_doesnt_compile.xsd":
> <?xml version="1.0" encoding="UTF-8"?>
> <schema
> xmlns="http://www.w3.org/2001/XMLSchema"
> targetNamespace="http://www.sudokucaptain.com/CommandString111609"
> xmlns:cs="http://www.sudokucaptain.com/CommandString111609">
>
> <element name="TestElement">
> <complexType>
> <choice minOccurs="0" maxOccurs="unbounded">
> <element name="element1" />
> <element name="element2" />
> </choice>
> </complexType>
> </element>
>
> </schema>
>
> The only difference between these two files is this line:
> <choice minOccurs="0" maxOccurs="unbounded">
>
> I think JAXB would have a hard time working with a List containing unrelated
> types. Their only common ancestor would be "Object". It would still be nice,
> however, if this could be done as it would offer an alternative to creating
> large groups of related types and substitution groups.
>
> John L.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: XJC and "choice" element.

2009-11-24T10:45:45Z

Wolfgang Laun wrote:

> This does not depend on <choice...> alone. Can you post a full .xsd
> producing the exception?
> -W
>
> On 11/22/09, John Leonard <jleonard.20081@...> wrote:
>
>> Does JAXB understand the following use of the "choice" element?
>>
>> <choice minOccurs="0" maxOccurs="unbounded">
>> <element...
>> <element...
>> ...
>> </choice>
>>
>> Here is the output of XJC when I run it from the command line on a file
>> containing such code:
>> parsing a schema...
>> compiling a schema...
>> [INFO] generating code
>> unknown location
>>
>> Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
>> at $Proxy7.required(Unknown Source)
>> at
>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotateReferenc
>> e(AbstractField.java:197)
>> at
>> com.sun.tools.xjc.generator.bean.field.AbstractField.annotate(Abstrac
>> tField.java:156)
>> at
>> com.sun.tools.xjc.generator.bean.field.AbstractListField.generate(Abs
>> tractListField.java:124)
>> at
>> com.sun.tools.xjc.generator.bean.field.UntypedListField.<init>(Untype
>> dListField.java:107)
>> at
>> com.sun.tools.xjc.generator.bean.field.UntypedListFieldRenderer.gener
>> ate(UntypedListFieldRenderer.java:72)
>> at
>> com.sun.tools.xjc.generator.bean.field.DefaultFieldRenderer.generate(
>> DefaultFieldRenderer.java:79)
>> at
>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(Bean
>> Generator.java:747)
>> at
>> com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(Bean
>> Generator.java:535)
>> at
>> com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.j
>> ava:235)
>> at
>> com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator
>> .java:175)
>> at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)
>> at com.sun.tools.xjc.Driver.run(Driver.java:343)
>> at com.sun.tools.xjc.Driver.run(Driver.java:191)
>> at com.sun.tools.xjc.Driver._main(Driver.java:116)
>> at com.sun.tools.xjc.Driver.access$000(Driver.java:74)
>> at com.sun.tools.xjc.Driver$1.run(Driver.java:96)
>> Caused by: java.lang.NoSuchMethodException:
>> javax.xml.bind.annotation.XmlElement
>> Ref.required()
>> at java.lang.Class.getDeclaredMethod(Unknown Source)
>> at
>> com.sun.codemodel.TypedAnnotationWriter.invoke(TypedAnnotationWriter.
>> java:107)
>> ... 17 more
>>
>> Thanks,
>> John L.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

File "xjc_compiles.xsd":
<?xml version="1.0" encoding="UTF-8"?>
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.sudokucaptain.com/CommandString111609"
xmlns:cs="http://www.sudokucaptain.com/CommandString111609">

<element name="TestElement">
<complexType>
<choice>
<element name="element1" />
<element name="element2" />
</choice>
</complexType>
</element>

</schema>

File "xjc_doesnt_compile.xsd":
<?xml version="1.0" encoding="UTF-8"?>
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.sudokucaptain.com/CommandString111609"
xmlns:cs="http://www.sudokucaptain.com/CommandString111609">

<element name="TestElement">
<complexType>
<choice minOccurs="0" maxOccurs="unbounded">
<element name="element1" />
<element name="element2" />
</choice>
</complexType>
</element>

</schema>

The only difference between these two files is this line:
<choice minOccurs="0" maxOccurs="unbounded">

I think JAXB would have a hard time working with a List containing
unrelated types. Their only common ancestor would be "Object". It would
still be nice, however, if this could be done as it would offer an
alternative to creating large groups of related types and substitution
groups.

John L.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: question about modularization

2009-11-23T11:00:16Z

Felipe Gaúcho wrote:

> Now, I have some questions, mainly regarding modularization issues.
> Maybe you could help me on this:
>
> - Let's assume we have module A with a.xsd inside and module B with
> b.xsd. a.xsd defines type t, type u and type v; type u is abstract.
> a.xsd uses the types t and v and extends type u.
>
> The question is now if it's possible to generate the according
> JAXB-Java-classes at build time for every module separately. This would
> mean that we have calsses for the types t, u and v in module A. And
> class that extends type u in module B. This would mean that during build
> time of module B, JAXB has to know that the classes of a.xsd have been
> generated already and as well their names and packages.
> - Is this possible?
>

yes, it is. Look at
http://weblogs.java.net/blog/2006/09/05/separate-compilation-jaxb-ri-21
> - Does this make sense?
>
> Another question is about file resolving.
> - Is there a possibility to provide an alternative file resolver (e.g.
> that looks referenced schema files up in the classpath)?
>
not sure what you mean or what you want to achieve. If you mean this as
a XML input the answer is "no", but please try describe your use case in
more detail..

Pavel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: question about modularization

2009-11-23T10:52:38Z

On 11/23/09, Felipe Gaúcho <fgaucho@...> wrote:

Yes.
> - Does this make sense?
Yes.

The way to do this (without customization) is to put the Schema definitions for
types t, u, v into a namespace resulting in the package name for A and
the things that use (and extend) these types into B's namespace. The
schema b.xsd
would use xsd:import schema a.xsd so that there is only one glorious
xjc run, producing all classes at the same time.

Outlines for a.xsd and b.xsd:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="/some/where/a"
xmlns:a="/some/where/a">
</xsd:schema>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="/some/where/b"
xmlns:b="/some/where/b"
xmlns:a="/some/where/a">
<xsd:import namespace="/some/where/a"
schemaLocation="a.xsd"/>

<xsd:element name="foo" type="a:u"/>
</xsd:schema>

>
> Another question is about file resolving.
> - Is there a possibility to provide an alternative file resolver (e.g.
> that looks referenced schema files up in the classpath)?

Your question isn't clear to me. Schema files (presumably to be used
for validation) aren't different from any other data files in your
classpath. Class.getResourceAsStream(String path) should do the trick.

-W

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

question about modularization

2009-11-23T10:19:32Z

Now, I have some questions, mainly regarding modularization issues.
Maybe you could help me on this:

- Let's assume we have module A with a.xsd inside and module B with
b.xsd. a.xsd defines type t, type u and type v; type u is abstract.
a.xsd uses the types t and v and extends type u.

The question is now if it's possible to generate the according
JAXB-Java-classes at build time for every module separately. This would
mean that we have calsses for the types t, u and v in module A. And
class that extends type u in module B. This would mean that during build
time of module B, JAXB has to know that the classes of a.xsd have been
generated already and as well their names and packages.
- Is this possible?
- Does this make sense?

Another question is about file resolving.
- Is there a possibility to provide an alternative file resolver (e.g.
that looks referenced schema files up in the classpath)?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: XJC get the annotaion of an created field or as alternative the property order

2009-11-23T07:44:36Z

Hey /lexi,
thank you, this should help me (:
regards Flori

On 23.11.2009, at 16:40, Aleksei Valikov wrote:

> Hi,
>
>> Hello XJC-Users,
>> is there a way to get to annotations of an generated class?
>> Assume ich have a ClassOutline classOutline.
>> Is there a method, like: classOutline.target.getAnnotations();
>>
>> The reason, I like to get these information is, that I like to access to XmlType propOrder-Annotation.
>>
>> For Example, JAXB generates
>> @XmlAccessorType(XmlAccessType.FIELD)
>> @XmlType(name = "MyClassType", propOrder = {
>> "firstField",
>> "secondField",
>> "thirdField",
>> "anOtherField"
>> })
>> public class MyClass {}
>>
>> Is it possible to access the annotation of the created prop-order annotation, to get the order of the created fields? To know, that the secondField is really the second field and anOtherField is the fourth field? Or is it possible to find out the property/field order?
>
> You can't get this information from the code model without hacks. And
> it's not the right way anyway.
>
> The right way would be to get this information from the CClassInfo.
> See how the propOrder field is generated:
>
> CClassInfo target = ...;
> ...
> if(target.isOrdered()) {
> for(CPropertyInfo p : target.getProperties() ) {
> if( ! (p instanceof CAttributePropertyInfo )) {
> if (!( (p instanceof CReferencePropertyInfo) &&
> ((CReferencePropertyInfo)p).isDummy())) {
> xtw.propOrder(p.getName(false));
> }
> }
> }
> } else {
> // produce empty array
> xtw.getAnnotationUse().paramArray("propOrder");
> }
>
> Bye.
> /lexi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

Re: XJC get the annotaion of an created field or as alternative the property order

2009-11-23T07:40:22Z

Hi,

> Hello XJC-Users,
> is there a way to get to annotations of an generated class?
> Assume ich have a ClassOutline classOutline.
> Is there a method, like: classOutline.target.getAnnotations();
>
> The reason, I like to get these information is, that I like to access to XmlType propOrder-Annotation.
>
> For Example, JAXB generates
> @XmlAccessorType(XmlAccessType.FIELD)
> @XmlType(name = "MyClassType", propOrder = {
> "firstField",
> "secondField",
> "thirdField",
> "anOtherField"
> })
> public class MyClass {}
>
> Is it possible to access the annotation of the created prop-order annotation, to get the order of the created fields? To know, that the secondField is really the second field and anOtherField is the fourth field? Or is it possible to find out the property/field order?

You can't get this information from the code model without hacks. And
it's not the right way anyway.

The right way would be to get this information from the CClassInfo.
See how the propOrder field is generated:

CClassInfo target = ...;
...
if(target.isOrdered()) {
for(CPropertyInfo p : target.getProperties() ) {
if( ! (p instanceof CAttributePropertyInfo )) {
if (!( (p instanceof CReferencePropertyInfo) &&
((CReferencePropertyInfo)p).isDummy())) {
xtw.propOrder(p.getName(false));
}
}
}
} else {
// produce empty array
xtw.getAnnotationUse().paramArray("propOrder");
}

Bye.
/lexi

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

XJC get the annotaion of an created field or as alternative the property order

2009-11-23T07:32:22Z

Hello XJC-Users,
is there a way to get to annotations of an generated class?
Assume ich have a ClassOutline classOutline.
Is there a method, like: classOutline.target.getAnnotations();

The reason, I like to get these information is, that I like to access to XmlType propOrder-Annotation.

For Example, JAXB generates
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "MyClassType", propOrder = {
"firstField",
"secondField",
"thirdField",
"anOtherField"
})
public class MyClass {}

Is it possible to access the annotation of the created prop-order annotation, to get the order of the created fields? To know, that the secondField is really the second field and anOtherField is the fourth field? Or is it possible to find out the property/field order?

regards Flori

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...