Team, I recently noticed a problem perhaps related to Tom's[1] regarding the
schemaLocation value in a JAXB binding file[2]. CXF enumerates schemas
using Schema Component Descriptors (SCD's) within a WSDL differently from
Metro, resulting in JAXB binding files being incompatible between the two:
The one that doesn't pass the TCK? ;-)
Jeff
On Jul 14, 2010, at 11:56 AM, Glen Mazza wrote:
>
> Team, I recently noticed a problem perhaps related to Tom's[1] regarding the
> schemaLocation value in a JAXB binding file[2]. CXF enumerates schemas
> using Schema Component Descriptors (SCD's) w
But are the JAXB binding files that are passed into a wsdl2java tool part of
the TCK?
jgenender wrote:
>
> The one that doesn't pass the TCK? ;-)
>
> Jeff
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/Metro-vs-CXF-difference-in-enumerating-schemas-within-a-WSDL-tp10929
Hi all,
I have managed to create two sample OAuth aplications:
ordinary OAuth 1.0a client: http://www.oauthclient.appspot.com
and authorization server that uses CXF OAuth module:
http://www.cxfoauthserver.appspot.com
Both sample applications and changes in oauth library are commited in sandbox.
> Granted, the CXF dev list might not be the most unbiased of forums, but any
> idea which team is "wrong"?
Technically, neither.Nothing in the jax-ws spec that dictates how this is
supposed to be handled.
Not sure what else to say. :-(
Maybe something more like:
:-(
Dan
On Wedne
Actually, am I making a mistake? I thought those were SCD's but apparently
they're just simple XPath? I can't tell the difference.
SCD's are just an extension[1][2] of the JAXB RI, *not* part of the JAXB
specification--where you're supposed to be using XPath instead. However, if
you're using S
Umm, I think there's a solution here:
mybindingfile.xjb:
May I say that in all likelihood, the problem is that the XJC version used
by CXF's codegen plugin and the XJC version used by Metro's Maven plugin is
just different, and they interpret the schemaLocations in the JAXB bind
