Nabble - java.net - JAXB

Using JAXB 2.2 with JavaSE 6

2009-12-17T16:49:03Z

Hi All:

On this page:

https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

I read:

"Use the system property java.endorsed.dirs when you launch your application, and have it point to the directory that contains the 2.1/2.2 jaxb-api.jar. This allows you use use JAXB 2.1/2.2 without modifying the JRE. Make sure not to include any other JAXB RI jar files (such as jsr173-api.jar or jaxb-impl.jar.)"

I like to make sure I get this exactly right. I will put the single JAXB file jaxb-api.jar in the directory pointed to by java.endorsed.dirs.

What about the other JAXB jar files? Can they be on the plain old classpath?

WRT jsr173-api.jar, since the API is in JavaSE 6, can I ignored it altogether and not distribute it?

Thank you,

Gary Gregory
Seagull Software
ggregory@...
www.seagullsoftware.com

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

From forum: java.net - jaxb users

Re: FW: How to map Java enum to XML element (not #PCDATA) body?

2009-12-17T11:52:32Z

So I should caution you that @XmlJavaTypeAdapter and @XmlRootElement are not
compatible. The adapter is not called if <e> is a document root.

For classes such as ThirdPartyElement, which users contribute for marshalling and
unmarshalling, you can force them to use factory methods
public E newInstance(final V1 v1){
return V_1;
}
public E newInstance(final V2 v2){
return V_2;
}
which won't let them create any wild E objects in the first place.

-W

On Thu, Dec 17, 2009 at 7:54 PM, Markus Karg <markus.karg@...> wrote:

Wolfgang,

I never said that your code is not working at all, but just the proposed solution it outlines does not work in my particular case. The problem is that third parties might use class E in conjunction with their own code, e. g.

@XmlRootElement

public class ThirdPartyElement {

   public E e;

}

In that case, the third party author must take care to implement the singleton support you are proposing. As a result, that singleton support ends up in lots of places, and if only one of them are broken…: Happy searching! ;-)

The cause is that the unmarshall-Callbacks cannot replace the current object. It just can modify the object, or it can modify the parent, what both is suboptimal.

The solution I just sent to the mailing list solves this problem, as the singleton stuff in self-contained in the class E itself. So no third party author has to take care, resulting in no code places which could break. For me, this looks like the ultimate solution to the problem, but maybe you have a better idea? :-)

Regards

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Donnerstag, 17. Dezember 2009 18:45

To: users@...

Subject: Re: FW: How to map Java enum to XML element (not #PCDATA) body?

Markus,

this has to be discussed with a little more background. I understand that you have an XML schema, which apparently defines <e> with a subordinate choice with alternatives <v1/>,...<vN/>. No Java code is generated from this schema; you write the class E by hand.

One would think that elements <e> occurs in the XML schema, and that's why I wonder what these objects E might have to do with the API you are providing. If you are providing unmarshalling for XML according to the schema, my proposed solution works.

Marshalling is slightly different, but you haven't used this word yet ;-)

A short sample code of what your API must provide in connection with class E might help.

-W

On Thu, Dec 17, 2009 at 3:40 PM, Markus Karg <markus.karg@...> wrote:

Anybody having an idea how to solve this?

From: Markus Karg [mailto:markus.karg@...]
Sent: Dienstag, 15. Dezember 2009 21:33
To: 'users@...'
Subject: RE: How to map Java enum to XML element (not #PCDATA) body?

Wolfgang,

your proposed solution unfortunately does not work! :-(

You are assuming that I know locations of any code that is using my enum. But this is not the case. I am writing a library that anybody can use. The job of providing a singleton has to be done *inside* my library (i. e. JAXB itself must know that an instance has to be replaced by another instance *before* providing the reference to a using instance), not *outside* (not in the caller's class). Otherwise each user would have to know about the singleton problem and take care of it, what is very, very error prone.

I need a solution that works *within* my library. Somethink like an "Unmarshal Resolver". I know I can register unmarshal listeners, but how to tell in that's event handler that the outcome is a *different* instance?

Thanks!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

What you want is a unique instance of E for each of the unique settings of its fields v1, v2,... with a unique instance of V1, V2,..., respectively.

Since you are not compiling the Java classes from the XML schema, you could write all setters of fields of type E so that

public void setE( E e ){
    this.e = E.getSingleton( e );
}

E.getSingleton() would have to determine which of e's fields v1, v2,... is not null and return the corresponding E.V_1, E.V_2,...

-W

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

<e><v1/></e>

shall result in the same Java enum instance than

<e>

    <v1>

    </v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

This perfectly unmarshalls any kind of formatting and whitespacing of <e><v1/></e> and I am really happy with it so far, BUT it does not produce singletongs. Instead, I am getting another instance of E and V1 each time. This is rather bad, since I now must use the equals operator to compare them, while it would be certainly great to in fact have the same instances to be able to compare references:

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

RE: FW: How to map Java enum to XML element (not #PCDATA) body?

2009-12-17T10:53:45Z

Wolfgang,

I never said that your code is not working at all, but just the proposed solution it outlines does not work in my particular case. The problem is that third parties might use class E in conjunction with their own code, e. g.

@XmlRootElement

public class ThirdPartyElement {

public E e;

}

In that case, the third party author must take care to implement the singleton support you are proposing. As a result, that singleton support ends up in lots of places, and if only one of them are broken…: Happy searching! ;-)

The cause is that the unmarshall-Callbacks cannot replace the current object. It just can modify the object, or it can modify the parent, what both is suboptimal.

The solution I just sent to the mailing list solves this problem, as the singleton stuff in self-contained in the class E itself. So no third party author has to take care, resulting in no code places which could break. For me, this looks like the ultimate solution to the problem, but maybe you have a better idea? :-)

Regards

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Donnerstag, 17. Dezember 2009 18:45
To: users@...
Subject: Re: FW: How to map Java enum to XML element (not #PCDATA) body?

Markus,

this has to be discussed with a little more background. I understand that you have an XML schema, which apparently defines <e> with a subordinate choice with alternatives <v1/>,...<vN/>. No Java code is generated from this schema; you write the class E by hand.

One would think that elements <e> occurs in the XML schema, and that's why I wonder what these objects E might have to do with the API you are providing. If you are providing unmarshalling for XML according to the schema, my proposed solution works.

Marshalling is slightly different, but you haven't used this word yet ;-)

A short sample code of what your API must provide in connection with class E might help.

-W

On Thu, Dec 17, 2009 at 3:40 PM, Markus Karg <markus.karg@...> wrote:

Anybody having an idea how to solve this?

From: Markus Karg [mailto:markus.karg@...]
Sent: Dienstag, 15. Dezember 2009 21:33
To: 'users@...'
Subject: RE: How to map Java enum to XML element (not #PCDATA) body?

Wolfgang,

your proposed solution unfortunately does not work! :-(

You are assuming that I know locations of any code that is using my enum. But this is not the case. I am writing a library that anybody can use. The job of providing a singleton has to be done *inside* my library (i. e. JAXB itself must know that an instance has to be replaced by another instance *before* providing the reference to a using instance), not *outside* (not in the caller's class). Otherwise each user would have to know about the singleton problem and take care of it, what is very, very error prone.

I need a solution that works *within* my library. Somethink like an "Unmarshal Resolver". I know I can register unmarshal listeners, but how to tell in that's event handler that the outcome is a *different* instance?

Thanks!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

What you want is a unique instance of E for each of the unique settings of its fields v1, v2,... with a unique instance of V1, V2,..., respectively.

Since you are not compiling the Java classes from the XML schema, you could write all setters of fields of type E so that

public void setE( E e ){
this.e = E.getSingleton( e );
}

E.getSingleton() would have to determine which of e's fields v1, v2,... is not null and return the corresponding E.V_1, E.V_2,...

-W

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

This perfectly unmarshalls any kind of formatting and whitespacing of <e><v1/></e> and I am really happy with it so far, BUT it does not produce singletongs. Instead, I am getting another instance of E and V1 each time. This is rather bad, since I now must use the equals operator to compare them, while it would be certainly great to in fact have the same instances to be able to compare references:

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

Re: FW: How to map Java enum to XML element (not #PCDATA) body?

2009-12-17T09:44:46Z

On Thu, Dec 17, 2009 at 3:40 PM, Markus Karg <markus.karg@...> wrote:

Anybody having an idea how to solve this?

From: Markus Karg [mailto:markus.karg@...]
Sent: Dienstag, 15. Dezember 2009 21:33
To: 'users@...'
Subject: RE: How to map Java enum to XML element (not #PCDATA) body?

Wolfgang,

your proposed solution unfortunately does not work! :-(

You are assuming that I know locations of any code that is using my enum. But this is not the case. I am writing a library that anybody can use. The job of providing a singleton has to be done *inside* my library (i. e. JAXB itself must know that an instance has to be replaced by another instance *before* providing the reference to a using instance), not *outside* (not in the caller's class). Otherwise each user would have to know about the singleton problem and take care of it, what is very, very error prone.

I need a solution that works *within* my library. Somethink like an "Unmarshal Resolver". I know I can register unmarshal listeners, but how to tell in that's event handler that the outcome is a *different* instance?

Thanks!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

What you want is a unique instance of E for each of the unique settings of its fields v1, v2,... with a unique instance of V1, V2,..., respectively.

Since you are not compiling the Java classes from the XML schema, you could write all setters of fields of type E so that

public void setE( E e ){
    this.e = E.getSingleton( e );
}

E.getSingleton() would have to determine which of e's fields v1, v2,... is not null and return the corresponding E.V_1, E.V_2,...

-W

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

<e><v1/></e>

shall result in the same Java enum instance than

<e>

    <v1>

    </v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

This perfectly unmarshalls any kind of formatting and whitespacing of <e><v1/></e> and I am really happy with it so far, BUT it does not produce singletongs. Instead, I am getting another instance of E and V1 each time. This is rather bad, since I now must use the equals operator to compare them, while it would be certainly great to in fact have the same instances to be able to compare references:

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

RE: How to map Java enum to XML element (not #PCDATA) body?

2009-12-17T08:08:48Z

Meanwhile I found a solution and think that it seems to be quite optimal, see below.

Any comments appreciated (maybe still too complex?)! :-)

@XmlAccessorType(FIELD)

@XmlJavaTypeAdapter(E.class)

@XmlRootElement()

public final class E extends XmlAdapter<E, E> {

public static final E V_1 = new E(V1.SINGLETON, null);

public static final E V_2 = new E(null, V2.SINGLETON);

private E v1;

private E v2;

// Singleton

private E() {

// For unmarshalling only.

}

// Enum

private E(final V1 v1, final V2 v2) {

this.v1 = v1;

this.v2 = v2;

}

@Override

public final E marshal(final E v) throws Exception {

return v;

}

@Override

public final E unmarshal(final E v) throws Exception {

if (v.v1 != null)

return V_1;

if (v.v2 != null)

return V_2;

return v;

}

A @XmlRootElement that itself is it's own @XmlJavaTypeAdapter and XmlAdapter, mapping itself to itself, actually is nothing else but an "(Un)marshaller.Listener on steroids": It is able to replace instances of itself by other instances on iteself at both, marshalling and unmarshalling. That trick allows to implement not only highly complex enums, but also any kind of value-aware (!) factories, like here, a multi-singleton. :-)

Regards

Markus

From: Markus Karg [mailto:markus.karg@...]
Sent: Donnerstag, 17. Dezember 2009 15:41
To: users@...
Subject: FW: How to map Java enum to XML element (not #PCDATA) body?

Anybody having an idea how to solve this?

From: Markus Karg [mailto:markus.karg@...]
Sent: Dienstag, 15. Dezember 2009 21:33
To: 'users@...'
Subject: RE: How to map Java enum to XML element (not #PCDATA) body?

Wolfgang,

your proposed solution unfortunately does not work! :-(

Thanks!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

FW: How to map Java enum to XML element (not #PCDATA) body?

2009-12-17T06:40:33Z

Anybody having an idea how to solve this?

From: Markus Karg [mailto:markus.karg@...]
Sent: Dienstag, 15. Dezember 2009 21:33
To: 'users@...'
Subject: RE: How to map Java enum to XML element (not #PCDATA) body?

Wolfgang,

your proposed solution unfortunately does not work! :-(

Thanks!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

Provider and Licence question

2009-12-17T06:05:08Z

Hello,

My question is about: https://jaxb2-commons.dev.java.net/

It is not very clear for me... But who is developing "JAXB2-Commons"? Is it Sun?

Another question is: what is the license of "JAXB2-Commons"?

Regards,

Anthony MÜLLER

From: Muller, Anthony
Sent: jeudi 17 décembre 2009 14:56
To: 'users@...'
Subject: subscribe

From forum: java.net - jaxb users

Provider and Licence question

2009-12-17T06:02:00Z

Hello,

My question is about: https://jaxb2-commons.dev.java.net/

It is not very clear for me... But who is developing "JAXB2-Commons"? Is it Sun?

Another question is: what is the license of "JAXB2-Commons"?

Regards,

Anthony MÜLLER

From: Muller, Anthony
Sent: jeudi 17 décembre 2009 14:56
To: 'users@...'
Subject: subscribe

From forum: java.net - jaxb users

Re: JAXB Commons Lang Plugin 2.2 is released

2009-12-16T13:35:52Z

For now I've just changed it from 2.2 to 2.1.8. You can try re-downloading it from the usual place.

On Wed, Dec 16, 2009 at 9:16 AM, <david@...> wrote:

On Mon, 14 Dec 2009, Hanson Char wrote:

https://jaxb2-commons.dev.java.net/commons-lang-plugin/index.html#Enhance091213

It depends on this artifact which I cannot find:
<dependency>
<groupId>com.sun.xml</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>2.2</version>
</dependency>

Can they both get uploaded to central?

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

From forum: java.net - jaxb users

Re: JAXB Commons Lang Plugin 2.2 is released

2009-12-16T13:32:32Z

damn, stupid c&p error, sorry.

I meant

<repositories>
<repository>
<id>maven2-repository.dev.java.net</id>
<name>Java.net Repository for Maven</name>
<url>http://download.java.net/maven/2/</url>
<layout>default</layout>
</repository>
</repositories>

Pavel Bucek wrote:

> Yes, they will be but its not possible right now, because we
> discovered that somebody published jaxb-api-2.2 two years ago (!) so
> this has to be removed/replaced before pushing jaxb-impl-2.2,
> jaxb-xjc-2.2 and jaxb1-impl-2.2
>
> Please do not publish to maven central without our approval.
>
> Thanks,
> Pavel
>
> ps.: in the meantime, add this to your pom file:
>
> <repositories>
> <repository>
> <id>java.net2</id>
> <name>java net maven 2 repository</name>
> <url>http://maven.glassfish.org/content/groups/glassfish</url>
> </repository>
> </repositories>
>
> and it should work.
>
>
>
> david@... wrote:
>> On Mon, 14 Dec 2009, Hanson Char wrote:
>>
>>> https://jaxb2-commons.dev.java.net/commons-lang-plugin/index.html#Enhance091213
>>>
>> It depends on this artifact which I cannot find:
>> <dependency>
>> <groupId>com.sun.xml</groupId>
>> <artifactId>jaxb-xjc</artifactId>
>> <version>2.2</version>
>> </dependency>
>>
>> Can they both get uploaded to central?
>>
>>
>> --
>> 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@...
>>
>
>
> ---------------------------------------------------------------------
> 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@...

From forum: java.net - jaxb users

Re: JAXB Commons Lang Plugin 2.2 is released

2009-12-16T13:10:49Z

Yes, they will be but its not possible right now, because we discovered
that somebody published jaxb-api-2.2 two years ago (!) so this has to be
removed/replaced before pushing jaxb-impl-2.2, jaxb-xjc-2.2 and
jaxb1-impl-2.2

Please do not publish to maven central without our approval.

Thanks,
Pavel

ps.: in the meantime, add this to your pom file:

<repositories>
<repository>
<id>java.net2</id>
<name>java net maven 2 repository</name>
<url>http://maven.glassfish.org/content/groups/glassfish</url>
</repository>
</repositories>

and it should work.

david@... wrote:

> On Mon, 14 Dec 2009, Hanson Char wrote:
>
>> https://jaxb2-commons.dev.java.net/commons-lang-plugin/index.html#Enhance091213
>>
> It depends on this artifact which I cannot find:
> <dependency>
> <groupId>com.sun.xml</groupId>
> <artifactId>jaxb-xjc</artifactId>
> <version>2.2</version>
> </dependency>
>
> Can they both get uploaded to central?
>
>
> --
> 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@...
>

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

From forum: java.net - jaxb users

Re: JAXB Commons Lang Plugin 2.2 is released

2009-12-16T09:16:09Z

On Mon, 14 Dec 2009, Hanson Char wrote:

> https://jaxb2-commons.dev.java.net/commons-lang-plugin/index.html#Enhance091213
It depends on this artifact which I cannot find:
<dependency>
<groupId>com.sun.xml</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>2.2</version>
</dependency>

Can they both get uploaded to central?

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

From forum: java.net - jaxb users

RE: How to map Java enum to XML element (not #PCDATA) body?

2009-12-15T12:33:02Z

Wolfgang,

your proposed solution unfortunately does not work! :-(

Thanks!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

RE: How to map Java enum to XML element (not #PCDATA) body?

2009-12-15T12:17:16Z

Wolfgang, thank you. The solution is so pretty obvious that I wonder why I actually asked the question. ;-)

Thanks a lot!

Markus

From: Wolfgang Laun [mailto:wolfgang.laun@...]
Sent: Dienstag, 15. Dezember 2009 20:15
To: users@...
Subject: Re: How to map Java enum to XML element (not #PCDATA) body?

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

Re: How to map Java enum to XML element (not #PCDATA) body?

2009-12-15T11:15:13Z

On Tue, Dec 15, 2009 at 5:58 PM, Markus Karg <markus.karg@...> wrote:

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

<e><v1/></e>

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

This perfectly unmarshalls any kind of formatting and whitespacing of <e><v1/></e> and I am really happy with it so far, BUT it does not produce singletongs. Instead, I am getting another instance of E and V1 each time. This is rather bad, since I now must use the equals operator to compare them, while it would be certainly great to in fact have the same instances to be able to compare references:

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

How to map Java enum to XML element (not #PCDATA) body?

2009-12-15T08:58:28Z

Using @XmlEnumValue it is possible to map Java enums to XML elements, like in this example>

@XmlRootElement

public enum E {

@XmlEnumValue("v1") V_1,

@XmlEnumValue("v2") V_2,

…

}

While this is working fine in case of #PCDATA values, I now am experiencing the problem that I need to map values that are not #PCDATA but in fact are XML elements:

For example,

shall result in the same Java enum instance than

<e>

<v1>

</v1>

</e>

and so on.

That means, I cannot write

@XmlEnumValue("<v1/>") V_1,

@XmlEnumValue("<v2/>") V_2,

in Java, because that would not result in an instance of B when unmarshalling a formatted XML file.

Can anybody tell me a solution working in JAXB 2.1 that will solve this problem?

I started with a rather complex workaround like this one (derived from the singleton pattern):

@XmlAccessorType(FIELD)

@XmlRootElement

public class E {

public static final E V_1 = new E(new V1());

public static final E V_2 = new E(new V2());

private V1 v1;

private V2 v2;

private E() { }

private E(V1 v1) { this.v1 = v1; }

private E(V2 v2) { this.v2 = v2; }

}

@XmlRootElement

public final class V1 { }

@XmlRootElement

public final class V2 { }

if (unmarshalledObject == E.V1)

So my questions are:

* How can I get singletons, i. e. always the same instance of E.V1 and E.V2 instead of new copies for each reference?

* Ain't there a simpler way to get enums with dynamically formatted and whitespaced XML element bodies?

BTW, since the XML schema is far out of my control, I am sorry, no, I cannot change the fact that the body is not a #PCDATA but an XML element.

Thanks a lot!

Markus

From forum: java.net - jaxb users

JAXB Commons Lang Plugin 2.2 is released

2009-12-14T10:08:35Z

https://jaxb2-commons.dev.java.net/commons-lang-plugin/index.html#Enhance091213

To enable this plugin to work with Java 6.

Cheers,
Hanson

From forum: java.net - jaxb users

JAXB Fluent API 2.2 is released

2009-12-13T11:08:01Z

https://jaxb2-commons.dev.java.net/fluent-api/index.html#Enhance091213

To enable this plugin to work with Java 6.

Cheers,
Hanson

From forum: java.net - jaxb users

[ANN] JAXB 2.2 is released

2009-12-11T05:47:14Z

JAXB team would like to announce availability of the JAXB RI 2.2
[1] (see changelog [2]). The release contains updated version of JAXB api implementation
with few improvements targeted mostly for JAX-WS 2.2 integration.

If you want to work with the new JAXB api version on JDK 6 which itself contains older JAXB
implementation, make sure you follow the endorsed dir setup as described in [4].

As usual, if you have any thoughts or comments, please post them to
users@.... For bug reports and feature enhancement
requests, please use IssueTracker [3].

[1] https://jaxb.dev.java.net/2.2/
[2] https://jaxb.dev.java.net/nonav/2.2/docs/changelog2.html
[3] https://jaxb.dev.java.net/issues/
[4] https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html#Using_JAXB_2_1_or_JAXB_2_2_with_JavaSE_6
--
Martin Grebac
Sun Microsystems martin.grebac@...

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

From forum: java.net - jaxb users

JAXB 2.2 is released

2009-12-11T05:47:14Z

JAXB team would like to announce availability of the JAXB RI 2.2
[1] (see changelog [2]). The release contains updated version of JAXB api implementation
with few improvements targeted mostly for JAX-WS 2.2 integration.

If you want to work with the new JAXB api version on JDK 6 which itself contains older JAXB
implementation, make sure you follow the endorsed dir setup as described in [4].

As usual, if you have any thoughts or comments, please post them to
users@.... For bug reports and feature enhancement
requests, please use IssueTracker [3].

[1] https://jaxb.dev.java.net/2.2/
[2] https://jaxb.dev.java.net/nonav/2.2/docs/changelog2.html
[3] https://jaxb.dev.java.net/issues/
[4] https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html#Using_JAXB_2_1_or_JAXB_2_2_with_JavaSE_6
--
Martin Grebac
Sun Microsystems martin.grebac@...

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

From forum: java.net - jaxb announce

Re: maven-jaxb2-plugin disappeared (again) ?

2009-12-11T03:13:58Z

Hi,

> There is no trace of
>
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin
>
> i.e. there is no 'jaxb2' dir in http://download.java.net/maven/2/org/jvnet/
>
> Last week it was there... any ideas what now ?

Hm...

Anyway, I've started triggered a build on Hudson, the artifact will be
uploaded within the next hour.

Bye,
/lexi

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

From forum: java.net - jaxb users

Re: maven-jaxb2-plugin disappeared (again) ?

2009-12-11T02:50:42Z

Hi,
this might have been caused by the javanet outage. Stay tuned, we'll
investigate. Sorry about the inconvenience.
MartiNG

seko wrote:

> There is no trace of
>
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin
>
> i.e. there is no 'jaxb2' dir in http://download.java.net/maven/2/org/jvnet/
>
> Last week it was there... any ideas what now ?
> --
> Seko
>
>
>

--
Martin Grebac, http://blogs.sun.com/mgrebac

Web Technologies & Standards
Sun Microsystems Czech

ICQ: 93478885

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

From forum: java.net - jaxb users

maven-jaxb2-plugin disappeared (again) ?

2009-12-11T02:30:12Z

There is no trace of

org.jvnet.jaxb2.maven2:maven-jaxb2-plugin

i.e. there is no 'jaxb2' dir in http://download.java.net/maven/2/org/jvnet/

Last week it was there... any ideas what now ?
--
Seko

From forum: java.net - jaxb users

jaxb and webservice issue BARE ,Wrapped ,JAXB

2009-12-10T12:45:42Z

I have a webservice generated from a wsdl that has this:

@SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL,parameterStyle=SOAPBinding.ParameterStyle.WRAPPED)

But i want to create my own class that that uses JAXB to unmarshall the SOAP message (due to various reason)

Now the problem is that if i generate classes based on schema that the original wsdl has I end up with like I would have a ParameterStyle.BARE web service....and it does NOT work to unmarshal using jaxb :((
because of namespace related issues.

How can i specify to jaxb to generate classes takeing into consideration that i hava a WRapped style soap messgae not BARE...???

THANK YOU !!!

From forum: java.net - jaxb users

Re: ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10

2009-12-10T12:21:05Z

Great. FYI, this has triggered issue 726, which helps to improve JAXB code.
Thanks.
-W

On Thu, Dec 10, 2009 at 5:29 PM, KARR, DAVID (ATTCINW) <dk068x@...> wrote:

> -----Original Message-----
> From: KARR, DAVID (ATTCINW)
> Sent: Wednesday, December 09, 2009 2:45 PM
> To: users@...

> Subject: ClassCastException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10
>
> I'm running WebLogic 10MP1. I'm constructing an application that uses
> CXF, which uses jaxb-api-2.1.jar and jaxb-impl-2.1.12.jar.
>
> After I put those jars into WEB-INF/lib and restarted, I got the
> following:
>
> java.lang.ClassCastException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl
> at
> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:150)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
> at
>
org.apache.cxf.wsdl.JAXBExtensionHelper.createJAXBContext(JAXBExtension
> H
> elper.java:196)
>
> I'm using "prefer-web-inf-classes" in weblogic.xml and
> "prefer-application-packages" in weblogic-application.xml (specifying
> "javax.wsdl.*" and "com.sun.xml.bind.v2.*").

It appears that after I constructed an EAR for this project, put my jars
into the EAR, and set "prefer-application-packages", I stopped getting
this error.

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

From forum: java.net - jaxb users

RE: ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10

2009-12-10T08:29:47Z

> -----Original Message-----
> From: KARR, DAVID (ATTCINW)
> Sent: Wednesday, December 09, 2009 2:45 PM
> To: users@...
> Subject: ClassCastException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10
>
> I'm running WebLogic 10MP1. I'm constructing an application that uses
> CXF, which uses jaxb-api-2.1.jar and jaxb-impl-2.1.12.jar.
>
> After I put those jars into WEB-INF/lib and restarted, I got the
> following:
>
> java.lang.ClassCastException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl
> at
> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:150)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
> at
>

org.apache.cxf.wsdl.JAXBExtensionHelper.createJAXBContext(JAXBExtension
> H
> elper.java:196)
>
> I'm using "prefer-web-inf-classes" in weblogic.xml and
> "prefer-application-packages" in weblogic-application.xml (specifying
> "javax.wsdl.*" and "com.sun.xml.bind.v2.*").

It appears that after I constructed an EAR for this project, put my jars
into the EAR, and set "prefer-application-packages", I stopped getting
this error.

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

From forum: java.net - jaxb users

RE: Re: Compute xs:any and xs:attribute

2009-12-10T07:53:24Z

Hi
Thanks

What I mean was to separate xs:any and xs:attribute from the document with the namespaces defining them.

An example is:

<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:ou="urn:oma:xml:xdm:resource-list:oma-uriusage"
        xmlns:oxe="urn:oma:xml:xdm:extensions" xmlns:oga="urn:oma:xml:poc:group-advertisement" xmlns:opu="urn:oma:xml:poc:oma-pocusage"
        xmlns:oiu="urn:oma:xml:im:oma-imusage">
        <list name="bookmarkedGroups">
                <entry uri="sip:group1_joebloggs@...">
                        <display-name>Joe Bloggs’s golf team</display-name>
                        <ou:uriusages>
                                <oxe:common-usage id="a1">
                                        <oga:group-advertisement>
                                                <oga:note>This group will meet next week</oga:note>
                                                <oga:group type="dialed-in">
                                                        <oga:display-name>Joe Bloggs’s golf team</oga:display-name>
                                                        <oga:uri>sip:group1_joebloggs@...</oga:uri>
                                                        <oxe:group-media>
                                                                <oxe:all-media-except>
                                                                        <oxe:file-transfer />
                                                                </oxe:all-media-except>
                                                        </oxe:group-media>
                                                        <oxe:supported-services>
                                                                <oxe:service enabler="poc" />
                                                                <oxe:service enabler="im" />
                                                        </oxe:supported-services>
                                                </oga:group>
                                        </oga:group-advertisement>
                                </oxe:common-usage>
                                <opu:pocusage>chat</opu:pocusage>
                                <oiu:imusage>chat</oiu:imusage>
                        </ou:uriusages>
                </entry>
                <entry uri="sip:group1_bob@...">
                        <display-name>Bob’s ski friends</display-name>
                        <ou:uriusages>
                                <opu:pocusage>prearranged</opu:pocusage>
                        </ou:uriusages>
                </entry>
        </list>
</resource-lists>

The red part is not defined by the default namespace (urn:ietf:params:xml:ns:resource-lists).

If I separate this document I get one document which is defined by a known namespace:

<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" >
        <list name="bookmarkedGroups">
                <entry uri="sip:group1_joebloggs@...">
                        <display-name>Joe Bloggs’s golf team</display-name>
                </entry>
                <entry uri="sip:group1_bob@...">
                        <display-name>Bob’s ski friends</display-name>
                </entry>
        </list>
</resource-lists>

The red parts will be computed as follows with the name spaces defining it:

This document will be saved in a structured way. (Relational database)

<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:ou="urn:oma:xml:xdm:resource-list:oma-uriusage"
        xmlns:oxe="urn:oma:xml:xdm:extensions" xmlns:oga="urn:oma:xml:poc:group-advertisement" xmlns:opu="urn:oma:xml:poc:oma-pocusage"
        xmlns:oiu="urn:oma:xml:im:oma-imusage">
<ou:uriusages>
    <oxe:common-usage id="a1">
        <oga:group-advertisement>
             <oga:note>This group will meet next week</oga:note>
             <oga:group type="dialed-in">
                 <oga:display-name>Joe Bloggs’s golf team</oga:display-name>
                 <oga:uri>sip:group1_joebloggs@...</oga:uri>
                 <oxe:group-media>
                     <oxe:all-media-except>
                         <oxe:file-transfer />
                     </oxe:all-media-except>
                 </oxe:group-media>
                 <oxe:supported-services>
                     <oxe:service enabler="poc" />
                     <oxe:service enabler="im" />
                 </oxe:supported-services>
             </oga:group>
        </oga:group-advertisement>
    </oxe:common-usage>
    <opu:pocusage>chat</opu:pocusage>
    <oiu:imusage>chat</oiu:imusage>
</ou:uriusages>
</resource-lists>

<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:ou="urn:oma:xml:xdm:resource-list:oma-uriusage">
<ou:uriusages>
<opu:pocusage>prearranged</opu:pocusage>

</ou:uriusages>

</resource-lists>

These two documents will be saved in a database as CLOB/BLOB.

When returning the whole document, all these fragments will be put togther by my application.

But my problem is how to compute/separate, put the name spaces needed for these 2 documents.

Lulseged

-----Original Message-----
From: aleksei.valikov@... [aleksei.valikov@...] On Behalf Of Aleksei Valikov
Sent: den 10 december 2009 16:02
To: users@...
Subject: Re: Compute xs:any and xs:attribute

Hi,

> I am saving xml documents structured in a relational database. But it
> will not work if the schema defining the xml document contains xs:any
> or xs:anyAttribute.
>
> Is there anyway where I can compute xs:any or xs:attribute and its
> namespace separatly?

What do you mean by "compute separately"?

> I am not going to parse these xs:any or xs:attribute in my application
> but need to return back when asked by an external application which
> created these xs:any and xs:attribute types.

Well, you have to store them somewhere. Consider storing @XmlAnyElement as BLOB/CLOB in the database and @XmlAnyAttribute as string/string map.

> This will help me to save the xs:any or xs:attribute types as they
> are together with the namespaces defined in a model and the rest of
> the xml document will be modeled i a relational database.

ps. Are you aware of Hyperjaxb3?
See http://confluence.highsource.org/display/HJ3/Home

Bye.
/lexi

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

From forum: java.net - jaxb users

Re: Compute xs:any and xs:attribute

2009-12-10T07:02:21Z

Hi,

> I am saving xml documents structured in a relational database. But it will
> not work if the schema defining the xml document contains xs:any or
> xs:anyAttribute.
>
> Is there anyway where I can compute xs:any or xs:attribute and its
> namespace separatly?

What do you mean by "compute separately"?

> I am not going to parse these xs:any or xs:attribute in
> my application but need to return back when asked by an external application
> which created these xs:any and xs:attribute types.

Well, you have to store them somewhere. Consider storing
@XmlAnyElement as BLOB/CLOB in the database and @XmlAnyAttribute as
string/string map.

> This will help me to save the xs:any or xs:attribute types as they are
> together with the namespaces defined in a model and the rest of the xml
> document will be modeled i a relational database.

ps. Are you aware of Hyperjaxb3?
See http://confluence.highsource.org/display/HJ3/Home

Bye.
/lexi

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

From forum: java.net - jaxb users

Re: Generate from schemas which resides within jars?

2009-12-10T06:47:43Z

Hi,

> Is it possible to have JAXB2 generate code from schemas when they are within
> a jar which is on the classpath - or do I have to point to the actual files?

XJC loads schemas via URL, so you can use JAR URL
(jar:file:/c:/almanac/my.jar!/com/acme/foo.xsd) to point to your
schema. You can also use catalog file to remap "public URL" like
http://www.acme.com/foo.xsd onto "system URL" like JAR URL mentioned
above or even use an own catalog resolver.
You can find few hints here:

https://maven-jaxb2-plugin.dev.java.net/docs/guide.html

Bye.
/lexi

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

From forum: java.net - jaxb users

Compute xs:any and xs:attribute

2009-12-10T06:43:47Z

Compute xs:any and xs:attribute

I am saving xml documents structured in a relational database. But it will not work if the schema defining the xml document contains xs:any or xs:anyAttribute.

Is there anyway where I can compute xs:any or xs:attribute and its namespace separatly? I am not going to parse these xs:any or xs:attribute in my application but need to return back when asked by an external application which created these xs:any and xs:attribute types.

This will help me to save the xs:any or xs:attribute types as they are together with the namespaces defined in a model and the rest of the xml document will be modeled i a relational database.

Lulseged

From forum: java.net - jaxb users

Generate from schemas which resides within jars?

2009-12-10T06:31:09Z

Hi.

Is it possible to have JAXB2 generate code from schemas when they are
within a jar which is on the classpath - or do I have to point to the
actual files?

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

From forum: java.net - jaxb users

Re: ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10

2009-12-10T04:51:03Z

Weblogic has an older version of JAXB embedded in it. Can't tell you which version because I'm away from work.

Rico

From: Wolfgang Laun <wolfgang.laun@...>
To: users@...
Sent: Thu, December 10, 2009 6:14:20 AM
Subject: Re: ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10

This stack trace line
at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
doesn't match the source from JAXB 2.1.12.

Are you sure that there is no other jaxb-api.jar anywhere in the class path?

What jdk version are you using?

-W

On Wed, Dec 9, 2009 at 11:45 PM, KARR, DAVID (ATTCINW) <dk068x@...> wrote:

I'm running WebLogic 10MP1. I'm constructing an application that uses
CXF, which uses jaxb-api-2.1.jar and jaxb-impl-2.1.12.jar.

After I put those jars into WEB-INF/lib and restarted, I got the
following:

java.lang.ClassCastException:
com.sun.xml.bind.v2.runtime.JAXBContextImpl
at
javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:150)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
at
org.apache.cxf.wsdl.JAXBExtensionHelper.createJAXBContext(JAXBExtensionH
elper.java:196)

I'm using "prefer-web-inf-classes" in weblogic.xml and
"prefer-application-packages" in weblogic-application.xml (specifying
"javax.wsdl.*" and "com.sun.xml.bind.v2.*").

In my searches, I've found other people who have run into this in
WebLogic and other servers, but I haven't found anyone who's resolved
this problem.

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

From forum: java.net - jaxb users

Re: ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10

2009-12-10T04:14:20Z

This stack trace line
at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
doesn't match the source from JAXB 2.1.12.

Are you sure that there is no other jaxb-api.jar anywhere in the class path?

What jdk version are you using?

-W

On Wed, Dec 9, 2009 at 11:45 PM, KARR, DAVID (ATTCINW) <dk068x@...> wrote:

I'm running WebLogic 10MP1. I'm constructing an application that uses
CXF, which uses jaxb-api-2.1.jar and jaxb-impl-2.1.12.jar.

After I put those jars into WEB-INF/lib and restarted, I got the
following:

java.lang.ClassCastException:
com.sun.xml.bind.v2.runtime.JAXBContextImpl
at
javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:150)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
at
org.apache.cxf.wsdl.JAXBExtensionHelper.createJAXBContext(JAXBExtensionH
elper.java:196)

I'm using "prefer-web-inf-classes" in weblogic.xml and
"prefer-application-packages" in weblogic-application.xml (specifying
"javax.wsdl.*" and "com.sun.xml.bind.v2.*").

In my searches, I've found other people who have run into this in
WebLogic and other servers, but I haven't found anyone who's resolved
this problem.

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

From forum: java.net - jaxb users

ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl in WebLogic 10

2009-12-09T14:45:28Z

I'm running WebLogic 10MP1. I'm constructing an application that uses
CXF, which uses jaxb-api-2.1.jar and jaxb-impl-2.1.12.jar.

After I put those jars into WEB-INF/lib and restarted, I got the
following:

java.lang.ClassCastException:
com.sun.xml.bind.v2.runtime.JAXBContextImpl
at
javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:150)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
at
org.apache.cxf.wsdl.JAXBExtensionHelper.createJAXBContext(JAXBExtensionH
elper.java:196)

I'm using "prefer-web-inf-classes" in weblogic.xml and
"prefer-application-packages" in weblogic-application.xml (specifying
"javax.wsdl.*" and "com.sun.xml.bind.v2.*").

In my searches, I've found other people who have run into this in
WebLogic and other servers, but I haven't found anyone who's resolved
this problem.

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

From forum: java.net - jaxb users

Re: error "Type mismatch: cannot convert from XmlAccessType to AccessType"

2009-12-09T04:20:21Z

Thank you very much!!!

Though I am not exactly sure your meaning(not your problem but my own poor knowledge of jaxb),but I check out a new version of jaxb-api.jar, and replace the old one,it works, the problem is resolved now.

Thanks!!!!!

2009/12/9 Wolfgang Laun <wolfgang.laun@...>

On Wed, Dec 9, 2009 at 12:32 PM, maven apache <apachemaven0@...> wrote:

2009/12/9 Wolfgang Laun <wolfgang.laun@...>
You are running JAXB runtime bundled with JDK 6 against JAva sources compiled with
a much older JAXB's schema compiler xjc.

Sorry ,because I am not  familiar with jaxb( I used to work with xmlbeans..), so do you mean my jdk version should be lower?

Because this is a third-part project, I do not have the schema. So I do not know which xjc they use.
In fact , not matter I use 1.5 or 1.6 ,the problem exists still.

This is revealing because JDK 1.5 came without JAXB support. This means that somewhere you have
very old jaxb runtime jars containing the obsolete annotation class AccessType.

Stick with JDK 1.6.

I suggest you locate all jars (wherever they might be, referred to from Eclipse) and run
   jar -tf jaxb-api.jar | grep AccessType
If this doesn't show
   javax/xml/bind/annotation/XmlAccessType.class
but
   javax/xml/bind/annotation/AccessType.class
then throw it (and all others near it!) away.

PPS: Screenshots are nice, but the important info is hidden, i.e., the comment header
of the generated Java source.

The header is here: http://imagebin.org/74721

Ugh, the timestamp is from June 2005, which is a liability. You'll just have to hope that
the code generated then doesn't contain any snags. Alert the "third party" to the
pending risk.

If you don't have the schema (which is the usual way of communicating an XML interface,
NOT the Java classes that were generated in some setup), you should try and get it, or else
hope that it hasn't changed since.

Cheers
-W

From forum: java.net - jaxb users