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 09:13:16 UTC
[jira] Created: (AXIS2-672) Operation definitions from services.xml
ignored when no WSDL provided
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
Priority: Critical
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
[jira] Assigned: (AXIS2-672) Operation definitions from
services.xml ignored when no WSDL provided
Posted by "Dennis Sosnoski (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (AXIS2-672) Operation definitions from
services.xml ignored when no WSDL provided
Posted by "Dennis Sosnoski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-672?page=all ]
Dennis Sosnoski resolved AXIS2-672:
-----------------------------------
Resolution: Fixed
Commited fix for post-1.0 builds: http://svn.apache.org/viewcvs?rev=400181&view=rev
> 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
[jira] Closed: (AXIS2-672) Operation definitions from services.xml
ignored when no WSDL provided
Posted by "Dennis Sosnoski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Sosnoski closed AXIS2-672.
---------------------------------
> Operation definitions from services.xml ignored when no WSDL provided
> ---------------------------------------------------------------------
>
> Key: AXIS2-672
> URL: https://issues.apache.org/jira/browse/AXIS2-672
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.0
> Environment: n/a
> Reporter: Dennis Sosnoski
> Assigned To: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-672) Operation definitions from services.xml
ignored when no WSDL provided
Posted by "Dennis Sosnoski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-672?page=all ]
Dennis Sosnoski updated AXIS2-672:
----------------------------------
Attachment: operations.diff
> 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
> 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