There are some particular issues relating to dealing with, alternately the exception DataType and the fault DataType, and getting these through the Tuscany databinding framework.
Some of these I've worked around already and am working to post a more detailed update myself (for example I modified DataTransformationInterceptor to match element names of XMLType fault logicals rather than using an equals() comparison). Scott On 9/11/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > Yes, I think this should work. I'm trying to get a simple case > through the Web Service binding and the databinding transformers at the > moment and I'm running into various issues. I'll post a more detailed > update later. > > Simon > > Scott Kurz wrote: > > > Say I wanted to have a remotable Java interface with a method like: > > > > int myMethod() throws java.sql.SQLException; > > > > Should I be able to throw this exception, say, across the web service > > binding? > > > > I don't see why not. JAX-WS Sec 3.7 describes how to build a fault > bean > > out of an exception like SQLException which doesn't conform to the > pattern > > in JAX-WS Sec 2.5. A tool like wsgen should be able to generate a > WSDL > > with a corresponding fault element, typed by the default mapping > obtained by > > viewing SQLException as a JavaBean (Sec 3.7) per JAXB. > > > > (For a complicated data type the default JAXB mapping isn't enough > without > > annotations, but for simpler examples it might be OK.) > > > > Do we view this as a valid remote interface? I'm not asking whether it > > works today.. just whether it seems like it should work. > > > > Scott > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
