Hi,
Yes, I think so too. Back when we were defining this I believe we planned to make it optional, this might just have been a typo. Anybody have issues with making it optional? All this would require would be a change to the doc that described the java binding extensions and a (probably minor) change to the java provider.
Also exactly the same argument applies to the EJB binding extension, where I believe the method name should be optional too, and should default to the WSDL operation name.
Nirmal.
| [EMAIL PROTECTED]
01/30/2003 04:57 AM
|
To: [EMAIL PROTECTED] cc: Subject: DO NOT REPLY [Bug 16587] New: - WSDL java:operation methodName attribute is mandatory |
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16587>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16587
WSDL java:operation methodName attribute is mandatory
Summary: WSDL java:operation methodName attribute is mandatory
Product: Axis-WSIF
Version: current (nightly)
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Basic Architecture
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The WSDL java:operation methodName attribute is defined as being mandatory :
http://ws.apache.org/wsif/providers/wsdl_extensions/java_extension.html
Is this really neccessary? I don't see whay it couldn't be optional like the
rest of the java:operation attributes, and default to the portType operation
name. This would make writting the WSDL for a Java binding much easier.
