Hi, Some thoughts about the example simplification - really it would be good to simplify the sample, but the client+server scenario should remain as JUnit test I think. You can see below some problems I currently have exactly with this scenario.
I started looking at the following issues: 1. sharing common Configuration object 2. Being able to directly implement a WSDL interface Unfortunately I was not able to execute the sample JUnit test after I checked out the latest sources. The problem occurs when executing the scenario in which the XQuery component is a remote one and is exposed as Web Service. When I investigated the problem it appeared that the "targetOperation" of the DataTransformationInteceptor on the server side (i.e. the one that is called by Axis2ServiceProvider.invokeTarget) has input type with SDO data bindings of the input parameters, while I should have had Saxon type data binding. In the contrary if I look at the "contract" variable of the Axis2ServiceProvider - the databinding of the input parameters of the operation are correct. Is there something done recently in this direction, which could have led to the problem? ---------- One more note: Currently it will be possible (I will verify it after i have finished with the implementation :) ) for an XQuery component to implement a WSDL interface, bt it will not be possible to call a reference which has WSDL interface. At least i do not see how, because Saxon wants a java interface, which to be called. Can we think of some workaround? Bye, Vasil >-------- Оригинално писмо -------- >От: Jean-Sebastien Delfino <[EMAIL PROTECTED]> >Относно: Including the XQuery sample in the next release? >До: [email protected] >Изпратено на: Неделя, 2007, Септември 2 20:16:00 EEST >---------------------------------- > >Hi, > >I'm thinking that we should include the XQuery implementation that Vasil >has contributed in our next release as I think that XQuery gives us a >great way to work with / mediate / transform XML data sources. > >To get ready for that and help Tuscany users understand what they can do >with XQuery, I'd like to suggest the following improvements and >simplifications to the XQuery sample at [1]. > >- Move the .xq files from src/main/resources/META-INF/sca to >src/main/resources/xquery so that they are in plain sight and people >realize that they are first class development artifacts; > >- support WSDL interfaces, basically removing the requirement to >generate SDOs and write many Java interfaces, to help show that you can >something useful with just XQuery without having to write any Java code; > >- I'm not sure about this one, but I was also thinking that we could >simplify the sample by using local components instead of having a client >+ a server and web services in the middle... the idea is that a simpler >example will be more effective at demonstrating the value of XQuery. > >In a parallel thread I'd like to start discussing how we could show >XQuery components in the tutorial that we are preparing for ApacheCon >2007, for example to extract data out of the Amazon Web Services that >we're planning to use in the tutorial. > >Thoughts? > >[1] >http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/quote-xquery/ > >-- >Jean-Sebastien > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > ----------------------------------------------------------------- ЕЛА и направи свой сайт, намери нови приятели! WWW.ZOOM.BG --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
