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=17966>. 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=17966 Request flow for named service in client-config.wsdd is not followed. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-03-13 19:23 ------- It seems that beta-3 was more forgiving of bad QNames. In the 1.0 actual code the QName for Call.setOperation(QName qname) was bad. It seems that the client service name maust also match the name of the TargetService. call.setOperationName(new QName(TransactionBrokerID, "sendTransaction")); In this call, the value of TransactionBrokerID did not match the value of the target service in MessageContext.setTargetService(String tserv) causing the handler to not be invoked.
