[
http://jira.codehaus.org/browse/XFIRE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129330#action_129330
]
Wim Verreycken commented on XFIRE-671:
--------------------------------------
I expereience the same behaviour when all operations ARE in the interface, but
different portTypes+bindings are in one wsdl
I suppose this is related? does the patch fix this problem as well?
imo, clients should not be obligated to copy the remote interface
If the other portTypes are not soap, copying the entire interface will result
in runtime exceptions
when any of the method are called on the proxy.
So it is certainly a Bug, not an Imrovement, if you ask me.
Please look into this.
Thanks for all comments.
> Could not find operation <operation_name> in the service model - when not all
> WSDL operations are in the client Interface
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: XFIRE-671
> URL: http://jira.codehaus.org/browse/XFIRE-671
> Project: XFire
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.1
> Environment: XFire 1.2.1
> Reporter: Andres Bernasconi
> Assignee: Dan Diephouse
> Attachments: patch.txt
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> My application is client to a very complex Web Service (WSDL) with lots of
> operations for which I only care about one or two.
> My service interface in the client only defines those methods that are
> important to me; not ALL the operations defined in the WSDL are in my class.
> Everything worked fine until I upgraded from 1.1.2 to 1.2.1 where now it
> seems mandatory to declare all WSDL operations in the interface. Since it
> worked correctly in older versions I believe it could be defined as a Bug,
> unless this was meant as an Improvement.
> Either way hope this gets fixed. (It would be easy enough to add an if in the
> WSDLServiceConfigurator.java source file)
> Best Regards
> Andres Bernasconi.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
