You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Nicolas De Loof <ni...@capgemini.com> on 2006/01/26 08:56:26 UTC
alternative configuration to server-config.wsdd ?
Hello,
My webapp includes axis and a web service endpoint.
The deploy.wsdd is generated as part of the build process (as endpoint
interface is not yet stable), but it requires to manually update the
server-config.wsdd to include the deploy.wsdd content.
Using AdminClient to deploy is not a solution as the web service has to
be started with the webapp (axis configuration is static)
Is there any way to replace WEB-INF/server-config.wsdd based
configuration by a "programmable" configuration ? I'd like to extend
AxisServlet and automatically deploy my web service at application
startup from it's generated deploy.wsdd.
Nico.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: alternative configuration to server-config.wsdd ?
Posted by Nicolas De Loof <ni...@capgemini.com>.
Looks interesting, I'll try this.
Thanks !
Cyrille Le Clerc a écrit :
> Hello,
>
> Static deployment of web services in Axis is documented in the Wiki
>: http://wiki.apache.org/ws/FrontPage/Axis/StaticDeployment
>
> I personally like to statically deploy with Ant. It looks like this :
><java classname="org.apache.axis.utils.Admin"
> fork="true" dir="${webapp.install}/WEB-INF">
> <arg value="server" />
> <arg value="${webapp.install}/wsdd/deploy.wsdd" />
> <classpath>
> <pathelement location="${build.dir}/classes"/>
> <path refid="axis.classpath"/>
> </classpath>
></java>
>
> Hope this helps,
>
> Cyrille
>
>--
>Cyrille Le Clerc
>cyrille.leclerc@pobox.com
>cyrille.leclerc@fr.ibm.com
>
>On 1/26/06, Tony Ingraldi <ti...@echostorm.net> wrote:
>
>
>>Nicolas,
>>
>>Have you considered using org.apache.axis.utils.Admin? It can be
>>used to create a server-config.wsdd file from a deploy.wsdd file.
>>
>>i.e.
>>
>> java -cp $AXISCLASSPATH org.apache.axis.utils.Admin server deploy.wsdd
>>
>>
>>You may need to tweak the generated server-config.wsdd file, but the
>>tweaking could potentially be automated with your scripting language
>>of preference.
>>
>>
>>On Jan 26, 2006, at 2:56 AM, Nicolas De Loof wrote:
>>
>>
>>
>>>The deploy.wsdd is generated as part of the build process (as
>>>endpoint interface is not yet stable), but it requires to manually
>>>update the server-config.wsdd to include the deploy.wsdd content.
>>>Using AdminClient to deploy is not a solution as the web service
>>>has to be started with the webapp (axis configuration is static)
>>>
>>>Is there any way to replace WEB-INF/server-config.wsdd based
>>>configuration by a "programmable" configuration ? I'd like to
>>>extend AxisServlet and automatically deploy my web service at
>>>application startup from it's generated deploy.wsdd.
>>>
>>>
>>--
>> Tony Ingraldi
>> tingraldi@echostorm.net
>>
>>
>
>
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: alternative configuration to server-config.wsdd ?
Posted by Cyrille Le Clerc <cy...@pobox.com>.
Hello,
Static deployment of web services in Axis is documented in the Wiki
: http://wiki.apache.org/ws/FrontPage/Axis/StaticDeployment
I personally like to statically deploy with Ant. It looks like this :
<java classname="org.apache.axis.utils.Admin"
fork="true" dir="${webapp.install}/WEB-INF">
<arg value="server" />
<arg value="${webapp.install}/wsdd/deploy.wsdd" />
<classpath>
<pathelement location="${build.dir}/classes"/>
<path refid="axis.classpath"/>
</classpath>
</java>
Hope this helps,
Cyrille
--
Cyrille Le Clerc
cyrille.leclerc@pobox.com
cyrille.leclerc@fr.ibm.com
On 1/26/06, Tony Ingraldi <ti...@echostorm.net> wrote:
> Nicolas,
>
> Have you considered using org.apache.axis.utils.Admin? It can be
> used to create a server-config.wsdd file from a deploy.wsdd file.
>
> i.e.
>
> java -cp $AXISCLASSPATH org.apache.axis.utils.Admin server deploy.wsdd
>
>
> You may need to tweak the generated server-config.wsdd file, but the
> tweaking could potentially be automated with your scripting language
> of preference.
>
>
> On Jan 26, 2006, at 2:56 AM, Nicolas De Loof wrote:
>
> > The deploy.wsdd is generated as part of the build process (as
> > endpoint interface is not yet stable), but it requires to manually
> > update the server-config.wsdd to include the deploy.wsdd content.
> > Using AdminClient to deploy is not a solution as the web service
> > has to be started with the webapp (axis configuration is static)
> >
> > Is there any way to replace WEB-INF/server-config.wsdd based
> > configuration by a "programmable" configuration ? I'd like to
> > extend AxisServlet and automatically deploy my web service at
> > application startup from it's generated deploy.wsdd.
>
> --
> Tony Ingraldi
> tingraldi@echostorm.net
Re: alternative configuration to server-config.wsdd ?
Posted by Nicolas De Loof <ni...@capgemini.com>.
Interesting idea, I'll take a look at ant XSLT support.
Thanks a lot !
Daniel Beland a écrit :
>
>
> If you use maven (or ant), why don't you simply perform XSLT to
> integrate each deploy.wsdd in the server-config.wsdd.
>
> That's what I did in a war:webapp postGoal.
>
>
>
> On 1/26/06, *Nicolas De Loof* <nicolas.deloof@capgemini.com
> <ma...@capgemini.com>> wrote:
>
>
> I have to replace the className parameter in generated deploy.wsdd and
> add some custom typeMappings.
> Replacing className is easy, but adding typeMapping elements is more
> difficult in my ant (maven.xml) build script.
>
> I'm trying another solution :
>
> It extends AxisServlet and it's init method :
> It loads the (wsdl2java generated) deploy.wsdd, and uses WSDDService
> methods to replace className parameter, append typemappings
> defined in
> another xml file and deploy the service using
> "ServiceAdmin.deployService(wsddService);"
>
> This doesn't work exactly as expected but I'm working on it...
>
> Nico.
>
> Tony Ingraldi a écrit :
>
> > Nicolas,
> >
> > Have you considered using org.apache.axis.utils.Admin? It can be
> > used to create a server-config.wsdd file from a deploy.wsdd file.
> >
> > i.e.
> >
> > java -cp $AXISCLASSPATH org.apache.axis.utils.Admin server
> > deploy.wsdd
> >
> >
> > You may need to tweak the generated server-config.wsdd file, but the
> > tweaking could potentially be automated with your scripting
> language
> > of preference.
> >
> >
> > On Jan 26, 2006, at 2:56 AM, Nicolas De Loof wrote:
> >
> >> The deploy.wsdd is generated as part of the build process (as
> >> endpoint interface is not yet stable), but it requires to manually
> >> update the server-config.wsdd to include the deploy.wsdd content.
> >> Using AdminClient to deploy is not a solution as the web
> service has
> >> to be started with the webapp (axis configuration is static)
> >>
> >> Is there any way to replace WEB-INF/server-config.wsdd based
> >> configuration by a "programmable" configuration ? I'd like
> to extend
> >> AxisServlet and automatically deploy my web service
> at application
> >> startup from it's generated deploy.wsdd.
> >
> >
> > --
> > Tony Ingraldi
> > tingraldi@echostorm.net <ma...@echostorm.net>
> >
>
> This message contains information that may be privileged or
> confidential and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are
> not the intended recipient, you are not authorized to read,
> print, retain, copy, disseminate, distribute, or use this message
> or any part thereof. If you receive this message in error, please
> notify the sender immediately and delete all copies of this message.
>
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: alternative configuration to server-config.wsdd ?
Posted by Daniel Beland <dc...@gmail.com>.
If you use maven (or ant), why don't you simply perform XSLT to integrate
each deploy.wsdd in the server-config.wsdd.
That's what I did in a war:webapp postGoal.
On 1/26/06, Nicolas De Loof <ni...@capgemini.com> wrote:
>
>
> I have to replace the className parameter in generated deploy.wsdd and
> add some custom typeMappings.
> Replacing className is easy, but adding typeMapping elements is more
> difficult in my ant (maven.xml) build script.
>
> I'm trying another solution :
>
> It extends AxisServlet and it's init method :
> It loads the (wsdl2java generated) deploy.wsdd, and uses WSDDService
> methods to replace className parameter, append typemappings defined in
> another xml file and deploy the service using
> "ServiceAdmin.deployService(wsddService);"
>
> This doesn't work exactly as expected but I'm working on it...
>
> Nico.
>
> Tony Ingraldi a écrit :
>
> > Nicolas,
> >
> > Have you considered using org.apache.axis.utils.Admin? It can be
> > used to create a server-config.wsdd file from a deploy.wsdd file.
> >
> > i.e.
> >
> > java -cp $AXISCLASSPATH org.apache.axis.utils.Admin server
> > deploy.wsdd
> >
> >
> > You may need to tweak the generated server-config.wsdd file, but the
> > tweaking could potentially be automated with your scripting language
> > of preference.
> >
> >
> > On Jan 26, 2006, at 2:56 AM, Nicolas De Loof wrote:
> >
> >> The deploy.wsdd is generated as part of the build process (as
> >> endpoint interface is not yet stable), but it requires to manually
> >> update the server-config.wsdd to include the deploy.wsdd content.
> >> Using AdminClient to deploy is not a solution as the web service has
> >> to be started with the webapp (axis configuration is static)
> >>
> >> Is there any way to replace WEB-INF/server-config.wsdd based
> >> configuration by a "programmable" configuration ? I'd like to extend
> >> AxisServlet and automatically deploy my web service at application
> >> startup from it's generated deploy.wsdd.
> >
> >
> > --
> > Tony Ingraldi
> > tingraldi@echostorm.net
> >
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>
>
Re: alternative configuration to server-config.wsdd ?
Posted by Nicolas De Loof <ni...@capgemini.com>.
I have to replace the className parameter in generated deploy.wsdd and
add some custom typeMappings.
Replacing className is easy, but adding typeMapping elements is more
difficult in my ant (maven.xml) build script.
I'm trying another solution :
It extends AxisServlet and it's init method :
It loads the (wsdl2java generated) deploy.wsdd, and uses WSDDService
methods to replace className parameter, append typemappings defined in
another xml file and deploy the service using
"ServiceAdmin.deployService(wsddService);"
This doesn't work exactly as expected but I'm working on it...
Nico.
Tony Ingraldi a écrit :
> Nicolas,
>
> Have you considered using org.apache.axis.utils.Admin? It can be
> used to create a server-config.wsdd file from a deploy.wsdd file.
>
> i.e.
>
> java -cp $AXISCLASSPATH org.apache.axis.utils.Admin server
> deploy.wsdd
>
>
> You may need to tweak the generated server-config.wsdd file, but the
> tweaking could potentially be automated with your scripting language
> of preference.
>
>
> On Jan 26, 2006, at 2:56 AM, Nicolas De Loof wrote:
>
>> The deploy.wsdd is generated as part of the build process (as
>> endpoint interface is not yet stable), but it requires to manually
>> update the server-config.wsdd to include the deploy.wsdd content.
>> Using AdminClient to deploy is not a solution as the web service has
>> to be started with the webapp (axis configuration is static)
>>
>> Is there any way to replace WEB-INF/server-config.wsdd based
>> configuration by a "programmable" configuration ? I'd like to extend
>> AxisServlet and automatically deploy my web service at application
>> startup from it's generated deploy.wsdd.
>
>
> --
> Tony Ingraldi
> tingraldi@echostorm.net
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: alternative configuration to server-config.wsdd ?
Posted by Tony Ingraldi <ti...@echostorm.net>.
Nicolas,
Have you considered using org.apache.axis.utils.Admin? It can be
used to create a server-config.wsdd file from a deploy.wsdd file.
i.e.
java -cp $AXISCLASSPATH org.apache.axis.utils.Admin server deploy.wsdd
You may need to tweak the generated server-config.wsdd file, but the
tweaking could potentially be automated with your scripting language
of preference.
On Jan 26, 2006, at 2:56 AM, Nicolas De Loof wrote:
> The deploy.wsdd is generated as part of the build process (as
> endpoint interface is not yet stable), but it requires to manually
> update the server-config.wsdd to include the deploy.wsdd content.
> Using AdminClient to deploy is not a solution as the web service
> has to be started with the webapp (axis configuration is static)
>
> Is there any way to replace WEB-INF/server-config.wsdd based
> configuration by a "programmable" configuration ? I'd like to
> extend AxisServlet and automatically deploy my web service at
> application startup from it's generated deploy.wsdd.
--
Tony Ingraldi
tingraldi@echostorm.net