Hi,
I thought about a solution with an ant script calling an XSLT
transformation to synchronize my old service.xml (with references to
modules) with my new generated one by wsdl2java.
Has anybody done this already? Is there an easier way to do this?
In order to provide a generic solution I'd need a xsd or a complete
description of the service.xml. Is there one available somewhere? I only
found some older threads in the mailing list pointing to some path in
the svn repo I couldn't find.
Thanks,
Matthias.
Von: Gaiser, Matthias
Gesendet: Mittwoch, 20. Februar 2008 17:17
An: axis-user@ws.apache.org
Betreff: AW: Generating service.xml with wsdl2java
Hello Dirk,
Thank you for your answer. That is exactly what I want to do. And I
think there are lots of other people out there which have the same
problem or am I wrong?
My question now is if there is a kind of standard way to alter the
default services.xml?
This altering of the services.xml may not be an easy task.
Regards,
Matthias.
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 20. Februar 2008 15:09
An: axis-user@ws.apache.org
Betreff: RE: Generating service.xml with wsdl2java
Hi,
I suggest to create an ant-script which alters the 'default'
services.xml so you don't have to change
This manually everytime.
For instance alter the call to the skelton to the implementation
Regards
Dirk
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: woensdag 20 februari 2008 14:29
To: axis-user@ws.apache.org
Subject: Generating service.xml with wsdl2java
Hi all,
I am generating the server-side code from a wsdl with wsdl2java which
generates the corresponding java classes and the service.xml.
Now I am changing the service.xml to add some handlers, messagereceiver,
etc.
When some methods are added to wsdl, I am generating the code again with
wsdl2java and it replaces my service.xml which means I lose all my
changes of it.
Is there a way to automatically synchronize the old service.xml with the
new one?
Thanks,
Matthias.
The information transmitted via this e-mail is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination
or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer.
