exist-development — eXist Developer's List

Re: [Exist-development] default context in functions

[Dmitriy S. <sha...@gm...>]

On Wed, 2010-07-21 at 14:05 +0200, James Fuller wrote:
> On 21 July 2010 13:37, Dmitriy Shabanov <sha...@gm...> wrote:
> > Note: There are functions like fn:string or fn:base-uri that "... In the
> > zero-argument version of the function, $arg defaults to the context
> > item. That is, calling fn:string() is equivalent to calling
> > fn:string(.). ..."
> >
> > The question "why" didn't get answer ...
> 
> yes, we could suggest to xquery WG that user defined functions might
> have a similar shorthand
> but there are probs with this route as well.

This questing at xsl group F2F meeting at Prague got no answer. Guess,
same result for xquery group.

My two cent to have context item as parameter if no provided, but groups
think that it can confuse end-user (same time there are some functions,
strange :-)

-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] default context in functions

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

On 21 July 2010 13:37, Dmitriy Shabanov <sha...@gm...> wrote:
> Note: There are functions like fn:string or fn:base-uri that "... In the
> zero-argument version of the function, $arg defaults to the context
> item. That is, calling fn:string() is equivalent to calling
> fn:string(.). ..."
>
> The question "why" didn't get answer ...

yes, we could suggest to xquery WG that user defined functions might
have a similar shorthand
but there are probs with this route as well.

James Fuller

Re: [Exist-development] default context in functions

[Dmitriy S. <sha...@gm...>]

Note: There are functions like fn:string or fn:base-uri that "... In the
zero-argument version of the function, $arg defaults to the context
item. That is, calling fn:string() is equivalent to calling
fn:string(.). ..."

The question "why" didn't get answer ...

-- 
Cheers,

Dmitriy Shabanov

On Wed, 2010-07-21 at 13:23 +0200, James Fuller wrote:
> noticed a few irregularities in my original posting, for the sake of
> clarity I will summarise:
> 
> as expected, this works
> --------------------------------------------------------------------
> 
> declare function local:test($arg){
> name($arg)
> };
> 
> let $a := <test><a></a><b/></test>
> return
> local:test($a)
> 
> --------------------------------------------------------------------
> 
> then we have
> 
> --------------------------------------------------------------------
> 
> declare function local:test(){
> name()
> };
> 
> let $a := <test><a></a><b/></test>
> return
> $a/local:test()
> 
> --------------------------------------------------------------------
> 
> which works, and I can see the sense of it, as we are using the xpath
> to set context, but can't find the 'words' in the specs that allow
> this.
> 
> similarly
> 
> --------------------------------------------------------------------
> 
> declare function local:test(){
> name(.)
> };
> 
> //*/local:test()
> 
> --------------------------------------------------------------------
> 
> but what is defo not conformant is something like
> 
> --------------------------------------------------------------------
> 
> declare function local:test(){
> //*
> };
> 
> local:test()
> 
> --------------------------------------------------------------------
> 
> which just arbitrarily gives function access to db root context.
> 
> a few thoughts as I am occupied working on other stuff at the moment
> but will scan the specs soon:
> 
> * does an unadorned function, e.g. without being in an explicit xpath
> actually have a default context always supplied ? e.g. is local:test()
> shorthand for /./local-test() or something of the kind ?
> 
> * is context passed via xpath e.g. //$arg/local:test() or
> //*/local:test() ok, seems to invalidate what is said in the XQuery
> section 3.1.5
> 
> * as a lot of existing xquery code (mine included) wil break with this
> change, as suggested we need both an exist option and a util function
> to switch behaviors and have default configured as to how things work
> now. For those who want more conformant behavior or more security on
> the context that a function is allowed can switch this default
> configuration

Re: [Exist-development] default context in functions

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

noticed a few irregularities in my original posting, for the sake of
clarity I will summarise:

as expected, this works
--------------------------------------------------------------------

declare function local:test($arg){
name($arg)
};

let $a := <test><a></a><b/></test>
return
local:test($a)

--------------------------------------------------------------------

then we have

--------------------------------------------------------------------

declare function local:test(){
name()
};

let $a := <test><a></a><b/></test>
return
$a/local:test()

--------------------------------------------------------------------

which works, and I can see the sense of it, as we are using the xpath
to set context, but can't find the 'words' in the specs that allow
this.

similarly

--------------------------------------------------------------------

declare function local:test(){
name(.)
};

//*/local:test()

--------------------------------------------------------------------

but what is defo not conformant is something like

--------------------------------------------------------------------

declare function local:test(){
//*
};

local:test()

--------------------------------------------------------------------

which just arbitrarily gives function access to db root context.

a few thoughts as I am occupied working on other stuff at the moment
but will scan the specs soon:

* does an unadorned function, e.g. without being in an explicit xpath
actually have a default context always supplied ? e.g. is local:test()
shorthand for /./local-test() or something of the kind ?

* is context passed via xpath e.g. //$arg/local:test() or
//*/local:test() ok, seems to invalidate what is said in the XQuery
section 3.1.5

* as a lot of existing xquery code (mine included) wil break with this
change, as suggested we need both an exist option and a util function
to switch behaviors and have default configured as to how things work
now. For those who want more conformant behavior or more security on
the context that a function is allowed can switch this default
configuration

thx, J

Re: [Exist-development] default context in functions

[Thomas W. <tho...@gm...>]

James,

On the top of the configuration setting it will be a good idea to have an
option set the value on fly for the current running XQuery.

We may have cases where on the same machine we have old and new code and we
need to make sure changing the setting in the config to the current behavior
will still allow the new code to run properly switching on fly to the new
mode.

I hope this will help.

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 21 July 2010 11:30, James Fuller <jam...@ex...> wrote:

> sure,
>
> but I think this maybe a far ranging issue, e.g.
>
> declare function local:test(){
> //*
> };
>
> local:test()
>
> demonstrates that irregardless of arity, functions called do not
> restriction any xquery context ... this would have some pretty big
> ramifications for people's existing xquery code/apps that expect the
> behavior; perhaps we need to introduce an exist option to be able to
> switch/configure.
>
> It also means that its not just a simple check on xquery context, say
> in the abstract class org.exist.xquery.Function but we have to do some
> changes to ensure that no xquery context at all is provided.
>
> unsure about doing this, any more thoughts ?
>
> thx, J
>
>
> On 21 July 2010 12:16, Adam Retter <ad...@ex...> wrote:
> > Yes I agree we should fix this, are you volunteering ;-)
> >
> > On 18 July 2010 10:35, James Fuller <jam...@ex...> wrote:
> >> courtesy Norm Walsh via twitter
> >>
> >> paraphrasing: 'During eval of a fn, the context item, pos, size is
> >> undefined, except where it is def by some expr inside the fn'
> >>
> >> section 3.1.5 Function Calls in XQuery spec defines the correct
> >> behavior for this.
> >>
> >> so looks like we need to sort this out, we should probably also create
> >> an xquery level unit test for this as well ... something I think we
> >> should do whenever we apply a patch/bug/tweak that can be
> >> characterized easily as expected result from xquery unit test.
> >>
> >> J
> >>
> >>
> >>
> >>
> >> On 17 July 2010 14:21, Dmitriy Shabanov <sha...@gm...> wrote:
> >>> On Sat, 2010-07-17 at 13:31 +0200, James Fuller wrote:
> >>>> I can appreciate that both functions ( e.g. local:test() and name() )
> >>>> when given no argument use default context but can't find in xquery
> >>>> related specs what the rules are for default context for a function
> >>>> with no arguments.
> >>>
> >>> The function don't have context. You right, it should throw error.
> (BTW,
> >>> I like the way it work now)
> >>>
> >>>> should this throw an [XPDY0002] evaluation of an expression relies on
> >>>> some part of the dynamic context that has not been assigned a value:
> >>>> {context item}.
> >>>
> >>> --
> >>> Cheers,
> >>>
> >>> Dmitriy Shabanov
> >>>
> >>>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by Sprint
> >> What will you do first with EVO, the first 4G phone?
> >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> >> _______________________________________________
> >> 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
> >
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

Re: [Exist-development] Trunk does not build?

[Adam R. <ad...@ex...>]

On 21 July 2010 11:48, Dmitriy Shabanov <sha...@gm...> wrote:
> On Wed, 2010-07-21 at 10:59 +0100, Adam Retter wrote:
>> >  Adam did
>> > commit test without fix :(
>>
>> Yes indeed, it was agreed though, I needed the test case so that
>> Wolfgang could take a look at it this afternoon and try and solve the
>> problem...
>
> Can it be disabled till fix? (BTW, XQTS have similar one and it is not
> simple to resolve)

I dont think its a problem. Its a single failing test in
ModuleStoreTests, results in an Error. Otherwise as far as I am aware,
ALL other tests should pass :-)

> --
> Cheers,
>
> Dmitriy Shabanov
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] default context in functions

[Dmitriy S. <sha...@gm...>]

On Wed, 2010-07-21 at 12:30 +0200, James Fuller wrote:
> demonstrates that irregardless of arity, functions called do not
> restriction any xquery context ... this would have some pretty big
> ramifications for people's existing xquery code/apps that expect the
> behavior; perhaps we need to introduce an exist option to be able to
> switch/configure.

+1 for an configurable option

-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] Trunk does not build?

[Dmitriy S. <sha...@gm...>]

On Wed, 2010-07-21 at 10:59 +0100, Adam Retter wrote:
> >  Adam did
> > commit test without fix :(
> 
> Yes indeed, it was agreed though, I needed the test case so that
> Wolfgang could take a look at it this afternoon and try and solve the
> problem...

Can it be disabled till fix? (BTW, XQTS have similar one and it is not
simple to resolve)

-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] default context in functions

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

sure,

but I think this maybe a far ranging issue, e.g.

declare function local:test(){
//*
};

local:test()

demonstrates that irregardless of arity, functions called do not
restriction any xquery context ... this would have some pretty big
ramifications for people's existing xquery code/apps that expect the
behavior; perhaps we need to introduce an exist option to be able to
switch/configure.

It also means that its not just a simple check on xquery context, say
in the abstract class org.exist.xquery.Function but we have to do some
changes to ensure that no xquery context at all is provided.

unsure about doing this, any more thoughts ?

thx, J


On 21 July 2010 12:16, Adam Retter <ad...@ex...> wrote:
> Yes I agree we should fix this, are you volunteering ;-)
>
> On 18 July 2010 10:35, James Fuller <jam...@ex...> wrote:
>> courtesy Norm Walsh via twitter
>>
>> paraphrasing: 'During eval of a fn, the context item, pos, size is
>> undefined, except where it is def by some expr inside the fn'
>>
>> section 3.1.5 Function Calls in XQuery spec defines the correct
>> behavior for this.
>>
>> so looks like we need to sort this out, we should probably also create
>> an xquery level unit test for this as well ... something I think we
>> should do whenever we apply a patch/bug/tweak that can be
>> characterized easily as expected result from xquery unit test.
>>
>> J
>>
>>
>>
>>
>> On 17 July 2010 14:21, Dmitriy Shabanov <sha...@gm...> wrote:
>>> On Sat, 2010-07-17 at 13:31 +0200, James Fuller wrote:
>>>> I can appreciate that both functions ( e.g. local:test() and name() )
>>>> when given no argument use default context but can't find in xquery
>>>> related specs what the rules are for default context for a function
>>>> with no arguments.
>>>
>>> The function don't have context. You right, it should throw error. (BTW,
>>> I like the way it work now)
>>>
>>>> should this throw an [XPDY0002] evaluation of an expression relies on
>>>> some part of the dynamic context that has not been assigned a value:
>>>> {context item}.
>>>
>>> --
>>> Cheers,
>>>
>>> Dmitriy Shabanov
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> 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
>

Re: [Exist-development] default context in functions

[Adam R. <ad...@ex...>]

Yes I agree we should fix this, are you volunteering ;-)

On 18 July 2010 10:35, James Fuller <jam...@ex...> wrote:
> courtesy Norm Walsh via twitter
>
> paraphrasing: 'During eval of a fn, the context item, pos, size is
> undefined, except where it is def by some expr inside the fn'
>
> section 3.1.5 Function Calls in XQuery spec defines the correct
> behavior for this.
>
> so looks like we need to sort this out, we should probably also create
> an xquery level unit test for this as well ... something I think we
> should do whenever we apply a patch/bug/tweak that can be
> characterized easily as expected result from xquery unit test.
>
> J
>
>
>
>
> On 17 July 2010 14:21, Dmitriy Shabanov <sha...@gm...> wrote:
>> On Sat, 2010-07-17 at 13:31 +0200, James Fuller wrote:
>>> I can appreciate that both functions ( e.g. local:test() and name() )
>>> when given no argument use default context but can't find in xquery
>>> related specs what the rules are for default context for a function
>>> with no arguments.
>>
>> The function don't have context. You right, it should throw error. (BTW,
>> I like the way it work now)
>>
>>> should this throw an [XPDY0002] evaluation of an expression relies on
>>> some part of the dynamic context that has not been assigned a value:
>>> {context item}.
>>
>> --
>> Cheers,
>>
>> Dmitriy Shabanov
>>
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> 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

Re: [Exist-development] Trunk does not build?

[Adam R. <ad...@ex...>]

>  Adam did
> commit test without fix :(

Yes indeed, it was agreed though, I needed the test case so that
Wolfgang could take a look at it this afternoon and try and solve the
problem...

> On Tue, 2010-07-20 at 23:43 +0100, Adam Retter wrote:
>> Yes I see the problems as well, but I believe these were prior to my commits?
>>
>>
>> On 20 July 2010 19:52, Dannes Wessels <da...@ex...> wrote:
>> > All,
>> >
>> > junit in trunk seems to fail since rev1200, but 8 commits since then. Do the tests run locally okay for you?
>> >
>
> --
> Cheers,
>
> Dmitriy Shabanov
>
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] Trunk does not build?

[Dmitriy S. <sha...@gm...>]

The Wolfgang did change mods, so tests should be corrected. And Adam did
commit test without fix :(

On Tue, 2010-07-20 at 23:43 +0100, Adam Retter wrote:
> Yes I see the problems as well, but I believe these were prior to my commits?
> 
> 
> On 20 July 2010 19:52, Dannes Wessels <da...@ex...> wrote:
> > All,
> >
> > junit in trunk seems to fail since rev1200, but 8 commits since then. Do the tests run locally okay for you?
> >

-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] Trunk does not build?

[Adam R. <ad...@ex...>]

Yes I see the problems as well, but I believe these were prior to my commits?


On 20 July 2010 19:52, Dannes Wessels <da...@ex...> wrote:
> All,
>
> junit in trunk seems to fail since rev1200, but 8 commits since then. Do the tests run locally okay for you?
>
> Kind regards
>
> Dannes
>
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> 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

[Exist-development] Trunk does not build?

[Dannes W. <da...@ex...>]

All,

junit in trunk seems to fail since rev1200, but 8 commits since then. Do the tests run locally okay for you?

Kind regards

Dannes

--
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] Strange NPE....

[Andrzej J. T. <an...@ch...>]

Wolfgang:

> java.lang.NullPointerException
> 	at org.exist.stax.EmbeddedXMLStreamReader.verifyOriginNodeId(EmbeddedXMLStreamReader.java:250)
> 	at org.exist.stax.EmbeddedXMLStreamReader.next(EmbeddedXMLStreamReader.java:240)
> 	at org.exist.dom.VirtualNodeSet.addChildren(VirtualNodeSet.java:503)
> 	at org.exist.dom.VirtualNodeSet.getNodes(VirtualNodeSet.java:449)
> 	at org.exist.dom.VirtualNodeSet.realize(VirtualNodeSet.java:567)
> 	at org.exist.dom.VirtualNodeSet.getLength(VirtualNodeSet.java:736)
> 	at org.exist.dom.VirtualNodeSet.isEmpty(VirtualNodeSet.java:646)
> 	at org.exist.xquery.Atomize.atomize(Atomize.java:75)
> 	at org.exist.xquery.Atomize.eval(Atomize.java:66)
> 	at org.exist.xquery.CastExpression.eval(CastExpression.java:95)
> 	at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
> 	at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
> 	at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
> 	at org.exist.xquery.DynamicCardinalityCheck.eval(DynamicCardinalityCheck.java:71)
> 	at org.exist.xquery.UntypedValueCheck.eval(UntypedValueCheck.java:82)
> 	at org.exist.xquery.FunctionCall.evalFunction(FunctionCall.java:274)
> 	at org.exist.xquery.FunctionCall.eval(FunctionCall.java:201)
> 	at org.exist.xquery.GeneralComparison.genericCompare(GeneralComparison.java:501)
> 	at org.exist.xquery.GeneralComparison.genericCompare(GeneralComparison.java:494)
> 	at org.exist.xquery.GeneralComparison.eval(GeneralComparison.java:449)
> 	at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)

>
> It looks like some inconsistency in the persistent DOM of the
> document. I would suggest to run the consistency checker to see if it
> reports any issues.

I don't think it's a persistent DOM problem...for a couple of reasons:

1) Rerunning the exact same job, that traverses the identical data, does not consistently throw this exception. If there
was a DOM issue, I think it would die consistently, non?

2) Looking at the code where it died, the line in EmbeddedXMLStreamReader.verifyOriginNodeId() that NPE'ed is:

	origin.setInternalAddress(StoredNode.UNKNOWN_NODE_IMPL_ADDRESS);

   but the two lines before that are:

	if (!nodeId.equals(origin.getNodeId())) {
	    LOG.warn("expected node id " + origin.getNodeId() + ", got " + nodeId + "; resyncing address");

   the only way for line 250 to NPE would be if origin was null.  But if origin was null, then it should have NPE'ed in
   the if or LOG statements first!

   The conclusion is that there is a concurrency issue somewhere....and orgin was changed from a valid value to null
   by another thread sometime between the LOG statement and before line 250.

Any thoughts or ideas?

Thanks!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] default context in functions

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

courtesy Norm Walsh via twitter

paraphrasing: 'During eval of a fn, the context item, pos, size is
undefined, except where it is def by some expr inside the fn'

section 3.1.5 Function Calls in XQuery spec defines the correct
behavior for this.

so looks like we need to sort this out, we should probably also create
an xquery level unit test for this as well ... something I think we
should do whenever we apply a patch/bug/tweak that can be
characterized easily as expected result from xquery unit test.

J




On 17 July 2010 14:21, Dmitriy Shabanov <sha...@gm...> wrote:
> On Sat, 2010-07-17 at 13:31 +0200, James Fuller wrote:
>> I can appreciate that both functions ( e.g. local:test() and name() )
>> when given no argument use default context but can't find in xquery
>> related specs what the rules are for default context for a function
>> with no arguments.
>
> The function don't have context. You right, it should throw error. (BTW,
> I like the way it work now)
>
>> should this throw an [XPDY0002] evaluation of an expression relies on
>> some part of the dynamic context that has not been assigned a value:
>> {context item}.
>
> --
> Cheers,
>
> Dmitriy Shabanov
>
>

Re: [Exist-development] default context in functions

[Dmitriy S. <sha...@gm...>]

On Sat, 2010-07-17 at 13:31 +0200, James Fuller wrote:
> I can appreciate that both functions ( e.g. local:test() and name() )
> when given no argument use default context but can't find in xquery
> related specs what the rules are for default context for a function
> with no arguments.

The function don't have context. You right, it should throw error. (BTW,
I like the way it work now)

> should this throw an [XPDY0002] evaluation of an expression relies on
> some part of the dynamic context that has not been assigned a value:
> {context item}.

-- 
Cheers,

Dmitriy Shabanov

[Exist-development] default context in functions

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

wondering if we are a little lax with how default context is
accessible to functions

the following xquery is fine

--------------------------------------------------------------------

declare function local:test($arg){
name($arg)
};

let $a := <test><a></a><b/></test>
return
$a/local:test(.)

--------------------------------------------------------------------

and indeed runs properly

but what I found interesting was the following xquery

--------------------------------------------------------------------

declare function local:test(){
name()
};

let $a := <test><a></a><b/></test>
return
$a/local:test()

--------------------------------------------------------------------

this also runs, which maybe a little strange.

I can appreciate that both functions ( e.g. local:test() and name() )
when given no argument use default context but can't find in xquery
related specs what the rules are for default context for a function
with no arguments.

should this throw an [XPDY0002] evaluation of an expression relies on
some part of the dynamic context that has not been assigned a value:
{context item}.

or am I missing something ?

thx, James Fuller

Re: [Exist-development] Adding number formatting functions to the util function module

[Thomas W. <tho...@gm...>]

I am glad the localization is in the focus now.

Dan, I think the the proposal is good but it does not cover all issues
related to the localisation.

I think the best way to organise the code is to create a module dedicated
for all localisation functions called  l18n.

The functions I can see there for now could be:

localized-date( $date as xs:datetime, $locale as xs:string)
 localized-currency( $number as xs:double, $locale as xs:string)
 localized-percent( $number as xs:double,  $locale as xs:string)
localized-number( $number as xs:double,  $locale as xs:string)

and many other localized function to come...

I do believe it is much better to have a specialised function for every data
type instead of a generic function with a parameter.
It is much more clear when one reads the code with dedicted functions.

Loren, I agree with you  number-to-formatted-string should go to util module
because of it generic nature.

I hope this will help.

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 15 July 2010 20:13, Dan McCreary <dan...@gm...> wrote:

> My apologies,
>
> I was aware of the XQuery 1.1 specification for *format-number()* but I
> did not communicate this format clearly to Loren.
>
> Here is the proposed format in the 1.1 XQuery Working Draft standard:
>
> http://www.w3.org/TR/xquery-11/#id-decimal-format-decl
>
> I believe we should be working to try to make it consistent with this
> specification (i.e. also XPath 2.0)
>
> - Dan
>
>
> On Thu, Jul 15, 2010 at 12:39 PM, Loren Cahlander <
> lor...@gm...> wrote:
>
>>  I am in the process of adding the formatting of a number to a formatted
>> string.  There are three general purpose functions that format the number to
>> a general number, currency or percentage according to the optionally
>> specified locale.  The fourth function takes in a format string according to
>> the format specification for the java.text.DecimalFormat Java class.
>>
>> Please supply me with your comments.  Dan will be developing XQuery unit
>> tests to validate the functions.  You will find the function docs below.
>>
>> Thank you,
>>
>> Loren
>>
>>
>>
>>  number-to-currency-string<http://localhost:8080/exist/functions/util/number-to-currency-string>
>> ------------------------------
>> util:number-to-currency-string($number as xs:double, $locale as
>> xs:string?) xs:string?
>>  Returns a currency number formatted for the specified locale if
>> specified (default otherwise) as an xs:string value.
>>     $number The number $locale two-letter ISO-639 code representing the
>> locale
>>  ------------------------------
>> Returns the formatted string
>>  number-to-formatted-string<http://localhost:8080/exist/functions/util/number-to-formatted-string>
>> ------------------------------
>> util:number-to-formatted-string($number as xs:double, $format as
>> xs:string) xs:string?
>>  Returns the number formatted as an xs:string value.
>>     $number The number $format The format pattern string. Please see the
>> JavaDoc for java.text.DecimalFormat to get the specifics of this format
>> string.
>>  ------------------------------
>> Returns the formatted string
>>  number-to-percent-string<http://localhost:8080/exist/functions/util/number-to-percent-string>
>> ------------------------------
>> util:number-to-percent-string($number as xs:double, $locale as xs:string?)
>> xs:string?
>>  Returns a percentage number formatted for the specified locale if
>> specified (default otherwise) as an xs:string value.
>>     $number The number $locale two-letter ISO-639 code representing the
>> locale
>>  ------------------------------
>> Returns the formatted string
>>  number-to-string<http://localhost:8080/exist/functions/util/number-to-string>
>> ------------------------------
>> util:number-to-string($number as xs:double, $locale as xs:string?)
>> xs:string?
>>  Returns a general-purpose number formatted for the specified locale if
>> specified (default otherwise) as an xs:string value.
>>     $number The number $locale two-letter ISO-639 code representing the
>> locale
>>  ------------------------------
>> Returns the formatted string
>>
>>
>>
>>
>
>
> --
> Dan McCreary
> Semantic Solutions Architect
> office: (952) 931-9198
> cell: (612) 986-1552
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

Re: [Exist-development] Trunk test fails

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

uggg,

thx Dannes for notifying this I should have checked teamcity ... spent
the last few hours on my local build wondering why my changes were
making the build fail.

checking, I think it maybe some of Dmitriy recent stuff.

hey Dmitriy, can you have a quick check ? thx in advance ,J

On 15 July 2010 22:42, Dannes Wessels <da...@ex...> wrote:
> >From team city:
>
> UsersAndPermissionsTest.testCreateUser  View test details   (org.exist.soap)
>    AxisFault
>    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>    faultSubcode:
>    Please wait... Show stacktrace »
>    « Hide stacktrace
>    « Hide stacktrace
>
> First failed in build #1.5-rev11970-813
> with 3 changes RemoteDatabaseImplTest.testGetCollection View test
> details (org.exist.xmldb.XmldbRemoteTests: org.exist.xmldb)
>    junit.framework.AssertionFailedError: Failed to generate request:
> Unsupported Java type: org.exist.security.UserImpl
>    at junit.framework.Assert.fail(Assert.java:47)
>    at org.exist.xmldb.RemoteDatabaseImplTest.testGetCollection(RemoteDatabaseImplTest.java:91)
>    Please wait... Show stacktrace »
>
> Dmitriy, please could you check? do you run junit suite before commit?
>
> thnx
>
> Dannes
>
>
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

[Exist-development] Trunk test fails

[Dannes W. <da...@ex...>]

>From team city:

UsersAndPermissionsTest.testCreateUser  View test details   (org.exist.soap)
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    Please wait... Show stacktrace »
    « Hide stacktrace
    « Hide stacktrace

First failed in build #1.5-rev11970-813
with 3 changes RemoteDatabaseImplTest.testGetCollection View test
details (org.exist.xmldb.XmldbRemoteTests: org.exist.xmldb)
    junit.framework.AssertionFailedError: Failed to generate request:
Unsupported Java type: org.exist.security.UserImpl
    at junit.framework.Assert.fail(Assert.java:47)
    at org.exist.xmldb.RemoteDatabaseImplTest.testGetCollection(RemoteDatabaseImplTest.java:91)
    Please wait... Show stacktrace »

Dmitriy, please could you check? do you run junit suite before commit?

thnx

Dannes


-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] Adding number formatting functions to the util function module

[Loren C. <lor...@gm...>]

The conf.xml file just needs <module class="org.exist.xslt.functions.XSLTModule" uri="http://exist-db.org/xquery/xslt"/> added to it.


On Jul 15, 2010, at 02:21 PM, Dmitriy Shabanov wrote:

> XSL have status recommendation & it have this function.
> 
> eXist have this module
> http://exist.svn.sourceforge.net/viewvc/exist/trunk/eXist/extensions/xslt/src/org/exist/xslt/functions/
> 
> (NOTE: the module namespace must be changed to
> http://www.w3.org/1999/XSL/Transform)
> 
> -- 
> Cheers,
> 
> Dmitriy Shabanov
> 
> On Thu, 2010-07-15 at 14:13 -0500, Dan McCreary wrote:
>> My apologies,
>> 
>> I was aware of the XQuery 1.1 specification for format-number() but I
>> did not communicate this format clearly to Loren.
>> 
>> Here is the proposed format in the 1.1 XQuery Working Draft standard:
>> 
>> http://www.w3.org/TR/xquery-11/#id-decimal-format-decl
>> 
>> I believe we should be working to try to make it consistent with this
>> specification (i.e. also XPath 2.0)
>> 
>> - Dan
>> 
>> On Thu, Jul 15, 2010 at 12:39 PM, Loren Cahlander
>> <lor...@gm...> wrote:
>>        I am in the process of adding the formatting of a number to a
>>        formatted string.  There are three general purpose functions
>>        that format the number to a general number, currency or
>>        percentage according to the optionally specified locale.  The
>>        fourth function takes in a format string according to the
>>        format specification for the java.text.DecimalFormat Java
>>        class.
>> 
>> 
>>        Please supply me with your comments.  Dan will be developing
>>        XQuery unit tests to validate the functions.  You will find
>>        the function docs below.
>> 
>> 
>>        Thank you,
>> 
>> 
>>        Loren
>> 
>> 
>> 
>> 
>> 
>> 
>>        number-to-currency-string
>> 
>>        ______________________________________________________________
>>        util:number-to-currency-string($number as xs:double, $locale
>>        as xs:string?) xs:string?
>>        Returns a currency number formatted for the specified locale
>>        if specified (default otherwise) as an xs:string value.
>> 
>> 
>>        $number
>>        The number
>>        $locale
>>        two-letter ISO-639 code
>>        representing the locale
>> 
>>        ______________________________________________________________
>>        Returns the formatted string
>>        number-to-formatted-string
>> 
>>        ______________________________________________________________
>>        util:number-to-formatted-string($number as xs:double, $format
>>        as xs:string) xs:string?
>>        Returns the number formatted as an xs:string value.
>> 
>> 
>>        $number
>>        The number
>>        $format
>>        The format pattern string.
>>        Please see the JavaDoc for
>>        java.text.DecimalFormat to get
>>        the specifics of this format
>>        string.
>> 
>>        ______________________________________________________________
>>        Returns the formatted string
>>        number-to-percent-string
>> 
>>        ______________________________________________________________
>>        util:number-to-percent-string($number as xs:double, $locale as
>>        xs:string?) xs:string?
>>        Returns a percentage number formatted for the specified locale
>>        if specified (default otherwise) as an xs:string value.
>> 
>> 
>>        $number
>>        The number
>>        $locale
>>        two-letter ISO-639 code
>>        representing the locale
>> 
>>        ______________________________________________________________
>>        Returns the formatted string
>>        number-to-string
>> 
>>        ______________________________________________________________
>>        util:number-to-string($number as xs:double, $locale as
>>        xs:string?) xs:string?
>>        Returns a general-purpose number formatted for the specified
>>        locale if specified (default otherwise) as an xs:string value.
>> 
>> 
>>        $number
>>        The number
>>        $locale
>>        two-letter ISO-639 code
>>        representing the locale
>> 
>>        ______________________________________________________________
>>        Returns the formatted string
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> Dan McCreary
>> Semantic Solutions Architect
>> office: (952) 931-9198
>> cell: (612) 986-1552
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________ Exist-development mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-development
> 

Re: [Exist-development] Adding number formatting functions to the util function module

[Dmitriy S. <sha...@gm...>]

XSL have status recommendation & it have this function.

eXist have this module
http://exist.svn.sourceforge.net/viewvc/exist/trunk/eXist/extensions/xslt/src/org/exist/xslt/functions/

(NOTE: the module namespace must be changed to
http://www.w3.org/1999/XSL/Transform)

-- 
Cheers,

Dmitriy Shabanov

On Thu, 2010-07-15 at 14:13 -0500, Dan McCreary wrote:
> My apologies,
> 
> I was aware of the XQuery 1.1 specification for format-number() but I
> did not communicate this format clearly to Loren.
> 
> Here is the proposed format in the 1.1 XQuery Working Draft standard:
> 
> http://www.w3.org/TR/xquery-11/#id-decimal-format-decl
> 
> I believe we should be working to try to make it consistent with this
> specification (i.e. also XPath 2.0)
> 
> - Dan
> 
> On Thu, Jul 15, 2010 at 12:39 PM, Loren Cahlander
> <lor...@gm...> wrote:
>         I am in the process of adding the formatting of a number to a
>         formatted string.  There are three general purpose functions
>         that format the number to a general number, currency or
>         percentage according to the optionally specified locale.  The
>         fourth function takes in a format string according to the
>         format specification for the java.text.DecimalFormat Java
>         class.
>         
>         
>         Please supply me with your comments.  Dan will be developing
>         XQuery unit tests to validate the functions.  You will find
>         the function docs below.
>         
>         
>         Thank you,
>         
>         
>         Loren
>         
>         
>         
>         
>         
>         
>         number-to-currency-string
>         
>         ______________________________________________________________
>         util:number-to-currency-string($number as xs:double, $locale
>         as xs:string?) xs:string?
>         Returns a currency number formatted for the specified locale
>         if specified (default otherwise) as an xs:string value.
>         
>         
>         $number
>         The number
>         $locale
>         two-letter ISO-639 code
>         representing the locale
>         
>         ______________________________________________________________
>         Returns the formatted string
>         number-to-formatted-string
>         
>         ______________________________________________________________
>         util:number-to-formatted-string($number as xs:double, $format
>         as xs:string) xs:string?
>         Returns the number formatted as an xs:string value.
>         
>         
>         $number
>         The number
>         $format
>         The format pattern string.
>         Please see the JavaDoc for
>         java.text.DecimalFormat to get
>         the specifics of this format
>         string.
>         
>         ______________________________________________________________
>         Returns the formatted string
>         number-to-percent-string
>         
>         ______________________________________________________________
>         util:number-to-percent-string($number as xs:double, $locale as
>         xs:string?) xs:string?
>         Returns a percentage number formatted for the specified locale
>         if specified (default otherwise) as an xs:string value.
>         
>         
>         $number
>         The number
>         $locale
>         two-letter ISO-639 code
>         representing the locale
>         
>         ______________________________________________________________
>         Returns the formatted string
>         number-to-string
>         
>         ______________________________________________________________
>         util:number-to-string($number as xs:double, $locale as
>         xs:string?) xs:string?
>         Returns a general-purpose number formatted for the specified
>         locale if specified (default otherwise) as an xs:string value.
>         
>         
>         $number
>         The number
>         $locale
>         two-letter ISO-639 code
>         representing the locale
>         
>         ______________________________________________________________
>         Returns the formatted string
>         
>         
>         
>         
>         
>         
> 
> 
> 
> -- 
> Dan McCreary
> Semantic Solutions Architect
> office: (952) 931-9198
> cell: (612) 986-1552
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________ Exist-development mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] Adding number formatting functions to the util function module

[Dan M. <dan...@gm...>]

My apologies,

I was aware of the XQuery 1.1 specification for *format-number()* but I did
not communicate this format clearly to Loren.

Here is the proposed format in the 1.1 XQuery Working Draft standard:

http://www.w3.org/TR/xquery-11/#id-decimal-format-decl

I believe we should be working to try to make it consistent with this
specification (i.e. also XPath 2.0)

- Dan

On Thu, Jul 15, 2010 at 12:39 PM, Loren Cahlander <lor...@gm...
> wrote:

> I am in the process of adding the formatting of a number to a formatted
> string.  There are three general purpose functions that format the number to
> a general number, currency or percentage according to the optionally
> specified locale.  The fourth function takes in a format string according to
> the format specification for the java.text.DecimalFormat Java class.
>
> Please supply me with your comments.  Dan will be developing XQuery unit
> tests to validate the functions.  You will find the function docs below.
>
> Thank you,
>
> Loren
>
>
>
> number-to-currency-string<http://localhost:8080/exist/functions/util/number-to-currency-string>
> ------------------------------
> util:number-to-currency-string($number as xs:double, $locale as xs:string?)
> xs:string?
> Returns a currency number formatted for the specified locale if specified
> (default otherwise) as an xs:string value.
> $numberThe number$localetwo-letter ISO-639 code representing the locale
> ------------------------------
> Returns the formatted string
> number-to-formatted-string<http://localhost:8080/exist/functions/util/number-to-formatted-string>
> ------------------------------
> util:number-to-formatted-string($number as xs:double, $format as xs:string)
> xs:string?
> Returns the number formatted as an xs:string value.
> $numberThe number$formatThe format pattern string. Please see the JavaDoc
> for java.text.DecimalFormat to get the specifics of this format string.
> ------------------------------
> Returns the formatted string
> number-to-percent-string<http://localhost:8080/exist/functions/util/number-to-percent-string>
> ------------------------------
> util:number-to-percent-string($number as xs:double, $locale as xs:string?)
> xs:string?
> Returns a percentage number formatted for the specified locale if specified
> (default otherwise) as an xs:string value.
> $numberThe number$localetwo-letter ISO-639 code representing the locale
> ------------------------------
> Returns the formatted string
> number-to-string<http://localhost:8080/exist/functions/util/number-to-string>
> ------------------------------
> util:number-to-string($number as xs:double, $locale as xs:string?)
> xs:string?
> Returns a general-purpose number formatted for the specified locale if
> specified (default otherwise) as an xs:string value.
> $numberThe number$localetwo-letter ISO-639 code representing the locale
> ------------------------------
> Returns the formatted string
>
>
>
>


-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1552

[Exist-development] security refactoring

[Dmitriy S. <sha...@gm...>]

Hello,

I want to add new accounts: 

 - 'system account' (id = 0, dba group), it will be use by system only.
It will be useful as owner of the /system resources, so it will be never
modified by anybody, only by system it self (throw special functions);

 - 'nobody' (id = -1, guest group), the use didn't offer himself. This
account can't be used as resource owner.

Next in my plan (next two weeks):

 - change the major version number of the security subsystem;

 - add collection /system/security, it will be use for setting, accounts
and roles information;

 - use collections: /system/security/( internal, openid, ldap,
activeDirectory) & etc, one per realm, other words each realm will have 
separate collection. 

 - each realm's collection will have subcollection: role (or should I
use 'group' as name?), user & file: settings.xml (I'll implement runtime
reconfiguration)

 - each group or user will be at single file.

(I will put converter to transform old structure to new one)

Any comments?

-- 
Cheers,

Dmitriy Shabanov