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: Joe W. <jo...@gm...> - 2011-08-07 17:43:09
|
Hi all, On 6 Aug 2011, at 10:34 , Wolfgang Meier wrote: > I noticed the same issue of whitespace being lost. An update would be great. On Sat, Aug 6, 2011 at 5:12 AM, Dannes Wessels <da...@ex...> wrote: > sure, let's do it. I'd like to propose a to step thing…. > (1) just upgrade to 0.9 Okay, I've updated trunk to 0.9 in rev. 15092. See http://exist.svn.sourceforge.net/exist/?rev=15092&view=rev. For those who want to test/try tika 0.9: Note that if you have a local.build.properties, you'll need to update yours to match the new URL for 0.9 in the build.properties file I just committed. > (2) I'll split into jars, so we avoid double class entries > my question….. is there a (small) test case I can run, to show that the > stuff is still working? remote parse of a document or so…. Sounds good! As to your question, I tried creating a small test along these lines but encountered a problem -- apparently in the httpclient? The script downloads a PDF and parses it, but returns no text on each of the 35 pages - no error, but no text. If, instead, I read the same PDF from the database, tika returns all of the text. Strange! Here is my test script: === xquery version "1.0"; import module namespace content=" http://exist-db.org/xquery/contentextraction" at "java:org.exist.contentextraction.xquery.ContentExtractionModule"; declare namespace httpclient = "http://exist-db.org/xquery/httpclient"; let $uri := 'http://webcomposite.com/resource/pdf/x-advxquery-pdf.pdf' let $response := httpclient:get(xs:anyURI($uri), false(), ()) let $pdf := util:string-to-binary(util:base64-decode($response/httpclient:body/string())) let $content := content:get-metadata-and-content($pdf) return $content === The content returned is as follows: <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta name="xmpTPg:NPages" content="35"/> <meta name="Type" content="COSName{Info}"/> <meta name="producer" content="null"/> <meta name="Content-Type" content="application/pdf"/> <title/> </head> <body> <div class="page"> <p/> </div> <div class="page"> <p/> </div> (and so on for 35 divs.) But if I download the PDF and put it in the database and read from the database, the query returns with the expected results: === xquery version "1.0"; import module namespace content=" http://exist-db.org/xquery/contentextraction" at "java:org.exist.contentextraction.xquery.ContentExtractionModule"; let $pdf := util:binary-doc('/db/x-advxquery-pdf.pdf') let $content := content:get-metadata-and-content($pdf) return $content === The returned content is as follows: <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta name="xmpTPg:NPages" content="35"/> <meta name="Type" content="COSName{Info}"/> <meta name="producer" content="null"/> <meta name="Content-Type" content="application/pdf"/> <title/> </head> <body> <div class="page"> <p>Advancing with XQuery: Develop application idioms Work with extension functions, unit tests and assertions, recursion and sorting, and higher-order functions Skill Level: Intermediate James R. Fuller ( jim...@we...) Technical Director FlameDigital Limited & Webcomposite s.r.o. 30 Sep 2008 The XQuery specification is well over a year old now. A surfeit of solid implementations combined with (if developer chatter is anything to go by) marked new interest, seems to indicate that XQuery is finally experiencing higher adoption rates. Possibly this is due to developers starting to figure out how to utilize XQuery within a rich mixture of XML technologies (such as XML databases. XSLT, XML Schema). Learn how to use XQuery beyond its original role as an XML query language and apply it toward the development of middleware and Web applications. Section 1. Before you start Before you examine XQuery code samples, here's how to get the most of this tutorial, and instructions on how to install and use the included source code (see Downloads). About this tutorial This tutorial is about using XQuery to develop applications and middleware. It outlines some of XQuery's limitations while you develop applications, gives you Advancing with XQuery: Develop application idioms © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 35</p> </div> (and so on for 35 pages.) I'm not sure what is causing the httpclient version of this script to fail. But if we can get it to work, it could be the basis of a test, along the lines of what Dannes requested. Cheers, Joe |
From: Dannes W. <da...@ex...> - 2011-08-07 14:31:18
|
On 7 Aug 2011, at 16:18 , Wolfgang Meier wrote: > > You can still get some 500's, if you click Adam's Akismet and Asirra links in the sidebar (the articles are shown nicely in the default search). The worst thing is, I think clicking these links (or perhaps some other links) brings down the server (or at least occupies it intensively, leading to timeouts). Sorry! > > I think the 500 is caused by a module caching bug. We'll need to update to 1.4.x. I'll try to do that today, so we have a stable wiki for release. > > currently finishing the 1.4.1 works….. will release a 'rc' this afternoon. D. -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org |
From: Wolfgang M. <wol...@ex...> - 2011-08-07 14:19:04
|
> You can still get some 500's, if you click Adam's Akismet and Asirra links in the sidebar (the articles are shown nicely in the default search). The worst thing is, I think clicking these links (or perhaps some other links) brings down the server (or at least occupies it intensively, leading to timeouts). Sorry! I think the 500 is caused by a module caching bug. We'll need to update to 1.4.x. I'll try to do that today, so we have a stable wiki for release. > - - I know you are busy now doing others things, but for others Sunday is time for poking around! And for thinking that it is a shame that this module has been allowed to languish since 2009. I started migrating the whole interface into an app package, but I'll need an idle weekend to finish it (and i normally don't have any ;-). Wolfgang |
From: Jens Ø. P. <oe...@gm...> - 2011-08-07 13:56:43
|
Yeah, '500' - I used Joe's mail because the message was the exact same. You can still get some 500's, if you click Adam's Akismet and Asirra links in the sidebar (the articles are shown nicely in the default search). The worst thing is, I think clicking these links (or perhaps some other links) brings down the server (or at least occupies it intensively, leading to timeouts). Sorry! - - I know you are busy now doing others things, but for others Sunday is time for poking around! And for thinking that it is a shame that this module has been allowed to languish since 2009. Cheers all the same, Jens PS: After timeouts, now it is down again: HTTP ERROR: 500 An error occurred while executing the urlrewrite query: error found while loading module atom: IO exception while loading module 'http://www.w3.org/2005/Atom' from 'file:/home/existdb/atomic.exist-db.org/AtomicWiki/xquery/src/org/exist/atomic/atom.xql' RequestURI=/blogs/eXist/AkismetAPI Powered by Jetty:// and HTTP ERROR: 500 An error occurred: Failed to read query from dispatcher.xql RequestURI=/blogs/eXist/ Powered by Jetty:// On Aug 7, 2011, at 2:35 PM, Dannes Wessels wrote: > > On 7 Aug 2011, at 13:41 , Jens Østergaard Petersen wrote: > >> Down again? > > > It isn;t for me….. same '500' ? > > cheers > > Dannes > > -- > Dannes Wessels > eXist-db Open Source Native XML Database > e: da...@ex... > w: http://www.exist-db.org > > > > > > |
From: Jens Ø. P. <oe...@gm...> - 2011-08-07 12:43:34
|
Now it isn't: Leif-Jöran must have started it again …. Take care, Jens On Aug 7, 2011, at 2:35 PM, Dannes Wessels wrote: > > On 7 Aug 2011, at 13:41 , Jens Østergaard Petersen wrote: > >> Down again? > > > It isn;t for me….. same '500' ? > > cheers > > Dannes > > -- > Dannes Wessels > eXist-db Open Source Native XML Database > e: da...@ex... > w: http://www.exist-db.org > > > > > > |
From: Dannes W. <da...@ex...> - 2011-08-07 12:35:14
|
On 7 Aug 2011, at 13:41 , Jens Østergaard Petersen wrote: > Down again? It isn;t for me….. same '500' ? cheers Dannes -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org |
From: Jens Ø. P. <oe...@gm...> - 2011-08-07 11:41:42
|
Down again? Jens On Dec 16, 2010, at 3:05 AM, Joe Wicentowski wrote: > http://atomic.exist-db.org/blogs/eXist/ > > => > > HTTP ERROR: 500 > > An error occurred while executing the urlrewrite query: error found > while loading module atom: IO exception while loading module > 'http://www.w3.org/2005/Atom' from > 'file:/home/existdb/atomic.exist-db.org/AtomicWiki/xquery/src/org/exist/atomic/atom.xql' > RequestURI=/blogs/eXist/ > > Powered by Jetty:// > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
From: Dannes W. <di...@ex...> - 2011-08-06 15:34:18
|
It's only what I read here :) Sent from my iPhone On 6 aug. 2011, at 12:04, Adam Retter <ad...@ex...> wrote: > Why slower? Maven 3 builds eXist-db for me significantly faster than Ant. |
From: Adam R. <ad...@ex...> - 2011-08-06 10:04:41
|
On 6 August 2011 10:14, Dannes Wessels <da...@ex...> wrote: > > On 6 Aug 2011, at 7:41 , Joe Wicentowski wrote: > > Looks like there's a discussion about improving dependency management in > Tika: > > https://issues.apache.org/jira/browse/TIKA-686 > > Maybe this will be helpful for you, or is something you think is worth > weighing in on if this still bugs you? > > :-) it is good to see there are discussions, but it is funny it immediately > end up in a maven discussion and slow build performance :-) Why slower? Maven 3 builds eXist-db for me significantly faster than Ant. > -- > Dannes Wessels > eXist-db Open Source Native XML Database > e: da...@ex... > w: http://www.exist-db.org > > > > > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > 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: Dannes W. <da...@ex...> - 2011-08-06 09:12:39
|
Hi On 6 Aug 2011, at 10:34 , Wolfgang Meier wrote: > I noticed the same issue of whitespace being lost. An update would be great. sure, let's do it. I'd like to propose a to step thing…. (1) just upgrade to 0.9 (2) I'll split into jars, so we avoid double class entries my question….. is there a (small) test case I can run, to show that the stuff is still working? remote parse of a document or so…. cheers Dannes -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org |
From: Dannes W. <da...@ex...> - 2011-08-06 08:37:26
|
heho, On 6 Aug 2011, at 10:14 , Dannes Wessels wrote: > :-) it is good to see there are discussions, but it is funny it immediately end up in a maven discussion and slow build performance :-) The way the Tika project works keeps surprising me……. anyway, I got the sources, ran the build etc etc. In the end the file tika-bundle/target/tika-bundle-0.9.jar shows what is actually needed ; the thirdpary jar files are there individually bundled. The next step is then identify the actual dependancies, and have them downloaded with our 'fetch' ant task. (*) need some attention Archive: tika-bundle/target/tika-bundle-0.9.jar testing: apache-mime4j-0.6.jar OK testing: asm-3.1.jar OK testing: bcmail-jdk15-1.45.jar OK testing: bcprov-jdk15-1.45.jar OK testing: boilerpipe-1.1.0.jar OK (*) testing: commons-compress-1.1.jar OK (*) testing: dom4j-1.6.1.jar OK testing: fontbox-1.4.0.jar OK testing: jempbox-1.4.0.jar OK testing: metadata-extractor-2.4.0-beta-1.jar OK testing: netcdf-4.2-min.jar OK testing: pdfbox-1.4.0.jar OK testing: poi-3.7.jar OK testing: poi-ooxml-3.7.jar OK testing: poi-ooxml-schemas-3.7.jar OK testing: poi-scratchpad-3.7.jar OK testing: rome-0.9.jar OK testing: tagsoup-1.2.jar OK (*) testing: xmlbeans-2.3.0.jar OK I wonder if this list is complete, I am sure there was this log-framework dependancy……. in 0,8 ? D. -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org |
From: Wolfgang M. <wol...@ex...> - 2011-08-06 08:34:37
|
Hi, I noticed the same issue of whitespace being lost. An update would be great. Wolfgang Am 06.08.2011 06:16 schrieb "Joe Wicentowski" <jo...@gm...>: > Hi all, > > Tika 0.8 suffers from a well-documented problem, in which spaces are > stripped from PDF content [1]. This problem was fixed in 0.9 [2], > which was released back in February. Since eXist 1.5dev trunk > contains 0.8, I experienced this problem where extracted PDF text had > no spaces. When I replaced the 0.8 jar with 0.9, the problem was > gone. I was using content:get-metadata-and-content() to extract text > from a PDF file stored in the db. I experienced the problem with both > PDFs I tested under 0.8. > > I'd suggest that we update to 0.9. I'd be happy to update trunk if > the core devs give me the heads up, if it would help [3], but perhaps > there are other considerations here I'm not aware of. Thoughts? > > Cheers, > Joe > > [1] https://issues.apache.org/jira/browse/TIKA-548 > [2] http://www.apache.org/dist/tika/CHANGES-0.9.txt > [3] http://tika.apache.org/download.html > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
From: Dannes W. <da...@ex...> - 2011-08-06 08:14:28
|
On 6 Aug 2011, at 7:41 , Joe Wicentowski wrote: > Looks like there's a discussion about improving dependency management in Tika: > > https://issues.apache.org/jira/browse/TIKA-686 > > Maybe this will be helpful for you, or is something you think is worth > weighing in on if this still bugs you? :-) it is good to see there are discussions, but it is funny it immediately end up in a maven discussion and slow build performance :-) D. -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org |
From: Dannes W. <da...@ex...> - 2011-08-06 08:11:41
|
Hi Joe, I guess you can upgrade, but there might be some conflicts with the 'embedded' third party classes embedded in tika.jar ; I had on my plan to investigate some time here, but well……. :-) D. On 6 Aug 2011, at 6:15 , Joe Wicentowski wrote: > I'd suggest that we update to 0.9. I'd be happy to update trunk if > the core devs give me the heads up, if it would help [3], but perhaps > there are other considerations here I'm not aware of. Thoughts? -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org |
From: Joe W. <jo...@gm...> - 2011-08-06 05:41:29
|
Hi Dannes, Looks like there's a discussion about improving dependency management in Tika: https://issues.apache.org/jira/browse/TIKA-686 Maybe this will be helpful for you, or is something you think is worth weighing in on if this still bugs you? Cheers, Joe On Tue, Jul 19, 2011 at 2:43 PM, Dannes Wessels <da...@ex...> wrote: > yes, somehow Tika decided to include all 3rd party libs in their own > library..... > brrrrrrrrr > If Tika is to stay (is it?) I'll waste some time in splitting the download a > bit. The documentation of the project is not very strong however...... |
From: Joe W. <jo...@gm...> - 2011-08-06 04:16:16
|
Hi all, Tika 0.8 suffers from a well-documented problem, in which spaces are stripped from PDF content [1]. This problem was fixed in 0.9 [2], which was released back in February. Since eXist 1.5dev trunk contains 0.8, I experienced this problem where extracted PDF text had no spaces. When I replaced the 0.8 jar with 0.9, the problem was gone. I was using content:get-metadata-and-content() to extract text from a PDF file stored in the db. I experienced the problem with both PDFs I tested under 0.8. I'd suggest that we update to 0.9. I'd be happy to update trunk if the core devs give me the heads up, if it would help [3], but perhaps there are other considerations here I'm not aware of. Thoughts? Cheers, Joe [1] https://issues.apache.org/jira/browse/TIKA-548 [2] http://www.apache.org/dist/tika/CHANGES-0.9.txt [3] http://tika.apache.org/download.html |
From: Dannes W. <da...@ex...> - 2011-08-04 06:34:07
|
Hi, 2011/8/4 Василий Старцев <wst...@gm...>: > I try to pack some collection. I use this: compression:zip(("xmldb:exist:///db/main/"),true()) > or compression:zip(("/db/main/main.html"),true()) and it return exception. > Are used 1 parameter is not correctly URI? you might want to have a look at https://secure.wikimedia.org/wikibooks/en/wiki/XQuery/Get_zipped_XML_file or hava a look at the expath package.... cheers Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Василий С. <wst...@gm...> - 2011-08-04 00:33:24
|
I try to pack some collection. I use this: *compression:zip*(( "xmldb:exist:///db/main/"),*true*()) or *compression:zip*(( "/db/main/main.html"),*true*()) and it return exception. Are used 1 parameter is not correctly URI? -- С наилучшими пожеланиями Василий Старцев |
From: Joern T. <joe...@go...> - 2011-08-03 11:15:19
|
Hi, ehcache is already present in eXist - at least in the betterFORM extension. But i think it's not yet used elsewhere in eXist. Joern 2011/8/3 Вячеслав Седов <sch...@gm...>: > hi, > > anyone here seen this? - http://www.ehcache.org/ > > "Ehcache is an open source, standards-based cache used to boost > performance, offload the database and simplify scalability. Ehcache is > robust, proven and full-featured and this has made it the most > widely-used Java-based cache." > > to my mind it look nice > > with best wishes, > Slav > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
From: Вячеслав С. <sch...@gm...> - 2011-08-03 10:52:21
|
hi, anyone here seen this? - http://www.ehcache.org/ "Ehcache is an open source, standards-based cache used to boost performance, offload the database and simplify scalability. Ehcache is robust, proven and full-featured and this has made it the most widely-used Java-based cache." to my mind it look nice with best wishes, Slav |
From: Patrick B. <pat...@jo...> - 2011-07-21 15:13:46
|
Ok, can you direct me to more information on this design? I'm happy to incorporate it. On Thu, Jul 21, 2011 at 5:50 AM, Adam Retter <ad...@ex...> wrote: > In the new design I proposed for trunk there were separate functions > for node level update vs document update. > > On 21 July 2011 03:10, Patrick Bosek <pat...@jo...> wrote: > > Hi Everyone, > > > > I've recently realized that the UPDATE_DOCUMENT_EVENT trigger is called > when > > ever a node level update is run (ie: update insert $blah into $blaher) is > > run from an XQuery. This can cause several problems, mostly with > versioning > > and efficiency. I didn't think this was the intended behavior, if I refer > to > > Wolfgang's statements from an older thread: > > > > "Yes. The versioning trigger is not enabled for node level updates. > > Creating a new revision for every small update would be overkill." > > > > I have a proposal that I think solves everyone's needs, and since I've > > already done a good bit of work with the triggers in the trunk (mostly > just > > allowing multiple triggers for a single event), I'm happy to implement it > if > > we can agree it's the correct path. > > > > I think we should simply add another event > > ("XQUERY_MODIFICATION_DOCUMENT_EVENT" perhaps?). This way we can still > react > > to node level updates when we want to, but not be forced to when we only > > want to consider updates from an xmldb:store(). > > > > Thoughts? > > > > > > Cheers, > > > > -- > > Patrick Bosek > > Jorsek Software > > Cell (585) 820 9634 > > Office (877) 492 2960 > > Jorsek.com > > > > > > > ------------------------------------------------------------------------------ > > 5 Ways to Improve & Secure Unified Communications > > Unified Communications promises greater efficiencies for business. UC can > > improve internal communications as well as offer faster, more efficient > ways > > to interact with customers and streamline customer service. Learn more! > > http://www.accelacomm.com/jaw/sfnl/114/51426253/ > > _______________________________________________ > > 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 > -- Patrick Bosek Jorsek Software Cell (585) 820 9634 Office (877) 492 2960 Jorsek.com |
From: Adam R. <ad...@ex...> - 2011-07-21 09:51:09
|
In the new design I proposed for trunk there were separate functions for node level update vs document update. On 21 July 2011 03:10, Patrick Bosek <pat...@jo...> wrote: > Hi Everyone, > > I've recently realized that the UPDATE_DOCUMENT_EVENT trigger is called when > ever a node level update is run (ie: update insert $blah into $blaher) is > run from an XQuery. This can cause several problems, mostly with versioning > and efficiency. I didn't think this was the intended behavior, if I refer to > Wolfgang's statements from an older thread: > > "Yes. The versioning trigger is not enabled for node level updates. > Creating a new revision for every small update would be overkill." > > I have a proposal that I think solves everyone's needs, and since I've > already done a good bit of work with the triggers in the trunk (mostly just > allowing multiple triggers for a single event), I'm happy to implement it if > we can agree it's the correct path. > > I think we should simply add another event > ("XQUERY_MODIFICATION_DOCUMENT_EVENT" perhaps?). This way we can still react > to node level updates when we want to, but not be forced to when we only > want to consider updates from an xmldb:store(). > > Thoughts? > > > Cheers, > > -- > Patrick Bosek > Jorsek Software > Cell (585) 820 9634 > Office (877) 492 2960 > Jorsek.com > > > ------------------------------------------------------------------------------ > 5 Ways to Improve & Secure Unified Communications > Unified Communications promises greater efficiencies for business. UC can > improve internal communications as well as offer faster, more efficient ways > to interact with customers and streamline customer service. Learn more! > http://www.accelacomm.com/jaw/sfnl/114/51426253/ > _______________________________________________ > 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: Patrick B. <pat...@jo...> - 2011-07-21 01:10:27
|
Hi Everyone, I've recently realized that the UPDATE_DOCUMENT_EVENT trigger is called when ever a node level update is run (ie: update insert $blah into $blaher) is run from an XQuery. This can cause several problems, mostly with versioning and efficiency. I didn't think this was the intended behavior, if I refer to Wolfgang's statements from an older thread: "Yes. The versioning trigger is not enabled for node level updates. Creating a new revision for every small update would be overkill." I have a proposal that I think solves everyone's needs, and since I've already done a good bit of work with the triggers in the trunk (mostly just allowing multiple triggers for a single event), I'm happy to implement it if we can agree it's the correct path. I think we should simply add another event ("XQUERY_MODIFICATION_DOCUMENT_EVENT" perhaps?). This way we can still react to node level updates when we want to, but not be forced to when we only want to consider updates from an xmldb:store(). Thoughts? Cheers, -- Patrick Bosek Jorsek Software Cell (585) 820 9634 Office (877) 492 2960 Jorsek.com |
From: Вячеслав С. <sch...@gm...> - 2011-07-20 09:14:07
|
thank for fast response Dannes, sorry about 'false alarm' look like davfs work with 127.0.0.1 instead localhost in url - so sudo mount -t davfs http://127.0.0.1:8080/exist/webdav/db/ /home/sla/localhost work as expected 20 июля 2011 г. 13:02 пользователь Dannes Wessels <da...@ex...> написал: > hi, > > 2011/7/20 Вячеслав Седов <sch...@gm...>: >> got from fresh trunk >> something new? > > what version DAVFS, what configuration items, did you search on the > MailingList, etc....... > > D. > > -- > 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...> - 2011-07-20 09:02:34
|
hi, 2011/7/20 Вячеслав Седов <sch...@gm...>: > got from fresh trunk > something new? what version DAVFS, what configuration items, did you search on the MailingList, etc....... D. -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |