exist-development — eXist Developer's List

[Exist-development] XMLDBModule

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

I do think that we should split accounts management's functions from
http://exist-db.org/xquery/xmldb to
http://exist-db.org/xquery/security/accounts .

Any objections?

-- 
Cheers,

Dmitriy Shabanov

[Exist-development] is it bug or not?

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

I want to discuss: 

Can't convert a Java String to an XQuery xs:string - ID: 2839748

http://sourceforge.net/tracker/?func=detail&aid=2839748&group_id=17691&atid=117691

is it bug or not?

-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] Added the option of checking server name for URL rewriting

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

Hello Thomas,

The matching could be implemented by changing the following code in RewriteConfig.java:

                /*
                 * If the URLRewrite is a ControllerForward, then test to see if there is a condition
                 * on the server name.  If there is a condition on the server name and the names do not
                 * match, then ignore this ControllerForward.
                 */
                if (action instanceof ControllerForward) {
                	if (serverName != null) {
                		String controllerServerName = ((ControllerForward)action).getServerName();
                		if (controllerServerName != null) {
                			if (!serverName.equalsIgnoreCase(controllerServerName)) {
                				continue;
                			}
                		}
                	}
                	
                }

As for the access log file, that is specified in the Jetty config file.  

    <Ref id="RequestLog">
      <Set name="requestLog">
        <New id="RequestLogImpl" class="org.eclipse.jetty.server.NCSARequestLog">
          <Set name="filename"><SystemProperty name="jetty.home" default="."/>/logs/yyyy_mm_dd.request.log</Set>
          <Set name="filenameDateFormat">yyyy_MM_dd</Set>
          <Set name="retainDays">90</Set>
          <Set name="append">true</Set>
          <Set name="extended">true</Set>
          <Set name="logCookies">false</Set>
          <Set name="LogTimeZone">GMT</Set>
          <Set name="LogServer">true</Set>
        </New>
      </Set>
    </Ref>


The format of the logfile entries are as follows based on the parameters:

Extended

LogServer

Format

False

False

"%host %other %logname %time1 %methodurl %code %bytesd"

False

True

"%virtualname %host %other %logname %time1 %methodurl %code %bytesd"

True

False

"%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot"

True

True

"%virtualname %host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot"

With the following being the legend: 


#   %virtualname      Web sever virtual hostname. Use this tag when same log
#                     contains data of several virtual web servers. AWStats
#                     will discard records not in SiteDomain nor HostAliases
#   %host             Client hostname or IP address (or Sender host for mail log)
#   %other            Means another not used field
#   %logname          Authenticated login/user with format: john
#   %time1            Date and time with format: [dd/mon/yyyy:hh:mm:ss +0000] or [dd/mon/yyyy:hh:mm:ss]
#   %methodurl        Method and URL with format: "GET /index.html HTTP/x.x"
#   %code             Return code status (with format for web log: 999)
#   %bytesd           Size of document in bytes
#   %refererquot      Referer page with format: "http://from.com/from.htm"
#   %uaquot           User agent with format: "Mozilla/4.0 (compatible, ...)"



You could write your own RequestLogger and have the server name mapped into the log file name.  I am planning on adding the JavaDoc to the NCSARequestLogger (https://bugs.eclipse.org/bugs/show_bug.cgi?id=302350) so that the impact of changing the parameter values is clear.

Loren

On Feb 10, 2010, at 02:23 AM, Thomas White wrote:

> 
> Loren,
> 
> This is a very useful extension. I like it very much.
> I would like to suggest two additional features: 
> specify the name of the log file explicitly.
> to allow wildcat symbols in the server name:
>  <root server-name="images*,.example.com" pattern="/*" path="xmldb:exist:///db/images/" log-name="images-xxx,example.com"/>
> 
> This is particularly useful when we want images in a web page to load quicker, to bypass the browser limit of downloading only up to 2 files simultaneously from a domain.
> 
> Thomas

Re: [Exist-development] Added the option of checking server name for URL rewriting

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

Loren,

This is a very useful extension. I like it very much.
I would like to suggest two additional features:

   1. specify the name of the log file explicitly.
   2. to allow wildcat symbols in the server name:

 <root server-name="images*,.example.com <http://site1.example.com/>"
pattern="/*" path="xmldb:exist:///db/images/" log-name="images-xxx,
example.com <http://site1.example.com/>"/>

This is particularly useful when we want images in a web page to load
quicker, to bypass the browser limit of downloading only up to 2 files
simultaneously from a domain.

Thomas


------

Thomas White

Mobile:+44 7711 922 966
Skype: thomaswhite
gTalk: thomas.0007
Linked-In:http://www.linkedin.com/in/thomaswhite0007
facebook: http://www.facebook.com/thomas.0007



On 9 February 2010 20:35, Loren Cahlander <lor...@gm...> wrote:

> I am open to suggestions.
>

Re: [Exist-development] Added the option of checking server name for URL rewriting

[Joe W. <jo...@gm...>]

Sorry, my bad!  You have it right.

- Joe

On Tuesday, February 9, 2010, Loren Cahlander <lor...@gm...> wrote:
> The .* is the default for root:
>
>     <root pattern=".*" path="/"/>
>
> I just added localhost in the server-name attribute
>
>     <root server-name="localhost" pattern=".*" path="/"/>
>
>
> Loren
>
> On Feb 9, 2010, at 02:12 PM, Joe Wicentowski wrote:
>
>> Loren,
>>
>> Very neat.  One observation:  In a couple of cases your @pattern was
>> ".*".  I believe these should all be "/*", not ".*".
>>
>> Joe

Re: [Exist-development] Added the option of checking server name for URL rewriting

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

To add the server name to the jetty request logs (tools/jetty/logs/*), you need to add a parameter to the jetty.xml in the trunk branch only:

    <Ref id="RequestLog">
      <Set name="requestLog">
        <New id="RequestLogImpl" class="org.eclipse.jetty.server.NCSARequestLog">
          <Set name="filename"><SystemProperty name="jetty.home" default="."/>/logs/yyyy_mm_dd.request.log</Set>
          <Set name="filenameDateFormat">yyyy_MM_dd</Set>
          <Set name="retainDays">90</Set>
          <Set name="append">true</Set>
          <Set name="extended">true</Set>
          <Set name="logCookies">false</Set>
          <Set name="LogTimeZone">GMT</Set>
          <Set name="LogServer">true</Set>
        </New>
      </Set>
    </Ref>

This will only work on the trunk, because that parameter can only be set under Jetty7.  It adds the server name on the request at the beginning of the logfile entry before the ip address of the requesting computer.

I also change the extended parameter to true, because that gives the referring URL and the browser agent information in the log file.  This supplies a great deal of information for web statistics such as awstats.


On Feb 9, 2010, at 01:56 PM, Loren Cahlander wrote:

> There is an option (off of trunk version 11177) now to send web queries to different collections within eXist based on the server name in the URL:
> 
> i.e.
> With the following configuration changes in controller-config.xml
> 
> from:
>     <root pattern=".*" path="/"/>
> 
> to:
>     <root server-name="site1.example.com" pattern="/*" path="xmldb:exist:///db/org/site1/"/>
>     <root server-name="site2.example.com" pattern="/*" path="xmldb:exist:///db/org/site2/"/>
>     <root server-name="site3.example.com" pattern="/*" path="xmldb:exist:///db/org/site3/"/>
>     <root server-name="localhost" pattern=".*" path="/"/>
>     <root server-name="site4.example.com" pattern=".*" path="/"/>
> 
> http://site1.example.com/ would be redirected to /db/org/site1
> http://site2.example.com/ would be redirected to /db/org/site2
> http://site3.example.com/ would be redirected to /db/org/site3
> http://localhost/ would be directed to index.xml in the webapp directory as it is normally done.
> http://site4.example.com/ would be directed to index.xml
> 
> NOTE: The server-name attribute is optional.  If it is omitted, then the behavior operates as normal.
> 
> This will allow for the hosting of multiple websites in one eXist instance.  
> 
> I still need to work on the jetty configuration, so that the logs for each individual website can be separated out from the other websites.

Re: [Exist-development] Added the option of checking server name for URL rewriting

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

I am open to suggestions.

On Feb 9, 2010, at 02:12 PM, Evgeny Gazdovsky wrote:

> Agree! what about adding hosts/sites dynamically without restarting exist?
> I'm plain handle that in controller.xql and some xml metafile for site description.
> Think it can be more flex in this case.
>  
> 
> 2010/2/9 Loren Cahlander <lor...@gm...>
> There is an option (off of trunk version 11177) now to send web queries to different collections within eXist based on the server name in the URL:
> 
> i.e.
> With the following configuration changes in controller-config.xml
> 
> from:
>     <root pattern=".*" path="/"/>
> 
> to:
>     <root server-name="site1.example.com" pattern="/*" path="xmldb:exist:///db/org/site1/"/>
>     <root server-name="site2.example.com" pattern="/*" path="xmldb:exist:///db/org/site2/"/>
>     <root server-name="site3.example.com" pattern="/*" path="xmldb:exist:///db/org/site3/"/>
>     <root server-name="localhost" pattern=".*" path="/"/>
>     <root server-name="site4.example.com" pattern=".*" path="/"/>
> 
> http://site1.example.com/ would be redirected to /db/org/site1
> http://site2.example.com/ would be redirected to /db/org/site2
> http://site3.example.com/ would be redirected to /db/org/site3
> http://localhost/ would be directed to index.xml in the webapp directory as it is normally done.
> http://site4.example.com/ would be directed to index.xml
> 
> NOTE: The server-name attribute is optional.  If it is omitted, then the behavior operates as normal.
> 
> This will allow for the hosting of multiple websites in one eXist instance.  
> 
> I still need to work on the jetty configuration, so that the logs for each individual website can be separated out from the other websites.
> 
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
> 
> 

Re: [Exist-development] Added the option of checking server name for URL rewriting

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

The .* is the default for root:

    <root pattern=".*" path="/"/>

I just added localhost in the server-name attribute

    <root server-name="localhost" pattern=".*" path="/"/>


Loren

On Feb 9, 2010, at 02:12 PM, Joe Wicentowski wrote:

> Loren,
> 
> Very neat.  One observation:  In a couple of cases your @pattern was
> ".*".  I believe these should all be "/*", not ".*".
> 
> Joe
> 
> 
> On Tue, Feb 9, 2010 at 2:56 PM, Loren Cahlander
> <lor...@gm...> wrote:
>> There is an option (off of trunk version 11177) now to send web queries to
>> different collections within eXist based on the server name in the URL:
>> i.e.
>> With the following configuration changes in controller-config.xml
>> from:
>>     <root pattern=".*" path="/"/>
>> to:
>>     <root server-name="site1.example.com" pattern="/*"
>> path="xmldb:exist:///db/org/site1/"/>
>>     <root server-name="site2.example.com" pattern="/*"
>> path="xmldb:exist:///db/org/site2/"/>
>>     <root server-name="site3.example.com" pattern="/*"
>> path="xmldb:exist:///db/org/site3/"/>
>>     <root server-name="localhost" pattern=".*" path="/"/>
>>     <root server-name="site4.example.com" pattern=".*" path="/"/>
>> http://site1.example.com/ would be redirected to /db/org/site1
>> http://site2.example.com/ would be redirected to /db/org/site2
>> http://site3.example.com/ would be redirected to /db/org/site3
>> http://localhost/ would be directed to index.xml in the webapp directory as
>> it is normally done.
>> http://site4.example.com/ would be directed to index.xml
>> NOTE: The server-name attribute is optional.  If it is omitted, then the
>> behavior operates as normal.
>> This will allow for the hosting of multiple websites in one eXist instance.
>> 
>> I still need to work on the jetty configuration, so that the logs for each
>> individual website can be separated out from the other websites.

Re: [Exist-development] Added the option of checking server name for URL rewriting

[Joe W. <jo...@gm...>]

Loren,

Very neat.  One observation:  In a couple of cases your @pattern was
".*".  I believe these should all be "/*", not ".*".

Joe


On Tue, Feb 9, 2010 at 2:56 PM, Loren Cahlander
<lor...@gm...> wrote:
> There is an option (off of trunk version 11177) now to send web queries to
> different collections within eXist based on the server name in the URL:
> i.e.
> With the following configuration changes in controller-config.xml
> from:
>     <root pattern=".*" path="/"/>
> to:
>     <root server-name="site1.example.com" pattern="/*"
> path="xmldb:exist:///db/org/site1/"/>
>     <root server-name="site2.example.com" pattern="/*"
> path="xmldb:exist:///db/org/site2/"/>
>     <root server-name="site3.example.com" pattern="/*"
> path="xmldb:exist:///db/org/site3/"/>
>     <root server-name="localhost" pattern=".*" path="/"/>
>     <root server-name="site4.example.com" pattern=".*" path="/"/>
> http://site1.example.com/ would be redirected to /db/org/site1
> http://site2.example.com/ would be redirected to /db/org/site2
> http://site3.example.com/ would be redirected to /db/org/site3
> http://localhost/ would be directed to index.xml in the webapp directory as
> it is normally done.
> http://site4.example.com/ would be directed to index.xml
> NOTE: The server-name attribute is optional.  If it is omitted, then the
> behavior operates as normal.
> This will allow for the hosting of multiple websites in one eXist instance.
>
> I still need to work on the jetty configuration, so that the logs for each
> individual website can be separated out from the other websites.

Re: [Exist-development] Added the option of checking server name for URL rewriting

[Evgeny G. <gaz...@gm...>]

Agree! what about adding hosts/sites dynamically without restarting exist?
I'm plain handle that in controller.xql and some xml metafile for site
description.
Think it can be more flex in this case.


2010/2/9 Loren Cahlander <lor...@gm...>

> There is an option (off of trunk version 11177) now to send web queries to
> different collections within eXist based on the server name in the URL:
>
> i.e.
> With the following configuration changes in controller-config.xml
>
> from:
>     <root pattern=".*" path="/"/>
>
> to:
>     <root server-name="site1.example.com" pattern="/*"
> path="xmldb:exist:///db/org/site1/"/>
>     <root server-name="site2.example.com" pattern="/*"
> path="xmldb:exist:///db/org/site2/"/>
>     <root server-name="site3.example.com" pattern="/*"
> path="xmldb:exist:///db/org/site3/"/>
>     <root server-name="localhost" pattern=".*" path="/"/>
>     <root server-name="site4.example.com" pattern=".*" path="/"/>
>
> http://site1.example.com/ would be redirected to /db/org/site1
> http://site2.example.com/ would be redirected to /db/org/site2
> http://site3.example.com/ would be redirected to /db/org/site3
> http://localhost/ would be directed to index.xml in the webapp directory
> as it is normally done.
> http://site4.example.com/ would be directed to index.xml
>
> NOTE: The server-name attribute is optional.  If it is omitted, then the
> behavior operates as normal.
>
> This will allow for the hosting of multiple websites in one eXist instance.
>
>
> I still need to work on the jetty configuration, so that the logs for each
> individual website can be separated out from the other websites.
>
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

[Exist-development] Added the option of checking server name for URL rewriting

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

There is an option (off of trunk version 11177) now to send web queries to different collections within eXist based on the server name in the URL:

i.e.
With the following configuration changes in controller-config.xml

from:
    <root pattern=".*" path="/"/>

to:
    <root server-name="site1.example.com" pattern="/*" path="xmldb:exist:///db/org/site1/"/>
    <root server-name="site2.example.com" pattern="/*" path="xmldb:exist:///db/org/site2/"/>
    <root server-name="site3.example.com" pattern="/*" path="xmldb:exist:///db/org/site3/"/>
    <root server-name="localhost" pattern=".*" path="/"/>
    <root server-name="site4.example.com" pattern=".*" path="/"/>

http://site1.example.com/ would be redirected to /db/org/site1
http://site2.example.com/ would be redirected to /db/org/site2
http://site3.example.com/ would be redirected to /db/org/site3
http://localhost/ would be directed to index.xml in the webapp directory as it is normally done.
http://site4.example.com/ would be directed to index.xml

NOTE: The server-name attribute is optional.  If it is omitted, then the behavior operates as normal.

This will allow for the hosting of multiple websites in one eXist instance.  

I still need to work on the jetty configuration, so that the logs for each individual website can be separated out from the other websites.

Re: [Exist-development] build.sh errors

[Elliotte R. H. <el...@ib...>]

Whatever was going on, it's fixed now. One more svn update followed by
an "ant clean" and it all built. Likely just an old .jar or .class
file in an inconvenient place. Sorry for the noise.

-- 
Elliotte Rusty Harold
el...@ib...

[Exist-development] Data Change notifications (i.e. push)

[The A. <Ans...@gm...>]

Hi,

Might be a newb question, but I'm curious if there is an XML-RPC-based standard and servlet for signing up to receive change notifications to a given document (or something more deep, like XPath match - although that would be pretty heavy), and whether it is implemented/intended/thought about as an extension to eXists. 

For my purposes, almost any level of granularity of change notification could be workable for my application (the finer the better in terms of depth: knowing whether a given node or it's children was updated, rather than something like "any updates to an attribute named 'blah' anywhere in any document"), I just don't see it. I could work around it with a side-band message queue, but I was wondering if there was something more elegant I'm missing. 

I'm just beginning to play around with eXists now, and you've done some great work - thank you for it,

TA

Re: [Exist-development] build.sh errors

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

Hi,

On Mon, Feb 8, 2010 at 8:03 PM, Joe Wicentowski <jo...@gm...> wrote:

>  With several commits this morning, it'll help folks try to reproduce
> the problem if you could report the exact eXist revision number.
>
>
I have been applying patches, compiling and testting (junit, xqts) all day,
and have seen no issues...... I run the same configuration (macosx, 64 bit
java)

cheers

Dannes

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

Re: [Exist-development] build.sh errors

[Joe W. <jo...@gm...>]

>> I just did a fresh checkout of trunk here (rev 11159) and ran
>> build.sh, it all succeeded correctly :-)
>>
>> BUILD SUCCESSFUL
>> Total time: 17 seconds
>>
>> Which JDK are you using, is it definitely a Sun one?
>
> It's the apple port of Sun's JDK. I synced this morning. Nor worth a
> lot of effort if no one else sees the problem.

With several commits this morning, it'll help folks try to reproduce
the problem if you could report the exact eXist revision number.

Joe

Re: [Exist-development] build.sh errors

[Elliotte R. H. <el...@ib...>]

On Mon, Feb 8, 2010 at 8:41 AM, Adam Retter <ad...@ex...> wrote:
> I just did a fresh checkout of trunk here (rev 11159) and ran
> build.sh, it all succeeded correctly :-)
>
> BUILD SUCCESSFUL
> Total time: 17 seconds
>
> Which JDK are you using, is it definitely a Sun one?
>

It's the apple port of Sun's JDK. I synced this morning. Nor worth a
lot of effort if no one else sees the problem.

-- 
Elliotte Rusty Harold
el...@ib...

Re: [Exist-development] [Exist-commits] SF.net SVN: exist:[11140] trunk/eXist/webapp/administration/scripts

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

I promise :-)

On Mon, Feb 8, 2010 at 5:06 PM, Dmitriy Shabanov <sha...@gm...>wrote:

> I'm working under pluggable web applications, let me finish & we will
> back to discussion.
>
> Please, don't touch ;)
>
>
-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] [Exist-commits] SF.net SVN: exist:[11140] trunk/eXist/webapp/administration/scripts

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

I'm working under pluggable web applications, let me finish & we will
back to discussion.

Please, don't touch ;)

-- 
Cheers,

Dmitriy Shabanov

 
On Sun, 2010-02-07 at 22:09 +0100, Dannes Wessels wrote:
> Some questions about recent commits
> 
>         
>         trunk/eXist/webapp/administration/scripts/dynatree/license-bsd.txt
>         
>          trunk/eXist/webapp/administration/scripts/dynatree/license-gpl2.txt
> 
> Are these licenses checked to be compatible with our L-GPL? GPL2 is
> clearly not....
> 
> and... how many versions of jquery do we have? find . -name "jquery*"
> | grep -v svn
> ./administration/scripts/dataTables/jquery.dataTables-1.6.1.js
> ./administration/scripts/dataTables/jquery.dataTables-1.6.1.min.js
> ./administration/scripts/dataTables/jquery.dataTables-1.6.1.min.js.gz
> ./administration/scripts/dynatree/jquery.dynatree-0.5.2.js
> ./administration/scripts/dynatree/jquery.dynatree-0.5.2.min.js
> ./administration/scripts/jquery
> ./administration/scripts/jquery/jquery-1.4.1.js
> ./administration/scripts/jquery/jquery-1.4.1.min.js
> ./administration/scripts/jquery.cookie
> ./administration/scripts/jquery.cookie/jquery.cookie.js
> ./administration/scripts/jquery.ui
> ./administration/scripts/jquery.ui/jquery.ui.full-1.7.2.min.js
> ./biblio/jquery-utils.js
> ./biblio/jquery.xql
> ./scripts/jquery
> ./scripts/jquery/css/jquery.autocomplete.css
> ./scripts/jquery/css/smoothness/jquery-ui-1.7.2.custom.css
> ./scripts/jquery/jquery-1.3.2.min.js
> ./scripts/jquery/jquery-ui-1.7.2.custom.min.js
> ./scripts/jquery/jquery.autocomplete.min.js
>  
> 
> we have .js , .js.gzm  1.3.2, af few 1.7.2 's .... all over the
> archive.
> 
> I remember we decided that we would not do it this way? Please can we
> merge to one consistent set of scripts, with the licenses checked
> of-course..... And have some version info on come of the js files....
> 
> regards
> 
> Dannes

Re: [Exist-development] build.sh errors

[Wolfgang M. <wol...@ex...>]

> After checking exist out of svn and running build.sh I get a few strange errors:

Strange, a fresh copy from svn, but it builds without errors here.
Maybe you checked out a revision which temporarily broke the build.
The xmlrpc tests were modified on the weekend.

Wolfgang

Re: [Exist-development] build.sh errors

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

I just did a fresh checkout of trunk here (rev 11159) and ran
build.sh, it all succeeded correctly :-)

BUILD SUCCESSFUL
Total time: 17 seconds

Which JDK are you using, is it definitely a Sun one?


On 8 February 2010 12:41, Elliotte Rusty Harold <el...@ib...> wrote:
> After checking exist out of svn and running build.sh I get a few strange errors:
>
> test-compile:
>     [echo] Compiling with Java 1.6 from 1.6 source to 1.6 target,
> debug on, optimize on, deprecation off
>    [javac] Compiling 14 source files to
> /Users/elharo/Projects/exist/trunk/exist/test/classes
>    [javac] /Users/elharo/Projects/exist/trunk/exist/test/src/org/exist/performance/actions/StoreFromFile.java:45:
> cannot access EXistException
>    [javac] class file for EXistException not found
>    [javac] public class StoreFromFile extends AbstractAction {
>    [javac]        ^
>    [javac] /Users/elharo/Projects/exist/trunk/exist/test/src/org/exist/xmlrpc/QuerySessionTest.java:142:
> cannot access DBBroker
>    [javac] class file for DBBroker not found
>    [javac]         File[] files = generator.generate(test, generateXQ);
>    [javac]                                 ^
>    [javac] /Users/elharo/Projects/exist/trunk/exist/test/src/org/exist/xmlrpc/XmlRpcTest.java:58:
> cannot access XmldbURI
>    [javac] class file for XmldbURI not found
>    [javac]     private final static XmldbURI TARGET_RESOURCE =
> TARGET_COLLECTION.append(TestConstants.TEST_XML_URI);
>
>
> As near as I can tell, these classes and members are not actually
> missing. Any ideas? Anyone seen this before?
>
> --
> Elliotte Rusty Harold
> el...@ib...
>
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Adam Retter

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

[Exist-development] build.sh errors

[Elliotte R. H. <el...@ib...>]

After checking exist out of svn and running build.sh I get a few strange errors:

test-compile:
     [echo] Compiling with Java 1.6 from 1.6 source to 1.6 target,
debug on, optimize on, deprecation off
    [javac] Compiling 14 source files to
/Users/elharo/Projects/exist/trunk/exist/test/classes
    [javac] /Users/elharo/Projects/exist/trunk/exist/test/src/org/exist/performance/actions/StoreFromFile.java:45:
cannot access EXistException
    [javac] class file for EXistException not found
    [javac] public class StoreFromFile extends AbstractAction {
    [javac]        ^
    [javac] /Users/elharo/Projects/exist/trunk/exist/test/src/org/exist/xmlrpc/QuerySessionTest.java:142:
cannot access DBBroker
    [javac] class file for DBBroker not found
    [javac]         File[] files = generator.generate(test, generateXQ);
    [javac]                                 ^
    [javac] /Users/elharo/Projects/exist/trunk/exist/test/src/org/exist/xmlrpc/XmlRpcTest.java:58:
cannot access XmldbURI
    [javac] class file for XmldbURI not found
    [javac]     private final static XmldbURI TARGET_RESOURCE =
TARGET_COLLECTION.append(TestConstants.TEST_XML_URI);


As near as I can tell, these classes and members are not actually
missing. Any ideas? Anyone seen this before?

-- 
Elliotte Rusty Harold
el...@ib...

Re: [Exist-development] [Exist-commits] SF.net SVN: exist:[11140] trunk/eXist/webapp/administration/scripts

[Wolfgang M. <wol...@ex...>]

> Are these licenses checked to be compatible with our L-GPL? GPL2 is clearly
> not....

This should not be too much of a problem for a library which entirely
runs on the client and is not an integral part of eXist.

However, we agreed that all commonly used js libraries should go into
/webapp/scripts. You can use a controller.xql to forward the browser
request to the common libraries without introducing location-dependent
links.

> ./biblio/jquery-utils.js
> ./biblio/jquery.xql

This is my stuff. Don't touch it please.

Wolfgang

Re: [Exist-development] [Exist-commits] SF.net SVN: exist:[11140] trunk/eXist/webapp/administration/scripts

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

Dannes,

In jQuery we have a main module usually jquery-x.x.x.js and self contained
modules called plugins. It is a common practice plugin file names to be in
the format  jquery.{plugin-name}-{version}.js for the commend version and
jquery.{plugin-name}-{version}.min.js for the minified version.

The way JavaScript files are organised in the list you sent, follow the best
practices for JavaScript projects.

I am still not involved in the this part of eXist project but from looking
at the list and in my experience in working on large jQuery projects, I can
assure you the JavaScript files are fine the way they are.

Regards,
Thomas




------

Thomas White

Mobile:+44 7711 922 966
Skype: thomaswhite
gTalk: thomas.0007
Linked-In:http://www.linkedin.com/in/thomaswhite0007
facebook: http://www.facebook.com/thomas.0007



On 7 February 2010 21:09, Dannes Wessels <da...@ex...> wrote:

> Some questions about recent commits
>
>     trunk/eXist/webapp/administration/scripts/dynatree/license-bsd.txt
>>    trunk/eXist/webapp/administration/scripts/dynatree/license-gpl2.txt
>>
>
> Are these licenses checked to be compatible with our L-GPL? GPL2 is clearly
> not....
>
> and... how many versions of jquery do we have? find . -name "jquery*" |
> grep -v svn
> ./administration/scripts/dataTables/jquery.dataTables-1.6.1.js
> ./administration/scripts/dataTables/jquery.dataTables-1.6.1.min.js
> ./administration/scripts/dataTables/jquery.dataTables-1.6.1.min.js.gz
> ./administration/scripts/dynatree/jquery.dynatree-0.5.2.js
> ./administration/scripts/dynatree/jquery.dynatree-0.5.2.min.js
> ./administration/scripts/jquery
> ./administration/scripts/jquery/jquery-1.4.1.js
> ./administration/scripts/jquery/jquery-1.4.1.min.js
> ./administration/scripts/jquery.cookie
> ./administration/scripts/jquery.cookie/jquery.cookie.js
> ./administration/scripts/jquery.ui
> ./administration/scripts/jquery.ui/jquery.ui.full-1.7.2.min.js
> ./biblio/jquery-utils.js
> ./biblio/jquery.xql
> ./scripts/jquery
> ./scripts/jquery/css/jquery.autocomplete.css
> ./scripts/jquery/css/smoothness/jquery-ui-1.7.2.custom.css
> ./scripts/jquery/jquery-1.3.2.min.js
> ./scripts/jquery/jquery-ui-1.7.2.custom.min.js
> ./scripts/jquery/jquery.autocomplete.min.js
>
> we have .js , .js.gzm  1.3.2, af few 1.7.2 's .... all over the archive.
>
> I remember we decided that we would not do it this way? Please can we merge
> to one consistent set of scripts, with the licenses checked of-course.....
> And have some version info on come of the js files....
>
> regards
>
> Dannes
>
>
>
>
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>
>
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the
> business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

Re: [Exist-development] [Exist-commits] SF.net SVN: exist:[11140] trunk/eXist/webapp/administration/scripts

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

Some questions about recent commits

   trunk/eXist/webapp/administration/scripts/dynatree/license-bsd.txt
>    trunk/eXist/webapp/administration/scripts/dynatree/license-gpl2.txt
>

Are these licenses checked to be compatible with our L-GPL? GPL2 is clearly
not....

and... how many versions of jquery do we have? find . -name "jquery*" | grep
-v svn
./administration/scripts/dataTables/jquery.dataTables-1.6.1.js
./administration/scripts/dataTables/jquery.dataTables-1.6.1.min.js
./administration/scripts/dataTables/jquery.dataTables-1.6.1.min.js.gz
./administration/scripts/dynatree/jquery.dynatree-0.5.2.js
./administration/scripts/dynatree/jquery.dynatree-0.5.2.min.js
./administration/scripts/jquery
./administration/scripts/jquery/jquery-1.4.1.js
./administration/scripts/jquery/jquery-1.4.1.min.js
./administration/scripts/jquery.cookie
./administration/scripts/jquery.cookie/jquery.cookie.js
./administration/scripts/jquery.ui
./administration/scripts/jquery.ui/jquery.ui.full-1.7.2.min.js
./biblio/jquery-utils.js
./biblio/jquery.xql
./scripts/jquery
./scripts/jquery/css/jquery.autocomplete.css
./scripts/jquery/css/smoothness/jquery-ui-1.7.2.custom.css
./scripts/jquery/jquery-1.3.2.min.js
./scripts/jquery/jquery-ui-1.7.2.custom.min.js
./scripts/jquery/jquery.autocomplete.min.js

we have .js , .js.gzm  1.3.2, af few 1.7.2 's .... all over the archive.

I remember we decided that we would not do it this way? Please can we merge
to one consistent set of scripts, with the licenses checked of-course.....
And have some version info on come of the js files....

regards

Dannes




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

[Exist-development] Cocoon issue

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

Hi,

I found that the URL http://localhost:8080/exist/cocoon/xmldb/db/ does not
function anymore. In the logging I see lines like

*8090 [qtp181871104-20] WARN org.eclipse.jetty.util.log - Aliased resource:
file:/Users/wessels/Development/existdb/1.5/test-complete/webapp/sitemap.xmap~=file:/Users/wessels/Development/existdb/1.5/test-complete/webapp/sitemap.xmap

*I guess some recent changes caused this change in behaviour.....

D.

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