thanks Keith, Just wanted to make sure that the idea didn't fade away! As you can see from this thread, this problem creeps up in a number of places, so I hope you will find the time to fully implement it eventually. Thanks for pursuing this!
Bob. -----Original Message----- From: Keith Visco [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 3:59 PM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] Castor support for additional nodes in XML Robert Ollila wrote: > > How about having the client use XSL to transform any messages into the > original client structure and thus "weeding out" any extra fields? The XSL > transformation would be done prior to unmarshalling the message. In a > recent thread Keith Visco and Ned Wolpert indicated that it might be > worthwhile to implement more direct support for this type of thing in the > Caster framework. Keith, has there been any more investigation on this? Hi Bob...yes, I actually played around with it about a week ago. I got a quick prototype working, but I haven't had time to revist this or clean up the code. It's pretty easy to do, but I just haven't had the time to finish it. We are readying a product release at Intalio, so the company has drawn on all it's resources including Intalio related ExoLab resources. So whenever I can sneak some Castor time I try to just fix bugs instead of adding new features. Once the product enters the official release cycle...ie all blocking bugs are fixed, then I believe I can return more of my attention back to Castor. Thanks, --Keith ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
