You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by ggsoft <gg...@gmx.net> on 2010/07/28 14:21:44 UTC
Jaxws Versioning Problem
Hi all,
today i was thrown into the exact same problem as i found described
by Goran on this mailing list.
Is there any solution to this?
Regards
ggsoft
Hi,
I want to add a minor version update with backward compatibility (add
service method) to a existing web service build with cxf.
What I have done so far is all the steps proposed in this paper
http://blogs.iona.com/sos/20070410-WSDL-Versioning-Best-Practise.pdf.
Additionally, I've added second implementation of the web service. In the
cxf-servlet.xml file, I've modified the endpoint element
to the new version of the service running on the same address.
<jaxws:endpoint id="Service-v1d1" implementor="#serviceV1d1Ws"
wsdlLocation="Service-v1.wsdl" address="/service/1">
<jaxws:properties>
<entry key="schema-validation-enabled" value="true" />
</jaxws:properties>
<jaxws:inInterceptors>
<ref bean="accessControlInterceptor" />
<ref bean="logInboundInterceptor"/>
</jaxws:inInterceptors>
<jaxws:outInterceptors>
<ref bean="logOutboundInterceptor"/>
</jaxws:outInterceptors>
</jaxws:endpoint>
Now, for the issue I encountered:
1. when I try to call the web service from a client with the 1.0
implementation, the client is throwing an java.net.MalformedURLException
because the soap address for the 1.0 version is still 'service/1' and not
a fully functional address like it is for 1.1 -
http://localhost:8081/web-service/service/1.
This is what I see in browser for the service definitions in the wsdl:
<wsdl:service name="Service_v1_0">
<wsdl:port binding="tns:Service_v1_0_SoapBinding" name="Service">
<soap:address location="service/1"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="Service_v1_1">
<wsdl:port binding="tns:Service_v1_1_SoapBinding" name="Service">
<soap:address location="http://localhost:8081/web-service/service/1"/>
</wsdl:port>
</wsdl:service>
I don't see why the soap address isn't generated for both versions of the
service. Any help will be appreciated. Thanks.
--
Netcetera goes mobile - travel in and around Zürich with our free iPhone
application Wemlin:
http://mobile.netcetera.ch/wemlin
Goran Cvetkoski | [hidden email]
<http://cxf.547215.n5.nabble.com/user/SendEmail.jtp?type=node&node=567100&i=0>
phone +389 -2- 30 64 532 | fax +389 -2- 30 79 495
Netcetera | 1000 Skopje | Macedonia | http://netcetera.com.mk
<http://netcetera.com.mk?by-user=t>
RE: Version 2.2.10 scehdule?
Posted by Gary Gregory <GG...@seagullsoftware.com>.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Monday, August 16, 2010 11:10
> To: users@cxf.apache.org
> Cc: Gary Gregory
> Subject: Re: Version 2.2.10 scehdule?
>
> On Monday 16 August 2010 1:57:33 pm Gary Gregory wrote:
> > > -----Original Message-----
> > > From: Daniel Kulp [mailto:dkulp@apache.org]
> > > Sent: Wednesday, August 11, 2010 12:23
> > > To: users@cxf.apache.org
> > > Cc: Gary Gregory
> > > Subject: Re: Version 2.2.10 scehdule?
> > >
> > > On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote:
> > > > Hi All,
> > > >
> > > > We are currently using a 2.2.10 snapshot build to address two bugs.
> > > >
> > > > Is there a schedule for a 2.2.10 release?
> > >
> > > Whenever I get some time to do it. I meant to do it yesterday, but have
> > > been pulled every which direction the last couple days and just haven't
> > > had enough time to devote to doing it. :-(
> > >
> > > Hopefully real soon.
> >
> > Ping?
> > ;)
>
> It's "released", but not synced to all the mirrors and such yet so I haven't
> announced it. Looks like it's already at central though:
>
> http://repo2.maven.org/maven2/org/apache/cxf/apache-cxf/2.2.10/
>
Great, thank you Dan.
Gary
>
>
> Dan
>
>
>
> > G
> >
> > > Dan
> > >
> > > > Gary Gregory
> > > > Senior Software Engineer
> > > > Seagull Software
> > > > email: ggregory@seagullsoftware.com
> > > > email: ggregory@apache.org
> > > > www.seagullsoftware.com
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org
> > > http://dankulp.com/blog
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
Re: Version 2.2.10 scehdule?
Posted by Daniel Kulp <dk...@apache.org>.
On Monday 16 August 2010 1:57:33 pm Gary Gregory wrote:
> > -----Original Message-----
> > From: Daniel Kulp [mailto:dkulp@apache.org]
> > Sent: Wednesday, August 11, 2010 12:23
> > To: users@cxf.apache.org
> > Cc: Gary Gregory
> > Subject: Re: Version 2.2.10 scehdule?
> >
> > On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote:
> > > Hi All,
> > >
> > > We are currently using a 2.2.10 snapshot build to address two bugs.
> > >
> > > Is there a schedule for a 2.2.10 release?
> >
> > Whenever I get some time to do it. I meant to do it yesterday, but have
> > been pulled every which direction the last couple days and just haven't
> > had enough time to devote to doing it. :-(
> >
> > Hopefully real soon.
>
> Ping?
> ;)
It's "released", but not synced to all the mirrors and such yet so I haven't
announced it. Looks like it's already at central though:
http://repo2.maven.org/maven2/org/apache/cxf/apache-cxf/2.2.10/
Dan
> G
>
> > Dan
> >
> > > Gary Gregory
> > > Senior Software Engineer
> > > Seagull Software
> > > email: ggregory@seagullsoftware.com
> > > email: ggregory@apache.org
> > > www.seagullsoftware.com
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://dankulp.com/blog
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
RE: Version 2.2.10 scehdule?
Posted by Gary Gregory <GG...@seagullsoftware.com>.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, August 11, 2010 12:23
> To: users@cxf.apache.org
> Cc: Gary Gregory
> Subject: Re: Version 2.2.10 scehdule?
>
> On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote:
> > Hi All,
> >
> > We are currently using a 2.2.10 snapshot build to address two bugs.
> >
> > Is there a schedule for a 2.2.10 release?
>
> Whenever I get some time to do it. I meant to do it yesterday, but have been
> pulled every which direction the last couple days and just haven't had enough
> time to devote to doing it. :-(
I know the feeling!
Thanks for the update.
Gary
>
> Hopefully real soon.
>
> Dan
>
>
> >
> > Gary Gregory
> > Senior Software Engineer
> > Seagull Software
> > email: ggregory@seagullsoftware.com
> > email: ggregory@apache.org
> > www.seagullsoftware.com
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
RE: Version 2.2.10 scehdule?
Posted by Gary Gregory <GG...@seagullsoftware.com>.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, August 11, 2010 12:23
> To: users@cxf.apache.org
> Cc: Gary Gregory
> Subject: Re: Version 2.2.10 scehdule?
>
> On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote:
> > Hi All,
> >
> > We are currently using a 2.2.10 snapshot build to address two bugs.
> >
> > Is there a schedule for a 2.2.10 release?
>
> Whenever I get some time to do it. I meant to do it yesterday, but have been
> pulled every which direction the last couple days and just haven't had enough
> time to devote to doing it. :-(
>
> Hopefully real soon.
Ping?
;)
G
>
> Dan
>
>
> >
> > Gary Gregory
> > Senior Software Engineer
> > Seagull Software
> > email: ggregory@seagullsoftware.com
> > email: ggregory@apache.org
> > www.seagullsoftware.com
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
Re: Version 2.2.10 scehdule?
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 11 August 2010 3:21:22 pm Gary Gregory wrote:
> Hi All,
>
> We are currently using a 2.2.10 snapshot build to address two bugs.
>
> Is there a schedule for a 2.2.10 release?
Whenever I get some time to do it. I meant to do it yesterday, but have been
pulled every which direction the last couple days and just haven't had enough
time to devote to doing it. :-(
Hopefully real soon.
Dan
>
> Gary Gregory
> Senior Software Engineer
> Seagull Software
> email: ggregory@seagullsoftware.com
> email: ggregory@apache.org
> www.seagullsoftware.com
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Version 2.2.10 scehdule?
Posted by Gary Gregory <GG...@seagullsoftware.com>.
Hi All,
We are currently using a 2.2.10 snapshot build to address two bugs.
Is there a schedule for a 2.2.10 release?
Gary Gregory
Senior Software Engineer
Seagull Software
email: ggregory@seagullsoftware.com
email: ggregory@apache.org
www.seagullsoftware.com
Re: Jaxws Versioning Problem
Posted by Daniel Kulp <dk...@apache.org>.
On Monday 09 August 2010 4:41:49 am ggsoft wrote:
> Does anyone have an answer to this?
Honestly, I've never read that paper. However, from CXF's perspective, if
you don't call an Endpoint.publish (or have an jaxws:endpoint) with the
appropriate Service/Port, it really won't have a URL or anything to inject
into that port in the wsdl and it would leave it alone.
Dan
> Am 28.07.2010 14:21, schrieb ggsoft:
> > Hi all,
> >
> > today i was thrown into the exact same problem as i found described
> > by Goran on this mailing list.
> > Is there any solution to this?
> >
> > Regards
> > ggsoft
> > Hi,
> >
> > I want to add a minor version update with backward compatibility (add
> > service method) to a existing web service build with cxf.
> >
> > What I have done so far is all the steps proposed in this paper
> > http://blogs.iona.com/sos/20070410-WSDL-Versioning-Best-Practise.pdf.
> > Additionally, I've added second implementation of the web service. In the
> > cxf-servlet.xml file, I've modified the endpoint element
> >
> > to the new version of the service running on the same address.
> >
> >
> > <jaxws:endpoint id="Service-v1d1" implementor="#serviceV1d1Ws"
> > wsdlLocation="Service-v1.wsdl" address="/service/1">
> > <jaxws:properties>
> > <entry key="schema-validation-enabled" value="true" />
> > </jaxws:properties>
> > <jaxws:inInterceptors>
> > <ref bean="accessControlInterceptor" />
> > <ref bean="logInboundInterceptor"/>
> > </jaxws:inInterceptors>
> > <jaxws:outInterceptors>
> > <ref bean="logOutboundInterceptor"/>
> > </jaxws:outInterceptors>
> > </jaxws:endpoint>
> >
> > Now, for the issue I encountered:
> >
> > 1. when I try to call the web service from a client with the 1.0
> > implementation, the client is throwing an java.net.MalformedURLException
> > because the soap address for the 1.0 version is still 'service/1' and not
> > a fully functional address like it is for 1.1 -
> > http://localhost:8081/web-service/service/1.
> > This is what I see in browser for the service definitions in the wsdl:
> >
> > <wsdl:service name="Service_v1_0">
> > <wsdl:port binding="tns:Service_v1_0_SoapBinding" name="Service">
> > <soap:address location="service/1"/>
> > </wsdl:port>
> > </wsdl:service>
> >
> > <wsdl:service name="Service_v1_1">
> > <wsdl:port binding="tns:Service_v1_1_SoapBinding" name="Service">
> > <soap:address location="http://localhost:8081/web-service/service/1"/>
> > </wsdl:port>
> > </wsdl:service>
> >
> > I don't see why the soap address isn't generated for both versions of the
> > service. Any help will be appreciated. Thanks.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Jaxws Versioning Problem
Posted by ggsoft <gg...@gmx.net>.
Does anyone have an answer to this?
Am 28.07.2010 14:21, schrieb ggsoft:
>
> Hi all,
>
> today i was thrown into the exact same problem as i found described
> by Goran on this mailing list.
> Is there any solution to this?
>
> Regards
> ggsoft
> Hi,
>
> I want to add a minor version update with backward compatibility (add
> service method) to a existing web service build with cxf.
>
> What I have done so far is all the steps proposed in this paper
> http://blogs.iona.com/sos/20070410-WSDL-Versioning-Best-Practise.pdf.
> Additionally, I've added second implementation of the web service. In the
> cxf-servlet.xml file, I've modified the endpoint element
>
> to the new version of the service running on the same address.
>
>
> <jaxws:endpoint id="Service-v1d1" implementor="#serviceV1d1Ws"
> wsdlLocation="Service-v1.wsdl" address="/service/1">
> <jaxws:properties>
> <entry key="schema-validation-enabled" value="true" />
> </jaxws:properties>
> <jaxws:inInterceptors>
> <ref bean="accessControlInterceptor" />
> <ref bean="logInboundInterceptor"/>
> </jaxws:inInterceptors>
> <jaxws:outInterceptors>
> <ref bean="logOutboundInterceptor"/>
> </jaxws:outInterceptors>
> </jaxws:endpoint>
>
> Now, for the issue I encountered:
>
> 1. when I try to call the web service from a client with the 1.0
> implementation, the client is throwing an java.net.MalformedURLException
> because the soap address for the 1.0 version is still 'service/1' and not
> a fully functional address like it is for 1.1 -
> http://localhost:8081/web-service/service/1.
> This is what I see in browser for the service definitions in the wsdl:
>
> <wsdl:service name="Service_v1_0">
> <wsdl:port binding="tns:Service_v1_0_SoapBinding" name="Service">
> <soap:address location="service/1"/>
> </wsdl:port>
> </wsdl:service>
>
> <wsdl:service name="Service_v1_1">
> <wsdl:port binding="tns:Service_v1_1_SoapBinding" name="Service">
> <soap:address location="http://localhost:8081/web-service/service/1"/>
> </wsdl:port>
> </wsdl:service>
>
> I don't see why the soap address isn't generated for both versions of the
> service. Any help will be appreciated. Thanks.
>