Dannes Wessels | 1 Jan 2008 12:04
Picon

Re: XQuery Update and Schema Validation

Hi,

On Dec 31, 2007 9:45 PM, scltul <scltul <at> yahoo.com> wrote:
> Is there a way to make an XQuery Update validate against the XML document
> being modified?
>
> Parsing an XML document causes validation, but an <update insert> into the
> same document using the XQuery Update mechanism can be done without
> constraint.

I think of two things..... using a 'trigger' and using the
xml-validation extension functions.

Not sure how to combine however........

D.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Andrzej Jan Taramina | 1 Jan 2008 18:34

dist-war target dependencies changed?

Hey Dizzz....

I just noticed that you changed how the dist-war target works a bit over a 
week ago.

What's the rationale behind not doing a compile?  You can't generate the jar 
files if you don't have the classes compiled, so it would seem to me that 
dist-war should still depend on a compile step.

I typically do clean rebuilds with the following sequence of the following 
targets:

	clean
 	prepare-extensions
     dist-war

But now with your changes of 12/20, nothing gets compiled.

Are you sure this is a good approach?  Sounds broken to me...

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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
(Continue reading)

Dannes Wessels | 1 Jan 2008 19:08
Picon

Re: dist-war target dependencies changed?

Hi,

well the problem was; when the jars were signed, one could not
generate the war files any more because in this scenario the exist*jar
files would be signed using a different certificate.

'dist-war' has been changed in such a way that it actually only wraps
existing jar files into the war file.

it would be then:

clean
all
prepare-extensions ==> for what? all does everything
dist-war

regards

Dannes

On Jan 1, 2008 6:34 PM, Andrzej Jan Taramina <andrzej <at> chaeron.com> wrote:
> Hey Dizzz....
>
> I just noticed that you changed how the dist-war target works a bit over a
> week ago.
>
> What's the rationale behind not doing a compile?  You can't generate the jar
> files if you don't have the classes compiled, so it would seem to me that
> dist-war should still depend on a compile step.
>
(Continue reading)

Andrzej Jan Taramina | 1 Jan 2008 20:04

Re: dist-war target dependencies changed?

> well the problem was; when the jars were signed, one could not
> generate the war files any more because in this scenario the exist*jar
> files would be signed using a different certificate.
> 
> 'dist-war' has been changed in such a way that it actually only wraps
> existing jar files into the war file.
> 
> it would be then:
> 
> clean
> all
> prepare-extensions ==> for what? all does everything
> dist-war

Can't remember why I always had to do the prep-ext....if it's automatic with 
all then no biggie.

The problem I see with this approach is that dist-war will generate a bad war 
file if you don't do an all ahead of time.  That is a classic case where you 
should have a dependency so that doing dist-war will generate anything it 
needs that is not already there.  If the jars don't exist then dist-war 
should generate them.  That is good practice with ant.

So why wouldn't you make dist-war dependent on all?  If the compiled classes 
are all up to date and all the jars are already there, then it shouldn't re-
gen/re-sign them, if the ant build scripts are constructed properly.

And if the dependencies are not handled well in "all", and some stuff is re-
generated, so be it...that just wastes a bit of processing time during the 
build of the war, but will guarantee that you always get a runnable war file.
(Continue reading)

gonzberg | 2 Jan 2008 15:15
Picon
Picon

local exist homepage: SAXParseException

Hello everybody,
I just tried to visit the exist homepage on my server (www.myserver.org:8181/exist) and I get the
following exception:

org.apache.cocoon.ProcessingException: Error executing pipeline.:
http://www.w3.org/TR/html4/loose.dtd:31:3:org.xml.sax.SAXParseException: The declaration for
the entity "HTML.Version" must end with '>'.

How can I fix this? I use exist-1.0.

Thanks, G
--

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Dannes Wessels | 2 Jan 2008 17:22
Picon

Re: local exist homepage: SAXParseException

Hi,

On Jan 2, 2008 3:15 PM,  <gonzberg <at> gmx.de> wrote:
> org.apache.cocoon.ProcessingException: Error executing pipeline.:
http://www.w3.org/TR/html4/loose.dtd:31:3:org.xml.sax.SAXParseException: The declaration for
the entity "HTML.Version" must end with '>'.

> How can I fix this? I use exist-1.0.

My suggestion is to revert all changes you made in you local eXist-db
install, because it used to work, right? I think there is a change in
index.xml ....

When you did not change anything.... which version of exist are your
running (1.0.?)? Executed as War? Installed using Jar installer?

regards

Dannes

--

-- 
# Dannes Wessels # The Netherlands #

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
ooly | 3 Jan 2008 12:16
Picon
Favicon

Parentheses error in collection or resource's name

Hi i've a big problem using eXists: if i search to make access on collection or resources containing one or more parentheses, this access fail (i.e. the resource name is AER(EL).ABCDEF) if i try to access with web address: http://localhost:8080/exist/rest//db/mydatabase/ab/AER(EL).ABCDEF i receive the error: HTTP ERROR: 404 Document //db/mydatabase/ab/AER(EL).ABCDEF not found RequestURI=/exist/rest//db/mydatabase/ab/AER%28EL%29.ABCDEF Powered by Jetty:// if i try access to other resorce like AER.ABCDEF (http://localhost:8080/exist/rest//db/mydatabase/ab/AER.ABCDEF) work well. ) Thanks for your support Regards Michele

View this message in context: Parentheses error in collection or resource's name
Sent from the exist-open mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Exist-open mailing list
Exist-open <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/exist-open
Dannes Wessels | 3 Jan 2008 14:12
Picon

Re: Parentheses error in collection or resource's name

On Jan 3, 2008 12:16 PM, ooly <ooly <at> interfree.it> wrote:
> collection or resources containing one or more parentheses, this access fail
> (i.e. the resource name is AER(EL).ABCDEF) if i try to access with web
> address: http://localhost:8080/exist/rest//db/mydatabase/ab/AER(EL).ABCDEF i
> receive the error: HTTP ERROR: 404 Document

a related issue has been tackled in 1.1.2dev ; see
http://sourceforge.net/tracker/index.php?func=detail&aid=1757796&group_id=17691&atid=117691
I guess ( and ) are no valid characters on a Uri, these should be escaped?.

regards

Dannes

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
gonzberg | 3 Jan 2008 15:56
Picon
Picon

Re: local exist homepage: SAXParseException

hi dannes,
right, it used to work. I did not change anything and the error occurs on two servers. I installed exist with
the .jar installer (long time ago...)

I assume the problem is that I run an outdated version of exist.
eXist Version:  1.0-dev
eXist Build: 	20060321

I think I can fix it by installing a newer version, but I hesitate to install another version if it's not
necessary. I just though there could be a quick fix..

Thanks, gonzberg

-------- Original-Nachricht --------
> Datum: Wed, 2 Jan 2008 17:22:32 +0100
> Von: "Dannes Wessels" <dizzzz <at> gmail.com>
> An: gonzberg <at> gmx.de
> CC: exist-open <at> lists.sourceforge.net
> Betreff: Re: [Exist-open] local exist homepage: SAXParseException

> Hi,
> 
> On Jan 2, 2008 3:15 PM,  <gonzberg <at> gmx.de> wrote:
> > org.apache.cocoon.ProcessingException: Error executing pipeline.:
> http://www.w3.org/TR/html4/loose.dtd:31:3:org.xml.sax.SAXParseException: The
> declaration for the entity "HTML.Version" must end with '>'.
> 
> > How can I fix this? I use exist-1.0.
> 
> My suggestion is to revert all changes you made in you local eXist-db
> install, because it used to work, right? I think there is a change in
> index.xml ....
> 
> When you did not change anything.... which version of exist are your
> running (1.0.?)? Executed as War? Installed using Jar installer?
> 
> regards
> 
> Dannes
> 
> -- 
> # Dannes Wessels # The Netherlands #

--

-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Dannes Wessels | 3 Jan 2008 19:10
Picon

Re: local exist homepage: SAXParseException

Hi,

On Jan 3, 2008 3:56 PM,  <gonzberg <at> gmx.de> wrote:
> I think I can fix it by installing a newer version, but I hesitate to install another version if it's not necessary.
> I just though there could be a quick fix..

hmmm can you indicate since when this problem occurs? Maybe there is a
relation ship with our wiki, or basically the change there.

Installing a new version would be truly a good option but........
there is a good chance that you'll need to change your queries as
well, since eXist-db has become significantly more strict.....

regards

Dannes

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Gmane