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 Alistair Young <al...@smo.uhi.ac.uk> on 2006/08/08 18:39:25 UTC
[Axis2] Preserving the original WSDL
Hi there, me again! Is there any way to preserve the original WSDL when
deploying a service? The generated WSDL is not much use as it has removed
all the <types> elements so no data binding can occur.
I read somewhere that you can put the WSDL in META-INF but that didn't do
anything.
--
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
Isle of Skye
Scotland
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [AXIS2] Preserving the original WSDL
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Mirmit;
can you please create JIRA , I think its a bug in Axis2
Thanks
Deepal
Nirmit Desai wrote:
>Hey Alistair, all,
>
>I am having the same problem and it is severely restrictive. Did you get
>this to work?
>
>I read that article, and my service name in the WSDL, the name of the aar
>and the name of the service in services.xml are the same. And I have only
>one service at a time.
>
>I want many services implementing a portType. But when I deploy the
>services (one by one), the name of the portType is modified to suit the
>name of the service like xServicePortType instead of the one i put in my
>original WSDL. I have put the WSDL in META-INF and also set useOriginalwsdl
>to true.
>
>What do i need to do to have axis expose the WSDL I gave to it?
>
>-Nirmit
>
>
>
>
> Alistair Young
> <alistair@smo.uhi
> .ac.uk> To
> axis-user@ws.apache.org
> 08/09/2006 03:24 cc
> AM
> Subject
> Re: [AXIS2] Preserving the original
> Please respond to WSDL
> axis-user@ws.apac
> he.org
>
>
>
>
>
>
>
>
>aha! what a day, I must be working too hard! My wsdl namespace for
><xs:schema> was wrong so Axis2 was removing it. So Axis2 doesn't just
>pick up the wsdl and display it. It must process it too.
>
>Anyway, I can now get on with using this groovy new web services
>toolkit.
>
>Alistair
>
>On 8 Aug 2006, at 20:58, Alistair Young wrote:
>
>
>
>>this is painful! I found this site which explains it more:
>>
>>http://www.developer.com/open/article.php/10930_3589126_2
>>
>>and now I have the <types> element appearing in something that
>>resembles
>>the original wsdl. However, it's a real mess. The <types> has one
>>child:
>>
>><xs:schema targetNamespace="urn:minerva"
>>elementFormDefault="unqualified"
>>attributeFormDefault="unqualified"/>
>>
>>so the full xsd:schema definitions of the types are missing and no
>>data
>>binding for clients can be done.
>>
>>Axis2 has also added an HTTP POST binding which should not be
>>there. It's
>>also added a load of soap12 namespaces which aren't in the original
>>wsdl.
>>
>>I just can't get axis2 to reproduce the original wsdl. Is Axis2
>>sensitive
>>to namespace declarations?
>>
>>--
>>Alistair Young
>>Senior Software Engineer
>>UHI@Sabhal Mòr Ostaig
>>Isle of Skye
>>Scotland
>>
>>
>>
>>>apparently this in services.xml is meant to work but it doesn't:
>>>
>>><parameter name="useOriginalwsdl">true</parameter>
>>>
>>>the generated wsdl is lacking all original <types>
>>>
>>>Could someone guide me to a solution please?
>>>
>>><service>
>>> <description>Test service</description>
>>> <parameter name="ServiceClass" locked="false">org.test.Test</
>>>parameter>
>>> <parameter name="useOriginalwsdl">true</parameter>
>>> <operation name="combineMinervaObjects">
>>> <messageReceiver
>>>class="org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver"/>
>>> </operation>
>>></service>
>>>
>>>thanks,
>>>
>>>Alistair
>>>
>>>
>>>--
>>>Alistair Young
>>>Senior Software Engineer
>>>UHI@Sabhal Mòr Ostaig
>>>Isle of Skye
>>>Scotland
>>>
>>>
>>>
>>>>Hi there, me again! Is there any way to preserve the original
>>>>WSDL when
>>>>deploying a service? The generated WSDL is not much use as it has
>>>>removed
>>>>all the <types> elements so no data binding can occur.
>>>>
>>>>I read somewhere that you can put the WSDL in META-INF but that
>>>>didn't
>>>>do
>>>>anything.
>>>>
>>>>--
>>>>Alistair Young
>>>>Senior Software Engineer
>>>>UHI@Sabhal Mòr Ostaig
>>>>Isle of Skye
>>>>Scotland
>>>>
>>>>
>>>>
>>>>--------------------------------------------------------------------
>>>>-
>>>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [AXIS2] Preserving the original WSDL
Posted by Nirmit Desai <ni...@us.ibm.com>.
Hey Alistair, all,
I am having the same problem and it is severely restrictive. Did you get
this to work?
I read that article, and my service name in the WSDL, the name of the aar
and the name of the service in services.xml are the same. And I have only
one service at a time.
I want many services implementing a portType. But when I deploy the
services (one by one), the name of the portType is modified to suit the
name of the service like xServicePortType instead of the one i put in my
original WSDL. I have put the WSDL in META-INF and also set useOriginalwsdl
to true.
What do i need to do to have axis expose the WSDL I gave to it?
-Nirmit
Alistair Young
<alistair@smo.uhi
.ac.uk> To
axis-user@ws.apache.org
08/09/2006 03:24 cc
AM
Subject
Re: [AXIS2] Preserving the original
Please respond to WSDL
axis-user@ws.apac
he.org
aha! what a day, I must be working too hard! My wsdl namespace for
<xs:schema> was wrong so Axis2 was removing it. So Axis2 doesn't just
pick up the wsdl and display it. It must process it too.
Anyway, I can now get on with using this groovy new web services
toolkit.
Alistair
On 8 Aug 2006, at 20:58, Alistair Young wrote:
> this is painful! I found this site which explains it more:
>
> http://www.developer.com/open/article.php/10930_3589126_2
>
> and now I have the <types> element appearing in something that
> resembles
> the original wsdl. However, it's a real mess. The <types> has one
> child:
>
> <xs:schema targetNamespace="urn:minerva"
> elementFormDefault="unqualified"
> attributeFormDefault="unqualified"/>
>
> so the full xsd:schema definitions of the types are missing and no
> data
> binding for clients can be done.
>
> Axis2 has also added an HTTP POST binding which should not be
> there. It's
> also added a load of soap12 namespaces which aren't in the original
> wsdl.
>
> I just can't get axis2 to reproduce the original wsdl. Is Axis2
> sensitive
> to namespace declarations?
>
> --
> Alistair Young
> Senior Software Engineer
> UHI@Sabhal Mòr Ostaig
> Isle of Skye
> Scotland
>
>> apparently this in services.xml is meant to work but it doesn't:
>>
>> <parameter name="useOriginalwsdl">true</parameter>
>>
>> the generated wsdl is lacking all original <types>
>>
>> Could someone guide me to a solution please?
>>
>> <service>
>> <description>Test service</description>
>> <parameter name="ServiceClass" locked="false">org.test.Test</
>> parameter>
>> <parameter name="useOriginalwsdl">true</parameter>
>> <operation name="combineMinervaObjects">
>> <messageReceiver
>> class="org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver"/>
>> </operation>
>> </service>
>>
>> thanks,
>>
>> Alistair
>>
>>
>> --
>> Alistair Young
>> Senior Software Engineer
>> UHI@Sabhal Mòr Ostaig
>> Isle of Skye
>> Scotland
>>
>>> Hi there, me again! Is there any way to preserve the original
>>> WSDL when
>>> deploying a service? The generated WSDL is not much use as it has
>>> removed
>>> all the <types> elements so no data binding can occur.
>>>
>>> I read somewhere that you can put the WSDL in META-INF but that
>>> didn't
>>> do
>>> anything.
>>>
>>> --
>>> Alistair Young
>>> Senior Software Engineer
>>> UHI@Sabhal Mòr Ostaig
>>> Isle of Skye
>>> Scotland
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [AXIS2] Preserving the original WSDL
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
aha! what a day, I must be working too hard! My wsdl namespace for
<xs:schema> was wrong so Axis2 was removing it. So Axis2 doesn't just
pick up the wsdl and display it. It must process it too.
Anyway, I can now get on with using this groovy new web services
toolkit.
Alistair
On 8 Aug 2006, at 20:58, Alistair Young wrote:
> this is painful! I found this site which explains it more:
>
> http://www.developer.com/open/article.php/10930_3589126_2
>
> and now I have the <types> element appearing in something that
> resembles
> the original wsdl. However, it's a real mess. The <types> has one
> child:
>
> <xs:schema targetNamespace="urn:minerva"
> elementFormDefault="unqualified"
> attributeFormDefault="unqualified"/>
>
> so the full xsd:schema definitions of the types are missing and no
> data
> binding for clients can be done.
>
> Axis2 has also added an HTTP POST binding which should not be
> there. It's
> also added a load of soap12 namespaces which aren't in the original
> wsdl.
>
> I just can't get axis2 to reproduce the original wsdl. Is Axis2
> sensitive
> to namespace declarations?
>
> --
> Alistair Young
> Senior Software Engineer
> UHI@Sabhal Mòr Ostaig
> Isle of Skye
> Scotland
>
>> apparently this in services.xml is meant to work but it doesn't:
>>
>> <parameter name="useOriginalwsdl">true</parameter>
>>
>> the generated wsdl is lacking all original <types>
>>
>> Could someone guide me to a solution please?
>>
>> <service>
>> <description>Test service</description>
>> <parameter name="ServiceClass" locked="false">org.test.Test</
>> parameter>
>> <parameter name="useOriginalwsdl">true</parameter>
>> <operation name="combineMinervaObjects">
>> <messageReceiver
>> class="org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver"/>
>> </operation>
>> </service>
>>
>> thanks,
>>
>> Alistair
>>
>>
>> --
>> Alistair Young
>> Senior Software Engineer
>> UHI@Sabhal Mòr Ostaig
>> Isle of Skye
>> Scotland
>>
>>> Hi there, me again! Is there any way to preserve the original
>>> WSDL when
>>> deploying a service? The generated WSDL is not much use as it has
>>> removed
>>> all the <types> elements so no data binding can occur.
>>>
>>> I read somewhere that you can put the WSDL in META-INF but that
>>> didn't
>>> do
>>> anything.
>>>
>>> --
>>> Alistair Young
>>> Senior Software Engineer
>>> UHI@Sabhal Mòr Ostaig
>>> Isle of Skye
>>> Scotland
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [AXIS2] sec.properties location
Posted by "Jones, Alan R" <al...@boeing.com>.
Never mind... Was simply a typo in the services.xml file: had
<signaturepropFile> instead of <signaturePropFile> (capital"P"). Dumb
mistake.
Thanks,
Alan J
--------------------------------------------
Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
-----Original Message-----
From: Jones, Alan R
Sent: Tuesday, August 08, 2006 2:22 PM
To: axis-user@ws.apache.org; alistair@smo.uhi.ac.uk
Subject: [AXIS2] sec.properties location
It appears my InflowSecurity Handler is not seeing the sec.properties
file (see snippet of exception below)...My .aar file is as follows:
testwebservice/TestService.class
testwebservice/PWCallbackHandler.class
META-INF/services.xml
META-INF/services.wsdl
META-INF/Manifest.mf
sec.properties
services.jks
This is what is what I have in my services.xml file:
<signaturepropFile>sec.properties</signaturepropFile>
So, where else could I possibly put the sec.properties file where it can
be picked up? This follows the security sample. Any suggestions are
appreciated.
--aj
-------------------------
org.apache.axis2.AxisFault: WSHandler: Signature: no crypto property
file
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:287)
at
testwebservice.TestServiceStub.provideService(TestServiceStub.java:113)
at testwebservice.TestClient.main(TestClient.java:73)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: WSHandler:
Signature: no crypto property file; nested exception is:
org.apache.ws.security.WSSecurityException: WSHandler:
Signature: no crypto property file
at
org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDoAllReceiver
.java:336)
at
org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoAllHandler.j
ava:82)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:284)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86
9)...
-----------------------------------------
Thanks,
Alan J
--------------------------------------------
Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
[AXIS2] sec.properties location
Posted by "Jones, Alan R" <al...@boeing.com>.
It appears my InflowSecurity Handler is not seeing the sec.properties
file (see snippet of exception below)...My .aar file is as follows:
testwebservice/TestService.class
testwebservice/PWCallbackHandler.class
META-INF/services.xml
META-INF/services.wsdl
META-INF/Manifest.mf
sec.properties
services.jks
This is what is what I have in my services.xml file:
<signaturepropFile>sec.properties</signaturepropFile>
So, where else could I possibly put the sec.properties file where it can
be picked up? This follows the security sample. Any suggestions are
appreciated.
--aj
-------------------------
org.apache.axis2.AxisFault: WSHandler: Signature: no crypto property
file
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:287)
at
testwebservice.TestServiceStub.provideService(TestServiceStub.java:113)
at testwebservice.TestClient.main(TestClient.java:73)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: WSHandler:
Signature: no crypto property file; nested exception is:
org.apache.ws.security.WSSecurityException: WSHandler:
Signature: no crypto property file
at
org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDoAllReceiver
.java:336)
at
org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoAllHandler.j
ava:82)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:284)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86
9)...
-----------------------------------------
Thanks,
Alan J
--------------------------------------------
Alan R Jones
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [AXIS2] Preserving the original WSDL
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
this is painful! I found this site which explains it more:
http://www.developer.com/open/article.php/10930_3589126_2
and now I have the <types> element appearing in something that resembles
the original wsdl. However, it's a real mess. The <types> has one child:
<xs:schema targetNamespace="urn:minerva" elementFormDefault="unqualified"
attributeFormDefault="unqualified"/>
so the full xsd:schema definitions of the types are missing and no data
binding for clients can be done.
Axis2 has also added an HTTP POST binding which should not be there. It's
also added a load of soap12 namespaces which aren't in the original wsdl.
I just can't get axis2 to reproduce the original wsdl. Is Axis2 sensitive
to namespace declarations?
--
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
Isle of Skye
Scotland
> apparently this in services.xml is meant to work but it doesn't:
>
> <parameter name="useOriginalwsdl">true</parameter>
>
> the generated wsdl is lacking all original <types>
>
> Could someone guide me to a solution please?
>
> <service>
> <description>Test service</description>
> <parameter name="ServiceClass" locked="false">org.test.Test</parameter>
> <parameter name="useOriginalwsdl">true</parameter>
> <operation name="combineMinervaObjects">
> <messageReceiver
> class="org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver"/>
> </operation>
> </service>
>
> thanks,
>
> Alistair
>
>
> --
> Alistair Young
> Senior Software Engineer
> UHI@Sabhal Mòr Ostaig
> Isle of Skye
> Scotland
>
>> Hi there, me again! Is there any way to preserve the original WSDL when
>> deploying a service? The generated WSDL is not much use as it has
>> removed
>> all the <types> elements so no data binding can occur.
>>
>> I read somewhere that you can put the WSDL in META-INF but that didn't
>> do
>> anything.
>>
>> --
>> Alistair Young
>> Senior Software Engineer
>> UHI@Sabhal Mòr Ostaig
>> Isle of Skye
>> Scotland
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [AXIS2] Preserving the original WSDL
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
apparently this in services.xml is meant to work but it doesn't:
<parameter name="useOriginalwsdl">true</parameter>
the generated wsdl is lacking all original <types>
Could someone guide me to a solution please?
<service>
<description>Test service</description>
<parameter name="ServiceClass" locked="false">org.test.Test</parameter>
<parameter name="useOriginalwsdl">true</parameter>
<operation name="combineMinervaObjects">
<messageReceiver
class="org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver"/>
</operation>
</service>
thanks,
Alistair
--
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
Isle of Skye
Scotland
> Hi there, me again! Is there any way to preserve the original WSDL when
> deploying a service? The generated WSDL is not much use as it has removed
> all the <types> elements so no data binding can occur.
>
> I read somewhere that you can put the WSDL in META-INF but that didn't do
> anything.
>
> --
> Alistair Young
> Senior Software Engineer
> UHI@Sabhal Mòr Ostaig
> Isle of Skye
> Scotland
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org