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 "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org> on 2005/08/23 22:44:08 UTC
[jira] Created: (AXIS2-171) Handling multiple wsdl:service/port definitions in code gen
Handling multiple wsdl:service/port definitions in code gen
-----------------------------------------------------------
Key: AXIS2-171
URL: http://issues.apache.org/jira/browse/AXIS2-171
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: wsdl, databinding
Reporter: Ruchith Udayanga Fernando
Axis2-WSDL2java doesn't seem to properly handle WSDLs with multiple
service/port definitions referring to the 'SAME' binding.
Axis-1.2 generates multiple services in the above case with the same
service impl. And a single server-config.wsdd carries all the service
definitions.
To fix the above issue may be we can generate a service.xml with
multiple service definitions or can we have multiple 'service.xml's or
does this point us to the service groups that was discussed sometime
back?
More generally how should multiple 'port' definitions be handled when
they are referring to different 'bindings'?
--
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
[jira] Updated: (AXIS2-171) Handling multiple wsdl:service/port definitions in code gen
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-171?page=all ]
Ruchith Udayanga Fernando updated AXIS2-171:
--------------------------------------------
Attachment: ping.wsdl
sample wsdl attached
> Handling multiple wsdl:service/port definitions in code gen
> -----------------------------------------------------------
>
> Key: AXIS2-171
> URL: http://issues.apache.org/jira/browse/AXIS2-171
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: wsdl, databinding
> Reporter: Ruchith Udayanga Fernando
> Attachments: ping.wsdl
>
> Axis2-WSDL2java doesn't seem to properly handle WSDLs with multiple
> service/port definitions referring to the 'SAME' binding.
> Axis-1.2 generates multiple services in the above case with the same
> service impl. And a single server-config.wsdd carries all the service
> definitions.
> To fix the above issue may be we can generate a service.xml with
> multiple service definitions or can we have multiple 'service.xml's or
> does this point us to the service groups that was discussed sometime
> back?
> More generally how should multiple 'port' definitions be handled when
> they are referring to different 'bindings'?
--
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
[jira] Assigned: (AXIS2-171) Handling multiple wsdl:service/port
definitions in code gen
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-171?page=all ]
Ruchith Udayanga Fernando reassigned AXIS2-171:
-----------------------------------------------
Assign To: Ajith Harshana Ranabahu
> Handling multiple wsdl:service/port definitions in code gen
> -----------------------------------------------------------
>
> Key: AXIS2-171
> URL: http://issues.apache.org/jira/browse/AXIS2-171
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding, wsdl
> Reporter: Ruchith Udayanga Fernando
> Assignee: Ajith Harshana Ranabahu
> Attachments: ping.wsdl
>
> Axis2-WSDL2java doesn't seem to properly handle WSDLs with multiple
> service/port definitions referring to the 'SAME' binding.
> Axis-1.2 generates multiple services in the above case with the same
> service impl. And a single server-config.wsdd carries all the service
> definitions.
> To fix the above issue may be we can generate a service.xml with
> multiple service definitions or can we have multiple 'service.xml's or
> does this point us to the service groups that was discussed sometime
> back?
> More generally how should multiple 'port' definitions be handled when
> they are referring to different 'bindings'?
--
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
[jira] Resolved: (AXIS2-171) Handling multiple wsdl:service/port
definitions in code gen
Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-171?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-171:
-------------------------------------------
Resolution: Fixed
The latest change to the code generator allows to specifiy the port, if not it picks the first
> Handling multiple wsdl:service/port definitions in code gen
> -----------------------------------------------------------
>
> Key: AXIS2-171
> URL: http://issues.apache.org/jira/browse/AXIS2-171
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding, wsdl
> Reporter: Ruchith Udayanga Fernando
> Assignee: Ajith Harshana Ranabahu
> Attachments: ping.wsdl
>
> Axis2-WSDL2java doesn't seem to properly handle WSDLs with multiple
> service/port definitions referring to the 'SAME' binding.
> Axis-1.2 generates multiple services in the above case with the same
> service impl. And a single server-config.wsdd carries all the service
> definitions.
> To fix the above issue may be we can generate a service.xml with
> multiple service definitions or can we have multiple 'service.xml's or
> does this point us to the service groups that was discussed sometime
> back?
> More generally how should multiple 'port' definitions be handled when
> they are referring to different 'bindings'?
--
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