Re: [basex-talk] RestXQ parameter matching

2013-02-27 Thread Marco Lettere
Hello, I'd like to add just my two cents to the discussion. We have to implement a specification called hData that stores healthcare data in document oriented way. The specs organizes the documents in a tree structure based on record/section/subsection/subsection/... where subsections can be

[basex-talk] Address already in use

2013-02-27 Thread McDonald, Shaun
Thank you, both. I've dealt with that error, and now the browser just loads indefinitely. The http server's listening on 8984 and configured to stop on 8985. The db server is on 1984. Forgive me, I'm a link architect doing a POC without system support. It's been a while since I've had to

Re: [basex-talk] Address already in use

2013-02-27 Thread Ludovic Kuty
Here it is. I've just customized the paths to where BaseX is installed. # BaseX Property File. # General Options DBPATH = /Users/ludo/Applications/basex/data REPOPATH = /Users/ludo/Applications/basex/repo DEBUG = false LANG = English LANGKEYS = false # Client/Server Architecture HOST =

Re: [basex-talk] RestXQ parameter matching

2013-02-27 Thread Wendell Piez
Hi again, Yes, as I understand it Marco's request is the complementary opposite of mine, where in repository/{$path}/resource $path could match not only a path segment, but an arbitrary sequence of segments (which can be decomposed by the function when need be). Because it matches on

Re: [basex-talk] RestXQ parameter matching

2013-02-27 Thread Liam R E Quin
On Wed, 2013-02-27 at 10:58 -0500, Wendell Piez wrote: Because it matches on substrings not path segments, Apache Cocoon can do this and indeed it's very powerful. This is an area where I once tried to push for some standardization, and I still think defining a portable mechanism to map

Re: [basex-talk] RestXQ parameter matching

2013-02-27 Thread Marco Lettere
Yep, you got it exactly the right way. We are struggling to find a possible solution to that but still no way out and I think that together with yours the questions may converge into a more general restxq path flexibility issue. M. On 02/27/2013 04:58 PM, Wendell Piez wrote: Hi again, Yes,

Re: [basex-talk] Address already in use

2013-02-27 Thread McDonald, Shaun
Thanks, Ludovic. And many thanks to all three, whose assistance has helped me get the REST working! Cheers, Shaun -- Message: 1 Date: Wed, 27 Feb 2013 08:57:25 -0500 From: McDonald, Shaun shaun.mcdon...@oup.com To:

Re: [basex-talk] issuing XQuery via basex command line

2013-02-27 Thread Christian Grün
Dear Jonathan, please take your time and give us some more details on what you did; otherwise, it will be difficult for us to guess what you are fighting with. 1.Any ideas? Is this a limitation or a bug? I have not looked through the source code yet. See above ;) 2.Is there any way

Re: [basex-talk] RestXQ parameter matching

2013-02-27 Thread Christian Grün
Hi Marco, one way to circumvent this limitation is to specify a module with some default RESTXQ paths that only contain templates: declare function ... %restxq:path({$a}) ... { do($a) } declare function ... %restxq:path({$a}/{$b}) ... { do($a || '/' || $b) } declare function ...