You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Agustin Barto <ab...@gmail.com> on 2009/08/12 20:58:29 UTC
Question about namespaces ending in "v1.0"
I'm generating the server code for a WSDL which namespace ends with a
version number "http://foo.bar.com/service/v1.0", and the generated
java package is com.bar.foo.service.v1. The service refers to types
defined on the namespace "http://foo.bar.com/service/v1.0/types" and
the generated package for those is com.bar.foo.service.v1_0.types.
Is this the expected behavior? Shouldn't the service package also end
with v1_0 ?
Aside from explicitly supplying the package, is there a way to solve this?
Agustin
Re: Question about namespaces ending in "v1.0"
Posted by Daniel Kulp <dk...@apache.org>.
I've fixed this on trunk (2.3), but I'm reluctant to back port this as its
definitely and incompatible change as code that would have previously compiled
would no longer compile and such.
Anyway, this will be "fixed" in 2.3.
Dan
On Thu August 13 2009 3:45:15 pm Agustin Barto wrote:
> On Wed, Aug 12, 2009 at 6:21 PM, Daniel Kulp<dk...@apache.org> wrote:
> > Actually, I would call that bug. Can you log an issue?
> >
> > It kind of gets worse. If you have a namespace of v1.1, it ALSO would
> > just map to v1. Thus, two namespaces mapping to the same place. Not
> > good.
> >
> > That said, the RI does the same thing. I'm not seeing anything in the
> > JAX- WS spec that would call for this though. I'll need to dig in some
> > more tomorrow, but I definitely think I'd consider this a bug.
> >
> >
> > Dan
>
> I've created issue CXF-2392.
>
> Agustin
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Question about namespaces ending in "v1.0"
Posted by Agustin Barto <ab...@gmail.com>.
On Wed, Aug 12, 2009 at 6:21 PM, Daniel Kulp<dk...@apache.org> wrote:
>
> Actually, I would call that bug. Can you log an issue?
>
> It kind of gets worse. If you have a namespace of v1.1, it ALSO would just
> map to v1. Thus, two namespaces mapping to the same place. Not good.
>
> That said, the RI does the same thing. I'm not seeing anything in the JAX-
> WS spec that would call for this though. I'll need to dig in some more
> tomorrow, but I definitely think I'd consider this a bug.
>
>
> Dan
I've created issue CXF-2392.
Agustin
Re: Question about namespaces ending in "v1.0"
Posted by Daniel Kulp <dk...@apache.org>.
Actually, I would call that bug. Can you log an issue?
It kind of gets worse. If you have a namespace of v1.1, it ALSO would just
map to v1. Thus, two namespaces mapping to the same place. Not good.
That said, the RI does the same thing. I'm not seeing anything in the JAX-
WS spec that would call for this though. I'll need to dig in some more
tomorrow, but I definitely think I'd consider this a bug.
Dan
On Wed August 12 2009 2:58:29 pm Agustin Barto wrote:
> I'm generating the server code for a WSDL which namespace ends with a
> version number "http://foo.bar.com/service/v1.0", and the generated
> java package is com.bar.foo.service.v1. The service refers to types
> defined on the namespace "http://foo.bar.com/service/v1.0/types" and
> the generated package for those is com.bar.foo.service.v1_0.types.
>
> Is this the expected behavior? Shouldn't the service package also end
> with v1_0 ?
>
> Aside from explicitly supplying the package, is there a way to solve this?
>
> Agustin
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog