On 04/06/04 15:51, "Frank Zammetti" <[EMAIL PROTECTED]> wrote: > Hmm... If I understand your suggestion correctly, that would require a new > class for any Action you want to expose, correct? That's something I wanted > to avoid. It's good in the sense that no code has to change (config files > don't count in my mind, so that's OK to do), and while adding a whole new > class isn't as bad in my mind, it's still something I'd prefer to avoid if > possible.
You're right. One still needs to make a custom processForm on RequestProcessor to handle the "SOAPForm" correctly. > I haven't looked a Tiles at all yet (I'm actually fairly new to Struts > still), so I can't really make any intelligent comment on this (except, I > hope, for the comment that I can't make an intelligent comment on it! :) ) > >> How could one use your RequestProcessor if I am using Axis and >> publishing web services through WSDD or JWS files? > > I can't answer that either because while I know a little about Axis (a very > little), I don't know anything about WSDD or JWS. > Check the chapter 15 sample from the book Java Development with Ant. In a day or two you get the main picture (it covers web services development with ant and .net integration). Just handling strings is a little limited but what if... Instead of having the form defined and populated as a regular bean, why not make the marshaling of the xml document inside of the soap envelope? You do have the syntax that should be sent on the envelope. You just need the right bean to marshall to. (It may not be marshal but unmarshal... I get them both confused, all the time). Pedro Salgado --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
