Good day- I have done only some simple projects using XmlBeans but now have a more complex problem to solve. I want to stick with XmlBeans because it has proven to be the most productive XML binding environment I've used.
My need boils down to (I think) converting from an XmlBeans XObj$* store node instance and/or a Saxon NodeInfo istance to an XMLObject instance. I've gone through the source and XmlBeans does both of these, for example, in XmlCursor#getObject() and XmlObject #selectPath(...). The ability to get get a NodeInfo instance from an XmlBeans store node would also be nice but I think that's covered by the Saxon API (since the XObj subclasses I care about implement Node). I am hoping that there are hooks for user code to ac- complish this. If not, maybe someone can shed some light on why I don't need it. The purpose is to use XmlObject instances within custom XPath functions called via #selectPath(...). It seems that I can only get a DOM Node (XObj$*) or a Saxon NodeInfo (I think) to represent an XML element or attribute parameter. This appears to lock me into DOM or Saxon processing within the custom function. I'd like to be able to "pull up" the representation to my XmlBeans generated types, use the binding framework for processing, then convert the results to NodeInfo instances and return them to Saxon. I hope this makes sense. I've been racking my brain on this for too long today. TIA -dub --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
