Re: [Exist-open] regex in 1.4.2

[W.S. Hager <wshager@gm...>]

Hi Dannes,

I tried to use xsl:string-analyze to capture the groups, as per
http://en.m.wikibooks.org/wiki/XQuery/String_Analysis#section_1.

Unfortunately, neither result nor error is returned. Exist's text:groups
only returns the first captions. Functx:get-matches-and-non-matches throws
an error. It uses tokenize, which throws the error.

Sorry to not include any tests but I'm writing this from my phone. I'll
make some tests soon.

Cheers.
 Op 7 sep. 2012 21:53 schreef "Dannes Wessels" <dannes@...> het
volgende:

> Hi Wouter,
>
> On 7 Sep 2012, at 18:14 , W.S. Hager <wshager@...> wrote:
>
> Regular expressions in 1.4.2 do not behave the way I expect. I'm trying to
> implement https://github.com/persvr/rql basics in xquery, but it proves
> to be impossible due to regex problems. This expression (with ampersand
> escaped):
>
> (\))|([&\|,])?([\+\*\$\-:\w%\._]*)(\(?)
>
> produces an error for this string: eq(a,b)
>
> FORX0003: regular expression could match empty string
>
> Is there any way to work around this?
>
>
> As far as I know do the Xquery regex differ a bit from the java regex
> which differ a bit from the perl5 regex etc. This makes things a bit more
> complicated.
>
> In which function do you use the regex? Can you show a small piece of
> (self containing) xquery code (to reproduce).
>
> cheers
>
> Dannes
>

Re: [Exist-open] svn rev. 17101 build failure

[Adam Retter <adam@ex...>]

Whoops, I had JDK 7 enabled and not 6. JDK 7 seems to introduce some
generics for Swing which is nice, but means you cant compiled on 1.7.

I have now fixed to work with 1.6, this is in as revision 17102.


On 7 September 2012 20:50, Greg Newton <gregster@...> wrote:
> I did a build against rev.17099 this morning and had no problem, but
> just now tried to build 17101 (fresh checkout) and got this:
> <exist-code>/src/org/exist/client/NewResourceDialog.java:102: type
> javax.swing.JComboBox does not take parameters
> [javac] final JComboBox cmbResourceTypes = new
> JComboBox<ResourceType>(ResourceType.values());
>
> I also note that there are a few places in the build process where the
> old SVN repo is being used - specifically in the following files:
> <exist-code>/build/scripts/cruisecontrol/config.xml
> <exist-code>/build/scripts/cruisecontrol/subversion.xml
> <exist-code>/build/scripts/cruisecontrol/projects/build.exist.xml
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open



-- 
Adam Retter

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

[Exist-open] svn rev. 17101 build failure

[Greg Newton <gregster@uv...>]

I did a build against rev.17099 this morning and had no problem, but 
just now tried to build 17101 (fresh checkout) and got this:
<exist-code>/src/org/exist/client/NewResourceDialog.java:102: type 
javax.swing.JComboBox does not take parameters
[javac] final JComboBox cmbResourceTypes = new 
JComboBox<ResourceType>(ResourceType.values());

I also note that there are a few places in the build process where the 
old SVN repo is being used - specifically in the following files:
<exist-code>/build/scripts/cruisecontrol/config.xml
<exist-code>/build/scripts/cruisecontrol/subversion.xml
<exist-code>/build/scripts/cruisecontrol/projects/build.exist.xml

Re: [Exist-open] Locale bug for schema parsing

[Dannes Wessels <dannes@ex...>]

Hi,

so your suggestion is to add "-Duser.country=US -Duser.language=en" to JAVA_OPTS ? We need to figure out  the side effects, consequences etc.

Please could you check exist.log for clues what is the cause of the problem? I think it has already been reported in https://sourceforge.net/p/exist/bugs/778/ , the fix is already in place for the upcoming 2.0/2/1 release....

please could you check the log?

cheers

Dannes


On 7 Sep 2012, at 13:50 , merve <merve.ozbey@...> wrote:

> [log4j.configuration : file:/D:/devTlos3/eXist2.0/lo
> g4j.xml]
> org.exist.EXistException: database instance 'exist' is not available
>        at org.exist.storage.BrokerPool.getInstance(BrokerPool.java:312)
>        at org.exist.storage.BrokerPool.getInstance(BrokerPool.java:298)
>        at org.exist.jetty.JettyStart.run(JettyStart.java:179)
>        at org.exist.jetty.JettyStart.main(JettyStart.java:70)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.exist.start.Main.invokeMain(Main.java:137)
>        at org.exist.start.Main.run(Main.java:463)
>        at org.exist.start.Main.main(Main.java:59)
> 
> Then I changed JAVA_OPTS parameter in startup.bat file and I can start eXist
> with Turkish setting:
> 
> set JAVA_OPTS="-Xms128m -Xmx512m -Dfile.encoding=UTF-8
> -Djava.endorsed.dirs=%JAVA_ENDORSED_DIRS% -Duser.country=US
> -Duser.language=en"
> 
> Will you do something about this localization problem? 

Re: [Exist-open] regex in 1.4.2

[Dannes Wessels <dannes@ex...>]

Hi Wouter,
On 7 Sep 2012, at 18:14 , W.S. Hager <wshager@...> wrote:

> Regular expressions in 1.4.2 do not behave the way I expect. I'm trying to implement https://github.com/persvr/rql basics in xquery, but it proves to be impossible due to regex problems. This expression (with ampersand escaped):
> 
> (\))|([&\|,])?([\+\*\$\-:\w%\._]*)(\(?)
> 
> produces an error for this string: eq(a,b)
> 
> FORX0003: regular expression could match empty string
> 
> Is there any way to work around this?

As far as I know do the Xquery regex differ a bit from the java regex which differ a bit from the perl5 regex etc. This makes things a bit more complicated.

In which function do you use the regex? Can you show a small piece of (self containing) xquery code (to reproduce).

cheers

Dannes

Re: [Exist-open] RestXQ: fatal errors in Tomcat

[Dannes Wessels <dannes@ex...>]

Thank you all for the responses ; we have been mentioning abandoning the war file a longer time now, this is the first time that there is a bit more feedback from the community.

What we miss is a war-file 'owner', Chris it would be great if you could help us here.

There are a few "problems" with WAR files that started the war-file-or-not discussion

- finding local files in a reliable way is quite difficult
----> which makes it difficult to implement certain features in limited time
- exist-db relies on a few features e.g. a CustomProtocolHander
----> which is not possible in tomcat
- some servlet containers do not 'explode' the content of war files (e.g. they run from memory), making references to local files impossible
- some servlet containers do not allow to write data on arbitrary file locations (security managers)
- some users find it too difficult to alter the content of the war files to match local requirements
- quite a few users do not read the 'endorsed jars' instructions, causing issues as well
- for some features we sometimes need functions from a newer servlet specification (I expect more to come), which actually abandons the use in certain tomcat versions (this has never been communicated/verified)

etc...


So it is not just about maintaining the war file, there is a bit more pain involved. Since we do not define the requirements for a servlet container, we had several issues reported in the past about not working functions. This kind of support  costs more effort than I'd like.

And.... a non/partial working database makes the software look rather bad on mailinglist etc. I hope you understand this consideration.


But.... I think we can make a step forwards however by thinking of the following subjects:

- define which servlet containers we explicitly support (tomcat 5-6-7, websphere, ......)  --> prefer tomcat7 only
- limit the functionality (configuration, jars) in the war file
- ......


One question from my side: does the recently added package manager actually work in e.g. tomcat? and other features like betterform?

thnx for your constructive feedback

cheers

Dannes



On 7 Sep 2012, at 18:25 , Chris Tomlinson <chris.j.tomlinson@...> wrote:

> tbrc.org uses exist-db as a war deployed in a tomcat container and it would be rather a jolt to have that capability disappear. 
> 
> While I understand that exist-db is a an open source project and relies on the user community to support and develop it, I am puzzled about why a basic modular use case of exist-db that has been there from the earliest days would be jettisoned. 
> 
> I will offer to do what I can to help ensure that exist-db continues to be usable as a war file in tomcat (and jetty), but that to some extent depends on exist-db development being carried on in such a way as to not preclude such deployment. 
> 

Re: [Exist-open] RestXQ: fatal errors in Tomcat

[Chris Tomlinson <chris.j.tomlinson@gm...>]

Hello,

tbrc.org uses exist-db as a war deployed in a tomcat container and it would be rather a jolt to have that capability disappear. 

While I understand that exist-db is a an open source project and relies on the user community to support and develop it, I am puzzled about why a basic modular use case of exist-db that has been there from the earliest days would be jettisoned. 

I will offer to do what I can to help ensure that exist-db continues to be usable as a war file in tomcat (and jetty), but that to some extent depends on exist-db development being carried on in such a way as to not preclude such deployment. 

It seems to me that recent years have seen the development of exist-db as a standalone application solution and at tbrc.org for better or worse we have continued with an approach of an integrated exist-db as a back-end module with other middleware in a separate container - currently based on GWT. There is evidently a tension between whether exist-db is a container with jetty as a module or exist-db as a module able to be dropped into web services conforming containers.

Regards,
Chris



On Sep 7, 2012, at 4:32 AM, Adam Retter wrote:

>> Why would you abandon the WAR deployment? Lots of people use it. We're
>> only just migrating projects away from the Cocoon build to eXist WAR
>> under Tomcat, and now that one's going to disappear?
> 
> Its not concerete yet!
> 
> We are a small team and have lots of things to support and improve in
> eXist-db, if we can reduce the peripherary stuff whilst improving the
> core that makes us more effective. There are, we think, only a handful
> of users that use the WAR approach. If they make enough noise and there are more
> that we thought then we will certainly keep it.
> 
> Its an open source project and we have limited resources, but if
> someone would like to join the team as 'the war guy' that maintains
> the war build and tests it, then that would be great :-)
> 
> -- 
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> adam@...
> irc://irc.freenode.net/existdb
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open

[Exist-open] regex in 1.4.2

[W.S. Hager <wshager@gm...>]

Dear List,

Regular expressions in 1.4.2 do not behave the way I expect. I'm trying to
implement https://github.com/persvr/rql basics in xquery, but it proves to
be impossible due to regex problems. This expression (with ampersand
escaped):

(\))|([&\|,])?([\+\*\$\-:\w%\._]*)(\(?)

produces an error for this string: eq(a,b)

FORX0003: regular expression could match empty string

Is there any way to work around this?

Thanks.

Wouter




-- 

W.S. Hager
Lagua Web Solutions
http://lagua.nl

Re: [Exist-open] XQuery regex for valid XML element names

[Dave Finton <dave.finton@gm...>]

As it turns out, I found out how to get this to work. My main problem is
that I grew up with perl-style regular expressions. The regex syntax in
XQuery is very similar, but *just* different enough to throw me off when it
comes to complex patterns. I found a workaround, however: I split the regex
into two statements instead of trying to force everything into a single
line. According to my tests, this appears to work exactly as I want it to:

    *let* *$element-name* := *if* (*matches*(*$value*, '^[Xx][Mm][Ll]')) *
then*
        ''
    *else*
        *if* (*matches*(*$value*, '^\w[\w0-9-]*$')) *then*
            *$value*
        *else*
            ''
What was tripping me up was the additional rule stating element names
cannot start with "xml", "XML", or any case combination. Once I moved it to
its own if/then block then my life became a little easier.


On Fri, Sep 7, 2012 at 10:40 AM, Dave Finton <dave.finton@...> wrote:

> I did in fact think of the try/catch block solution (it was in fact
> mentioned in a couple of threads I ran across). If I really hit a wall then
> I'll probably go with that, but I want to avoid that since it feels like
> the programming equivalent of trying to fix a cracked window with a
> sledgehammer. ;^)
>
> I have run across the documentation you linked to, and that also looks
> good but it's also a lot of data to mine through. I'll keep mining, however.
>
> Since I'm very certain I can't be the first person to run across this
> problem, I'll be sure to post whatever solution I come up with to the list.
>
>
> On Fri, Sep 7, 2012 at 10:35 AM, Adam Retter <adam@...> wrote:
>
>> I dont know of an existing regexp, but you could build a regexp based
>> on the BNF defined in the spec here -
>> http://www.w3.org/TR/REC-xml/#sec-starttags
>>
>> Maybe simpler is just to try and construct an xs:QName() from your
>> element or attribute name inside of a try {} catch {} block, if its
>> not a valid QName it aint a valid element or attribute name ;-)
>>
>> On 7 September 2012 16:23, Dave Finton <dave.finton@...> wrote:
>> > I'm in the process of putting together a script that takes a
>> user-supplied
>> > or system-defined string (via a URL parameter usually) and using that
>> string
>> > as part of an XPath expression that will ultimately be processed in a
>> > util:eval(...) function call. One of the problems with this is the
>> potential
>> > for security vulnerabilities through code injection, so I want to make
>> sure
>> > the user-defined string passes a few tests before passing it along to
>> > util:eval. One such test is to make sure the user-supplied string is in
>> fact
>> > a valid XML element and/or attribute name. Here's where I ran into a
>> > problem.
>> >
>> > I started off on what I thought would be a 15-minute research project:
>> find
>> > a regex I can use in XQuery (i.e. something i can use in the
>> fn:matches(...)
>> > function) that I could use to validate or invalidate that a given
>> arbitrary
>> > string was a valid XML element and/or attribute label. I'm found some
>> > example in Java, PHP, and other languages, but nothing for XQuery. Even
>> > worse, the examples I did find were in comment threads where no one
>> seemed
>> > to agree what the "correct" solution is. I went through "official"
>> > documentation from various sources including those from the w3schools
>> web
>> > site as well, to no avail.
>> >
>> > The most helpful thing I could find were the following rules in plain
>> > English (from w3schools):
>> >
>> > Names can contain letters, numbers, and other characters
>> > Names cannot start with a number or punctuation character
>> > Names cannot start with the letters xml (or XML, or Xml, etc)
>> > Names cannot contain spaces
>> >
>> >
>> > Now I am in the process of putting together my own regex checking
>> algorithm,
>> > but I haven't had much luck in getting it to work correctly. I figured I
>> > would ask the greater community if there was a quick solution before I
>> spend
>> > too many hours trying to solve what I hoped would be a relatively simple
>> > problem. :-)
>> >
>> > eXist details:
>> > eXist 2.1 trunk, rev 17098
>> > Java 1.6
>> > MacOS X 10.7.4
>> >
>> > --
>> > David Finton
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond.
>> Discussions
>> > will include endpoint security, mobile security and the latest in
>> malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > Exist-open mailing list
>> > Exist-open@...
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> adam@...
>> irc://irc.freenode.net/existdb
>>
>
>
>
> --
> David Finton
>



-- 
David Finton

Re: [Exist-open] XQuery regex for valid XML element names

[Dave Finton <dave.finton@gm...>]

I did in fact think of the try/catch block solution (it was in fact
mentioned in a couple of threads I ran across). If I really hit a wall then
I'll probably go with that, but I want to avoid that since it feels like
the programming equivalent of trying to fix a cracked window with a
sledgehammer. ;^)

I have run across the documentation you linked to, and that also looks good
but it's also a lot of data to mine through. I'll keep mining, however.

Since I'm very certain I can't be the first person to run across this
problem, I'll be sure to post whatever solution I come up with to the list.

On Fri, Sep 7, 2012 at 10:35 AM, Adam Retter <adam@...> wrote:

> I dont know of an existing regexp, but you could build a regexp based
> on the BNF defined in the spec here -
> http://www.w3.org/TR/REC-xml/#sec-starttags
>
> Maybe simpler is just to try and construct an xs:QName() from your
> element or attribute name inside of a try {} catch {} block, if its
> not a valid QName it aint a valid element or attribute name ;-)
>
> On 7 September 2012 16:23, Dave Finton <dave.finton@...> wrote:
> > I'm in the process of putting together a script that takes a
> user-supplied
> > or system-defined string (via a URL parameter usually) and using that
> string
> > as part of an XPath expression that will ultimately be processed in a
> > util:eval(...) function call. One of the problems with this is the
> potential
> > for security vulnerabilities through code injection, so I want to make
> sure
> > the user-defined string passes a few tests before passing it along to
> > util:eval. One such test is to make sure the user-supplied string is in
> fact
> > a valid XML element and/or attribute name. Here's where I ran into a
> > problem.
> >
> > I started off on what I thought would be a 15-minute research project:
> find
> > a regex I can use in XQuery (i.e. something i can use in the
> fn:matches(...)
> > function) that I could use to validate or invalidate that a given
> arbitrary
> > string was a valid XML element and/or attribute label. I'm found some
> > example in Java, PHP, and other languages, but nothing for XQuery. Even
> > worse, the examples I did find were in comment threads where no one
> seemed
> > to agree what the "correct" solution is. I went through "official"
> > documentation from various sources including those from the w3schools web
> > site as well, to no avail.
> >
> > The most helpful thing I could find were the following rules in plain
> > English (from w3schools):
> >
> > Names can contain letters, numbers, and other characters
> > Names cannot start with a number or punctuation character
> > Names cannot start with the letters xml (or XML, or Xml, etc)
> > Names cannot contain spaces
> >
> >
> > Now I am in the process of putting together my own regex checking
> algorithm,
> > but I haven't had much luck in getting it to work correctly. I figured I
> > would ask the greater community if there was a quick solution before I
> spend
> > too many hours trying to solve what I hoped would be a relatively simple
> > problem. :-)
> >
> > eXist details:
> > eXist 2.1 trunk, rev 17098
> > Java 1.6
> > MacOS X 10.7.4
> >
> > --
> > David Finton
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Exist-open mailing list
> > Exist-open@...
> > https://lists.sourceforge.net/lists/listinfo/exist-open
> >
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> adam@...
> irc://irc.freenode.net/existdb
>



-- 
David Finton

Re: [Exist-open] XQuery regex for valid XML element names

[Adam Retter <adam@ex...>]

I dont know of an existing regexp, but you could build a regexp based
on the BNF defined in the spec here -
http://www.w3.org/TR/REC-xml/#sec-starttags

Maybe simpler is just to try and construct an xs:QName() from your
element or attribute name inside of a try {} catch {} block, if its
not a valid QName it aint a valid element or attribute name ;-)

On 7 September 2012 16:23, Dave Finton <dave.finton@...> wrote:
> I'm in the process of putting together a script that takes a user-supplied
> or system-defined string (via a URL parameter usually) and using that string
> as part of an XPath expression that will ultimately be processed in a
> util:eval(...) function call. One of the problems with this is the potential
> for security vulnerabilities through code injection, so I want to make sure
> the user-defined string passes a few tests before passing it along to
> util:eval. One such test is to make sure the user-supplied string is in fact
> a valid XML element and/or attribute name. Here's where I ran into a
> problem.
>
> I started off on what I thought would be a 15-minute research project: find
> a regex I can use in XQuery (i.e. something i can use in the fn:matches(...)
> function) that I could use to validate or invalidate that a given arbitrary
> string was a valid XML element and/or attribute label. I'm found some
> example in Java, PHP, and other languages, but nothing for XQuery. Even
> worse, the examples I did find were in comment threads where no one seemed
> to agree what the "correct" solution is. I went through "official"
> documentation from various sources including those from the w3schools web
> site as well, to no avail.
>
> The most helpful thing I could find were the following rules in plain
> English (from w3schools):
>
> Names can contain letters, numbers, and other characters
> Names cannot start with a number or punctuation character
> Names cannot start with the letters xml (or XML, or Xml, etc)
> Names cannot contain spaces
>
>
> Now I am in the process of putting together my own regex checking algorithm,
> but I haven't had much luck in getting it to work correctly. I figured I
> would ask the greater community if there was a quick solution before I spend
> too many hours trying to solve what I hoped would be a relatively simple
> problem. :-)
>
> eXist details:
> eXist 2.1 trunk, rev 17098
> Java 1.6
> MacOS X 10.7.4
>
> --
> David Finton
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>



-- 
Adam Retter

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

[Exist-open] XQuery regex for valid XML element names

[Dave Finton <dave.finton@gm...>]

I'm in the process of putting together a script that takes a user-supplied
or system-defined string (via a URL parameter usually) and using that
string as part of an XPath expression that will ultimately be processed in
a util:eval(...) function call. One of the problems with this is the
potential for security vulnerabilities through code injection, so I want to
make sure the user-defined string passes a few tests before passing it
along to util:eval. One such test is to make sure the user-supplied string
is in fact a valid XML element and/or attribute name. Here's where I ran
into a problem.

I started off on what I thought would be a 15-minute research project: find
a regex I can use in XQuery (i.e. something i can use in the
fn:matches(...) function) that I could use to validate or invalidate that a
given arbitrary string was a valid XML element and/or attribute label. I'm
found some example in Java, PHP, and other languages, but nothing for
XQuery. Even worse, the examples I did find were in comment threads where
no one seemed to agree what the "correct" solution is. I went through
"official" documentation from various sources including those from the
w3schools web site as well, to no avail.

The most helpful thing I could find were the following rules in plain
English (from w3schools):


   - Names can contain letters, numbers, and other characters
   - Names cannot start with a number or punctuation character
   - Names cannot start with the letters xml (or XML, or Xml, etc)
   - Names cannot contain spaces


Now I am in the process of putting together my own regex checking
algorithm, but I haven't had much luck in getting it to work correctly. I
figured I would ask the greater community if there was a quick solution
before I spend too many hours trying to solve what I hoped would be a
relatively simple problem. :-)

eXist details:
eXist 2.1 trunk, rev 17098
Java 1.6
MacOS X 10.7.4

-- 
David Finton

Re: [Exist-open] RestXQ: fatal errors in Tomcat

[Martin Holmes <mholmes@uv...>]

On 12-09-07 02:32 AM, Adam Retter wrote:
>> Why would you abandon the WAR deployment? Lots of people use it. We're
>> only just migrating projects away from the Cocoon build to eXist WAR
>> under Tomcat, and now that one's going to disappear?
>
> Its not concerete yet!
>
> We are a small team and have lots of things to support and improve in
> eXist-db, if we can reduce the peripherary stuff whilst improving the
> core that makes us more effective. There are, we think, only a handful
> of users that use the WAR approach. If they make enough noise and there are more
> that we thought then we will certainly keep it.
>
> Its an open source project and we have limited resources, but if
> someone would like to join the team as 'the war guy' that maintains
> the war build and tests it, then that would be great :-)

We do maintain a build server for the WARs here:

<http://plum.hcmc.uvic.ca:8080/>;

but we don't have anyone with the expertise to take over maintenance of 
the WAR distribution, unfortunately.

Cheers,
Martin

[Exist-open] Installer and Launcher issues on Open Indiana

[Adam Retter <adam@ex...>]

Further testing...

Open Indiana is the Open Solaris replacement which is similar to Solaris 11.

aretter@...:~$ uname -av
SunOS catsinspace 5.11 oi_151a5 i86pc i386 i86pc Solaris

aretter@...:~$ java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)

1) The new installer, does not seem to create a Desktop icon.
2) The icons on the start menu are broken (as they are in Linux Mint)
3) The start menu on the Desktop icon is broken (as they are in Linux Mint)
4) When Launching the eXist Database - the launcher splash screen is
just a completely grey box

The launcher does start and appears in the system tray, but right click and...

1) Open Dashboard, results in a 404
2) Open exist.log results in a dialog which says 'Failed to open exist.log'.

Hope that helps.

Cheers Adam.


-- 
Adam Retter

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

[Exist-open] New Launcher fails Linux Mint

[Adam Retter <adam@ex...>]

Linux Mint is a Ubuntu derivative but appears to have problems with
the changes made to eXist-db's startup/launcher process.

On Linux Mint 13 (Cinamon) x64.

aretter@... ~/eXist-db-2.1-dev $ uname -av
Linux xmlss-demo-linux 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10
20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Latest eXist-trunk, svn revision 17098

I have tested the following with *BOTH* Oracle JDK 1.6.0_35 x64 and
OpenJDK 1.6.0_24 x64.


1) Icons for the Desktop Item and the Start Menu Items are broken or
appear as black.

2)  when I run "eXist Database" icon I get a Java Dialog come up which
says "Running eXist-db via the launcher is not supported on your
platform. Please run it using startup.sh/startup.bar" <--- this seems
like a regression from the previous approach which did work.

If I attempt to run the equivalent of the desktop icon, "java -jar
start.jar" then I get output similar to this on the console:

Java opts:  -Dexist.home="/home/aretter/eXist-db-2.1-dev"
-Djava.endorsed.dirs="/home/aretter/eXist-db-2.1-dev/lib/endorsed"
     [null] Executing '/usr/lib/jvm/jdk1.6.0_35/jre/bin/java' with arguments:
     [null] '-Dexist.home=/home/aretter/eXist-db-2.1-dev'
     [null] '-Djava.endorsed.dirs=/home/aretter/eXist-db-2.1-dev/lib/endorsed'
     [null] '-jar'
     [null] '/home/aretter/eXist-db-2.1-dev/start.jar'
     [null] 'org.exist.launcher.Launcher'
     [null]
     [null] The ' characters around the executable and arguments are
     [null] not part of the command.
Execute:Java13CommandLauncher: Executing
'/usr/lib/jvm/jdk1.6.0_35/jre/bin/java' with arguments:
'-Dexist.home=/home/aretter/eXist-db-2.1-dev'
'-Djava.endorsed.dirs=/home/aretter/eXist-db-2.1-dev/lib/endorsed'
'-jar'
'/home/aretter/eXist-db-2.1-dev/start.jar'
'org.exist.launcher.Launcher'

The ' characters around the executable and arguments are
not part of the command.
spawned process java.lang.UNIXProcess@...


However running, bin/startup.sh works as one would expect using either
Oracle of OpenJDKs, so there seems to be some sort of bug in the
Launcher?

Cheers Adam.

-- 
Adam Retter

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

Re: [Exist-open] Locale bug for schema parsing

[merve <merve.ozbey@li...>]

Hello,

I have also localization problem with eXist 2.0. I could not install eXist
when language setting was Turkish. I changed language setting to English
then installed eXist, and started. But I can not start eXist using Turkish
setting, error message is here: 

07 Eyl 2012 14:34:53,524 [main] INFO  (JettyStart.java [run]:108) -
Configuring eXist from D:\devTlos3\eXist2.0\conf.xml

07 Eyl 2012 14:34:53,525 [main] INFO  (JettyStart.java [run]:109) -
07 Eyl 2012 14:34:53,526 [main] INFO  (JettyStart.java [run]:110) - Running
with Java 1.6.0_33 [Sun Microsystems Inc. (J
ava HotSpot(TM) 64-Bit Server VM) in D:\dev\Java\jdk1.6.0_33\jre]
07 Eyl 2012 14:34:53,526 [main] INFO  (JettyStart.java [run]:115) -
07 Eyl 2012 14:34:53,567 [main] INFO  (JettyStart.java [run]:119) - [eXist
Version : 2.0-tech-preview]
07 Eyl 2012 14:34:53,568 [main] INFO  (JettyStart.java [run]:121) - [eXist
Build : 20120211]
07 Eyl 2012 14:34:53,568 [main] INFO  (JettyStart.java [run]:123) - [eXist
Home : unknown]
07 Eyl 2012 14:34:53,571 [main] INFO  (JettyStart.java [run]:125) - [SVN
Revision : 15855]
07 Eyl 2012 14:34:53,571 [main] INFO  (JettyStart.java [run]:133) -
[Operating System : Windows 7 6.1 amd64]
07 Eyl 2012 14:34:53,572 [main] INFO  (JettyStart.java [run]:136) -
[jetty.home : D:\devTlos3\eXist2.0\tools\jetty]
07 Eyl 2012 14:34:53,572 [main] INFO  (JettyStart.java [run]:138) -
[log4j.configuration : file:/D:/devTlos3/eXist2.0/lo
g4j.xml]
org.exist.EXistException: database instance 'exist' is not available
        at org.exist.storage.BrokerPool.getInstance(BrokerPool.java:312)
        at org.exist.storage.BrokerPool.getInstance(BrokerPool.java:298)
        at org.exist.jetty.JettyStart.run(JettyStart.java:179)
        at org.exist.jetty.JettyStart.main(JettyStart.java:70)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.exist.start.Main.invokeMain(Main.java:137)
        at org.exist.start.Main.run(Main.java:463)
        at org.exist.start.Main.main(Main.java:59)

Then I changed JAVA_OPTS parameter in startup.bat file and I can start eXist
with Turkish setting:

set JAVA_OPTS="-Xms128m -Xmx512m -Dfile.encoding=UTF-8
-Djava.endorsed.dirs=%JAVA_ENDORSED_DIRS% -Duser.country=US
-Duser.language=en"

Will you do something about this localization problem? 

Thanks..



--
View this message in context: http://exist.2174344.n4.nabble.com/Locale-bug-for-schema-parsing-tp4518644p4656197.html
Sent from the exist-open mailing list archive at Nabble.com.

Re: [Exist-open] RestXQ: fatal errors in Tomcat

[Adam Retter <adam@ex...>]

> Why would you abandon the WAR deployment? Lots of people use it. We're
> only just migrating projects away from the Cocoon build to eXist WAR
> under Tomcat, and now that one's going to disappear?

Its not concerete yet!

We are a small team and have lots of things to support and improve in
eXist-db, if we can reduce the peripherary stuff whilst improving the
core that makes us more effective. There are, we think, only a handful
of users that use the WAR approach. If they make enough noise and there are more
that we thought then we will certainly keep it.

Its an open source project and we have limited resources, but if
someone would like to join the team as 'the war guy' that maintains
the war build and tests it, then that would be great :-)

-- 
Adam Retter

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

Re: [Exist-open] XML to JSON

[Wolfgang Meier <wolfgang@ex...>]

Hi Chris, 

> In addition to the reversibility argument:
> 
> - My API which provides JSON using json.xq (slightly modified) has been
> published and is in use. 
> 
> - Unless the serialization makes a distinction between elements and attributes,
> there will be ambiguity if an attribute and an element have the same name.

Ok, I added a serialization option "prefix-attributes=yes|no" to the JSON serializer (5 minutes work). The default is "no". Just add it to your other serialization options.

Wolfgang

Re: [Exist-open] pre tag within XQuery

[Loren Cahlander <loren.cahlander@gm...>]

That is the plan.  I have not tried just bringing in the brush into the app where I have added the items from the download from the syntaxhighlighter website.

I am figuring that it will have to be updated for XQuery 3.

On Sep 6, 2012, at 11:08 PM, Joe Wicentowski <joewiz@...> wrote:

> Hi Loren,
> 
>> I will have to bring our current XQuery brush file
>> webapp/scripts/syntax/shBrushXQuery.js to the upgraded highlighter.
> 
> You may want to confirm with the core devs here, but my sense is that
> everything in the webapp directory (docs, etc.) is being moved into
> separate apps.  So you should probably bundle whatever libraries your
> app needs in your app.
> 
> Joe

Re: [Exist-open] pre tag within XQuery

[Joe Wicentowski <joewiz@gm...>]

Hi Loren,

> I will have to bring our current XQuery brush file
> webapp/scripts/syntax/shBrushXQuery.js to the upgraded highlighter.

You may want to confirm with the core devs here, but my sense is that
everything in the webapp directory (docs, etc.) is being moved into
separate apps.  So you should probably bundle whatever libraries your
app needs in your app.

Joe

Re: [Exist-open] pre tag within XQuery

[Loren Cahlander <loren.cahlander@gm...>]

I will have to bring our current XQuery brush file webapp/scripts/syntax/shBrushXQuery.js to the upgraded highlighter.

On Sep 6, 2012, at 10:54 PM, Loren Cahlander <loren.cahlander@...> wrote:

> I think that this is in the SyntaxHighlighter javascript code.  You can check out http://alexgorbatchev.com/SyntaxHighlighter/manual/installation.html
> 
> 
> On Sep 6, 2012, at 10:45 PM, Martin Holmes <mholmes@...> wrote:
> 
>> Doesn't this:
>> 
>> <pre class="brush: js;">
>> 
>> mean a <pre> element with two classes, one 'brush:' and one 'js;'? Can 
>> you have class names ending with punctuation?
>> 
>> Cheers,
>> Martin
>> 
> 

Re: [Exist-open] pre tag within XQuery

[Loren Cahlander <loren.cahlander@gm...>]

I think that this is in the SyntaxHighlighter javascript code.  You can check out http://alexgorbatchev.com/SyntaxHighlighter/manual/installation.html


On Sep 6, 2012, at 10:45 PM, Martin Holmes <mholmes@...> wrote:

> Doesn't this:
> 
> <pre class="brush: js;">
> 
> mean a <pre> element with two classes, one 'brush:' and one 'js;'? Can 
> you have class names ending with punctuation?
> 
> Cheers,
> Martin
> 

Re: [Exist-open] pre tag within XQuery

[Martin Holmes <mholmes@uv...>]

Doesn't this:

<pre class="brush: js;">

mean a <pre> element with two classes, one 'brush:' and one 'js;'? Can 
you have class names ending with punctuation?

Cheers,
Martin

On 12-09-06 08:20 PM, Loren Cahlander wrote:
> Hello folks,
>
> /The obligatory reference of trunk revision 17066./
>
> I have not come across this before, so I am baffled. I need to return
> some xhtml that contains <pre></pre> tags.  What do I need to change?
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">;
> <htmlxmlns="http://www.w3.org/1999/xhtml"xml:lang="en"lang="en">;
> <head>
> <metahttp-equiv="Content-Type"content="text/html; charset=UTF-8"/>
> <title>Hello SyntaxHighlighter</title>
> <scripttype="text/javascript"src="/exist/apps/docs/resources/scripts/shCore.js"></script>
> <scripttype="text/javascript"src="/exist/apps/docs/resources/scripts/shBrushJScript.js"></script>
> <linktype="text/css"rel="stylesheet"
>              href="/exist/apps/docs/resources/css/shCoreDefault.css"/>
> <scripttype="text/javascript">SyntaxHighlighter.all();</script>
> </head>
>
> <bodystyle="background: white; font-family: Helvetica">
>
> <h1>Hello SyntaxHighlighter</h1>
> <preclass="brush: js;">
> function helloSyntaxHighlighter()
> {
> return "hi!";
> }
> </pre>
> </body>
> </html>
>
> I am trying to create the new docs app with the new syntax highlighter.
>   I am getting the following error:
>
>
>     HTTP ERROR 500
>
> Problem accessing /exist/apps/docs/fubar. Reason:
>
>      exerr:ERROR err:XPST0003: Static error: no closing end tag found for element constructor: pre [at line 26, column 2]
>
>
>       Caused by:
>
> org.exist.xquery.XPathException: exerr:ERROR err:XPST0003: Static erro
>   r: no closing end tag found for element constructor: pre [at line 26, column 2]
> 	at org.exist.xquery.parser.XQueryParser.elementWithAttributes(XQueryParser.java:11663)
> 	at org.exist.xquery.parser.XQueryParser.elementConstructor(XQueryParser.java:10683)
> 	at org.exist.xquery.parser.XQueryParser.elementContent(XQueryParser.java:12174)
> 	at org.exist.xquery.parser.XQueryParser.mixedElementContent(XQueryParser.java:11787)
> 	at org.exist.xquery.parser.XQueryParser.elementWithAttributes(XQueryParser.java:11619)
> 	at org.exist.xquery.parser.XQueryParser.elementConstructor(XQueryParser.java:10683)
> 	at org.exist.xquery.parser.XQueryParser.elementContent(XQueryParser.java:12174)
> 	at org.exist.xquery.parser.XQueryParser.mixedElementContent(XQueryParser.java:11787)
> 	at org.exist.xquery.parser.XQueryParser.elementWithAttributes(XQueryParser.java:11619)
> 	at org.exist.xquery.parser.XQueryParser.elementConstructor(XQueryParser.java:10683)
> 	at org.exist.xquery.parser.XQueryParser.directConstructor(XQueryParser.java:9174)
> 	at org.exist.xquery.parser.XQueryParser.primaryExpr(XQueryParser.java:8450)
> 	at org.exist.xquery.parser.XQueryParser.postfixExpr(XQueryParser.java:7760)
> 	at org.exist.xquery.parser.XQueryParser.stepExpr(XQueryParser.java:7722)
> 	at org.exist.xquery.parser.XQueryParser.relativePathExpr(XQueryParser.java:7287)
> 	at org.exist.xquery.parser.XQueryParser.pathExpr(XQueryParser.java:7080)
> 	at org.exist.xquery.parser.XQueryParser.valueExpr(XQueryParser.java:6937)
> 	at org.exist.xquery.parser.XQueryParser.unaryExpr(XQueryParser.java:6449)
> 	at org.exist.xquery.parser.XQueryParser.castExpr(XQueryParser.java:6200)
> 	at org.exist.xquery.parser.XQueryParser.castableExpr(XQueryParser.java:6106)
> 	at org.exist.xquery.parser.XQueryParser.treatExpr(XQueryParser.java:6013)
> 	at org.exist.xquery.parser.XQueryParser.instanceofExpr(XQueryParser.java:5921)
> 	at org.exist.xquery.parser.XQueryParser.intersectExceptExpr(XQueryParser.java:7238)
> 	at org.exist.xquery.parser.XQueryParser.unionExpr(XQueryParser.java:6708)
> 	at org.exist.xquery.parser.XQueryParser.multiplicativeExpr(XQueryParser.java:6643)
> 	at org.exist.xquery.parser.XQueryParser.additiveExpr(XQueryParser.java:6594)
> 	at org.exist.xquery.parser.XQueryParser.rangeExpr(XQueryParser.java:6514)
> 	at org.exist.xquery.parser.XQueryParser.stringConcatExpr(XQueryParser.java:6470)
> 	at org.exist.xquery.parser.XQueryParser.comparisonExpr(XQueryParser.java:5621)
> 	at org.exist.xquery.parser.XQueryParser.andExpr(XQueryParser.java:5590)
> 	at org.exist.xquery.parser.XQueryParser.orExpr(XQueryParser.java:4276)
> 	at org.exist.xquery.parser.XQueryParser.exprSingle(XQueryParser.java:3875)
> 	at org.exist.xquery.parser.XQueryParser.expr(XQueryParser.java:424)
> 	at org.exist.xquery.parser.XQueryParser.functionBody(XQueryParser.java:2664)
> 	at org.exist.xquery.parser.XQueryParser.functionDecl(XQueryParser.java:2309)
> 	at org.exist.xquery.parser.XQueryParser.functionDeclUp(XQueryParser.java:1493)
> 	at org.exist.xquery.parser.XQueryParser.prolog(XQueryParser.java:922)
> 	at org.exist.xquery.parser.XQueryParser.mainModule(XQueryParser.java:649)
> 	at org.exist.xquery.parser.XQueryParser.module(XQueryParser.java:562)
> 	at org.exist.xquery.parser.XQueryParser.xpath(XQueryParser.java:468)
> 	at org.exist.xquery.XQuery.compile(XQuery.java:139)
> 	at org.exist.xquery.XQuery.compile(XQuery.java:106)
> 	at org.exist.xquery.XQuery.compile(XQuery.java:90)
> 	at org.exist.http.urlrewrite.XQueryURLRewrite.runQuery(XQueryURLRewrite.java:687)
> 	at org.exist.http.urlrewrite.XQueryURLRewrite.service(XQueryURLRewrite.java:242)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> 	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1367)
> 	at de.betterform.agent.web.filter.XFormsFilter.doFilter(XFormsFilter.java:173)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)
> 	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:484)
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
> 	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:499)
> 	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:233)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)
> 	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)
> 	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
> 	at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
> 	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
> 	at org.eclipse.jetty.server.Server.handle(Server.java:350)
> 	at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)
> 	at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:890)
> 	at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:944)
> 	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:630)
> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
> 	at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)
> 	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606)
> 	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46)
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
> 	at java.lang.Thread.run(Thread.java:722)
>
> ------------------------------------------------------------------------
> /Powered by Jetty:///
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] pre tag within XQuery

[Loren Cahlander <loren.cahlander@gm...>]

That did not work.  What I ended up doing was to put the XHTML into a file and used doc().  I was just trying to start to utilize the SyntaxHighlighter.  I had to get that working before I could start the DocBook to XHTML conversion for the docs app.  You can check out http://greatlinkup.com:8080/exist/apps/docs/fubar


On Sep 6, 2012, at 10:40 PM, Joe Wicentowski <joewiz@...> wrote:

> Hi Loren,
> 
>> <pre class="brush: js;">
>> function helloSyntaxHighlighter()
>> {
>> return "hi!";
>> }
>> </pre>
> 
> You need to escape those curly braces:
> 
> <pre class="brush: js;">
> function helloSyntaxHighlighter()
> {{
>    return "hi!";
> }}
> </pre>
> 
> Joe

Re: [Exist-open] RestXQ: fatal errors in Tomcat

[Martin Holmes <mholmes@uv...>]

On 12-09-06 12:11 PM, Dannes Wessels wrote:
> Hi Ron,
>
>
> On 6 Sep 2012, at 12:42 , ron.vandenbranden@...
> <mailto:ron.vandenbranden@...> wrote:
>
>>    -include database content (though this might be controversial?)
>
> hmm, no that is probably too risky, as long we deliver the war files. In
> the future however, we might abandon the war deployment at all the
> alternative we then offer is: bring your war files into exist's jetty
> server.

Why would you abandon the WAR deployment? Lots of people use it. We're 
only just migrating projects away from the Cocoon build to eXist WAR 
under Tomcat, and now that one's going to disappear?

Cheers,
Martin

> D.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>