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: Joe W. <jo...@gm...> - 2010-03-19 19:52:39
|
On yet another related note, is there a reason why the local properties files don't share the same naming convention? local.build.properties (in extensions) local.properties (in extensions/indexes) If we could choose one, I like the latter! Joe On Fri, Mar 19, 2010 at 3:48 PM, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > On a related note, what's the lib module which is mentioned in > extensions/build.properties? > > Joe > > On Fri, Mar 19, 2010 at 7:13 AM, <el...@us...> wrote: >> Revision: 11477 >> http://exist.svn.sourceforge.net/exist/?rev=11477&view=rev >> Author: ellefj >> Date: 2010-03-19 11:13:25 +0000 (Fri, 19 Mar 2010) >> >> Log Message: >> ----------- >> More comments in build.properties. Gev, fix the description and the name of the sharepoint rescue gate feature. >> >> Modified Paths: >> -------------- >> trunk/eXist/extensions/build.properties >> >> Modified: trunk/eXist/extensions/build.properties >> =================================================================== >> --- trunk/eXist/extensions/build.properties 2010-03-19 10:12:29 UTC (rev 11476) >> +++ trunk/eXist/extensions/build.properties 2010-03-19 11:13:25 UTC (rev 11477) >> @@ -8,8 +8,11 @@ >> # $Id$ >> ########################################################## >> >> -# Features >> +## The followning two lists (features and modules) are alphabetically sorted. >> +## Please try to keep it that way. >> >> +## Features >> + >> #Cocoon extension >> include.feature.cocoon = true >> >> @@ -19,6 +22,13 @@ >> #Fluent API for eXist >> include.feature.fluent = true >> >> +# TODO: explain what this is >> +# The name is not descriptive. >> +# It should be changed since *the* gate is probably best known as >> +# http://gate.ac.uk/ >> +# Sharepoint rescue gate for your documents >> +include.feature.gate = false >> + >> #Security OpenID extensions for eXist >> include.feature.security.openid = false >> >> @@ -31,7 +41,7 @@ >> #XSLT extension >> include.feature.xslt = true >> >> -# Modules >> +## Modules >> >> # Cache module >> include.module.cache = false >> @@ -102,6 +112,3 @@ >> include.module.xslfo.avalon.api.url = http://www.apache.org/dist/excalibur/excalibur-framework/binaries/avalon-framework-api-4.3.zip >> include.module.xslfo.avalon.impl.url = http://www.apache.org/dist/excalibur/excalibur-framework/binaries/avalon-framework-impl-4.3.zip >> include.module.xslfo.url = http://apache.cs.uu.nl/dist/xmlgraphics/fop/binaries/fop-0.95-bin.zip >> - >> -# TODO: explain what this is >> -include.feature.gate = false >> >> >> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Exist-commits mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-commits >> > |
|
From: Joe W. <jo...@gm...> - 2010-03-19 19:49:28
|
Hi all, On a related note, what's the lib module which is mentioned in extensions/build.properties? Joe On Fri, Mar 19, 2010 at 7:13 AM, <el...@us...> wrote: > Revision: 11477 > http://exist.svn.sourceforge.net/exist/?rev=11477&view=rev > Author: ellefj > Date: 2010-03-19 11:13:25 +0000 (Fri, 19 Mar 2010) > > Log Message: > ----------- > More comments in build.properties. Gev, fix the description and the name of the sharepoint rescue gate feature. > > Modified Paths: > -------------- > trunk/eXist/extensions/build.properties > > Modified: trunk/eXist/extensions/build.properties > =================================================================== > --- trunk/eXist/extensions/build.properties 2010-03-19 10:12:29 UTC (rev 11476) > +++ trunk/eXist/extensions/build.properties 2010-03-19 11:13:25 UTC (rev 11477) > @@ -8,8 +8,11 @@ > # $Id$ > ########################################################## > > -# Features > +## The followning two lists (features and modules) are alphabetically sorted. > +## Please try to keep it that way. > > +## Features > + > #Cocoon extension > include.feature.cocoon = true > > @@ -19,6 +22,13 @@ > #Fluent API for eXist > include.feature.fluent = true > > +# TODO: explain what this is > +# The name is not descriptive. > +# It should be changed since *the* gate is probably best known as > +# http://gate.ac.uk/ > +# Sharepoint rescue gate for your documents > +include.feature.gate = false > + > #Security OpenID extensions for eXist > include.feature.security.openid = false > > @@ -31,7 +41,7 @@ > #XSLT extension > include.feature.xslt = true > > -# Modules > +## Modules > > # Cache module > include.module.cache = false > @@ -102,6 +112,3 @@ > include.module.xslfo.avalon.api.url = http://www.apache.org/dist/excalibur/excalibur-framework/binaries/avalon-framework-api-4.3.zip > include.module.xslfo.avalon.impl.url = http://www.apache.org/dist/excalibur/excalibur-framework/binaries/avalon-framework-impl-4.3.zip > include.module.xslfo.url = http://apache.cs.uu.nl/dist/xmlgraphics/fop/binaries/fop-0.95-bin.zip > - > -# TODO: explain what this is > -include.feature.gate = false > > > This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Exist-commits mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-commits > |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 18:20:55
|
On Fri, 2010-03-19 at 23:15 +0500, Dmitriy Shabanov wrote: > On Fri, 2010-03-19 at 14:11 -0400, Joe Wicentowski wrote: > > Hi Dmitriy, > > > > Sounds good, but one question: > > > > >> - PAM interface > > > > What's this? > > http://en.wikipedia.org/wiki/Pluggable_Authentication_Modules For something like http://jpam.sourceforge.net/documentation/configuration.html -- Cheers, Dmitriy Shabanov |
|
From: Joe W. <jo...@gm...> - 2010-03-19 18:19:45
|
Hi Dmitriy, Sounds good, but one question: >> - PAM interface What's this? Joe |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 18:17:07
|
On Fri, 2010-03-19 at 14:11 -0400, Joe Wicentowski wrote: > Hi Dmitriy, > > Sounds good, but one question: > > >> - PAM interface > > What's this? http://en.wikipedia.org/wiki/Pluggable_Authentication_Modules -- Cheers, Dmitriy Shabanov |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 17:57:00
|
On Fri, 2010-03-19 at 22:48 +0500, Dmitriy Shabanov wrote: > Hello good people, > > This week end I will commit changes that affects authentication way. > > Plan: > - move validation from user class to manager class > - SHA as default password encryption algorithm > - PAM interface - move /system/users.xml to /system/accounts/users.xml & groups.xml -- Cheers, Dmitriy Shabanov |
|
From: James F. <jam...@gm...> - 2010-03-19 17:53:37
|
On Fri, Mar 19, 2010 at 6:48 PM, Dmitriy Shabanov <sha...@gm...> wrote: > Hello good people, > > This week end I will commit changes that affects authentication way. > > Plan: > - move validation from user class to manager class > - SHA as default password encryption algorithm > - PAM interface thx for the notification on this. J |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 17:50:22
|
Hello good people, This week end I will commit changes that affects authentication way. Plan: - move validation from user class to manager class - SHA as default password encryption algorithm - PAM interface -- Cheers, Dmitriy Shabanov |
|
From: Andrzej J. T. <an...@ch...> - 2010-03-19 13:09:52
|
Wolfgang suggests: > However, we don't want to compromise privacy, so I think it would be > better if the user gets an XML fragment which he can check first and > then mail it to whoever he wants. +1 from me on Wolfgang's suggestion. I really don't like the email link idea that was initially proposed. -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
|
From: Adam R. <ad...@ex...> - 2010-03-19 11:34:10
|
Upon request I have added support for Prepared Statements to the SQL
Module, there is a new function call sql:prepare(...).
This has gone into trunk as revision 11478. Mark Lawson has kindly
offered to test this functionality, if anyone else makes use of the
SQL Module and wishes to use Prepared Statements then I would also
encourage their testing. I am looking forward to feedback :-)
Just like the Connections all PreparedStatements are cleaned up at the
end of the XQuery execution.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Adam R. <ad...@ex...> - 2010-03-19 11:24:41
|
Sounds good to me On 18 March 2010 18:54, Loren Cahlander <lor...@gm...> wrote: > The following 17 deprecated functions will be removed from trunk sometime > in the following month. This is to help with the maintenance of the > codebase. Unsupported functionality needs to be removed so that > enhancements that are being developed elsewhere in the system do not > inadvertently break an unsupported feature. > > Please check your code and make the appropriate changes to the replacement > functions. > > Regards, > > Loren > metadata <http://demo.exist-db.org/exist/functions/metadata> > ------------------------------ > http://exist-db.org/xquery/metadata > A module for accessing the metadata for the dynamic context. > metadata <http://demo.exist-db.org/exist/functions/metadata/metadata> > ------------------------------ > metadata:metadata() node()? > Retrieves metadata for the dynamic context. If the context item is > undefined an error is raised. > ------------------------------ > Returns the metadata documents > ------------------------------ > Deprecated: An orphaned experiment. This function could be removed at > anytime during the 1.5 development and will be removed in the 1.6 release. > request <http://demo.exist-db.org/exist/functions/request> > ------------------------------ > http://exist-db.org/xquery/request > A module for dealing with HTTP requests. > get-uploaded-file<http://demo.exist-db.org/exist/functions/request/get-uploaded-file> > ------------------------------ > request:get-uploaded-file($upload-param-name as xs:string) item()? > Retrieve the Java file object where the file part of a multi-part request > has been stored. Returns the empty sequence if the request is not a > multi-part request or the parameter name does not point to a file part. > $upload-param-nameThe parameter name > ------------------------------ > Deprecated: Deprecated in favour of get-uploaded-file-data() This function > could be removed at anytime during the 1.5 development and will be removed > in the 1.6 release. > text <http://demo.exist-db.org/exist/functions/text> > ------------------------------ > http://exist-db.org/xquery/text > A module for text searching extension functions. > kwic-display <http://demo.exist-db.org/exist/functions/text/kwic-display> > ------------------------------ > text:kwic-display($text as text()*, $width as xs:positiveInteger, > $callback-function as function, $parameters as item()*) node()* > Deprecated: kwic functionality is now provided by an XQuery module, see > http://exist-org/kwic.html.This function takes a sequence of text nodes in > $a, containing matches from a fulltext search. It highlights matching > strings within those text nodes in the same way as the > text:highlight-matches function. However, only a defined portion of the text > surrounding the first match (and maybe following matches) is returned. If > the text preceding the first match is larger than the width specified in the > second argument $b, it will be truncated to fill no more than (width - > keyword-length) / 2 characters. Likewise, the text following the match will > be truncated in such a way that the whole string sequence fits into width > characters. The third parameter $c is a callback function (defined with > util:function). $d may contain an additional sequence of values that will be > passed to the last parameter of the callback function. Any matching > character sequence is reported to the callback function, and the result of > the function call is inserted into the resulting node set where the matching > sequence occurred. For example, you can use this to mark all matching terms > with a <span class="highlight">abc</span>. The callback function should take > 3 or 4 arguments: 1) the text sequence corresponding to the match as > xs:string, 2) the text node to which this match belongs, 3) the sequence > passed as last argument to kwic-display. If the callback function accepts 4 > arguments, the last argument will contain additional information on the > match as a sequence of 4 integers: a) the number of the match if there's > more than one match in a text node - the first match will be numbered 1; b) > the offset of the match into the original text node string; c) the length of > the match as reported by the index. > $textThe text nodes$widthThe width$callback-functionThe callback function > $parametersThe parameters passed into the last argument of the callback > function > ------------------------------ > Returns the results > ------------------------------ > Deprecated: Improved kwic functionality is now provided by a separate > XQuery module, see http://exist-db.org/kwic.html. This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > kwic-display <http://demo.exist-db.org/exist/functions/text/kwic-display> > ------------------------------ > text:kwic-display($text as text()*, $width as xs:positiveInteger, > $callback-function as function, $result-callback as function, $parameters as > item()*) node()* > This function takes a sequence of text nodes in $a, containing matches from > a fulltext search. It highlights matching strings within those text nodes in > the same way as the text:highlight-matches function. However, only a defined > portion of the text surrounding the first match (and maybe following > matches) is returned. If the text preceding the first match is larger than > the width specified in the second argument $b, it will be truncated to fill > no more than (width - keyword-length) / 2 characters. Likewise, the text > following the match will be truncated in such a way that the whole string > sequence fits into width characters. The third parameter $c is a callback > function (defined with util:function). $d may contain an additional sequence > of values that will be passed to the last parameter of the callback > function. Any matching character sequence is reported to the callback > function, and the result of the function call is inserted into the resulting > node set where the matching sequence occurred. For example, you can use this > to mark all matching terms with a <span class="highlight">abc</span>. The > callback function should take 3 or 4 arguments: 1) the text sequence > corresponding to the match as xs:string, 2) the text node to which this > match belongs, 3) the sequence passed as last argument to kwic-display. If > the callback function accepts 4 arguments, the last argument will contain > additional information on the match as a sequence of 4 integers: a) the > number of the match if there's more than one match in a text node - the > first match will be numbered 1; b) the offset of the match into the original > text node string; c) the length of the match as reported by the index. > $textThe text nodes$widthThe width$callback-functionThe callback function > $result-callbackThe result callback function$parametersThe parameters > passed into the last argument of the callback function > ------------------------------ > Returns the results > ------------------------------ > Deprecated: Improved kwic functionality is now provided by a separate > XQuery module, see http://exist-db.org/kwic.html. This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > util <http://demo.exist-db.org/exist/functions/util> > ------------------------------ > http://exist-db.org/xquery/util > A module for various utility extension functions. > serialize <http://demo.exist-db.org/exist/functions/util/serialize> > ------------------------------ > util:serialize($a as node()*, $b as xs:string, $c as xs:string*) > xs:boolean? > Writes the node set passed in parameter $a into a file on the file system. > The full path to the file is specified in parameter $b. $c contains a > sequence of zero or more serialization parameters specified as key=value > pairs. The serialization options are the same as those recognized by > "declare option exist:serialize". The function does NOT automatically > inherit the serialization options of the XQuery it is called from. False is > returned if the specified file can not be created or is not writable, true > on success. The empty sequence is returned if the argument sequence is > empty. > ------------------------------ > Deprecated: Use the file:serialize() function in the file extension module > instead! This function could be removed at anytime during the 1.5 > development and will be removed in the 1.6 release. > validation <http://demo.exist-db.org/exist/functions/validation> > ------------------------------ > http://exist-db.org/xquery/validation > A module for XML validation and grammars functions. > validate <http://demo.exist-db.org/exist/functions/validation/validate> > ------------------------------ > validation:validate($instance as item()) xs:boolean > Validate xml. The grammar files (DTD, XML Schema) are resolved using the > global catalog file(s). > $instanceThe document referenced as xs:anyURI or a node (element or > returned by fn:doc()) > ------------------------------ > Returns true() if the document is valid and no single problem occured, > false() for all other conditions. For detailed validation information use > the corresponding -report() function. > ------------------------------ > Deprecated: Use the validation:parse(), validation:jaxv() or > valation:jing() functions. This function could be removed at anytime during > the 1.5 development and will be removed in the 1.6 release. > validate <http://demo.exist-db.org/exist/functions/validation/validate> > ------------------------------ > validation:validate($instance as item(), $grammar as xs:anyURI) node() > Validate document by using a specific grammar. > $instanceThe document referenced as xs:anyURI or a node (element or > returned by fn:doc())$grammarThe reference to an OASIS catalog file > (.xml), a collection (path ends with '/') or a grammar document. Supported > grammar documents extensions are ".dtd" ".xsd" ".rng" ".rnc" ".sch" and > ".nvdl". > ------------------------------ > Returns true() if the document is valid and no single problem occured, > false() for all other conditions. For detailed validation information use > the corresponding -report() function. > ------------------------------ > Deprecated: Use the validation:parse(), validation:jaxv() or > valation:jing() functions. This function could be removed at anytime during > the 1.5 development and will be removed in the 1.6 release. > validate-report<http://demo.exist-db.org/exist/functions/validation/validate-report> > ------------------------------ > validation:validate-report($instance as item()) node() > Validate xml. The grammar files (DTD, XML Schema) are resolved using the > global catalog file(s). An xml report is returned. > $instanceThe document referenced as xs:anyURI or a node (element or > returned by fn:doc()) > ------------------------------ > Returns a validation report. > ------------------------------ > Deprecated: Use the validation:parse-report(), validation:jaxv-report() or > valation:jing-report() functions. This function could be removed at anytime > during the 1.5 development and will be removed in the 1.6 release. > validate-report<http://demo.exist-db.org/exist/functions/validation/validate-report> > ------------------------------ > validation:validate-report($instance as item(), $grammar as xs:anyURI) > node() > Validate document by using a specific grammar. An xml report is returned. > $instanceThe document referenced as xs:anyURI or a node (element or > returned by fn:doc())$grammarThe reference to an OASIS catalog file > (.xml), a collection (path ends with '/') or a grammar document. Supported > grammar documents extensions are ".dtd" ".xsd" ".rng" ".rnc" ".sch" and > ".nvdl". > ------------------------------ > Returns a validation report. > ------------------------------ > Deprecated: Use the validation:parse-report(), validation:jaxv-report() or > valation:jing-report() functions. This function could be removed at anytime > during the 1.5 development and will be removed in the 1.6 release. > xmldb <http://demo.exist-db.org/exist/functions/xmldb> > ------------------------------ > http://exist-db.org/xquery/xmldb > A module for database manipulation functions. > collection-exists<http://demo.exist-db.org/exist/functions/xmldb/collection-exists> > ------------------------------ > xmldb:collection-exists($collection-path as xs:string, ...) xs:boolean > Returns true() if the collection $collection exists and is available, > otherwise false(). > $collection-pathThe collection path > ------------------------------ > Returns true() if the collection exists and is available, false() otherwise > ------------------------------ > Deprecated: Use xmldb:collection-available() instead. This function could > be removed at anytime during the 1.5 development and will be removed in the > 1.6 release. > document <http://demo.exist-db.org/exist/functions/xmldb/document> > ------------------------------ > xmldb:document($document-uris as xs:string+, ...) node()* > Returns the documents $document-uris in the input sequence. Collection URIs > can be specified either as a simple collection path or an XMLDB URI.If the > input sequence is empty, the function will load all documents in the > database. > $document-urisThe document URIs > ------------------------------ > Returns the documents > ------------------------------ > Deprecated: See the standard fn:doc() function This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > <http://demo.exist-db.org/exist/functions/xpath-functions> > ------------------------------ > http://www.w3.org/2005/xpath-functions > A module with the XQuery/XPath Core Library Functions > doctype <http://demo.exist-db.org/exist/functions/xpath-functions/doctype> > ------------------------------ > doctype($doctype as xs:string+) node()* > Returns the document nodes of the documents based on the DOCTYPE. > $doctypeone or more DOCTYPE names > ------------------------------ > Returns the document nodes matching the DOCTYPE names > ------------------------------ > Deprecated: This function is eXist-specific and deprecated. It should not > be in the standard functions namespace. Please use util:doctype() instead. > This function could be removed at anytime during the 1.5 development and > will be removed in the 1.6 release. > document<http://demo.exist-db.org/exist/functions/xpath-functions/document> > ------------------------------ > document($document-uris as xs:string+, ...) node()* > Returns the documents specified in the input sequence. This function is > specific to eXist and will be replaced with the corresponding fn:doc > function. Collection URIs can be specified either as a simple collection > path or an XMLDB URI. If the input sequence is empty, the function will load > all documents in the database. > $document-urisThe document URIs > ------------------------------ > Returns the documents > ------------------------------ > Deprecated: Moved to the 'http://exist-db.org/xquery/xmldb' namespace > since it conflicts with the XSLT 2.0 function. This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > item-at <http://demo.exist-db.org/exist/functions/xpath-functions/item-at> > ------------------------------ > item-at($source as item()*, $index as xs:integer) item()? > Returns the item in $source that is located at the position specified by > $index. > $sourceThe source sequence$indexThe index of the item in the source > sequence to return > ------------------------------ > Returns the item > ------------------------------ > Deprecated: This function is eXist-specific and deprecated. It should not > be in the standard functions namespace. Use e.g. $x[1] instead. This > function could be removed at anytime during the 1.5 development and will be > removed in the 1.6 release. > match-all<http://demo.exist-db.org/exist/functions/xpath-functions/match-all> > ------------------------------ > match-all($nodes as node()*, $regular-expression as xs:string+, ...) > node()* > Tries to match each of the regular expression strings passed in > $regular-expression and all following parameters against the keywords > contained in the old fulltext index. The keywords found are then compared to > the node set in $nodes. Every node containing all of the keywords is copied > to the result sequence. > $nodesThe node set that is to be searched for the keyword set > $regular-expressionThe regular expressions to be matched against the > fulltext index > ------------------------------ > Returns the sequence of all of the matching nodes > ------------------------------ > Deprecated: This function is eXist-specific and should not be in the > standard functions namespace. Please use text:match-all() instead. This > function could be removed at anytime during the 1.5 development and will be > removed in the 1.6 release. > match-any<http://demo.exist-db.org/exist/functions/xpath-functions/match-any> > ------------------------------ > match-any($nodes as node()*, $regular-expression as xs:string+, ...) > node()* > Tries to match each of the regular expression strings passed in > $regular-expression and all following parameters against the keywords > contained in the old fulltext index. The keywords found are then compared to > the node set in $nodes. Every node containing any of the keywords is copied > to the result sequence. > $nodesThe node set that is to be searched for the keyword set > $regular-expressionThe regular expressions to be matched against the > fulltext index > ------------------------------ > Returns the sequence of all of the matching nodes > ------------------------------ > Deprecated: This function is eXist-specific and should not be in the > standard functions namespace. Please use text:match-any() instead. This > function could be removed at anytime during the 1.5 development and will be > removed in the 1.6 release. > xcollection<http://demo.exist-db.org/exist/functions/xpath-functions/xcollection> > ------------------------------ > xcollection($collection-uris as xs:string+, ...) node()* > Returns the document nodes in the collections $collection-uris > non-recursively, i.e. does not include document nodes found in > sub-collections. > C.f. fn:collection(). Collection URIs can be specified either as a simple > collection path or an XMLDB URI. > $collection-urisThe collection URIs > ------------------------------ > Returns the document nodes from the specified collections excluding > sub-collections > ------------------------------ > Deprecated: This function is eXist-specific and deprecated. It should not > be in the standard functions namespace. Please use > http://exist-db.org/xquery/xmldb:xcollection() instead. This function > could be removed at anytime during the 1.5 development and will be removed > in the 1.6 release. > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 09:40:26
|
On Fri, 2010-03-19 at 10:32 +0100, Dannes Wessels wrote: > Hi, > > On Fri, Mar 19, 2010 at 9:09 AM, Dmitriy Shabanov > <sha...@gm...> wrote: > Remove lib/extensions/exist-security-openid.jar & disable it > at > build.properties. > > Well, we can disable it by default. > > In trunk it should be disabled by default. I don't use it, so I do not > need it. Please do.... > > It would be better to have it behind a configuration option? exist-security-openid.jar is configuration option :-) (if you have jar openid is enabled) -- Cheers, Dmitriy Shabanov |
|
From: Dannes W. <da...@ex...> - 2010-03-19 09:32:57
|
Hi, On Fri, Mar 19, 2010 at 9:09 AM, Dmitriy Shabanov <sha...@gm...>wrote: > Remove lib/extensions/exist-security-openid.jar & disable it at > build.properties. > > Well, we can disable it by default. > In trunk it should be disabled by default. I don't use it, so I do not need it. Please do.... It would be better to have it behind a configuration option? regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 09:20:55
|
On Fri, 2010-03-19 at 10:02 +0100, Wolfgang Meier wrote: > > It possible to use this > > http://forums.devshed.com/beginner-programming-16/using-mailto-with-an-attachment-66699.html > > Yes, but my point was: it should *not* be mailed automatically. Let > the user just copy and paste or attach the XML. mailto tag create mail at your default mail agent & in this example it also adding attachment. It will not send mail automatically! -- Cheers, Dmitriy Shabanov |
|
From: Wolfgang M. <wol...@ex...> - 2010-03-19 09:02:18
|
> It possible to use this > http://forums.devshed.com/beginner-programming-16/using-mailto-with-an-attachment-66699.html Yes, but my point was: it should *not* be mailed automatically. Let the user just copy and paste or attach the XML. Wolfgang |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 08:48:56
|
On Fri, 2010-03-19 at 09:24 +0100, Wolfgang Meier wrote: > > What do you want to achieve by this? > > Answering for Loren: I think the goal is clear: provide a simple way > to users to provide relevant information about the setup of their > eXist instance. This should include the general information displayed > on the admin page, but probably also some statistics about db size, > index sizes, caching space and the like. I have to think about the > details. > > However, we don't want to compromise privacy, so I think it would be > better if the user gets an XML fragment which he can check first and > then mail it to whoever he wants. It possible to use this http://forums.devshed.com/beginner-programming-16/using-mailto-with-an-attachment-66699.html -- Cheers, Dmitriy Shabanov |
|
From: Wolfgang M. <wol...@ex...> - 2010-03-19 08:24:32
|
> What do you want to achieve by this? Answering for Loren: I think the goal is clear: provide a simple way to users to provide relevant information about the setup of their eXist instance. This should include the general information displayed on the admin page, but probably also some statistics about db size, index sizes, caching space and the like. I have to think about the details. However, we don't want to compromise privacy, so I think it would be better if the user gets an XML fragment which he can check first and then mail it to whoever he wants. Wolfgang |
|
From: Thomas W. <tho...@gm...> - 2010-03-19 08:22:38
|
Loren, I think will be a good idea to create a short table with only three columns - 'depreciated function', 'replaced with', 'from version' and add it to the documentation. That will help developers when they come later with an old code to find out easily what to use instead of depreciated functions. Thomas ------ Thomas White Mobile:+44 7711 922 966 Skype: thomaswhite gTalk: thomas.0007 Linked-In:http://www.linkedin.com/in/thomaswhite0007 facebook: http://www.facebook.com/thomas.0007 On 18 March 2010 18:54, Loren Cahlander <lor...@gm...> wrote: > The following 17 deprecated functions will be removed from trunk sometime > in the following month. This is to help with the maintenance of the > codebase. Unsupported functionality needs to be removed so that > enhancements that are being developed elsewhere in the system do not > inadvertently break an unsupported feature. > > Please check your code and make the appropriate changes to the replacement > functions. > > Regards, > > Loren > metadata <http://demo.exist-db.org/exist/functions/metadata> > ------------------------------ > http://exist-db.org/xquery/metadata > A module for accessing the metadata for the dynamic context. > metadata <http://demo.exist-db.org/exist/functions/metadata/metadata> > ------------------------------ > metadata:metadata() node()? > Retrieves metadata for the dynamic context. If the context item is > undefined an error is raised. > ------------------------------ > Returns the metadata documents > ------------------------------ > Deprecated: An orphaned experiment. This function could be removed at > anytime during the 1.5 development and will be removed in the 1.6 release. > request <http://demo.exist-db.org/exist/functions/request> > ------------------------------ > http://exist-db.org/xquery/request > A module for dealing with HTTP requests. > get-uploaded-file<http://demo.exist-db.org/exist/functions/request/get-uploaded-file> > ------------------------------ > request:get-uploaded-file($upload-param-name as xs:string) item()? > Retrieve the Java file object where the file part of a multi-part request > has been stored. Returns the empty sequence if the request is not a > multi-part request or the parameter name does not point to a file part. > $upload-param-name The parameter name > ------------------------------ > Deprecated: Deprecated in favour of get-uploaded-file-data() This function > could be removed at anytime during the 1.5 development and will be removed > in the 1.6 release. > text <http://demo.exist-db.org/exist/functions/text> > ------------------------------ > http://exist-db.org/xquery/text > A module for text searching extension functions. > kwic-display <http://demo.exist-db.org/exist/functions/text/kwic-display> > ------------------------------ > text:kwic-display($text as text()*, $width as xs:positiveInteger, > $callback-function as function, $parameters as item()*) node()* > Deprecated: kwic functionality is now provided by an XQuery module, see > http://exist-org/kwic.html.This function takes a sequence of text nodes in > $a, containing matches from a fulltext search. It highlights matching > strings within those text nodes in the same way as the > text:highlight-matches function. However, only a defined portion of the text > surrounding the first match (and maybe following matches) is returned. If > the text preceding the first match is larger than the width specified in the > second argument $b, it will be truncated to fill no more than (width - > keyword-length) / 2 characters. Likewise, the text following the match will > be truncated in such a way that the whole string sequence fits into width > characters. The third parameter $c is a callback function (defined with > util:function). $d may contain an additional sequence of values that will be > passed to the last parameter of the callback function. Any matching > character sequence is reported to the callback function, and the result of > the function call is inserted into the resulting node set where the matching > sequence occurred. For example, you can use this to mark all matching terms > with a <span class="highlight">abc</span>. The callback function should take > 3 or 4 arguments: 1) the text sequence corresponding to the match as > xs:string, 2) the text node to which this match belongs, 3) the sequence > passed as last argument to kwic-display. If the callback function accepts 4 > arguments, the last argument will contain additional information on the > match as a sequence of 4 integers: a) the number of the match if there's > more than one match in a text node - the first match will be numbered 1; b) > the offset of the match into the original text node string; c) the length of > the match as reported by the index. > $text The text nodes $width The width $callback-function The callback > function $parameters The parameters passed into the last argument of the > callback function > ------------------------------ > Returns the results > ------------------------------ > Deprecated: Improved kwic functionality is now provided by a separate > XQuery module, see http://exist-db.org/kwic.html. This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > kwic-display <http://demo.exist-db.org/exist/functions/text/kwic-display> > ------------------------------ > text:kwic-display($text as text()*, $width as xs:positiveInteger, > $callback-function as function, $result-callback as function, $parameters as > item()*) node()* > This function takes a sequence of text nodes in $a, containing matches > from a fulltext search. It highlights matching strings within those text > nodes in the same way as the text:highlight-matches function. However, only > a defined portion of the text surrounding the first match (and maybe > following matches) is returned. If the text preceding the first match is > larger than the width specified in the second argument $b, it will be > truncated to fill no more than (width - keyword-length) / 2 characters. > Likewise, the text following the match will be truncated in such a way that > the whole string sequence fits into width characters. The third parameter $c > is a callback function (defined with util:function). $d may contain an > additional sequence of values that will be passed to the last parameter of > the callback function. Any matching character sequence is reported to the > callback function, and the result of the function call is inserted into the > resulting node set where the matching sequence occurred. For example, you > can use this to mark all matching terms with a <span > class="highlight">abc</span>. The callback function should take 3 or 4 > arguments: 1) the text sequence corresponding to the match as xs:string, 2) > the text node to which this match belongs, 3) the sequence passed as last > argument to kwic-display. If the callback function accepts 4 arguments, the > last argument will contain additional information on the match as a sequence > of 4 integers: a) the number of the match if there's more than one match in > a text node - the first match will be numbered 1; b) the offset of the match > into the original text node string; c) the length of the match as reported > by the index. > $text The text nodes $width The width $callback-function The callback > function $result-callback The result callback function $parameters The > parameters passed into the last argument of the callback function > ------------------------------ > Returns the results > ------------------------------ > Deprecated: Improved kwic functionality is now provided by a separate > XQuery module, see http://exist-db.org/kwic.html. This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > util <http://demo.exist-db.org/exist/functions/util> > ------------------------------ > http://exist-db.org/xquery/util > A module for various utility extension functions. > serialize <http://demo.exist-db.org/exist/functions/util/serialize> > ------------------------------ > util:serialize($a as node()*, $b as xs:string, $c as xs:string*) > xs:boolean? > Writes the node set passed in parameter $a into a file on the file > system. The full path to the file is specified in parameter $b. $c contains > a sequence of zero or more serialization parameters specified as key=value > pairs. The serialization options are the same as those recognized by > "declare option exist:serialize". The function does NOT automatically > inherit the serialization options of the XQuery it is called from. False is > returned if the specified file can not be created or is not writable, true > on success. The empty sequence is returned if the argument sequence is > empty. > ------------------------------ > Deprecated: Use the file:serialize() function in the file extension module > instead! This function could be removed at anytime during the 1.5 > development and will be removed in the 1.6 release. > validation <http://demo.exist-db.org/exist/functions/validation> > ------------------------------ > http://exist-db.org/xquery/validation > A module for XML validation and grammars functions. > validate <http://demo.exist-db.org/exist/functions/validation/validate> > ------------------------------ > validation:validate($instance as item()) xs:boolean > Validate xml. The grammar files (DTD, XML Schema) are resolved using the > global catalog file(s). > $instance The document referenced as xs:anyURI or a node (element or > returned by fn:doc()) > ------------------------------ > Returns true() if the document is valid and no single problem occured, > false() for all other conditions. For detailed validation information use > the corresponding -report() function. > ------------------------------ > Deprecated: Use the validation:parse(), validation:jaxv() or > valation:jing() functions. This function could be removed at anytime during > the 1.5 development and will be removed in the 1.6 release. > validate <http://demo.exist-db.org/exist/functions/validation/validate> > ------------------------------ > validation:validate($instance as item(), $grammar as xs:anyURI) node() > Validate document by using a specific grammar. > $instance The document referenced as xs:anyURI or a node (element or > returned by fn:doc()) $grammar The reference to an OASIS catalog file > (.xml), a collection (path ends with '/') or a grammar document. Supported > grammar documents extensions are ".dtd" ".xsd" ".rng" ".rnc" ".sch" and > ".nvdl". > ------------------------------ > Returns true() if the document is valid and no single problem occured, > false() for all other conditions. For detailed validation information use > the corresponding -report() function. > ------------------------------ > Deprecated: Use the validation:parse(), validation:jaxv() or > valation:jing() functions. This function could be removed at anytime during > the 1.5 development and will be removed in the 1.6 release. > validate-report<http://demo.exist-db.org/exist/functions/validation/validate-report> > ------------------------------ > validation:validate-report($instance as item()) node() > Validate xml. The grammar files (DTD, XML Schema) are resolved using the > global catalog file(s). An xml report is returned. > $instance The document referenced as xs:anyURI or a node (element or > returned by fn:doc()) > ------------------------------ > Returns a validation report. > ------------------------------ > Deprecated: Use the validation:parse-report(), validation:jaxv-report() or > valation:jing-report() functions. This function could be removed at anytime > during the 1.5 development and will be removed in the 1.6 release. > validate-report<http://demo.exist-db.org/exist/functions/validation/validate-report> > ------------------------------ > validation:validate-report($instance as item(), $grammar as xs:anyURI) > node() > Validate document by using a specific grammar. An xml report is returned. > $instance The document referenced as xs:anyURI or a node (element or > returned by fn:doc()) $grammar The reference to an OASIS catalog file > (.xml), a collection (path ends with '/') or a grammar document. Supported > grammar documents extensions are ".dtd" ".xsd" ".rng" ".rnc" ".sch" and > ".nvdl". > ------------------------------ > Returns a validation report. > ------------------------------ > Deprecated: Use the validation:parse-report(), validation:jaxv-report() or > valation:jing-report() functions. This function could be removed at anytime > during the 1.5 development and will be removed in the 1.6 release. > xmldb <http://demo.exist-db.org/exist/functions/xmldb> > ------------------------------ > http://exist-db.org/xquery/xmldb > A module for database manipulation functions. > collection-exists<http://demo.exist-db.org/exist/functions/xmldb/collection-exists> > ------------------------------ > xmldb:collection-exists($collection-path as xs:string, ...) xs:boolean > Returns true() if the collection $collection exists and is available, > otherwise false(). > $collection-path The collection path > ------------------------------ > Returns true() if the collection exists and is available, false() otherwise > ------------------------------ > Deprecated: Use xmldb:collection-available() instead. This function could > be removed at anytime during the 1.5 development and will be removed in the > 1.6 release. > document <http://demo.exist-db.org/exist/functions/xmldb/document> > ------------------------------ > xmldb:document($document-uris as xs:string+, ...) node()* > Returns the documents $document-uris in the input sequence. Collection > URIs can be specified either as a simple collection path or an XMLDB URI.If > the input sequence is empty, the function will load all documents in the > database. > $document-uris The document URIs > ------------------------------ > Returns the documents > ------------------------------ > Deprecated: See the standard fn:doc() function This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > <http://demo.exist-db.org/exist/functions/xpath-functions> > ------------------------------ > http://www.w3.org/2005/xpath-functions > A module with the XQuery/XPath Core Library Functions > doctype<http://demo.exist-db.org/exist/functions/xpath-functions/doctype> > ------------------------------ > doctype($doctype as xs:string+) node()* > Returns the document nodes of the documents based on the DOCTYPE. > $doctype one or more DOCTYPE names > ------------------------------ > Returns the document nodes matching the DOCTYPE names > ------------------------------ > Deprecated: This function is eXist-specific and deprecated. It should not > be in the standard functions namespace. Please use util:doctype() instead. > This function could be removed at anytime during the 1.5 development and > will be removed in the 1.6 release. > document<http://demo.exist-db.org/exist/functions/xpath-functions/document> > ------------------------------ > document($document-uris as xs:string+, ...) node()* > Returns the documents specified in the input sequence. This function is > specific to eXist and will be replaced with the corresponding fn:doc > function. Collection URIs can be specified either as a simple collection > path or an XMLDB URI. If the input sequence is empty, the function will load > all documents in the database. > $document-uris The document URIs > ------------------------------ > Returns the documents > ------------------------------ > Deprecated: Moved to the 'http://exist-db.org/xquery/xmldb' namespace > since it conflicts with the XSLT 2.0 function. This function could be > removed at anytime during the 1.5 development and will be removed in the 1.6 > release. > item-at<http://demo.exist-db.org/exist/functions/xpath-functions/item-at> > ------------------------------ > item-at($source as item()*, $index as xs:integer) item()? > Returns the item in $source that is located at the position specified by > $index. > $source The source sequence $index The index of the item in the source > sequence to return > ------------------------------ > Returns the item > ------------------------------ > Deprecated: This function is eXist-specific and deprecated. It should not > be in the standard functions namespace. Use e.g. $x[1] instead. This > function could be removed at anytime during the 1.5 development and will be > removed in the 1.6 release. > match-all<http://demo.exist-db.org/exist/functions/xpath-functions/match-all> > ------------------------------ > match-all($nodes as node()*, $regular-expression as xs:string+, ...) > node()* > Tries to match each of the regular expression strings passed in > $regular-expression and all following parameters against the keywords > contained in the old fulltext index. The keywords found are then compared to > the node set in $nodes. Every node containing all of the keywords is copied > to the result sequence. > $nodes The node set that is to be searched for the keyword set > $regular-expression The regular expressions to be matched against the > fulltext index > ------------------------------ > Returns the sequence of all of the matching nodes > ------------------------------ > Deprecated: This function is eXist-specific and should not be in the > standard functions namespace. Please use text:match-all() instead. This > function could be removed at anytime during the 1.5 development and will be > removed in the 1.6 release. > match-any<http://demo.exist-db.org/exist/functions/xpath-functions/match-any> > ------------------------------ > match-any($nodes as node()*, $regular-expression as xs:string+, ...) > node()* > Tries to match each of the regular expression strings passed in > $regular-expression and all following parameters against the keywords > contained in the old fulltext index. The keywords found are then compared to > the node set in $nodes. Every node containing any of the keywords is copied > to the result sequence. > $nodes The node set that is to be searched for the keyword set > $regular-expression The regular expressions to be matched against the > fulltext index > ------------------------------ > Returns the sequence of all of the matching nodes > ------------------------------ > Deprecated: This function is eXist-specific and should not be in the > standard functions namespace. Please use text:match-any() instead. This > function could be removed at anytime during the 1.5 development and will be > removed in the 1.6 release. > xcollection<http://demo.exist-db.org/exist/functions/xpath-functions/xcollection> > ------------------------------ > xcollection($collection-uris as xs:string+, ...) node()* > Returns the document nodes in the collections $collection-uris > non-recursively, i.e. does not include document nodes found in > sub-collections. > C.f. fn:collection(). Collection URIs can be specified either as a simple > collection path or an XMLDB URI. > $collection-uris The collection URIs > ------------------------------ > Returns the document nodes from the specified collections excluding > sub-collections > ------------------------------ > Deprecated: This function is eXist-specific and deprecated. It should not > be in the standard functions namespace. Please use > http://exist-db.org/xquery/xmldb:xcollection() instead. This function > could be removed at anytime during the 1.5 development and will be removed > in the 1.6 release. > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 08:13:48
|
What do you want to achieve by this? -- Cheers, Dmitriy Shabanov On Thu, 2010-03-18 at 21:06 +0100, Wolfgang Meier wrote: > > I am adding a link to the bottom of the System Status page that creates an email message to the exist-open mailing list with this information. This link is protected from the spammers, because you need to login as admin to see the page. Does anyone have any objections before I commit the code? > > I'm not sure it is a good idea to allow people to post this directly > to the list. The mailing list server will block messages from > unsubscribed users and we'll have to admit them manually. > > My plan was to add an XQuery function which could extract all relevant > system information, including some important figures concerning > caching, database size etc. The function would just create an XML > document which the user could then post to us. |
|
From: Dmitriy S. <sha...@gm...> - 2010-03-19 08:10:56
|
Remove lib/extensions/exist-security-openid.jar & disable it at build.properties. Well, we can disable it by default. -- Cheers, Dmitriy Shabanov On Thu, 2010-03-18 at 19:52 +0100, Dannes Wessels wrote: > All, > > during exist-db startup (trunk) I see the following: > > > > 17 Mar 2010 15:06:21,321 [main] INFO (JettyStart.java [run]:242) - > http://localhost:8085/exist > > 17 Mar 2010 15:06:21,327 [main] INFO (JettyStart.java [run]:256) - > http://localhost:8085/exist/openid > > > > the openId stuff is started by default. Since I do not use it myself, > I probably do not want to have it started? |
|
From: Wolfgang M. <wol...@ex...> - 2010-03-18 20:06:24
|
> I am adding a link to the bottom of the System Status page that creates an email message to the exist-open mailing list with this information. This link is protected from the spammers, because you need to login as admin to see the page. Does anyone have any objections before I commit the code? I'm not sure it is a good idea to allow people to post this directly to the list. The mailing list server will block messages from unsubscribed users and we'll have to admit them manually. My plan was to add an XQuery function which could extract all relevant system information, including some important figures concerning caching, database size etc. The function would just create an XML document which the user could then post to us. Wolfgang |
|
From: Loren C. <lor...@gm...> - 2010-03-18 19:59:04
|
I am adding a link to the bottom of the System Status page that creates an email message to the exist-open mailing list with this information. This link is protected from the spammers, because you need to login as admin to see the page. Does anyone have any objections before I commit the code? Loren System Status General eXist Version: 1.5.0dev eXist Build: 20100317 eXist Home: /Users/lcahlander/Documents/workspace/exist-trunk SVN Revision: 11472 Operating System: Mac OS X 10.6.2 x86_64 File encoding: UTF-8 Java Vendor: Apple Inc. Version: 1.6.0_17 Implementation: Java HotSpot(TM) 64-Bit Server VM Installation: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Memory Usage Max. Memory: 518976K Current Total: 128448K Free: 99789K Mail System Information to the eXist-open mailing list The link will create an email message with the following in the body: General eXist Version: 1.5.0dev eXist Build: 20100317 eXist Home: /Users/lcahlander/Documents/workspace/exist-trunk SVN Revision: 11472 Operating System: Mac OS X 10.6.2 x86_64 File encoding: UTF-8 Java Vendor: Apple Inc. Version: 1.6.0_17 Implementation: Java HotSpot(TM) 64-Bit Server VM Installation: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Memory Usage Max. Memory: 518976K Current Total: 128448K Free: 104903K |
|
From: Loren C. <lor...@gm...> - 2010-03-18 18:54:56
|
The following 17 deprecated functions will be removed from trunk sometime in the following month. This is to help with the maintenance of the codebase. Unsupported functionality needs to be removed so that enhancements that are being developed elsewhere in the system do not inadvertently break an unsupported feature. Please check your code and make the appropriate changes to the replacement functions. Regards, Loren metadata http://exist-db.org/xquery/metadata A module for accessing the metadata for the dynamic context. metadata metadata:metadata() node()? Retrieves metadata for the dynamic context. If the context item is undefined an error is raised. Returns the metadata documents Deprecated: An orphaned experiment. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. request http://exist-db.org/xquery/request A module for dealing with HTTP requests. get-uploaded-file request:get-uploaded-file($upload-param-name as xs:string) item()? Retrieve the Java file object where the file part of a multi-part request has been stored. Returns the empty sequence if the request is not a multi-part request or the parameter name does not point to a file part. $upload-param-name The parameter name Deprecated: Deprecated in favour of get-uploaded-file-data() This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. text http://exist-db.org/xquery/text A module for text searching extension functions. kwic-display text:kwic-display($text as text()*, $width as xs:positiveInteger, $callback-function as function, $parameters as item()*) node()* Deprecated: kwic functionality is now provided by an XQuery module, see http://exist-org/kwic.html.This function takes a sequence of text nodes in $a, containing matches from a fulltext search. It highlights matching strings within those text nodes in the same way as the text:highlight-matches function. However, only a defined portion of the text surrounding the first match (and maybe following matches) is returned. If the text preceding the first match is larger than the width specified in the second argument $b, it will be truncated to fill no more than (width - keyword-length) / 2 characters. Likewise, the text following the match will be truncated in such a way that the whole string sequence fits into width characters. The third parameter $c is a callback function (defined with util:function). $d may contain an additional sequence of values that will be passed to the last parameter of the callback function. Any matching character sequence is reported to the callback function, and the result of the function call is inserted into the resulting node set where the matching sequence occurred. For example, you can use this to mark all matching terms with a <span class="highlight">abc</span>. The callback function should take 3 or 4 arguments: 1) the text sequence corresponding to the match as xs:string, 2) the text node to which this match belongs, 3) the sequence passed as last argument to kwic-display. If the callback function accepts 4 arguments, the last argument will contain additional information on the match as a sequence of 4 integers: a) the number of the match if there's more than one match in a text node - the first match will be numbered 1; b) the offset of the match into the original text node string; c) the length of the match as reported by the index. $text The text nodes $width The width $callback-function The callback function $parameters The parameters passed into the last argument of the callback function Returns the results Deprecated: Improved kwic functionality is now provided by a separate XQuery module, see http://exist-db.org/kwic.html. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. kwic-display text:kwic-display($text as text()*, $width as xs:positiveInteger, $callback-function as function, $result-callback as function, $parameters as item()*) node()* This function takes a sequence of text nodes in $a, containing matches from a fulltext search. It highlights matching strings within those text nodes in the same way as the text:highlight-matches function. However, only a defined portion of the text surrounding the first match (and maybe following matches) is returned. If the text preceding the first match is larger than the width specified in the second argument $b, it will be truncated to fill no more than (width - keyword-length) / 2 characters. Likewise, the text following the match will be truncated in such a way that the whole string sequence fits into width characters. The third parameter $c is a callback function (defined with util:function). $d may contain an additional sequence of values that will be passed to the last parameter of the callback function. Any matching character sequence is reported to the callback function, and the result of the function call is inserted into the resulting node set where the matching sequence occurred. For example, you can use this to mark all matching terms with a <span class="highlight">abc</span>. The callback function should take 3 or 4 arguments: 1) the text sequence corresponding to the match as xs:string, 2) the text node to which this match belongs, 3) the sequence passed as last argument to kwic-display. If the callback function accepts 4 arguments, the last argument will contain additional information on the match as a sequence of 4 integers: a) the number of the match if there's more than one match in a text node - the first match will be numbered 1; b) the offset of the match into the original text node string; c) the length of the match as reported by the index. $text The text nodes $width The width $callback-function The callback function $result-callback The result callback function $parameters The parameters passed into the last argument of the callback function Returns the results Deprecated: Improved kwic functionality is now provided by a separate XQuery module, see http://exist-db.org/kwic.html. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. util http://exist-db.org/xquery/util A module for various utility extension functions. serialize util:serialize($a as node()*, $b as xs:string, $c as xs:string*) xs:boolean? Writes the node set passed in parameter $a into a file on the file system. The full path to the file is specified in parameter $b. $c contains a sequence of zero or more serialization parameters specified as key=value pairs. The serialization options are the same as those recognized by "declare option exist:serialize". The function does NOT automatically inherit the serialization options of the XQuery it is called from. False is returned if the specified file can not be created or is not writable, true on success. The empty sequence is returned if the argument sequence is empty. Deprecated: Use the file:serialize() function in the file extension module instead! This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. validation http://exist-db.org/xquery/validation A module for XML validation and grammars functions. validate validation:validate($instance as item()) xs:boolean Validate xml. The grammar files (DTD, XML Schema) are resolved using the global catalog file(s). $instance The document referenced as xs:anyURI or a node (element or returned by fn:doc()) Returns true() if the document is valid and no single problem occured, false() for all other conditions. For detailed validation information use the corresponding -report() function. Deprecated: Use the validation:parse(), validation:jaxv() or valation:jing() functions. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. validate validation:validate($instance as item(), $grammar as xs:anyURI) node() Validate document by using a specific grammar. $instance The document referenced as xs:anyURI or a node (element or returned by fn:doc()) $grammar The reference to an OASIS catalog file (.xml), a collection (path ends with '/') or a grammar document. Supported grammar documents extensions are ".dtd" ".xsd" ".rng" ".rnc" ".sch" and ".nvdl". Returns true() if the document is valid and no single problem occured, false() for all other conditions. For detailed validation information use the corresponding -report() function. Deprecated: Use the validation:parse(), validation:jaxv() or valation:jing() functions. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. validate-report validation:validate-report($instance as item()) node() Validate xml. The grammar files (DTD, XML Schema) are resolved using the global catalog file(s). An xml report is returned. $instance The document referenced as xs:anyURI or a node (element or returned by fn:doc()) Returns a validation report. Deprecated: Use the validation:parse-report(), validation:jaxv-report() or valation:jing-report() functions. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. validate-report validation:validate-report($instance as item(), $grammar as xs:anyURI) node() Validate document by using a specific grammar. An xml report is returned. $instance The document referenced as xs:anyURI or a node (element or returned by fn:doc()) $grammar The reference to an OASIS catalog file (.xml), a collection (path ends with '/') or a grammar document. Supported grammar documents extensions are ".dtd" ".xsd" ".rng" ".rnc" ".sch" and ".nvdl". Returns a validation report. Deprecated: Use the validation:parse-report(), validation:jaxv-report() or valation:jing-report() functions. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. xmldb http://exist-db.org/xquery/xmldb A module for database manipulation functions. collection-exists xmldb:collection-exists($collection-path as xs:string, ...) xs:boolean Returns true() if the collection $collection exists and is available, otherwise false(). $collection-path The collection path Returns true() if the collection exists and is available, false() otherwise Deprecated: Use xmldb:collection-available() instead. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. document xmldb:document($document-uris as xs:string+, ...) node()* Returns the documents $document-uris in the input sequence. Collection URIs can be specified either as a simple collection path or an XMLDB URI.If the input sequence is empty, the function will load all documents in the database. $document-uris The document URIs Returns the documents Deprecated: See the standard fn:doc() function This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. http://www.w3.org/2005/xpath-functions A module with the XQuery/XPath Core Library Functions doctype doctype($doctype as xs:string+) node()* Returns the document nodes of the documents based on the DOCTYPE. $doctype one or more DOCTYPE names Returns the document nodes matching the DOCTYPE names Deprecated: This function is eXist-specific and deprecated. It should not be in the standard functions namespace. Please use util:doctype() instead. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. document document($document-uris as xs:string+, ...) node()* Returns the documents specified in the input sequence. This function is specific to eXist and will be replaced with the corresponding fn:doc function. Collection URIs can be specified either as a simple collection path or an XMLDB URI. If the input sequence is empty, the function will load all documents in the database. $document-uris The document URIs Returns the documents Deprecated: Moved to the 'http://exist-db.org/xquery/xmldb' namespace since it conflicts with the XSLT 2.0 function. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. item-at item-at($source as item()*, $index as xs:integer) item()? Returns the item in $source that is located at the position specified by $index. $source The source sequence $index The index of the item in the source sequence to return Returns the item Deprecated: This function is eXist-specific and deprecated. It should not be in the standard functions namespace. Use e.g. $x[1] instead. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. match-all match-all($nodes as node()*, $regular-expression as xs:string+, ...) node()* Tries to match each of the regular expression strings passed in $regular-expression and all following parameters against the keywords contained in the old fulltext index. The keywords found are then compared to the node set in $nodes. Every node containing all of the keywords is copied to the result sequence. $nodes The node set that is to be searched for the keyword set $regular-expression The regular expressions to be matched against the fulltext index Returns the sequence of all of the matching nodes Deprecated: This function is eXist-specific and should not be in the standard functions namespace. Please use text:match-all() instead. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. match-any match-any($nodes as node()*, $regular-expression as xs:string+, ...) node()* Tries to match each of the regular expression strings passed in $regular-expression and all following parameters against the keywords contained in the old fulltext index. The keywords found are then compared to the node set in $nodes. Every node containing any of the keywords is copied to the result sequence. $nodes The node set that is to be searched for the keyword set $regular-expression The regular expressions to be matched against the fulltext index Returns the sequence of all of the matching nodes Deprecated: This function is eXist-specific and should not be in the standard functions namespace. Please use text:match-any() instead. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. xcollection xcollection($collection-uris as xs:string+, ...) node()* Returns the document nodes in the collections $collection-uris non-recursively, i.e. does not include document nodes found in sub-collections. C.f. fn:collection(). Collection URIs can be specified either as a simple collection path or an XMLDB URI. $collection-uris The collection URIs Returns the document nodes from the specified collections excluding sub-collections Deprecated: This function is eXist-specific and deprecated. It should not be in the standard functions namespace. Please use http://exist-db.org/xquery/xmldb:xcollection() instead. This function could be removed at anytime during the 1.5 development and will be removed in the 1.6 release. |
|
From: Dannes W. <da...@ex...> - 2010-03-18 18:53:18
|
All, during exist-db startup (trunk) I see the following: 17 Mar 2010 15:06:21,321 [main] INFO (JettyStart.java [run]:242) - http://localhost:8085/exist 17 Mar 2010 15:06:21,327 [main] INFO (JettyStart.java [run]:256) - http://localhost:8085/exist/openid the openId stuff is started by default. Since I do not use it myself, I probably do not want to have it started? cheers Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Adam R. <ad...@ex...> - 2010-03-17 21:34:33
|
On 17 March 2010 21:07, Wolfgang Meier <wol...@ex...> wrote:
>> This is just a simple example, see the attached diff, but I am
>> wondering if there is value in, expanding on this concept and pushing
>> xquery line context information into the datatype system for better
>> errors.
>
> It somehow doesn't feel right to add caller information to the
> returned data values. Our approach so far has been to catch the thrown
> exception on a higher level and add the line information there. See
> class FunctionCall for an example. I think this concept could be
> extended, though we won't be able to cover all cases where a type
> error could occur.
> But for your example, the if expression could certainly catch and
> rethrow the exception.
Okay cool :-)
I actually simplified, in my case the invoking expression was OpOr.
I agree that maybe it doesnt make sense to send in the Expression to
the Type, which is what lead me to thinking about changing the
Exception thrown by Types from XPathExpression (which I think we over
use too much) to something new like XMLDataTypeException, this should
then immediately highlight where this Exception is being thrown, we
can then write wrapper try/catch in the culprit Expressions that catch
that Exception, and throw an XPathException with the line and column
number of the Expression added in.
Hows that sound?
> Wolfgang
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
64 messages has been excluded from this view by a project administrator.
