You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org> on 2005/10/16 18:27:45 UTC
[jira] Created: (AXIS2-283) The SalesRankNPrice.wsdl is removed from the WSDL2Java test case!
The SalesRankNPrice.wsdl is removed from the WSDL2Java test case!
-----------------------------------------------------------------
Key: AXIS2-283
URL: http://issues.apache.org/jira/browse/AXIS2-283
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: databinding
Environment: WIn XP,JDK 1.4
Reporter: Ajith Harshana Ranabahu
Assigned to: Ajith Harshana Ranabahu
Priority: Minor
The new change to the WSDLPump made this to fail. Our rule for making schema's by wrapping causes this WSDL to have 2 identical global elements!
--
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
Re: [jira] Created: (AXIS2-283) The SalesRankNPrice.wsdl is
removed from the WSDL2Java test case!
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Mon, 2005-10-17 at 10:25 +0600, Ajith Ranabahu wrote:
> Hi,
> The WSDL is at
> http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/java/modules/codegen/test-resources/SalesRankNPrice.wsdl?rev=293558&view=markup
>
> This includes two porttypes which has the same operation name (but
> refers to two sets of messages). Our algorithm did not take into
> account multiple porttypes :)
Ah yes .. this is an old MSFT-style WSDL where they were generating one
portType for each binding. Duh. (Its from their SDL legacy.)
The solution is simple - we support generating stubs and skels only one
portType at a time. So let's add some code to check whether there's more
than one portType and if so ask the user to indicate which one to use
(for the skeleton). If its to generate a stub, we need to do the same
for multiple <service> elements and multiple <port> elements within a
service: the user needs to indicate which service/port to generate a
stub for.
Sanjiva.
Re: [jira] Created: (AXIS2-283) The SalesRankNPrice.wsdl is removed from the WSDL2Java test case!
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
The WSDL is at
http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/java/modules/codegen/test-resources/SalesRankNPrice.wsdl?rev=293558&view=markup
This includes two porttypes which has the same operation name (but refers to
two sets of messages). Our algorithm did not take into account multiple
porttypes :)
On 10/16/05, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>
> Hi Ajith,
>
> Can u indicate which operations' in/out messages have this problem?
> Because we're creating the wrapper element using the operation name this
> should work unless there's overloading. (??)
>
> We do need to work out how to deal with overloaded stuff, I think. We
> don't support overloading on the server side (following the lead of WSDL
> 2.0) but we may need to support it on the client side to talk to legacy
> services.
>
> Sanjiva.
>
> On Sun, 2005-10-16 at 18:27 +0200, Ajith Harshana Ranabahu (JIRA) wrote:
> > The SalesRankNPrice.wsdl is removed from the WSDL2Java test case!
> > -----------------------------------------------------------------
> >
> > Key: AXIS2-283
> > URL: http://issues.apache.org/jira/browse/AXIS2-283
> > Project: Apache Axis 2.0 (Axis2)
> > Type: Bug
> > Components: databinding
> > Environment: WIn XP,JDK 1.4
> > Reporter: Ajith Harshana Ranabahu
> > Assigned to: Ajith Harshana Ranabahu
> > Priority: Minor
> >
> >
> > The new change to the WSDLPump made this to fail. Our rule for making
> schema's by wrapping causes this WSDL to have 2 identical global elements!
> >
>
>
>
--
Ajith Ranabahu
Re: [jira] Created: (AXIS2-283) The SalesRankNPrice.wsdl is
removed from the WSDL2Java test case!
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Hi Ajith,
Can u indicate which operations' in/out messages have this problem?
Because we're creating the wrapper element using the operation name this
should work unless there's overloading. (??)
We do need to work out how to deal with overloaded stuff, I think. We
don't support overloading on the server side (following the lead of WSDL
2.0) but we may need to support it on the client side to talk to legacy
services.
Sanjiva.
On Sun, 2005-10-16 at 18:27 +0200, Ajith Harshana Ranabahu (JIRA) wrote:
> The SalesRankNPrice.wsdl is removed from the WSDL2Java test case!
> -----------------------------------------------------------------
>
> Key: AXIS2-283
> URL: http://issues.apache.org/jira/browse/AXIS2-283
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding
> Environment: WIn XP,JDK 1.4
> Reporter: Ajith Harshana Ranabahu
> Assigned to: Ajith Harshana Ranabahu
> Priority: Minor
>
>
> The new change to the WSDLPump made this to fail. Our rule for making schema's by wrapping causes this WSDL to have 2 identical global elements!
>
[jira] Resolved: (AXIS2-283) The SalesRankNPrice.wsdl is removed
from the WSDL2Java test case!
Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-283?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-283:
-------------------------------------------
Resolution: Fixed
The latest changes to the code base allows this to be processed. Now it's added to the test case again
> The SalesRankNPrice.wsdl is removed from the WSDL2Java test case!
> -----------------------------------------------------------------
>
> Key: AXIS2-283
> URL: http://issues.apache.org/jira/browse/AXIS2-283
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding
> Environment: WIn XP,JDK 1.4
> Reporter: Ajith Harshana Ranabahu
> Assignee: Ajith Harshana Ranabahu
> Priority: Minor
>
> The new change to the WSDLPump made this to fail. Our rule for making schema's by wrapping causes this WSDL to have 2 identical global elements!
--
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