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 "Dennis Sosnoski (JIRA)" <ji...@apache.org> on 2006/05/05 23:45:29 UTC

[jira] Assigned: (AXIS2-672) Operation definitions from services.xml ignored when no WSDL provided

     [ http://issues.apache.org/jira/browse/AXIS2-672?page=all ]

Dennis Sosnoski reassigned AXIS2-672:
-------------------------------------

    Assign To: Dennis Sosnoski

> Operation definitions from services.xml ignored when no WSDL provided
> ---------------------------------------------------------------------
>
>          Key: AXIS2-672
>          URL: http://issues.apache.org/jira/browse/AXIS2-672
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: core
>     Versions: 1.0
>  Environment: n/a
>     Reporter: Dennis Sosnoski
>     Assignee: Dennis Sosnoski
>     Priority: Critical
>  Attachments: operations.diff
>
> org.apache.axis2.deployment.ServiceBuilder tries to construct a WSDL if one is not provided by the service definition. This seems questionable at best, since the constructed schema for operation parameters is unlikely to bear much resemblance to the real one for the service (see AXIS2-458 on this). Even worse, though, is that the attempt to construct a WSDL populates the service operations, which means that the operation descriptions supplied in the services.xml are ignored.
> The fix is to move the questionable WSDL construction to after the processing of the operations from the service. Fix is attached as diff, not committing it myself because of the imminent 1.0 release. 

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