Re: Using XQJ API with Cocoon3
Hi Steven!!! +1 to your suggestion. I've never been fan of 'optional' module that aggregates every 3rd parties integrations, I'd like to see it rather splitted in a multi-module structure. Please let me know if you want me to work on it, I'll fill an issue on JIRA and work. TIA, have a nice day!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Wed, Jul 13, 2011 at 9:30 AM, Steven Dolg steven.d...@indoqa.com wrote: Am 05.07.2011 14:49, schrieb Simone Tripodi: Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in thedependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Hey, a little late to the party, but I wanted to add some comments. We should take a look at introducing topic specific modules. I fear that the optional module turns into a giant clump of all things unrelated. That's pretty much the opposite of the original intention: Have small, lightweight modules that you choose to use based on your actual requirements, allowing you to tailor your application package exactly to your needs. If I'm forced to use the optional module that brings dozens (::hyperbole::) of undesired features and dependencies just because I need one very specific feature, I'd be a little upset. (I don't like uploading 100 MB war files :/ ) But I wholeheartedly agree to the feature idea. DO WANT! :P Cheers, Steven Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssersrobby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
Re: Using XQJ API with Cocoon3
Am 14.07.2011 11:12, schrieb Simone Tripodi: Hi Steven!!! +1 to your suggestion. I've never been fan of 'optional' module that aggregates every 3rd parties integrations, I'd like to see it rather splitted in a multi-module structure. Please let me know if you want me to work on it, I'll fill an issue on JIRA and work. I'm not really up-to-date with what's currently in there, so my comment was more of a general nature. But it might be worth it to take a look and see if we could split this into several independent modules that serve a specific purpose. Coherence and coupling, ya'know... :P Cheers, Steven TIA, have a nice day!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Wed, Jul 13, 2011 at 9:30 AM, Steven Dolgsteven.d...@indoqa.com wrote: Am 05.07.2011 14:49, schrieb Simone Tripodi: Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in thedependenciesManagementin the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Hey, a little late to the party, but I wanted to add some comments. We should take a look at introducing topic specific modules. I fear that the optional module turns into a giant clump of all things unrelated. That's pretty much the opposite of the original intention: Have small, lightweight modules that you choose to use based on your actual requirements, allowing you to tailor your application package exactly to your needs. If I'm forced to use the optional module that brings dozens (::hyperbole::) of undesired features and dependencies just because I need one very specific feature, I'd be a little upset. (I don't like uploading 100 MB war files :/ ) But I wholeheartedly agree to the feature idea. DO WANT! :P Cheers, Steven Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssersrobby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
Re: Using XQJ API with Cocoon3
Am 05.07.2011 14:49, schrieb Simone Tripodi: Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in thedependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Hey, a little late to the party, but I wanted to add some comments. We should take a look at introducing topic specific modules. I fear that the optional module turns into a giant clump of all things unrelated. That's pretty much the opposite of the original intention: Have small, lightweight modules that you choose to use based on your actual requirements, allowing you to tailor your application package exactly to your needs. If I'm forced to use the optional module that brings dozens (::hyperbole::) of undesired features and dependencies just because I need one very specific feature, I'd be a little upset. (I don't like uploading 100 MB war files :/ ) But I wholeheartedly agree to the feature idea. DO WANT! :P Cheers, Steven Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssersrobby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
RE: Using XQJ API with Cocoon3
Hi Steven, I agree that an XQJ generator would be a perfect fit for a separate maven project. Either you need it or you don't and you get the freedom by (not) declaring the dependency. I think for non-general purpose code this makes perfect sense. Robby -Oorspronkelijk bericht- Van: Steven Dolg [mailto:steven.d...@indoqa.com] Verzonden: wo 13-7-2011 9:30 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Am 05.07.2011 14:49, schrieb Simone Tripodi: Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in thedependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Hey, a little late to the party, but I wanted to add some comments. We should take a look at introducing topic specific modules. I fear that the optional module turns into a giant clump of all things unrelated. That's pretty much the opposite of the original intention: Have small, lightweight modules that you choose to use based on your actual requirements, allowing you to tailor your application package exactly to your needs. If I'm forced to use the optional module that brings dozens (::hyperbole::) of undesired features and dependencies just because I need one very specific feature, I'd be a little upset. (I don't like uploading 100 MB war files :/ ) But I wholeheartedly agree to the feature idea. DO WANT! :P Cheers, Steven Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssersrobby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers winmail.dat
Re: Using XQJ API with Cocoon3
Simone Tripodi wrote: Hi Robby, AFAIK 3rd parties MPL licensed can be included, see http://www.apache.org/legal/resolved.html Yes. I investigated that once before: http://s.apache.org/gx Just follow the Category B instructions. -David
Using XQJ API with Cocoon3
Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
Re: Using XQJ API with Cocoon3
Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in the dependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
RE: Using XQJ API with Cocoon3
Hi Simone, as this is my last week before my holidays I don't think i will manage to get things really tested properly. But I look forward contributing input for this component as it really is a must-have if you want to hook up with any XMLDB supporting XQJ. The only real showstopper at this moment is that i have no clue how I can avoid declaring a dependency on the XMLDB specific implementation. The XQJGenerator so far is 100% using only the interfaces but they are packaged with the implementation :-( I will address this issue with both Sedna and BaseX and see if someone can create seperate jar for interface and let them all seperate implementation code from the interface in 2 separate jars. If the interface would be available from Maven central would also be a big bonus. Keep you posted, Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 14:49 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in the dependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers winmail.dat
Re: Using XQJ API with Cocoon3
Hi Robby, rather a 'must to have' it is IMHO a 'very cool to have' ;) just a silly question - and please take in consideration that I'm not familiar with the XQuery world - isn't there a JSR specification? Many thanks in advance, have a nice day! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 5:20 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi Simone, as this is my last week before my holidays I don't think i will manage to get things really tested properly. But I look forward contributing input for this component as it really is a must-have if you want to hook up with any XMLDB supporting XQJ. The only real showstopper at this moment is that i have no clue how I can avoid declaring a dependency on the XMLDB specific implementation. The XQJGenerator so far is 100% using only the interfaces but they are packaged with the implementation :-( I will address this issue with both Sedna and BaseX and see if someone can create seperate jar for interface and let them all seperate implementation code from the interface in 2 separate jars. If the interface would be available from Maven central would also be a big bonus. Keep you posted, Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 14:49 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in the dependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
RE: Using XQJ API with Cocoon3
Yes, it's an official JSR Specification available at http://www.jcp.org/en/jsr/detail?id=225 In the download section for the final 1.0 spec I could find the jar included in the zip. But i did try to find any XQJ jar in mvn repository and couldn't find one. Maybe we should upload the jar to a public maven repo ourselves? But what would be the group- and artifact id in that case? And it still leaves the issue that the implementations ship with the interface as well. Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 18:04 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby, rather a 'must to have' it is IMHO a 'very cool to have' ;) just a silly question - and please take in consideration that I'm not familiar with the XQuery world - isn't there a JSR specification? Many thanks in advance, have a nice day! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 5:20 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi Simone, as this is my last week before my holidays I don't think i will manage to get things really tested properly. But I look forward contributing input for this component as it really is a must-have if you want to hook up with any XMLDB supporting XQJ. The only real showstopper at this moment is that i have no clue how I can avoid declaring a dependency on the XMLDB specific implementation. The XQJGenerator so far is 100% using only the interfaces but they are packaged with the implementation :-( I will address this issue with both Sedna and BaseX and see if someone can create seperate jar for interface and let them all seperate implementation code from the interface in 2 separate jars. If the interface would be available from Maven central would also be a big bonus. Keep you posted, Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 14:49 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in the dependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers winmail.dat
RE: Using XQJ API with Cocoon3
I found out that Saxonica offers an XQJ implementation which allows you to use XQJ without the need to have an actual database up and running. There is a Saxon-HE version which has a Mozilla Public License. Does anyone have any idea if I could use this version together with Cocoon3 to write my unit tests? Kind regards, Robby -Oorspronkelijk bericht- Van: Robby Pelssers [mailto:robby.pelss...@ciber.com] Verzonden: di 5-7-2011 19:59 Aan: dev@cocoon.apache.org Onderwerp: RE: Using XQJ API with Cocoon3 Yes, it's an official JSR Specification available at http://www.jcp.org/en/jsr/detail?id=225 In the download section for the final 1.0 spec I could find the jar included in the zip. But i did try to find any XQJ jar in mvn repository and couldn't find one. Maybe we should upload the jar to a public maven repo ourselves? But what would be the group- and artifact id in that case? And it still leaves the issue that the implementations ship with the interface as well. Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 18:04 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby, rather a 'must to have' it is IMHO a 'very cool to have' ;) just a silly question - and please take in consideration that I'm not familiar with the XQuery world - isn't there a JSR specification? Many thanks in advance, have a nice day! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 5:20 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi Simone, as this is my last week before my holidays I don't think i will manage to get things really tested properly. But I look forward contributing input for this component as it really is a must-have if you want to hook up with any XMLDB supporting XQJ. The only real showstopper at this moment is that i have no clue how I can avoid declaring a dependency on the XMLDB specific implementation. The XQJGenerator so far is 100% using only the interfaces but they are packaged with the implementation :-( I will address this issue with both Sedna and BaseX and see if someone can create seperate jar for interface and let them all seperate implementation code from the interface in 2 separate jars. If the interface would be available from Maven central would also be a big bonus. Keep you posted, Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 14:49 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in the dependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers winmail.dat
Re: Using XQJ API with Cocoon3
Hi Robby, AFAIK 3rd parties MPL licensed can be included, see http://www.apache.org/legal/resolved.html HTH, have a nice day! All the best, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 9:57 PM, Robby Pelssers robby.pelss...@ciber.com wrote: I found out that Saxonica offers an XQJ implementation which allows you to use XQJ without the need to have an actual database up and running. There is a Saxon-HE version which has a Mozilla Public License. Does anyone have any idea if I could use this version together with Cocoon3 to write my unit tests? Kind regards, Robby -Oorspronkelijk bericht- Van: Robby Pelssers [mailto:robby.pelss...@ciber.com] Verzonden: di 5-7-2011 19:59 Aan: dev@cocoon.apache.org Onderwerp: RE: Using XQJ API with Cocoon3 Yes, it's an official JSR Specification available at http://www.jcp.org/en/jsr/detail?id=225 In the download section for the final 1.0 spec I could find the jar included in the zip. But i did try to find any XQJ jar in mvn repository and couldn't find one. Maybe we should upload the jar to a public maven repo ourselves? But what would be the group- and artifact id in that case? And it still leaves the issue that the implementations ship with the interface as well. Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 18:04 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby, rather a 'must to have' it is IMHO a 'very cool to have' ;) just a silly question - and please take in consideration that I'm not familiar with the XQuery world - isn't there a JSR specification? Many thanks in advance, have a nice day! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 5:20 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi Simone, as this is my last week before my holidays I don't think i will manage to get things really tested properly. But I look forward contributing input for this component as it really is a must-have if you want to hook up with any XMLDB supporting XQJ. The only real showstopper at this moment is that i have no clue how I can avoid declaring a dependency on the XMLDB specific implementation. The XQJGenerator so far is 100% using only the interfaces but they are packaged with the implementation :-( I will address this issue with both Sedna and BaseX and see if someone can create seperate jar for interface and let them all seperate implementation code from the interface in 2 separate jars. If the interface would be available from Maven central would also be a big bonus. Keep you posted, Robby -Oorspronkelijk bericht- Van: simone.trip...@gmail.com namens Simone Tripodi Verzonden: di 5-7-2011 14:49 Aan: dev@cocoon.apache.org Onderwerp: Re: Using XQJ API with Cocoon3 Hi Robby!!! as I wrote you on Twitter, this is something *really* interesting that must be included in the Cocoon distribution :) We can include that module quite easy, all you have to do is * checkout/update the C3 /trunk; * add needed dependencies in the dependenciesManagement in the /parent/pom.xml * add your code in the /cocoon-optional module in a proper package - see the existing codebase as samples how we already managed 3rd parties integrations * make a patch and submit it on JIRA Looking forward to hear from you soon, all the best!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers robby.pelss...@ciber.com wrote: Hi all, As Cocoon is an excellent framework for dealing with XML and hence in a lot of cases is stored in a XML Database it makes sense to offer out-of-the box functionality to extract data from it. From my personal experience I think most XMLDB implementers have abondoned the XMLDB API initiative and are focusing on XQuery for Java (XQJ) instead. I just started playing with the API today and wrote a bit of code to get more acquainted. I would like to start a little thread to find out if we can add a new XQJGenerator to the optional cocoon module. A first little exercise is mentioned on my blog but it's far from production ready. - TODO: allow wrapping query result in 1 root tag - Problem: the XQJ interface jar is packaged along with the implementations (Sedna, Exist, Marklogic). This means I had to actually declare a maven dependency on the implementation specific jar (in this case sedna-xqj-beta-5.jar). For the ones who think this would be a great add-on, check my first post at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3.html Kind regards, Robby Pelssers
