OK, I see, I already got them in a w3c Node format. Thanks Rob!
> Ok, I see, will try with on that. > > Was any particular reason why you gave up E4X? (peformance, etc?) > (I'm just new with it and any pit fall that I could avoid would be good to > know). Somebody please correct me if I am wrong! E4X basically wraps your XML parser's (probably Xerces) W3 DOM implementation, which is pretty heavy, memory-wise. If you deal with alot of complex XML, you will probably want to keep an eye on your memory usage. Currently, I tend toward XML DBs with XQuery and XSL when dealing with XML. best, -Rob On 5 sep, 12:25, Robert Koberg <[EMAIL PROTECTED]> wrote: > Sorry, I gave up on E4X a while ago. Maybe check out what apache's BSF > does with org.mozilla.javascript.xmlimpl.XML or XMLObject? > > best, > -Rob > > On Sep 5, 2008, at 11:01 AM, Carlos Montagut wrote: > > > Hi Rob, > > > > Why not just use the axiom document in rhino? > > > Well, I wanted to use inside the script all the functionally > > provided by E4X... In some cases the full payload will generated by > > the script, so E4X was a very easy way to generate them. > > > When I return a XML from JavaScript and I get it in Java, the object > > I get is an org.mozilla.javascript.xmlimpl.XML (which I don't have > > access, is not a public class). > > > Do you know which object should I instatiate in the Java side, that > > once I pass it to the Scope, in the JavaScrit side I see it as an > > XML of E4X (I could create this kind of object from using the AXIOM > > doc)? > > At least something that is not a serialized string that I should > > parse again... > > > Thanks again! > > > Carlos > > > 2008/9/5 Robert Koberg <[EMAIL PROTECTED]> > > > On Sep 5, 2008, at 10:15 AM, Carlos Montagut wrote: > > > Hi everyone, > > > Could you someone enlightme about the best way to exchange XML with a > > JavaScript function writen in Rhino back and fordward? > > > I have been looking in the documentation, see some clues about > > changing the E4X implmentation to AXIOM, but not much detail. > > > What I need to do is: > > > - Set an already parsed XML in the scope. > > - Get a E4X XML from the scope > > > It does not work that way. You would need to serialize out your > > axiom document to a form that can be used by E4X. > > > Why not just use the axiom document in rhino? > > > best, > > -Rob > > > In the Java side I'm working with AXIOM, since I will send that using > > Axis. > > My idea was to use Rhino JavaScript to modify the WS payload before > > sending it. > > > I already succed passing just a string and reparsing, but performance > > will be bettter if I could exchange back and ford an already parsed > > XML. > > > Any suggestion or idea will be more than wellcome. > > > Thanks ! > > > Carlos > > _______________________________________________ > > dev-tech-js-engine-rhino mailing list > > [EMAIL PROTECTED] > >https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
