You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2009/12/14 14:43:51 UTC
wsdlLocation management (and also a Question for Sergey)
I've got a webapp with a CXF service. When I'm doing development, I'm
fine with the usual default wsdlLocation. However, when I deploy,
there's a firewall.
Customizing the Spring app context and rebuilding the webapp is not an
attractive prospect. Has anyone come up with a scheme so that a
servlet parameter from web.xml can be provided to override, but things
still work if it's not there?
(Sergey, is there an equivalent set of issues for WADL?)
Re: wsdlLocation management (and also a Question for Sergey)
Posted by Benson Margulies <bi...@gmail.com>.
CXF has the the basic feature, the question is just to come up with a
clean way to configure it.
On Mon, Dec 14, 2009 at 9:00 AM, Alexandros Karypidis <ak...@yahoo.gr> wrote:
> Benson Margulies wrote:
>>
>> I've got a webapp with a CXF service. When I'm doing development, I'm
>> fine with the usual default wsdlLocation. However, when I deploy,
>> there's a firewall.
>>
>> Customizing the Spring app context and rebuilding the webapp is not an
>> attractive prospect. Has anyone come up with a scheme so that a
>> servlet parameter from web.xml can be provided to override, but things
>> still work if it's not there?
>>
>> (Sergey, is there an equivalent set of issues for WADL?)
>>
>
> WebLogic provides such a feature in "deployment plans" but it's not a
> J2EE-spec thing so...
>
> JBoss has a global setting on whether to re-write URLs or not. You could
> have it on when developing and off on the production server: if you have the
> production URL in your WSDL it will get replaced when developing, but not in
> production.
>
> I you want something cross-platform, I'm afraid you'll have to "roll your
> own", but maybe someone else knows of another way...
>
>
>
Re: wsdlLocation management (and also a Question for Sergey)
Posted by Alexandros Karypidis <ak...@yahoo.gr>.
Benson Margulies wrote:
> I've got a webapp with a CXF service. When I'm doing development, I'm
> fine with the usual default wsdlLocation. However, when I deploy,
> there's a firewall.
>
> Customizing the Spring app context and rebuilding the webapp is not an
> attractive prospect. Has anyone come up with a scheme so that a
> servlet parameter from web.xml can be provided to override, but things
> still work if it's not there?
>
> (Sergey, is there an equivalent set of issues for WADL?)
>
WebLogic provides such a feature in "deployment plans" but it's not a
J2EE-spec thing so...
JBoss has a global setting on whether to re-write URLs or not. You could
have it on when developing and off on the production server: if you have
the production URL in your WSDL it will get replaced when developing,
but not in production.
I you want something cross-platform, I'm afraid you'll have to "roll
your own", but maybe someone else knows of another way...
Re: wsdlLocation management (and also a Question for Sergey)
Posted by Daniel Kulp <dk...@apache.org>.
On Mon December 14 2009 8:43:51 am Benson Margulies wrote:
> I've got a webapp with a CXF service. When I'm doing development, I'm
> fine with the usual default wsdlLocation. However, when I deploy,
> there's a firewall.
Have you looked into the PropertyPlaceholderConfigurer things in Spring?
You should be able to have a properties file to define the wsdlLocation with a
separate one for deploy than for development. I think.
I think catalogs can also be used for this.
Dan
>
> Customizing the Spring app context and rebuilding the webapp is not an
> attractive prospect. Has anyone come up with a scheme so that a
> servlet parameter from web.xml can be provided to override, but things
> still work if it's not there?
>
> (Sergey, is there an equivalent set of issues for WADL?)
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog