Menu
▾
▴
exist-development — eXist Developer's List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
| 2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
| 2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
| 2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
| 2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Adam R. <ad...@ex...> - 2010-08-12 14:39:45
|
9.1.0.8 is really an intermediate step until we can get 9.2 working
which I hope will be very soon...
On 12 August 2010 14:15, Joern Turner <joe...@go...> wrote:
> Yes, i have feared that.
>
> We get compile errors with Saxon 9.1.0.8. Seems we need to adapt
> first. So at least betterFORM ran one day in eXist :(
>
> Would be good to know where the journey goes. If 9.1.0.8 is now the
> decision or if we should go for 9.2 directly.
>
> Thanks
>
> On Wed, Aug 11, 2010 at 6:48 PM, Adam Retter <ad...@ex...> wrote:
>>> trunk/eXist/lib/user/saxon-9.0.jar
>>> trunk/eXist/lib/user/saxon-dom-9.0.jar
>>>
>>> Saxon jars should go in the endorsed directory, for the HE version only one
>>> jar file is required.
>>
>> eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
>> processor. We cannot yet switch to SaxonHE due to a bug in Saxon
>> regarding loading its edition.properties.
>>
>> Cheers Adam.
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Joern T. <joe...@go...> - 2010-08-12 14:32:02
|
Ok - don't worry - managed to make our code compile again against 9.1.0.8
On Thu, Aug 12, 2010 at 3:15 PM, Joern Turner
<joe...@go...> wrote:
> Yes, i have feared that.
>
> We get compile errors with Saxon 9.1.0.8. Seems we need to adapt
> first. So at least betterFORM ran one day in eXist :(
>
> Would be good to know where the journey goes. If 9.1.0.8 is now the
> decision or if we should go for 9.2 directly.
>
> Thanks
>
> On Wed, Aug 11, 2010 at 6:48 PM, Adam Retter <ad...@ex...> wrote:
>>> trunk/eXist/lib/user/saxon-9.0.jar
>>> trunk/eXist/lib/user/saxon-dom-9.0.jar
>>>
>>> Saxon jars should go in the endorsed directory, for the HE version only one
>>> jar file is required.
>>
>> eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
>> processor. We cannot yet switch to SaxonHE due to a bug in Saxon
>> regarding loading its edition.properties.
>>
>> Cheers Adam.
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>
|
|
From: Joern T. <joe...@go...> - 2010-08-12 13:15:46
|
Yes, i have feared that.
We get compile errors with Saxon 9.1.0.8. Seems we need to adapt
first. So at least betterFORM ran one day in eXist :(
Would be good to know where the journey goes. If 9.1.0.8 is now the
decision or if we should go for 9.2 directly.
Thanks
On Wed, Aug 11, 2010 at 6:48 PM, Adam Retter <ad...@ex...> wrote:
>> trunk/eXist/lib/user/saxon-9.0.jar
>> trunk/eXist/lib/user/saxon-dom-9.0.jar
>>
>> Saxon jars should go in the endorsed directory, for the HE version only one
>> jar file is required.
>
> eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
> processor. We cannot yet switch to SaxonHE due to a bug in Saxon
> regarding loading its edition.properties.
>
> Cheers Adam.
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
|
|
From: Joern T. <joe...@go...> - 2010-08-12 12:48:20
|
On Thu, Aug 12, 2010 at 2:46 PM, Adam Retter <ad...@ex...> wrote: >> At least James said Cocoon will be removed. We initially put the >> cocoon lib into our uninstall dir but skipped that after James' >> statement. We do not depend on it. We just depend on ehcache in a newer version that cocoon also uses. > > Cocoon is now an extension, so you should not depend on it - I would > recommend putting libs you need into lib/optional as you are > practically a core part of eXist now, i.e. you are not an extension - > or do I have that wrong? i fear yes ;) As a first step we are an extension. > >>> >>> trunk/eXist/lib/user/saxon-9.0.jar >>> trunk/eXist/lib/user/saxon-dom-9.0.jar >>> >>> Saxon jars should go in the endorsed directory, for the HE version only one >>> jar file is required. Would that work for betterforms> >>> the purpose of lib/user is to allow endusers to add new jar files. Other >>> files should go to lib/optional. >>> last: please add LICENSE.txt files for each jar file you add (see all other >>> jar files). WIth this we can estimate whether the license actually allows us >>> to include that jar file. >> Will do. >> >> Cheers, >> >> Joern >> >> >>> Kind regards >>> Dannes >>> -- >>> eXist-db Native XML Database - http://exist-db.org >>> Join us on linked-in: http://www.linkedin.com/groups?gid=35624 >>> >>> >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> > > > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb > |
|
From: Adam R. <ad...@ex...> - 2010-08-12 12:46:09
|
> At least James said Cocoon will be removed. We initially put the > cocoon lib into our uninstall dir but skipped that after James' > statement. Cocoon is now an extension, so you should not depend on it - I would recommend putting libs you need into lib/optional as you are practically a core part of eXist now, i.e. you are not an extension - or do I have that wrong? >> >> trunk/eXist/lib/user/saxon-9.0.jar >> trunk/eXist/lib/user/saxon-dom-9.0.jar >> >> Saxon jars should go in the endorsed directory, for the HE version only one >> jar file is required. Would that work for betterforms> >> the purpose of lib/user is to allow endusers to add new jar files. Other >> files should go to lib/optional. >> last: please add LICENSE.txt files for each jar file you add (see all other >> jar files). WIth this we can estimate whether the license actually allows us >> to include that jar file. > Will do. > > Cheers, > > Joern > > >> Kind regards >> Dannes >> -- >> eXist-db Native XML Database - http://exist-db.org >> Join us on linked-in: http://www.linkedin.com/groups?gid=35624 >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Adam R. <ad...@ex...> - 2010-08-12 12:45:02
|
Yes there is a problem in combining Saxon HE and eXist-db - I am
trying to investigate at the moment...
On 12 August 2010 13:39, Joern Turner <joe...@go...> wrote:
> Ok, let's pray and hope that does not break our function libraries.
>
> Btw, is there any specific reason why Saxon 9.2 is not used?
>
>
> On Thu, Aug 12, 2010 at 2:20 PM, Adam Retter <ad...@ex...> wrote:
>> I have removed the commons-io and saxon jars from lib/user as these
>> exist elsewhere in lib/**
>>
>> On 11 August 2010 17:48, Adam Retter <ad...@ex...> wrote:
>>>> trunk/eXist/lib/user/saxon-9.0.jar
>>>> trunk/eXist/lib/user/saxon-dom-9.0.jar
>>>>
>>>> Saxon jars should go in the endorsed directory, for the HE version only one
>>>> jar file is required.
>>>
>>> eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
>>> processor. We cannot yet switch to SaxonHE due to a bug in Saxon
>>> regarding loading its edition.properties.
>>>
>>> Cheers Adam.
>>>
>>>
>>> --
>>> Adam Retter
>>>
>>> eXist Developer
>>> { United Kingdom }
>>> ad...@ex...
>>> irc://irc.freenode.net/existdb
>>>
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Joern T. <joe...@go...> - 2010-08-12 12:40:00
|
Ok, let's pray and hope that does not break our function libraries.
Btw, is there any specific reason why Saxon 9.2 is not used?
On Thu, Aug 12, 2010 at 2:20 PM, Adam Retter <ad...@ex...> wrote:
> I have removed the commons-io and saxon jars from lib/user as these
> exist elsewhere in lib/**
>
> On 11 August 2010 17:48, Adam Retter <ad...@ex...> wrote:
>>> trunk/eXist/lib/user/saxon-9.0.jar
>>> trunk/eXist/lib/user/saxon-dom-9.0.jar
>>>
>>> Saxon jars should go in the endorsed directory, for the HE version only one
>>> jar file is required.
>>
>> eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
>> processor. We cannot yet switch to SaxonHE due to a bug in Saxon
>> regarding loading its edition.properties.
>>
>> Cheers Adam.
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>>
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
|
|
From: Joern T. <joe...@go...> - 2010-08-12 12:29:06
|
Hi Dannes, thanks for reviewing. It's just that i put our libs into lib/user due to the recommendations of James (Fuller). Before we move on it would be nice to first fix the final consensus of the team before moving things around. Sorry, no complaint - just want to avoid unnecessary or confusing steps. Please read on... On Wed, Aug 11, 2010 at 4:00 PM, Dannes Wessels <da...@ex...> wrote: > jar review: > > On 11 Aug 2010, at 13:52 , jo...@us... wrote: > > trunk/eXist/lib/user/commons-io-1.4.jar > > already in lib optional Ok, than this should obviously be removed > > trunk/eXist/lib/user/commons-lang-2.4.jar > > in cocooon/lib, promote to lib/optional ? > > trunk/eXist/lib/user/dwr-2.0.5.jar > > trunk/eXist/lib/user/ehcache-1.6.2.jar > > already in cocoon/lib, promote? Is this version compatible with the existing > older version of cocoon? Or will we remove cocoon right now? At least James said Cocoon will be removed. We initially put the cocoon lib into our uninstall dir but skipped that after James' statement. > > trunk/eXist/lib/user/saxon-9.0.jar > trunk/eXist/lib/user/saxon-dom-9.0.jar > > Saxon jars should go in the endorsed directory, for the HE version only one > jar file is required. Would that work for betterforms> > the purpose of lib/user is to allow endusers to add new jar files. Other > files should go to lib/optional. > last: please add LICENSE.txt files for each jar file you add (see all other > jar files). WIth this we can estimate whether the license actually allows us > to include that jar file. Will do. Cheers, Joern > Kind regards > Dannes > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > > > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > |
|
From: Adam R. <ad...@ex...> - 2010-08-12 12:23:00
|
Erm eh? So we use a different classloader for things in lib/endorsed then? This does not seem to be the case in the ant build script? On 12 August 2010 08:22, Dannes Wessels <da...@ex...> wrote: > Hi, > On 11 Aug 2010, at 23:22 , Manfred Staudinger wrote: > > 2 problems with the JAXP XPath API were raised in december and closed > in january with "fixed in 9.2.0.5" - so I honestly do not see any open > problem!?? > > Well adam encountered into a non working situation, so there is an issue, > right? > Maybe......... hm.. I think we should check what happens if we load > saxon.jar into another directory. lib/optional for example. That might solve > the issue... > Kind regards > Dannes > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > > > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Adam R. <ad...@ex...> - 2010-08-12 12:20:19
|
I have removed the commons-io and saxon jars from lib/user as these
exist elsewhere in lib/**
On 11 August 2010 17:48, Adam Retter <ad...@ex...> wrote:
>> trunk/eXist/lib/user/saxon-9.0.jar
>> trunk/eXist/lib/user/saxon-dom-9.0.jar
>>
>> Saxon jars should go in the endorsed directory, for the HE version only one
>> jar file is required.
>
> eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
> processor. We cannot yet switch to SaxonHE due to a bug in Saxon
> regarding loading its edition.properties.
>
> Cheers Adam.
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Chris W. <kit...@go...> - 2010-08-12 09:57:03
|
HMAC-SHA1 is a two parameter function taking a key and data. On Thu, Aug 12, 2010 at 11:14 AM, Dannes Wessels <da...@ex...>wrote: > please could you try algorithm "HmacSHA1" ? > > cheers > > Dannes > > On 12 Aug 2010, at 10:09 , Chris Wallace wrote: > > > but the core algorithm for the HMAC-SHA1 Signing algorithm is a local > perl script. We have util:hash/SHA-1 function (although the documentation > doesn't list the available hash algorithms yet) so the only bit missing is > the HMAC part. > > Kind regards > > Dannes > > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > > > > > > > > > |
|
From: Dannes W. <da...@ex...> - 2010-08-12 09:15:14
|
On 12 Aug 2010, at 10:09 , Chris Wallace wrote: > but the core algorithm for the HMAC-SHA1 Signing algorithm is a local perl script. We have util:hash/SHA-1 function (although the documentation doesn't list the available hash algorithms yet) so the only bit missing is the HMAC part. the util-hash function is a thin wrapper around the Java classes. If java has it available, it will be available in the function. The reason why the list of algorithms is not includes is.... each JVM is free to provide more/less algoritms. It is a local JVM thing, it gives potential issues if we are more precise. Maybe we can ask the JVM for a list these days Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Dannes W. <da...@ex...> - 2010-08-12 09:14:52
|
please could you try algorithm "HmacSHA1" ? cheers Dannes On 12 Aug 2010, at 10:09 , Chris Wallace wrote: > but the core algorithm for the HMAC-SHA1 Signing algorithm is a local perl script. We have util:hash/SHA-1 function (although the documentation doesn't list the available hash algorithms yet) so the only bit missing is the HMAC part. Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Chris W. <kit...@go...> - 2010-08-12 08:09:13
|
Now that Twitter is switching from Basic Authentication to OAuth, (and of course is currently used for LinkedIn and other apps) we need an implementation for eXist. Dan made a start (see the Wikibook) and Norm Walsh has an implementation in XQuery for ML : http://github.com/ndw/XQuery-OAuth but the core algorithm for the HMAC-SHA1 Signing algorithm is a local perl script. We have util:hash/SHA-1 function (although the documentation doesn't list the available hash algorithms yet) so the only bit missing is the HMAC part. Before I attempt a version myself (I need it for my boat tracking application - assuming we ever fix our engine!) , are there any other resources available to help with this implementation? Chris |
|
From: Dannes W. <da...@ex...> - 2010-08-12 07:22:59
|
Hi, On 11 Aug 2010, at 23:22 , Manfred Staudinger wrote: > 2 problems with the JAXP XPath API were raised in december and closed > in january with "fixed in 9.2.0.5" - so I honestly do not see any open > problem!?? Well adam encountered into a non working situation, so there is an issue, right? Maybe......... hm.. I think we should check what happens if we load saxon.jar into another directory. lib/optional for example. That might solve the issue... Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Manfred S. <man...@gm...> - 2010-08-11 21:22:56
|
On 11/08/2010, Dannes Wessels <da...@ex...> wrote: > Yes similar issues, same file, Jaxp related: early november 2009. > > On Wed, Aug 11, 2010 at 10:15 PM, Dannes Wessels <da...@ex...> > wrote: >> I reported the issue to Mr Kay some time ago. Maybe one was "Failed to load configuration defined in edition.properties - ID: 2910299" http://sourceforge.net/tracker/?func=detail&aid=2910299&group_id=29872&atid=397617 which was closed "invalid" last december. 2 problems with the JAXP XPath API were raised in december and closed in january with "fixed in 9.2.0.5" - so I honestly do not see any open problem!?? Regards, Manfred |
|
From: Dannes W. <da...@ex...> - 2010-08-11 20:18:34
|
Yes similar issues, same file, Jaxp related: early november 2009. On Wed, Aug 11, 2010 at 10:15 PM, Dannes Wessels <da...@ex...> wrote: > I reported the issue to Mr Kay some time ago. > cheers -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Dannes W. <da...@ex...> - 2010-08-11 20:15:38
|
I reported the issue to Mr Kay some time ago. cheers Dannes On 11 Aug 2010, at 21:39 , Manfred Staudinger wrote: > I did not find an open issue with these symptons - do you have a bug > id for the tracker? > http://sourceforge.net/tracker/?group_id=29872 Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Manfred S. <man...@gm...> - 2010-08-11 19:39:49
|
On 11/08/2010, Adam Retter <ad...@ex...> wrote: > Unfortunately we are stuck with Saxon-B for the time being because > there is a bug in Saxon-HE 9.2.1.2 with regards to how it attempts to > load an internal properties file (edition.properties) as part of its > configuration. Hopefully this will be fixed soon and we can move to > Saxon HE. This issue manifests when using Ant xslt task or running > AllConcurrentTests in the eXist-db test suite. I did not find an open issue with these symptons - do you have a bug id for the tracker? http://sourceforge.net/tracker/?group_id=29872 Regards, Manfred |
|
From: Joe W. <jo...@gm...> - 2010-08-11 18:20:34
|
> eXist-db trunk has now been switched to provide XSLT 2.0 from Saxon by > default out of the box. This was Subversion revision 12387. Many thanks, Adam! > On 10 August 2010 08:44, Stefan Majewski <ste...@un...> wrote: >> +1 ; but also much in favour of eXists native implementation. I think >> switching for saxon as the current default does in no way imply that work on >> native xslt should be abandoned. I second Stefan here. Joe |
|
From: Adam R. <ad...@ex...> - 2010-08-11 16:54:47
|
> trunk/eXist/lib/user/saxon-9.0.jar
> trunk/eXist/lib/user/saxon-dom-9.0.jar
>
> Saxon jars should go in the endorsed directory, for the HE version only one
> jar file is required.
eXist-db trunk now ships with Saxon-B 9.1.0.8 as the default XSLT
processor. We cannot yet switch to SaxonHE due to a bug in Saxon
regarding loading its edition.properties.
Cheers Adam.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Adam R. <ad...@ex...> - 2010-08-11 16:53:20
|
eXist-db trunk has now been switched to provide XSLT 2.0 from Saxon by
default out of the box. This was Subversion revision 12387.
Unfortunately we are stuck with Saxon-B for the time being because
there is a bug in Saxon-HE 9.2.1.2 with regards to how it attempts to
load an internal properties file (edition.properties) as part of its
configuration. Hopefully this will be fixed soon and we can move to
Saxon HE. This issue manifests when using Ant xslt task or running
AllConcurrentTests in the eXist-db test suite.
Thanks Adam.
On 10 August 2010 08:44, Stefan Majewski <ste...@un...> wrote:
> On 07/08/10 13:34, Dannes Wessels wrote:
>>
>> -1 ; i'd like to see the native implementation working :-/
>
> +1 ; but also much in favour of eXists native implementation. I think
> switching for saxon as the current default does in no way imply that work on
> native xslt should be abandoned.
>
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: James F. <jam...@ex...> - 2010-08-11 15:00:48
|
Hello All, After discussing with Wolfgang et al and to prepare for upcoming releases (I have no timings on releases, this is just preliminary work) I will be marking bugs from 2009 and earlier as 'out of date' and then will be 'closing' them in a few weeks or so. All developers 'own' the bug list and if a bug that has been marked 'out of date' is important to you then mark its resolution appropriately (accepted/fixed/etc...). If you are a user and see that a bug report you submitted has been marked 'out of date' speak up and we will switch it to appropriate resolution. All bug reports are valuable but as time moves on and a bug remains on the list a few things happen: * architecture changes with successive releases, sometimes meaning the bug is not relevant anymore (sometimes this even results in the bug being fixed!) * if the bug has been around for a few years (as many have been) then it is either too hard too fix or not so critical for the mass of users ... this may not be the case, especially if one has spent a lot of time and effort contributing a patch or identifying bug, which is why I ask for developers and users to respond appropriately if they see a bug that is near/dear to them to switch resolution * some bugs may have actually been fixed but waiting on confirmation, this is a 'nudge' towards getting people to confirm Why are we doing this ? * general house cleaning e.g. we can't let this list continue to grow ad infinitum with actively managing it * focus resources on current issues to be more responsive to end user demands * to be more flexible when new potential developers submit patches and bug reports ... instead of making them wait * remember switching to 'out of date' does not mean we lose bug information ever (nor closing them) Thanks once again to all our bug submitters who have provided patches and reports in the past ... its had a real positive effect on eXist stability and operation and we hope by doing this 'housecleaning' that your future reports will be responded to more quickly by making sure we actively manage the bug list more from here on out. James Fuller |
|
From: Dannes W. <da...@ex...> - 2010-08-11 14:00:23
|
jar review: On 11 Aug 2010, at 13:52 , jo...@us... wrote: > trunk/eXist/lib/user/commons-io-1.4.jar already in lib optional > trunk/eXist/lib/user/commons-lang-2.4.jar in cocooon/lib, promote to lib/optional ? > trunk/eXist/lib/user/dwr-2.0.5.jar > trunk/eXist/lib/user/ehcache-1.6.2.jar already in cocoon/lib, promote? Is this version compatible with the existing older version of cocoon? Or will we remove cocoon right now? > trunk/eXist/lib/user/saxon-9.0.jar > trunk/eXist/lib/user/saxon-dom-9.0.jar Saxon jars should go in the endorsed directory, for the HE version only one jar file is required. Would that work for betterforms> the purpose of lib/user is to allow endusers to add new jar files. Other files should go to lib/optional. last: please add LICENSE.txt files for each jar file you add (see all other jar files). WIth this we can estimate whether the license actually allows us to include that jar file. Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Wolfgang M. <wol...@ex...> - 2010-08-11 13:14:07
|
I just checked the latest betterform integration in trunk. It works well out of the box. I also tried to migrate some of my own examples and found a few issues. Most important, the XForms filter seems to be applied *before* eXist's URL rewrite filter. I often use XQueryURLRewrite to transform an XML document into HTML, which would then contain XForms markup. The XForms filter should thus be applied *after* the URL rewrite filter. I tried switching both and it seemed to work - basically. However, the HTML was messed up when first passing an XML through my docbook stylesheets. I need more time to see what's wrong. > 2. Is there any plan for a generic error-page? We have one that is > implemented in xquery but that's specific for our needs (Though it > should not be hard to adapt for the more generic case) and is > configured via the standard <error-page> element in web.xml. This > works for our eXist / betterFORM bundling but of course is not > appropriate for integration in eXist as its now triggered for every > error occuring in eXist. I will add a feature to specify a generic error-page in the controller.xql. This will allow different error handlers to be configured for different directories/collections/requests. Wolfgang |
64 messages has been excluded from this view by a project administrator.
