Kevin, Your observations are perfectly valid and to-the-point. We are trying to answer some of the same questions you have raised.
Just to give you a little background : The application involves hundreds of Busines Objects and complex business rules. The number of different ways in which a client can manipulate Business objects (POST methods or RPC calls) is quite large (ofcourse we are planning to use Facades and BusinessDelegates to avoid too many granular actions). Our first stab at the design was to model all Business objects as Java Classes (We have good reasons not to use EJBs, but that is a different story). For some reasons, the front-end has to be a java swing application. We will have ValueObjects that will be passed back and forth between server and client. The transfer of value objects data between client tier and web/app tier could be (1) XML (2) Serialized objects. Sending XML representation of ValueObjects would increase our 'payload' by factor of atleast 5 (due to XML tags etc.) and also we have to write conversion routines. Our ValueObjects hierarchy is a bit complex. (JAXB could help here though.) On the other hand sending Serialized Value Objects tree seems straight forward and efficient. So we decided to give it a shot. Don't know if that is the best way. Regarding using the SOAP, we are seriously looking at it as an option. (Trying to get upto speed on web services is the first step...I guess :-)) I would value your take on this...please provide your opinion... thanks -----Original Message----- From: [EMAIL PROTECTED] [mailto:Kevin.Bedell@;sunlife.com] Sent: Thursday, October 17, 2002 2:28 PM To: Struts Users Mailing List Subject: RE: Can V in MVC be Swing in Struts? At the risk of me seeming simple and pointless, can I ask why you want manually code sending serialized objects over HTTP? What you're doing is reinventing SOAP and XML-RPC. These technologies are not that hard to use - especially XML-RPC. There are Java libraries available that handle all the communications for you and just hand your code XML docs. Not to mention debugging the application is much easier if you are using XML because at least it's readable english - You may also run the risk that you'll code a whole bunch of stuff this way and then later you'll be asked to refactor them as web services. 'Which is probably what you should've done to begin with', is what they'll say. Of course, I could be way off base. From my viewpoint I don't know what your requirements are - Kevin --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. --------------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
