Hi,
would you see the following implementation approach fit for a patch?
- add an optional String (bean-) property "content" to XMPPErorror.Condition
- adding code to parse/serialize the text nodes to the provider.
- add a Method XMPPError.getConditionObject() that returns the object instead of the string
It will not break the API but allow access to the condition's content.
I did of course imply changing the tests accordingly.