Hi, I meant to get this email off end of last week, but had other thing my mind (I got engaged this weekend)....
I opened a jira (http://issues.apache.org/jira/browse/TUSCANY-1149) and submitted a patch with a couple of sample tests.... I raised the jira since I don't really have any other way to share code with committers (although I guess I could have loaded the patch to the wiki). There are failures in the test cases, but due to my inexperience in the databindings component (having only looked at it a couple of weeks ago) I can't tell if they are due to bugs or user errors. Anyone able to give me a hand debugging this ? I have more cases available, but since they fail in a similar way, it seemed a good idea to get some help on this subset first. Regards, Dan On 27/02/07, ant elder <[EMAIL PROTECTED]> wrote:
On 2/27/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > [snip] > ant elder wrote: > > Was about to replying on the other thread but this one seems better > > ... this > > proposal sounds good to me. Over the weekend i added a JavaScript E4X > > databinding [1], and plan in the future to also add ones for Ruby ReXML, > > Python ElementTree, and perhaps something for Groovy as well. That could > > make itesting all the databinding combinations a little onerous, so > > testing > > specific combinations sounds good, eg e4x uses axiom so just e4x-axiom > > itests are probably enough if axiom is tested with all the others. > > > > ...ant > > > > [1] > > > https://svn.apache.org/repos/asf/incubator/tuscany/branches/sca-java-integration/sca/extensions/script/databinding.e4x/ > > > > > > I thought that E4X depended on XMLBeans, has this changed? Yes, there's an E4X impl based on axis2s axiom available now. This makes using JavaScript/E4X with our WS binding much more efficient as the E4X XML objects are backed by the actual OMElement without having to convert it to some other form. ...ant
