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                                                
>             <[EMAIL PROTECTED]                                             
>             .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                                
>             [EMAIL PROTECTED]                                             
>                  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
>>[EMAIL PROTECTED] 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
>>>[EMAIL PROTECTED] 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
>>>>[EMAIL PROTECTED] Mòr Ostaig
>>>>Isle of Skye
>>>>Scotland
>>>>
>>>>
>>>>
>>>>--------------------------------------------------------------------
>>>>-
>>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>>
>>>>        
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal
................................................................
~Future is Open~ 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to