Re: [Exist-open] First comments on the packaging support

[James F. <jam...@ex...>]

On 31 July 2010 20:13, Florent Georges <li...@fg...> wrote:
>  Hi,
>
>  Here are a first couple of comments about the packaging support
> in eXist.
>
>  1/ The prefix repo is statically bound to the eXist module
> namespace for repo management, http://exist-db.org/xquery/repo.
> This is not an error of course, I am just not sure that was
> intended.

this is a work in progress ;) things will change once we have hot
module loading in place

>
>  2/ The page http://localhost:8080/exist/repo/repo.xml contains
> a typo in the first example: the FunctX namespace is bound to the
> prefix repo, but the function call uses the prefix functx.
> Besides, the error msg is "prefix already bound" due to 1/.

svn update, latest typo fixed

>
>  3/ I didn't have to enable anything explicitely in order to use
> the repo module as well as to get the import statements resolved
> into the repository.  That is perfectly find for me, but I guess
> you prefer to have people enabling them explicitely in a first
> time.

like I said svn update ... there is a webapp/repo/packages directory
and links (with controller.xq) that does one click install/remove

>  For the later point I thought about runtime config, but I've
> just seen in http://localhost:8080/exist/repo/repo.xml that I
> should have set include.module.expathrepo = true at build time,
> which I did not.

svn update ... its part of core now and should just happen automagically

>  4/ The section 2 in the documentation (page repo.xml, at above
> URI) contains two example boxes, but the second one is empty.
>
>  5/ I am not sure this is a good idea to ship external packages
> directly in eXist.  I say I am not sure because I am really not.
> On the + side people have them directly at hand, and they have
> been tested with eXist, on the - side there are chance that they
> become obsolete quite soon...  Maybe the correct solution is to
> point directly to their respective project websites, or to CXAN
> (but yes I know, I would then have to update it first, that's
> probably a good opportunity :-) ).

of course, needed to have some examples though and the examples on
cxan use old namespace

ta, J

>
>  6/ Still on the same page (repo.xml), EXPath is spelt e few
> times Expath.  A detail really, but I think it is good to keep
> consistent, and use either EXPath or expath, depending on the
> usage.
>
>  7/ The repo module itself is very interesting.  I hesitated to
> include such a module in the spec itself.  I think having a first
> implementation (in a vendor-specific module) is very interesting
> to see what we can do.  The problem I can see is, if I am right,
> eXist needs to be restarted (that was actually why I did not
> include such functions in the spec), preventing the same script
> to install and then use the package (even though that not a big
> limitation).  But I think it will be interesting to standardize
> those functions, in order to be able to build nice portable
> repository management interfaces, as well as higher-order
> applications using a repository, like web application frameworks
> for instance.
>
>  Thanks again for you efforts,
>
> --
> Florent Georges
> http://fgeorges.org/
>
>
>
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>