Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 39686 invoked from network); 15 Jan 2004 20:12:19 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Jan 2004 20:12:19 -0000 Received: (qmail 22166 invoked by uid 500); 15 Jan 2004 20:11:57 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 21973 invoked by uid 500); 15 Jan 2004 20:11:56 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 21953 invoked from network); 15 Jan 2004 20:11:55 -0000 Message-ID: <8BE8ADB0C371D3118CFB00508B0725561377C847@mailser.bssg.com.ar> From: FONTDEVILA Diego To: "'axis-user@ws.apache.org'" Subject: RE: How to create the server-config.wsdd file in a script (withou t any running server) Date: Thu, 15 Jan 2004 17:15:13 -0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3DBA4.489D6560" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3DBA4.489D6560 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable What I did was use the AdminClient to publish my service with the = server running, and it created the service section in server-config.wsdd = (saved in WEB-INF in the axis webapp directory in Tomcat), then I took what I = needed from that file and copied it in my own version of server-config.wsdd, = the one I use for deploy inside the war file. Diego -----Original Message----- From: Heitzeg, Bill [mailto:bill.heitzeg.ctr@sabre.com] Sent: Jueves 15 de Enero de 2004 15:46 To: axis-user@ws.apache.org Subject: RE: How to create the server-config.wsdd file in a script (without any running server) Petr, I believe I'm doing what you're asking. I'm just placing everything directly in the server-config.wsdd and then kicking off Ant to build it = all into a war. In other words, I have a server-config.wsdd file as part = of my build project, I place all my config information in this file (what = would normally be passed in as part of deploy.wsdd) and then add it to the = war when I build. I don't use deploy.wsdd at all. If that doesn't help, I can send you what I have in a zip file. Bill -----Original Message----- From: Petr Kozelka [mailto:pkozelka@email.cz] Sent: Thursday, January 15, 2004 12:50 PM To: axis-user@ws.apache.org Subject: How to create the server-config.wsdd file in a script (without any running server) Hello, I need to create a WAR file containing whole AXIS + my webservice, in=20 order to make the deployment of my webservice same as deploying any=20 other WAR. The problem is that I did found no way to create the server-config.xml=20 file without having any server running. I need to do this in an ANT=20 script, because the whole process will be reproduced many times at=20 several machines, typically disconnected from the corporate network. But it seems that the AdminClient utility a) always tries to connect a server b) never returns the server-config.wsdd file to a caller-accessible=20 location; instead, it is created just on the server. Is there a way to convince the AdminClient or other utility to produce=20 the wsdd file at the clientside, without connecting webserver ? Thanks, Petr http://www.portalsociete.com=20 Vis=EDtenos, lo estamos esperando.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D La informaci=F3n aqu=ED contenida es confidencial y est=E1 dirigida solamente a las personas direccionadas en el mail. No debe ser considerada como recomendaci=F3n de compra o venta de valores. Todo acceso no autorizado, uso, reproducci=F3n, o divulgaci=F3n est=E1 prohibido. Ni SOCIETE GENERALE ni ninguna de sus subsidiarias o filiales asumir=E1n responsabilidad ni obligaci=F3n legal alguna por cualquier informaci=F3n incorrecta o alterada contenida en este mensaje. The information contained herein is confidential and is intended solely for the addressee(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ------_=_NextPart_001_01C3DBA4.489D6560 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: How to create the server-config.wsdd file in a script = (without any running server)

What I did was use the AdminClient to publish my = service with the server running, and it created the service section in = server-config.wsdd (saved in WEB-INF in the axis webapp directory in = Tomcat), then I took what I needed from that file and copied it in my = own version of server-config.wsdd, the one I use for deploy inside the = war file.

        =         =         =         =         Diego
-----Original Message-----
From: Heitzeg, Bill [mailto:bill.heitzeg.ctr@sabre= .com]
Sent: Jueves 15 de Enero de 2004 15:46
To: axis-user@ws.apache.org
Subject: RE: How to create the server-config.wsdd = file in a script
(without any running server)


Petr,
        I believe = I'm doing what you're asking.  I'm just placing everything = directly in the server-config.wsdd and then kicking off Ant to build it = all into a war.  In other words, I have a server-config.wsdd file = as part of my build project, I place all my config information in this = file (what would normally be passed in as part of deploy.wsdd) and then = add it to the war when I build.  I don't use deploy.wsdd at = all.

If that doesn't help, I can send you what I have in a = zip file.

Bill

-----Original Message-----
From: Petr Kozelka [mailto:pkozelka@email.cz]
Sent: Thursday, January 15, 2004 12:50 PM
To: axis-user@ws.apache.org
Subject: How to create the server-config.wsdd file = in a script (without
any running server)


Hello,

I need to create a WAR file containing whole AXIS + = my webservice, in
order to make the deployment of my webservice same = as deploying any
other WAR.

The problem is that I did found no way to create the = server-config.xml
file without having any server running. I need to do = this in an ANT
script, because the whole process will be reproduced = many times at
several machines, typically disconnected from the = corporate network.
But it seems that the AdminClient utility
   a) always tries to connect a = server
   b) never returns the server-config.wsdd = file to a caller-accessible
location; instead, it is created just on the = server.

Is there a way to convince the AdminClient or other = utility to produce
the wsdd file at the clientside, without connecting = webserver ?

Thanks,
Petr


http://www.portalsociete.com
Vis=EDtenos, lo estamos esperando.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
La informaci=F3n aqu=ED contenida es confidencial y = est=E1 dirigida
solamente a las personas direccionadas en el = mail.
No debe ser considerada como recomendaci=F3n de = compra o venta
de valores. Todo acceso no autorizado, uso, = reproducci=F3n, o
divulgaci=F3n est=E1 prohibido.
Ni SOCIETE GENERALE ni ninguna de sus subsidiarias o = filiales
asumir=E1n responsabilidad ni obligaci=F3n legal = alguna por cualquier
informaci=F3n incorrecta o alterada contenida en = este mensaje.

The information contained herein is confidential and = is intended
solely for the addressee(s).  It shall not be = construed as a
recommendation to buy or sell any security.  = Any unauthorized
access, use, reproduction, disclosure or = dissemination is prohibited.
Neither SOCIETE GENERALE nor any of its subsidiaries = or affiliates
shall assume any legal liability or responsibility = for any incorrect,
misleading or altered information contained = herein.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


------_=_NextPart_001_01C3DBA4.489D6560--