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=15362>. 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=15362 WSIF JMS Provider should be able to handle at least a notification transmission invocation Summary: WSIF JMS Provider should be able to handle at least a notification transmission invocation 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] WSIF JMS Provider should be able to handle at least a notification transmission invocation. To capture a prior thread described in the botp database (#155117) WSIF supports a request response invocation. This is fine for the client side but on the server side there is no WSIF implemented invocation to allow me to send back the response of this invocation (other than program directly against the JMS apis). There is an argument that WSIF is purely a client side api. If you make that argument, then I would say that JMS on the server side is really a client itself (since either side -client or server- is really viewed as a client in messaging).
