Alan, Please open a bug report at http://nagoya.apache.org for the dropped exceptions.
Thanks, dims --- Alan George <[EMAIL PROTECTED]> wrote: > Forgoing the ideal situation, it seams broken to me to just drop these > exceptions on the floor. > > I have made a local change to throw these exceptions. Does anyone know > of any issues with this change I should be aware of? > > Thanks again, > -alan > > > Chris Haddad wrote: > > >Alan - > > > >ideally you would be using a protocol higher up the stack, like > >WS-ReliableMessaging or WS-Transaction. > > > > > >/Chris > > > > > >On Thu, 19 Jun 2003, Alan George wrote: > > > > > > > >>I am attempting to write a transactional WS. The client will be setting > >>an SOTimeout on the connection. On the server side I would like to > >>catch the IOException (broken pipe) and roll back a UserTransaction. > >>Unfortunatly I have discovered the IOException is caught in the > >>Message.writeTo() and is dropped on the floor. IOException is already > >>in the throws. Why are these exceptions drop at this point? If I > >>modified to rethrow the exceptions would this break something else? > >> > >>Thanks for your advise, > >>-alan > >> > >> > >> > >> > ===== Davanum Srinivas - http://webservices.apache.org/~dims/ __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
