Not necesseraly Apache licensed, but compatible. It means no LGPL. See http://www.apache.org/legal/3party.html
Btw, Nux embed Saxon afaik (see http://dsd.lbl.gov/nux/index.html). On 8/21/06, radu3000 <[EMAIL PROTECTED]> wrote:
Nux - http://dsd.lbl.gov/nux/api/nux/xom/xquery/XQuery.html http://dsd.lbl.gov/nux/api/nux/xom/xquery/XQuery.html is a good one. - Does it really needs to be Apache? Philip Dodds-2 wrote: > > Also does anyone know of a good Apache-compatible XQuery implementation? > > P > > On 8/21/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> Note that transofrmations on request and answer can be easily achieved >> using >> two transformation services and using an EIP routing slip. >> >> routingslip -> request transformation >> -> service >> -> response transformation >> <-- >> >> On 8/21/06, radu3000 <[EMAIL PROTECTED]> wrote: >> > >> > Here are the relevant steps for the Transformation Component: >> > >> > a. it receives a buisenss entity like request - >> > PlanIndicatorRequest.xml; >> > b. it transforms (PlanIndicatorRequest.xquery) it into a select >> query - >> > plan_indicator_select.xml; >> > c. passes the response to the client which executes the sql query >> and >> > gets back a - resultset.xml; >> > d. it receives the resutset.xml and merges the request xml and >> resultset >> > xml into a - merged_resultset.xml >> > e. it finally applies a transformation >> (PlanIndicatorResponse.xquery) >> > to get back a business entilty like response xml to the client >> -response.xml >> > >> > The next thing we are working is to create a transfomation repository >> (just >> > a set of tables) that captures: >> > 1. Request/Response templates (schemas if you wish). >> > 2. Corresponding Request/Response xqueries. >> > 3. Relationships between templates and corresponding xqueries. >> > We need this for role separation - Data Modelers would provide an SQL >> based >> > on particular template and Xquery/BusinessDomain Specialists will >> provide >> > corresponding translation xqueries. The xqueries and could be >> preloaded and >> > precompiled (nux approach) so that it fast to get a transformation. >> > >> > The big advantage is that XQuery is truly language independent (XML). >> > Persisting them to a repository we achieve the goal of rolling out a >> global >> > transromation componnet (some say dictionary - although it is more than >> > this...) >> > >> > >> > gnodet wrote: >> > > >> > > On 8/18/06, radu3000 <[EMAIL PROTECTED]> wrote: >> > >> >> > >> Hello, >> > >> >> > >> I can see that servicemix does support XPATH, and XSLT - although I >> am >> > >> not >> > >> sure what exact version. >> > > >> > > Mainly 1.0 >> > > >> > >> >> > >> Do you have plans to embeed XQuery (saxon) for various >> transformations? >> > >> say >> > >> from a domain model based xml into rdbms and back. I do have a >> working >> > >> protype/infrastructure - I can share... >> > > >> > > Yeah, I guess it could be very useful. >> > > What are the features of your component currently ? >> > > >> > > >> > >> >> > >> Regards, >> > >> Radu. >> > >> -- >> > >> View this message in context: >> > >> http://www.nabble.com/XQuery-support--tf2129404.html#a5876968 >> > >> Sent from the ServiceMix - User forum at Nabble.com. >> > >> >> > >> >> > > >> > > >> > > -- >> > > Cheers, >> > > Guillaume Nodet >> > > >> > > >> > >> > -- >> > View this message in context: >> http://www.nabble.com/XQuery-support--tf2129404.html#a5906613 >> > Sent from the ServiceMix - User forum at Nabble.com. >> > >> > >> >> >> -- >> Cheers, >> Guillaume Nodet >> > > -- View this message in context: http://www.nabble.com/XQuery-support--tf2129404.html#a5908467 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
