Hi Basically I have been working alot of spring and hibernate stack. Everything is fine until you need to actually expose web service which comprises of part of your domain models. Hibernate will let you go in a loop or you will run into a famous error (lazily init :)). As such I have always used DTOs to deliver my ws data. (I hate DTOs by the way)
When I look at wicket, you can safely render the content in XML so I thought if I say expose my url .../MyService and param1, param2 etc... in a rest like manner to let other applications consume (using wicket models so no more DTOs to write). Just to check if it is done by anyone and what may be the drawback of this. -- View this message in context: http://www.nabble.com/Sanity-check%3A-rendering-xml-to-be-comsumed-by-other-applications-tp16074721p16074721.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
