Cool, thanks!
Do you think setObjectValue()/addChild() should actually throw faults instead of no'oping? The user might want to know this stuff failed... --G > -----Original Message----- > From: Glyn Normington [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 14, 2002 12:30 PM > To: [EMAIL PROTECTED] > Subject: RE: [PATCH] MessageElement value serialization, etc > > > >In fact to support this nicely, we should provide a MessageElement > constructor that matches the SOAPHeader one >(namespace, localPart, > objectValue). [Oh, sorry in the examples above I shouldn't > have used the > QNames, since >those constructors don't exist] > > > >I also think it doesn't make sense to set the object value > on an element > created from actual XML, so that >shouldn't work. > I've re-instanted most of Taras's changes and done the above. > The commit > log messages have more details. > > Glyn >
