Hi Christian,
I'm looking for a way to store a xml-subelement during a session as a subelement and not as a rootelement. The store- and the session:set-function save xml-elements as a root-elements, loosing the origional root.
My casus is that I have this batch-webservice that I want to turn into a online/interactive-webservice. The application makes use of the root- and ancestor functions/axis on xml-subelements. In the batch solution I have access to the origional xml-subelement. In the online-solution however I have not. This because the code is broken up due to a http-request/response interaction with the user. I would like the xml-subelement to survive this http-excursion in a way that its root-element stays available and the root- and ancestor-function gives the same result as in the batch-version.
Do you have any suggestions on this?
mvgr.
Rob Stapper