Menu
▾
▴
exist-development — eXist Developer's List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
| 2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
| 2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
| 2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
| 2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Adam R. <ad...@ex...> - 2012-12-29 13:26:23
|
Ah! Indeed I was using Chrome. On 29 December 2012 09:01, Jens Østergaard Petersen <oe...@gm...> wrote: > Hi Adam, > > Yes, this form does not work with Chrome (and Safari) - it is the same on Alain's site, <http://www.agencexml.com/xsltforms/flags.xml>. I guess that's the risk of doing the transformation in the browser …. > > There are some places where Alain uses PHP that need to be rewritten. > > Best, > > Jens > > On Dec 29, 2012, at 1:29 AM, Adam Retter <ad...@ex...> wrote: > >> On 28 December 2012 19:32, Dannes Wessels <da...@ex...> wrote: >>> Hi >>> >>> On 28 Dec 2012, at 16:44 , Jens Østergaard Petersen <oe...@gm...> >>> wrote: >>> >>> Would it be possible to update the XSLTForms Demo? What is displayed is the >>> very first draft I made …. The XSLT Files are old as well. >>> >> >> Typically - the first one I clicked on does not work its under SVG >> Examples and is called "Colored Flags". Good news is that the rest of >> the ones I checked do work ;-) >> >> >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Adam R. <ad...@ex...> - 2012-12-29 13:19:19
|
> However whilst experimenting to find a short reproducible test-case, I
> came upon this:
>
> xs:string(
> if(current-date() eq current-date() - xs:dayTimeDuration("P1D"))then
> ()
> else
> "thing"
> )
>
> Now this code should do exactly the same as the above code, as both ()
> and fn:error(...) are evaluated to an empty sequence. However they
> dont, and this code does not cause the warning you were seeing. In
> fact if I debug it, it seems that () is being evaluated not to the
> type "empty()" but instead to the type "node()".
>
> This definitely stikes me as a bug in eXist, as () is certainly an
> empty sequence and not a node...
>
> Wolf any thoughts please?
Digging a little deeper into this one, it looks to me like
PathExpr.returnsType() should be re-written from:
public int returnsType() {
if (steps.size() == 0)
//Not so simple. ITEM should be re-tuned in some circumstances
that have to be determined
return Type.NODE;
return steps.get(steps.size() - 1).returnsType();
}
to:
@Override
public int returnsType() {
if(steps.isEmpty()) {
return Type.EMPTY;
} else {
return steps.get(steps.size() - 1).returnsType();
}
}
I havent run the test suite yet, but a quick play with eXist and a few
demo apps and all appears to work - I will run the test suite
shortly...
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Adam R. <ad...@ex...> - 2012-12-29 13:11:17
|
Hey Joe,
Unfortunately you made this too interesting and easy to dig into for
me to resist!
So the problem is caused at compilation time, and its caused by this
function from FunctX:
declare function functx:duration-from-timezone
( $timezone as xs:string ) as xs:dayTimeDuration {
xs:dayTimeDuration(
if (not(matches($timezone,'Z|[\+\-]\d{2}:\d{2}')))
then error(xs:QName('functx:Invalid_Timezone_Value'))
else if ($timezone = 'Z')
then 'PT0S'
else replace($timezone,'\+?(\d{2}):\d{2}','PT$1H')
)
} ;
If I run this through the debugger, I can reduce this expression to
the following reproducible test case to cause your warning:
xs:string(
if(current-date() eq current-date() - xs:dayTimeDuration("P1D"))then
error(xs:QName("someError"))
else
"thing"
)
Basically the outer xs:string uses the CastExpression class in eXist,
and at compilation time it needs to understand what the possible type
of the evaluated if/else expression could be. As such it gets the type
of the result of the 'then' branch of the if expression, and also get
the type of the result of the 'else' branch of the if expression. It
then tries to find a super-type of these two types
(Type.getCommonSuperType(x, y) in eXist Java code).
You can see the XDM type hierarchy here:
http://www.w3.org/TR/xpath-datamodel/#types-hierarchy
In the case above, the type of the 'then' branch is "empty()", and the
type of the 'else' branch is "xs:string".
eXist simply complains that there is no super-type which satisfies
both empty() and xs:string, and defaults to returning the common
super-type as "item".
So is this correct?
The XDM spec says this about sequences -
http://www.w3.org/TR/xpath-datamodel/#sequences
It does not define this case, and so its open to interpretation
somewhat, however it says clearly "An item is equivalent to a
singleton sequence containing that item and vice versa."
So what is an Empty Sequence? IMHO an Empty Sequence cannot have a
super-type of Item, rather both Empty Sequence have xs:string have a
super-type of Sequence. eXist has no Type concept for Sequence.
The good news, is that eXist continues to function correctly, and that
this warning can probably just be ignored.
However whilst experimenting to find a short reproducible test-case, I
came upon this:
xs:string(
if(current-date() eq current-date() - xs:dayTimeDuration("P1D"))then
()
else
"thing"
)
Now this code should do exactly the same as the above code, as both ()
and fn:error(...) are evaluated to an empty sequence. However they
dont, and this code does not cause the warning you were seeing. In
fact if I debug it, it seems that () is being evaluated not to the
type "empty()" but instead to the type "node()".
This definitely stikes me as a bug in eXist, as () is certainly an
empty sequence and not a node...
Wolf any thoughts please?
On 29 December 2012 06:47, Joe Wicentowski <jo...@gm...> wrote:
> Hi all,
>
> I am trying to find the source of the "no supertype for empty()"
> warning that appears whenever I submit a query that imports the FunctX
> module. Steps to reproduce:
>
> 1. Using trunk, install the FunctX module
>
> 2. Submit the following query in eXide:
>
> ---
> xquery version "3.0";
>
> import module namespace functx="http://www.functx.com";
>
> 1
> ---
>
> 3. Observe the warning in exist.log:
>
> 2012-12-29 01:31:58,431 [eXistThread-48] WARN (Type.java
> [getSuperType]:396) - no supertype for empty()
> java.lang.Throwable
> at org.exist.xquery.value.Type.getSuperType(Type.java:396)
> at org.exist.xquery.value.Type.getCommonSuperType(Type.java:422)
> at org.exist.xquery.ConditionalExpression.returnsType(ConditionalExpression.java:149)
> at org.exist.xquery.PathExpr.returnsType(PathExpr.java:393)
> at org.exist.xquery.CastExpression.setExpression(CastExpression.java:63)
> at org.exist.xquery.CastExpression.<init>(CastExpression.java:54)
> at org.exist.xquery.FunctionFactory.castExpression(FunctionFactory.java:299)
> at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:92)
> at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:57)
> at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:53)
> at org.exist.xquery.parser.XQueryTreeParser.functionCall(XQueryTreeParser.java:9740)
> at org.exist.xquery.parser.XQueryTreeParser.primaryExpr(XQueryTreeParser.java:7008)
> at org.exist.xquery.parser.XQueryTreeParser.expr(XQueryTreeParser.java:3632)
> at org.exist.xquery.parser.XQueryTreeParser.functionDecl(XQueryTreeParser.java:5627)
> at org.exist.xquery.parser.XQueryTreeParser.prolog(XQueryTreeParser.java:4823)
> at org.exist.xquery.parser.XQueryTreeParser.libraryModule(XQueryTreeParser.java:4087)
> at org.exist.xquery.parser.XQueryTreeParser.module(XQueryTreeParser.java:3923)
> at org.exist.xquery.parser.XQueryTreeParser.xpath(XQueryTreeParser.java:3712)
> at org.exist.xquery.XQuery.compile(XQuery.java:157)
> at org.exist.xquery.XQuery.compile(XQuery.java:106)
> at org.exist.xquery.XQuery.compile(XQuery.java:90)
>
>
> I have read through this warning many times and cannot trace the cause
> of the warning. I would like to get to the bottom of the warning,
> since it causes confusion.
>
> I'd appreciate any tips you might have on debugging this issue.
>
> Thanks,
> Joe
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122912
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Wolfgang M. <wol...@ex...> - 2012-12-29 09:38:11
|
Hi Jens, > Is something being prepared to replace the (informative) home page at <http://exist-db.org>? Yes, there will be a brand new home page for 2.0 final. We hope it will be a nice surprise ;-) Wolfgang |
|
From: Jens Ø. P. <oe...@gm...> - 2012-12-29 09:31:16
|
Hi, Is something being prepared to replace the (informative) home page at <http://exist-db.org>? Cheers, Jens On Dec 28, 2012, at 8:32 PM, Dannes Wessels <da...@ex...> wrote: > Hi > > On 28 Dec 2012, at 16:44 , Jens Østergaard Petersen <oe...@gm...> wrote: > >> Would it be possible to update the XSLTForms Demo? What is displayed is the very first draft I made …. The XSLT Files are old as well. > > thnx for triggering me; the new version is available now on http://demo.exist-db.org/exist/apps/XSLTForms-Demo/index.html (looks nice!) > > >> >> Tamboti should probably be built to link to this URL: <http://demo.exist-db.org/exist/apps/library/modules/search/index.html>, not the one with our institute logo. The current version of Tamboti is 1.0.3. > > not sure what you mean, but wolf says he'll pick up... > > D. |
|
From: Jens Ø. P. <oe...@gm...> - 2012-12-29 09:01:58
|
Hi Adam, Yes, this form does not work with Chrome (and Safari) - it is the same on Alain's site, <http://www.agencexml.com/xsltforms/flags.xml>. I guess that's the risk of doing the transformation in the browser …. There are some places where Alain uses PHP that need to be rewritten. Best, Jens On Dec 29, 2012, at 1:29 AM, Adam Retter <ad...@ex...> wrote: > On 28 December 2012 19:32, Dannes Wessels <da...@ex...> wrote: >> Hi >> >> On 28 Dec 2012, at 16:44 , Jens Østergaard Petersen <oe...@gm...> >> wrote: >> >> Would it be possible to update the XSLTForms Demo? What is displayed is the >> very first draft I made …. The XSLT Files are old as well. >> > > Typically - the first one I clicked on does not work its under SVG > Examples and is called "Colored Flags". Good news is that the rest of > the ones I checked do work ;-) > > > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... > irc://irc.freenode.net/existdb |
|
From: Joe W. <jo...@gm...> - 2012-12-29 06:47:34
|
Hi all, I am trying to find the source of the "no supertype for empty()" warning that appears whenever I submit a query that imports the FunctX module. Steps to reproduce: 1. Using trunk, install the FunctX module 2. Submit the following query in eXide: --- xquery version "3.0"; import module namespace functx="http://www.functx.com"; 1 --- 3. Observe the warning in exist.log: 2012-12-29 01:31:58,431 [eXistThread-48] WARN (Type.java [getSuperType]:396) - no supertype for empty() java.lang.Throwable at org.exist.xquery.value.Type.getSuperType(Type.java:396) at org.exist.xquery.value.Type.getCommonSuperType(Type.java:422) at org.exist.xquery.ConditionalExpression.returnsType(ConditionalExpression.java:149) at org.exist.xquery.PathExpr.returnsType(PathExpr.java:393) at org.exist.xquery.CastExpression.setExpression(CastExpression.java:63) at org.exist.xquery.CastExpression.<init>(CastExpression.java:54) at org.exist.xquery.FunctionFactory.castExpression(FunctionFactory.java:299) at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:92) at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:57) at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:53) at org.exist.xquery.parser.XQueryTreeParser.functionCall(XQueryTreeParser.java:9740) at org.exist.xquery.parser.XQueryTreeParser.primaryExpr(XQueryTreeParser.java:7008) at org.exist.xquery.parser.XQueryTreeParser.expr(XQueryTreeParser.java:3632) at org.exist.xquery.parser.XQueryTreeParser.functionDecl(XQueryTreeParser.java:5627) at org.exist.xquery.parser.XQueryTreeParser.prolog(XQueryTreeParser.java:4823) at org.exist.xquery.parser.XQueryTreeParser.libraryModule(XQueryTreeParser.java:4087) at org.exist.xquery.parser.XQueryTreeParser.module(XQueryTreeParser.java:3923) at org.exist.xquery.parser.XQueryTreeParser.xpath(XQueryTreeParser.java:3712) at org.exist.xquery.XQuery.compile(XQuery.java:157) at org.exist.xquery.XQuery.compile(XQuery.java:106) at org.exist.xquery.XQuery.compile(XQuery.java:90) I have read through this warning many times and cannot trace the cause of the warning. I would like to get to the bottom of the warning, since it causes confusion. I'd appreciate any tips you might have on debugging this issue. Thanks, Joe |
|
From: Adam R. <ad...@ex...> - 2012-12-29 00:29:36
|
On 28 December 2012 19:32, Dannes Wessels <da...@ex...> wrote:
> Hi
>
> On 28 Dec 2012, at 16:44 , Jens Østergaard Petersen <oe...@gm...>
> wrote:
>
> Would it be possible to update the XSLTForms Demo? What is displayed is the
> very first draft I made …. The XSLT Files are old as well.
>
Typically - the first one I clicked on does not work its under SVG
Examples and is called "Colored Flags". Good news is that the rest of
the ones I checked do work ;-)
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Dannes W. <da...@ex...> - 2012-12-28 19:32:31
|
Hi On 28 Dec 2012, at 16:44 , Jens Østergaard Petersen <oe...@gm...> wrote: > Would it be possible to update the XSLTForms Demo? What is displayed is the very first draft I made …. The XSLT Files are old as well. thnx for triggering me; the new version is available now on http://demo.exist-db.org/exist/apps/XSLTForms-Demo/index.html (looks nice!) > > Tamboti should probably be built to link to this URL: <http://demo.exist-db.org/exist/apps/library/modules/search/index.html>, not the one with our institute logo. The current version of Tamboti is 1.0.3. not sure what you mean, but wolf says he'll pick up... D. |
|
From: Jens Ø. P. <oe...@gm...> - 2012-12-28 15:44:37
|
Hi Dannes, Thanks for your great work on the function documentation - it looks real nice! Would it be possible to update the XSLTForms Demo? What is displayed is the very first draft I made …. The XSLT Files are old as well. Tamboti should probably be built to link to this URL: <http://demo.exist-db.org/exist/apps/library/modules/search/index.html>, not the one with our institute logo. The current version of Tamboti is 1.0.3. Cheers, Jens On Dec 28, 2012, at 1:00 PM, Dannes Wessels <da...@ex...> wrote: > Hi, > > On 28 Dec 2012, at 12:28 , Adam Retter <ad...@ex...> wrote: > >> We are currently upgrading the website and demo server applications at >> exist-db.org, please bear with us whilst we take the site offline >> temporarily. >> >> This effects all exist-db.org sites. >> >> We will let you know soon when it is available again... > > > Server should be up again, all apps are updated > > http://demo.exist-db.org/apps/dashboard/index.html > > highlights: > - new version of eXide > - updated version of the "XQuery Function Documentation"-app > > cheers > > Dannes > > -- > Dannes Wessels > eXist-db Open Source Native XML Database > e: da...@ex... w: http://www.exist-db.org t: #existdb > > > > > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812_______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Joe W. <jo...@gm...> - 2012-12-27 05:42:45
|
Hi Wolfgang, > I uploaded functx, but you will need to update to shared-resources-0.2.5 first (which does the actual work of installing packages). Thank you! I've updated to trunk and all new versions of the included apps, and functx installs perfectly on its own. That's a big help! Unfortunately installation is not working as a dependency of my library xar (https://github.com/joewiz/unzip). eXide reports, "Failed to install dependency http://www.functx.com". exist.log adds some detail: 2012-12-27 00:35:50,529 [eXistThread-44] ERROR (FunError.java [eval]:138) - Failed to install dependency http://www.functx.com: (http://exist-db.org/xquery/apps#DEPENDENCY):Failed to install dependency http://www.functx.com The console also adds this, although the fact that its log level is only INFO makes me think this isn't relevant: INFO: Warning: package uses old-style content dir: '/Users/Joe/workspace/exist-trunk/webapp/WEB-INF/expathrepo/functx-1.0/functx' (That said, isn't it odd that package installation information is logged to the console?) By the way, I noticed an NPE when uninstalling functx. eXide reports, "Remove Application: The server reported an error:" (That's it - no error is specified after the colon.) exist.log reports only: 2012-12-27 00:30:36,280 [eXistThread-33] ERROR (EXistServlet.java [doPost]:472) - java.lang.NullPointerException The console has the fullest error, so I've pasted it in below [1]. These aren't critical issues for me - but I thought I should report the issues I noticed. Thanks again for your help with this! Joe [1] error from console when uninstalling functx in Package Manager 27 Dec 2012 00:30:36,282 [eXistThread-33] WARN (ServletHandler.java [doHandle]:522) - /exist/apps/dashboard/modules/install.xql javax.servlet.ServletException: An unknown error occurred: null at org.exist.http.servlets.EXistServlet.doPost(EXistServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:755) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:578) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1072) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:382) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1006) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:229) at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:103) at org.exist.http.urlrewrite.Forward.doRewrite(Forward.java:47) at org.exist.http.urlrewrite.XQueryURLRewrite.doRewrite(XQueryURLRewrite.java:555) at org.exist.http.urlrewrite.XQueryURLRewrite.service(XQueryURLRewrite.java:336) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1336) at de.betterform.agent.web.filter.XFormsFilter.doFilter(XFormsFilter.java:173) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:453) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1072) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:382) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1006) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:365) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:937) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:998) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.NullPointerException at org.exist.repo.Deployment.findElement(Deployment.java:568) at org.exist.repo.Deployment.undeploy(Deployment.java:207) at org.exist.xquery.modules.expathrepo.Deploy.eval(Deploy.java:111) at org.exist.xquery.BasicFunction.eval(BasicFunction.java:70) at org.exist.xquery.InternalFunctionCall.eval(InternalFunctionCall.java:55) at org.exist.xquery.LetExpr.eval(LetExpr.java:142) at org.exist.xquery.BindingExpression.eval(BindingExpression.java:156) at org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:96) at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:153) at org.exist.xquery.DynamicCardinalityCheck.eval(DynamicCardinalityCheck.java:74) at org.exist.xquery.Atomize.eval(Atomize.java:66) at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61) at org.exist.xquery.FunctionCall.evalFunction(FunctionCall.java:324) at org.exist.xquery.FunctionCall.eval(FunctionCall.java:229) at org.exist.xquery.LetExpr.eval(LetExpr.java:142) at org.exist.xquery.LetExpr.eval(LetExpr.java:187) at org.exist.xquery.BindingExpression.eval(BindingExpression.java:156) at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) at org.exist.xquery.PathExpr.eval(PathExpr.java:264) at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) at org.exist.xquery.SwitchExpression.eval(SwitchExpression.java:104) at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:57) at org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:98) at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:153) at org.exist.xquery.FunctionCall.evalFunction(FunctionCall.java:324) at org.exist.xquery.FunctionCall.eval(FunctionCall.java:229) at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) at org.exist.xquery.value.FunctionReference.eval(FunctionReference.java:80) at org.exist.xquery.DynamicFunctionCall.eval(DynamicFunctionCall.java:73) at org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:96) at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:153) at org.exist.xquery.FunctionCall.evalFunction(FunctionCall.java:324) at org.exist.xquery.FunctionCall.eval(FunctionCall.java:229) at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:57) at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:64) at org.exist.xquery.LetExpr.eval(LetExpr.java:189) at org.exist.xquery.LetExpr.eval(LetExpr.java:187) at org.exist.xquery.LetExpr.eval(LetExpr.java:187) at org.exist.xquery.LetExpr.eval(LetExpr.java:187) at org.exist.xquery.LetExpr.eval(LetExpr.java:187) at org.exist.xquery.BindingExpression.eval(BindingExpression.java:156) at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) at org.exist.xquery.PathExpr.eval(PathExpr.java:264) at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) at org.exist.xquery.XQuery.execute(XQuery.java:255) at org.exist.xquery.XQuery.execute(XQuery.java:202) at org.exist.http.RESTServer.executeXQuery(RESTServer.java:1476) at org.exist.http.RESTServer.doPost(RESTServer.java:634) at org.exist.http.servlets.EXistServlet.doPost(EXistServlet.java:445) ... 45 more |
|
From: Adam R. <ad...@ex...> - 2012-12-26 10:45:37
|
I have a remaining task to add cxan support so it should probably be removed from our own repo when that is done. On 26 Dec 2012 09:28, "Wolfgang Meier" <wol...@ex...> wrote: > Hi Joe, > > I uploaded functx, but you will need to update to shared-resources-0.2.5 > first (which does the actual work of installing packages). > > Wolfgang > > > Am Mittwoch, 26. Dezember 2012 um 07:35 schrieb Joe Wicentowski: > > > Hi all, > > > > I have updated my 'unzip' library (https://github.com/joewiz/unzip), > > to work with 2.0RC, but one remaining problem is that my library has a > > dependency on the FunctX library. The EXPath package format gives us > > a way to register dependencies by package namespace URI, e.g.: > > > > <dependency package="http://www.functx.com"/> > > > > I think this should work if FunctX is in the eXist-db public > > repository (c.f., the fundocs app registers its dependency on the > > shared-resources app this way), but I noticed that FunctX is no longer > > available there as I recall it used to. Could FunctX be re-added > > please? Or is there a reason not to include it? (The xar at > > http://test.cxan.org/pkg/functx works when I use the CXAN tab in the > > old web admin app's package manager pane.) > > > > Thanks, > > Joe > > > > > ------------------------------------------------------------------------------ > > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > > Remotely access PCs and mobile devices and provide instant support > > Improve your efficiency, and focus on delivering more value-add services > > Discover what IT Professionals Know. Rescue delivers > > http://p.sf.net/sfu/logmein_12329d2d > > _______________________________________________ > > Exist-development mailing list > > Exi...@li... (mailto: > Exi...@li...) > > https://lists.sourceforge.net/lists/listinfo/exist-development > > > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
|
From: Wolfgang M. <wol...@ex...> - 2012-12-26 09:28:11
|
Hi Joe, I uploaded functx, but you will need to update to shared-resources-0.2.5 first (which does the actual work of installing packages). Wolfgang Am Mittwoch, 26. Dezember 2012 um 07:35 schrieb Joe Wicentowski: > Hi all, > > I have updated my 'unzip' library (https://github.com/joewiz/unzip), > to work with 2.0RC, but one remaining problem is that my library has a > dependency on the FunctX library. The EXPath package format gives us > a way to register dependencies by package namespace URI, e.g.: > > <dependency package="http://www.functx.com"/> > > I think this should work if FunctX is in the eXist-db public > repository (c.f., the fundocs app registers its dependency on the > shared-resources app this way), but I noticed that FunctX is no longer > available there as I recall it used to. Could FunctX be re-added > please? Or is there a reason not to include it? (The xar at > http://test.cxan.org/pkg/functx works when I use the CXAN tab in the > old web admin app's package manager pane.) > > Thanks, > Joe > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Exist-development mailing list > Exi...@li... (mailto:Exi...@li...) > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Joe W. <jo...@gm...> - 2012-12-26 06:36:07
|
Hi all, I have updated my 'unzip' library (https://github.com/joewiz/unzip), to work with 2.0RC, but one remaining problem is that my library has a dependency on the FunctX library. The EXPath package format gives us a way to register dependencies by package namespace URI, e.g.: <dependency package="http://www.functx.com"/> I think this should work if FunctX is in the eXist-db public repository (c.f., the fundocs app registers its dependency on the shared-resources app this way), but I noticed that FunctX is no longer available there as I recall it used to. Could FunctX be re-added please? Or is there a reason not to include it? (The xar at http://test.cxan.org/pkg/functx works when I use the CXAN tab in the old web admin app's package manager pane.) Thanks, Joe |
|
From: Wolfgang M. <wol...@ex...> - 2012-12-24 16:56:11
|
Hi Joe, sorry, I was just working on some final fixes to the dashboard to 1) display if a certain version of eXist-db is required by a package, 2) allow apps to show an installation note or warning before the user installs. I used the demo app for testing and temporarily broke it. Installation should work again now though. Wolfgang Am Montag, 24. Dezember 2012 um 17:49 schrieb Joe Wicentowski: > Hi Dannes, > > > it should be OK right now..... > > It is! Thank you very much. The only public repo app I'm having > problems with is the demo app - which (1) has two entries in the list > of apps, and (2) installing either one yields the same error, "Install > Application: Failed to connect to public repo." Odd, because I have > no problem connecting to the demo server and even retrieving the list > of apps at http://demo.exist-db.org/exist/apps/public-repo/public. My > exist.log reports, "Retrieving package from > http://demo.exist-db.org/exist/apps/public-repo/find?name=http%3A%2F%2Fexist-db.org%2Fapps%2Fdemo" > and no error. But going to this URL yields this error: > > err:XPTY0004 checking function parameter 1 in call > util:binary-doc($config:app-root "/public/" $app/attribute::{}path): > XPTY0004: The actual cardinality for parameter $app/attribute::{}path > does not match the cardinality declared in the function's signature: > zero or one. Expected cardinality: $app/attribute::{}path, got zero or > one. [at line 15, column 72, source: > /db/apps/public-repo/modules/find.xql] > > It's odd to see an expected cardinality of "$app/attribute::{}path", > isn't it? Looking at the source of find.xql, 15:72 refers to the > $app/@path here: > > let $xar := util:binary-doc($config:app-root || "/public/" || > $app/@path) > > Is this a problem with error messages involving ||, I wonder? > > Joe > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Exist-development mailing list > Exi...@li... (mailto:Exi...@li...) > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Joe W. <jo...@gm...> - 2012-12-24 16:50:08
|
Hi Dannes, > it should be OK right now..... It is! Thank you very much. The only public repo app I'm having problems with is the demo app - which (1) has two entries in the list of apps, and (2) installing either one yields the same error, "Install Application: Failed to connect to public repo." Odd, because I have no problem connecting to the demo server and even retrieving the list of apps at http://demo.exist-db.org/exist/apps/public-repo/public. My exist.log reports, "Retrieving package from http://demo.exist-db.org/exist/apps/public-repo/find?name=http%3A%2F%2Fexist-db.org%2Fapps%2Fdemo" and no error. But going to this URL yields this error: err:XPTY0004 checking function parameter 1 in call util:binary-doc($config:app-root "/public/" $app/attribute::{}path): XPTY0004: The actual cardinality for parameter $app/attribute::{}path does not match the cardinality declared in the function's signature: zero or one. Expected cardinality: $app/attribute::{}path, got zero or one. [at line 15, column 72, source: /db/apps/public-repo/modules/find.xql] It's odd to see an expected cardinality of "$app/attribute::{}path", isn't it? Looking at the source of find.xql, 15:72 refers to the $app/@path here: let $xar := util:binary-doc($config:app-root || "/public/" || $app/@path) Is this a problem with error messages involving ||, I wonder? Joe |
|
From: Dannes W. <da...@ex...> - 2012-12-24 14:19:13
|
Hi Joe, it should be OK right now..... D. On 24 Dec 2012, at 6:45 , Joe Wicentowski <jo...@gm...> wrote: > 24 Dec 2012 00:37:27,674 [eXistThread-52] WARN (ServletHandler.java > [doHandle]:522) - > /exist/apps/dashboard/plugins/browsing/images/icon.png > org.exist.xquery.XPathException: err:XPST0017 error found while > loading module service: Error while loading module service.xql: > Function sm:get-groups() is not defined in module namespace: > http://exist-db.org/xquery/securitymanager [at line 218, column 35] > at org.exist.xquery.FunctionFactory.getInternalModuleFunction(FunctionFactory.java:359) > at org.exist.xquery.FunctionFactory.functionCall(FunctionFactory.java:328) > at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:101) > at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:57) > at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:53) > > Not sure if this is related or not, but I thought I'd report it anyway > since it seems to indicate that the security manager API has changed, > and perhaps Dashboard needs to be updated to reflect this. Apologies > if this issue is already known - but in case not... -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org t: #existdb |
|
From: Joe W. <jo...@gm...> - 2012-12-24 05:46:15
|
Hi all, I noticed that in 2.0RC2 trunk (rev 17908), whenever I try to install a package with the Dashboard app (v0.2.6), whether from the public repository or from my disk, I get this error in a dojo window: Install Application: Permission denied. You must be a member of the dba group. Of course I'm already logged in as admin, so this error doesn't make sense. I don't see any errors in exist.log or on the console, except for this from earlier in my session - apparently from when I first opened Dashboard: 24 Dec 2012 00:37:27,674 [eXistThread-52] WARN (ServletHandler.java [doHandle]:522) - /exist/apps/dashboard/plugins/browsing/images/icon.png org.exist.xquery.XPathException: err:XPST0017 error found while loading module service: Error while loading module service.xql: Function sm:get-groups() is not defined in module namespace: http://exist-db.org/xquery/securitymanager [at line 218, column 35] at org.exist.xquery.FunctionFactory.getInternalModuleFunction(FunctionFactory.java:359) at org.exist.xquery.FunctionFactory.functionCall(FunctionFactory.java:328) at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:101) at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:57) at org.exist.xquery.FunctionFactory.createFunction(FunctionFactory.java:53) Not sure if this is related or not, but I thought I'd report it anyway since it seems to indicate that the security manager API has changed, and perhaps Dashboard needs to be updated to reflect this. Apologies if this issue is already known - but in case not... Thanks, Joe |
|
From: Chris T. <chr...@gm...> - 2012-12-19 00:32:15
|
Hello, There's a bit of a discontinuity between the svn extension version and the use of 1.7.x for compatibility with latest eclipse. Why can't the svn extension be upgraded to current 1.7? I looked over the code recently and it appears to be possible though it is not code that I use or am familiar with. I guess moving the svn extension to git will solve a part of the problem but will the extension be compatible with an eXist that uses 1.7.x elsewhere? Chris On Dec 18, 2012, at 11:19 PM, Dmitriy Shabanov <sha...@gm...> wrote: > Yes, I plan to move svn extension to git and provide it with old svnkit jars. > > On Tue, Dec 18, 2012 at 8:52 PM, Joe Wicentowski <jo...@gm...> wrote: > FYI, the build process on trunk still fails whenever the build > properties are set to include.feature.svn = true, unless I copy the > old svnkit jars into lib/user. I'm concerned that new users who try > to use 2.0RC or 2.0-final will be frustrated when they try to enable > the SVN feature. Do you have an idea for how to solve this? I > proposed some ideas below. > > -- > Dmitriy Shabanov > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
|
From: Dmitriy S. <sha...@gm...> - 2012-12-18 17:34:44
|
Yes, I plan to move svn extension to git and provide it with old svnkit jars. On Tue, Dec 18, 2012 at 8:52 PM, Joe Wicentowski <jo...@gm...> wrote: > FYI, the build process on trunk still fails whenever the build > properties are set to include.feature.svn = true, unless I copy the > old svnkit jars into lib/user. I'm concerned that new users who try > to use 2.0RC or 2.0-final will be frustrated when they try to enable > the SVN feature. Do you have an idea for how to solve this? I > proposed some ideas below. > -- Dmitriy Shabanov |
|
From: Joe W. <jo...@gm...> - 2012-12-18 15:52:42
|
Hi Dmitriy, FYI, the build process on trunk still fails whenever the build properties are set to include.feature.svn = true, unless I copy the old svnkit jars into lib/user. I'm concerned that new users who try to use 2.0RC or 2.0-final will be frustrated when they try to enable the SVN feature. Do you have an idea for how to solve this? I proposed some ideas below. Thanks for your ideas, Joe On Sat, Jul 7, 2012 at 3:10 PM, Joe Wicentowski <jo...@gm...> wrote: > Hi Dmitriy, > >>>> use older version of svn jar >>> >>> DO you mean Joe needs to use an older version of a jar? is it the svnkit jar files? >> >> yes > > I see: the SVN extension skips downloading the svnkit jars if they're > already present, but if they're missing, it downloads version 1.3.3 > (see extensions/svn/build.xml line 75). Since I had already run > "build.sh svn-download", the jars were present, but this > "svn-download" step actually downloaded version 1.3.7 > (build/scripts/subversion.xml line 29). > > Given this, I thought the solution was to change > build/scripts/subversion.xml to reference version 1.3.3, but when I do > this, "build svn-download" fails, since this version isn't available > at the location where the script looks: > http://maven.tmatesoft.com/content/repositories/releases/org/tmatesoft/svnkit/svnkit-cli/1.3.3/svnkit-cli-1.3.3.jar. > So I think our options for fixing the build are either: > > 1. Find 1.3.3 and update the download URLs in > build/scripts/subversion.xml to point to that instead of 1.3.7. > > - or - > > 2. Fix the SVN extension's apparent incompatibility with 1.3.7. > > If there's anything I can do to help, let me know. > > Thanks, > Joe |
|
From: Andrzej J. T. <an...@ch...> - 2012-12-11 22:43:08
|
Wolfgang:
I've been trying to get my code running under the latest version of trunk (2.0)....but have run into
a weird xpath error again that I initially reported back in February....
I've attached both a text.xql file and test.xml file. Put them in /db and then execute the test.xql.
It dies with the following exception:
cannot convert xs:boolean('false') to a node set
Now if you look at the rather complex xpath statement, if you remove both the exists() and
normalize-space() comparisons at the end, it works. Also works if you remove the "and @extension =
$id" clause....or if you remove the "@root = "2.16.840.1.113883.4.98" and" clause.
Very strange behaviour. This is valid xpath...and worked fine in the older 1.5 version I used in
the past. Almost seems like there is something going on with the parser or the optimizer that is
causing this weird error.
I know that if you split the different conditions into separate paths eg [...][...] etc, it will
work, but the xpath in the test.xql sample file should be acceptable according to the xpath spec and
show not error out like this.
I'm not very conversant with the intricacies of the query/xpath engine/parser/optimizer, so was
hoping you could take a look. Hopefully this test case will let you replicate the issue and we can
resolve this long standing bug.
Thanks!
--
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|
|
From: Joe W. <jo...@gm...> - 2012-12-11 09:57:54
|
P.S. To all developers of undocumented or under-documented features: please commit your new/updated articles, or send me your drafts or brief summaries. It does not have to be long! Sent from my iPhone Forwarded message: > From: Joe Wicentowski <jo...@gm...> > To: exi...@li... <exi...@li...> > Date: Monday, December 10, 2012, 6:31:49 PM > Subject: Calling all 2.0RC testers: Documentation ok? > > Hi all, > > As the recent release of the eXist-db 2.0 Release Candidate makes > clear, the final release of eXist-db version 2.0 is nearing. If you > have downloaded 2.0RC, please explore the documentation app (installed > by default in your Dashboard; also, via > http://localhost:8080/exist/apps/doc). We need your help to fix any > typos or missing/confusing/out of date information. Please report > anything you notice in this thread. We will do our best to address > your reports before the final release. > > If you haven't tried 2.0RC, please do -- your reports will help ensure > a smooth release. See the announcement at > http://markmail.org/message/n4ofo7qsrk7oysvj. > > Cheers, > Joe > > |
|
From: Joe W. <jo...@gm...> - 2012-12-06 21:31:17
|
Hi all, I noticed that the Tomcat extension seems to be turned on by default. At least for me, when I build trunk, I get a lib/extensions/exist-tomcat-realm.jar when the build is complete. It's probably harmless, but shouldn't extensions be controlled by extensions/local.build.properties? Joe |
|
From: Joern T. <joe...@gm...> - 2012-12-06 09:26:23
|
On Wed, Dec 5, 2012 at 9:52 AM, Jens Østergaard Petersen <oe...@gm...> wrote: > Hi Joe, > > On Dec 4, 2012, at 7:16 PM, Joe Wicentowski <jo...@gm...> wrote: > > - BetterForm occupies 2 spaces in the installer package and the Dashboard; > in the installer the items are called "bfDemos" and "bfReferences". It also > occupies 2 spaces in the Dashboard, but both icons point to the same URL: > http://localhost:8080/exist/apps/betterform/dashboard.html. Seems a little > odd and potentially confusing to users. Can 2 apps be installed into the > same subcollection of /db/apps/? We are still in the process of sorting this out probably making the FeatureExplorer a standalone app. As we are working on the new homepage we haven't yet made progress on that yet. And yes, it's possible to have several apps deeper in the tree - we have betterform as our 'home' for apps putting the several different demos/apps below that. This is not a necessary but just a convention. > > > Both the betterFORM Demos and the betterFORM Feature Explorer files are > installed inside the betterform collection which is inside /db/apps/. The > betterform collection itself is installed when either of the two are > installed. The betterFORM dashboard is static and links to both the demos > and the feature explorer, even though both are not necessarily installed - > this does not look good. > > I think the idea is that users should have the choice of installing either > of these apps independently, but then the apps should actually be separate, > which they are not. If the demos and feature explorer depend on a betterFORM > library, this library should be installed as a dependency of the demos and > the feature explorer and, as Joe suggests, have different collections > immediately below /db/apps/ (it should probably be separately installable as > well). The apps do not depend on a specific library but on the betterFORM extension which is enabled by default so i think this shouldn't be a big issue. I agree that both demos have to be separated but i do not see the point why they should reside directly below 'apps'. > > - XSLTForms occupies 2 apps in the installer package, but it makes a clear > distinction between XSLTForms and its demo. This is good. Oddly, there is > only one icon in the Dashboard though. > > > The XSLTForms Files are a resource package and therefore has no web view, so > I don't think it should be displayed in the Dashboard. However, it should > appear as installed in the Package Manager when it is installed as a > dependency, which is not the case now. > > Also, I'd suggest making the demo's app name lower-cased (XSLTForms-Demo > > xsltforms-demo) ; otherwise, it appears first in the list of apps in > /db/apps. > > > The reason why I used upper-casing for the demo files is that XSLTForms is > an established product; upper-casing is not used for the library files, > since there is an established practice of referring to them with the > lower-cased form. There are other packages using upper-casing (TEIXLingual), > so perhaps it would be easiest simply to make sorting case-insensitive. > > Cheers, > > Jens > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
64 messages has been excluded from this view by a project administrator.
