That probably will work, as long as the code in CompositeProcessor that writes element extensions is not tripped up by it.
On Thu, Jan 8, 2009 at 5:34 PM, Luciano Resende <[email protected]>wrote: > > Independent of using a separate list or not, there is still an issue > related to storing the attribute QName to be used during the write > phase. How about we create a wrapper object that would have the > attribute QName and it's value (e.g ExtendedAttribute) ? And then we > could use the current list or if necessary use a separate one ? > > Thoughts ? > > -- > Luciano Resende > Apache Tuscany, Apache PhotArk > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ >
