Hi Tom,

I tried the same code with Axis 1.4, still same behavior.

--
Mohamed


-----Original Message-----
From: Tom Jordahl (JIRA) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 22, 2006 4:47 PM
To: [email protected]
Subject: [jira] Commented: (AXIS-2510) Problem with consuming a WSDL for
a Web Service

    [
http://issues.apache.org/jira/browse/AXIS-2510?page=comments#action_1241
7363 ] 

Tom Jordahl commented on AXIS-2510:
-----------------------------------

Could you try with the source in the tree or from a recent release
(1.4)?

> Problem with consuming a WSDL for a Web Service
> -----------------------------------------------
>
>          Key: AXIS-2510
>          URL: http://issues.apache.org/jira/browse/AXIS-2510
>      Project: Apache Axis
>         Type: Bug

>     Versions: 1.1
>  Environment: PRPC , All Platforms
>     Reporter: Sai Kumar Reddy Baddam

>
> Problem with consuming a WSDL for a Web Service,  NameSpace name was
the same as another name which caused the problem.  Although it is
technically ok to have them the same name, Apache Axis 1.1 had a problem
with it.
> The Axis 1.1 SOAP client does indeed not handle group references. An
inspection of the generated Java stub classes for a SOAP service will
show that any group references were completely ignored by the Axis
WSDL2JAVA generator.
> Workaround is to manually edit the WSDL file to consolidate all
<schema> nodes that have the same targetNameSpace into one single
<schema> node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
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]

Reply via email to