That's not good ... we're still on xfire-1.0 because of this ...
-----Original Message-----
From: Sebastien Cesbron [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 2:36 AM
To: [email protected]
Subject: Re: [xfire-user] Any Workarounds for XFIRE-739: wsdl: doesn't
describe pojos in xsd ?
Sorry but it seems this is not fix in the last release (1.2.4) so we
cannot use JAXB2.0 annotations with xfire 1.2.4
Seb
On 12/18/06, Christopher Moesel <[EMAIL PROTECTED]> wrote:
Thanks Tom-- it's very much appreciated!
-Chris
-----Original Message-----
From: Tomek Sztelak [mailto:[EMAIL PROTECTED]
Sent: Monday, December 18, 2006 12:34 PM
To: [email protected]
Subject: Re: [xfire-user] Any Workarounds for XFIRE-739: wsdl:
doesn't
describe pojos in xsd ?
Hi
Hard to tell any particular date. I didn't look at this bug yet,
Dan
is out of country, but we will try to fix this before next
release,
which should be some time soon.
On 12/18/06, Ruth, Brice D <[EMAIL PROTECTED]> wrote:
>
>
> Ugh, looks like you might be right. Dan, Tom - any ETA on
this?
>
>
> -----Original Message-----
> From: Christopher Moesel [mailto:[EMAIL PROTECTED] ]
> Sent: Monday, December 18, 2006 10:44 AM
> To: [email protected]
> Subject: RE: [xfire-user] Any Workarounds for XFIRE-739: wsdl:
doesn't
> describe pojos in xsd ?
>
>
>
>
> The release notes for 1.2.3 list:
>
>
>
> - JAXB WSDL generation fix
>
>
>
> Looking through the resolved bugs for that release, I think
that the
release
> notes may have been referring to XFIRE-568: "JAXB 2.0 with
Annotations
> generates invalid schema imports". Unfortunately, that is a
completely
> different problem than XFIRE-739, which is still marked
unresolved in
the
> bug tracker.
>
>
>
> -Chris
>
>
>
> -----Original Message-----
> From: Ruth, Brice D [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 18, 2006 11:02 AM
> To: [email protected]
> Subject: RE: [xfire-user] Any Workarounds for XFIRE-739: wsdl:
doesn't
> describe pojos in xsd ?
>
>
>
>
> That's disturbing news. Dan or Tom - can you shed any light on
this? I
> remember from the 1.2.3 release notes that this was supposed
to have
been
> fixed.
>
>
>
>
>
> -Brice
>
>
>
>
> -----Original Message-----
> From: Christopher Moesel [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 18, 2006 8:53 AM
> To: [email protected]
> Subject: RE: [xfire-user] Any Workarounds for XFIRE-739: wsdl:
doesn't
> describe pojos in xsd ?
>
> I am using the 1.2.3 release (details below). I suspect it
didn't
make it
> into the release since the bug has not been closed out in the
tracker
(and
> since I'm still having problems!).
>
>
>
> I am using:
>
>
>
> Xfire-all-1.2.3
>
> Xfire-jsr181-api-1.0-M1
>
> Jaxb-api-2.0
>
> Jaxb-impl-2.0.1
>
> Jaxb-xjc-2.0.1
>
>
>
> Thanks,
>
> Chris
>
>
>
> -----Original Message-----
> From: Ruth, Brice D [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 18, 2006 9:37 AM
> To: [email protected]
> Subject: RE: [xfire-user] Any Workarounds for XFIRE-739: wsdl:
doesn't
> describe pojos in xsd ?
>
>
>
>
> Are you using 1.2.3? This was supposed to have been fixed in
the
latest
> release. I, too, have this problem, but hadn't yet been able
to test
the
> latest release.
>
>
>
>
>
> -Brice
>
>
>
>
> -----Original Message-----
> From: Christopher Moesel [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 18, 2006 7:41 AM
> To: [email protected]
> Subject: [xfire-user] Any Workarounds for XFIRE-739: wsdl:
doesn't
describe
> pojos in xsd ?
>
> I've recently attempted to change from Aegis to JAXB 2.0 for
my XML
binding.
> I am using a JSR181 code-first deployment. It appears,
however, that
the
> generated WSDL does not contain schema definitions for any of
my POJOs
(nor
> ArrayOfString). It looks like this is a known bug and has been
discussed on
> the list previously.
>
>
>
> http://jira.codehaus.org/browse/XFIRE-739
>
>
>
> Are there any known workarounds, or do I need to go back to
Aegis? Is
there
> an expected release that the bugfix will be a part of?
>
>
>
> Thanks, as always, for a great product! We certainly
appreciate all
of the
> hard work you put into this!
>
>
>
> -Chris
--
-----
When one of our products stops working, we'll blame another
vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
