Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Adam Retter-7
Thats a very old build of eXist, even though it as listed as stable on
the webpage (although there is a health warning there as well).

I would recommend downloading the latest snapshot
(http://prdownloads.sourceforge.net/exist/eXist-snapshot-20050805.jar)
or building your own eXist from CVS (instructions are on the website).

Thanks Adam.

On Mon, 2005-09-19 at 16:54 +0100, Gareth Hall wrote:

>  Hi,
>  
> I am running eXist-1.0b2-build-1107. I am running the code below with
> Tomcat 5.5 and JRE 5.
>  
> I have a problem with documents appearing to be corrupted
> when retrieved using the following code: -
>  
>            // get root-collection
>             Collection col =
>                 DatabaseManager.getCollection(URI, username,
> password);
>             // get query-service
>             XPathQueryService service =
>                 (XPathQueryService)
> col.getService( "XPathQueryService", "1.0" );
>            
>             // set pretty-printing on
>             service.setProperty(OutputKeys.INDENT, "yes" );
>             service.setProperty(OutputKeys.ENCODING, encoding);
>            
>             // execute query and get results in ResourceSet
>             ResourceSet result = service.query(query);
>            
>             for ( int i = 0; i < (int) result.getSize(); i++ ) {
>  
>                 System.out.println((String)((XMLResource)
> result.getResource( (long) i)).getContent());  
>             }
>  
> When retrieving the XML document (which can be viewed via the Java
> client with no problems): -
>  
> <ADMIN id="1126626525826" created="13/09/2005 at 04:48" type="normal">
>     <NAME first="Gareth" family="Hall"/>
>     <EMAIL>[hidden email]</EMAIL>
>     <PASSWORD>f93fe2b182c016d7cb9b08981a3e26bc</PASSWORD>
> </ADMIN>
>  
> using the above code I running within Tomcat 5.5 I get the following
> output: -
>  
> <ADMIN id="1126626525826" created="13/09/2005 at 04:48"
> t??T??????(?????9♣5¶????
>
???↔????????????!??????(???☻♥?T?¶???v↨&WF??▬??♠▬66V?GW&R?6????T?¶???☻☻☻♥?♦§5
5t?$

> ??X?♫♫N♀XL?L????♂?►T????¤??♂?Q‼RS??
>  
> Does anybody have any idea why I am receiving this result?
>
> Thank you for your help.
>
> Gareth
>
> --
> Gareth Hall
> Mobile: +44 (0) 7971037081


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Gareth Hall
Hi,
 
I am not currently using this version - I am experiencing the issue with the latest build of exist. My point was that I do not experience this problem with version 0.9.
 
Another eXist user has advised me that he is experiencing the same problem and was unable to resolve the problem - he did however find out that there has to be a version
conflict between the xmldb.jar of eXist and the various versions of
cocoon.
 
Is this a possibility?
 
Gareth
 


 
On 9/19/05, Adam Retter <[hidden email]> wrote:
Thats a very old build of eXist, even though it as listed as stable on
the webpage (although there is a health warning there as well).

I would recommend downloading the latest snapshot
(http://prdownloads.sourceforge.net/exist/eXist-snapshot-20050805.jar)
or building your own eXist from CVS (instructions are on the website).

Thanks Adam.

On Mon, 2005-09-19 at 16:54 +0100, Gareth Hall wrote:
>  Hi,
>
> I am running eXist-1.0b2-build-1107. I am running the code below with
> Tomcat 5.5 and JRE 5.
>
> I have a problem with documents appearing to be corrupted

> when retrieved using the following code: -
>
>            // get root-collection
>             Collection col =
>                 DatabaseManager.getCollection(URI, username,
> password);
>             // get query-service
>             XPathQueryService service =
>                 (XPathQueryService)
> col.getService( "XPathQueryService", " 1.0" );
>
>             // set pretty-printing on
>             service.setProperty(OutputKeys.INDENT, "yes" );
>             service.setProperty(OutputKeys.ENCODING, encoding);
>
>             // execute query and get results in ResourceSet
>             ResourceSet result = service.query(query);
>
>             for ( int i = 0; i < (int) result.getSize(); i++ ) {
>
>                 System.out.println((String)((XMLResource)
> result.getResource( (long) i)).getContent());
>             }
>
> When retrieving the XML document (which can be viewed via the Java
> client with no problems): -
>
> <ADMIN id="1126626525826" created="13/09/2005 at 04:48" type="normal">
>     <NAME first="Gareth" family="Hall"/>
>     <EMAIL>[hidden email]</EMAIL>
>     <PASSWORD>f93fe2b182c016d7cb9b08981a3e26bc</PASSWORD>
> </ADMIN>
>
> using the above code I running within Tomcat 5.5 I get the following
> output: -
>
> <ADMIN id="1126626525826" created="13/09/2005 at 04:48"
> t??T??????(?????9♣5¶????
>
???↔????????????!??????(???☻♥?T?¶???v↨&WF??▬??♠▬66V?GW&R?6????T?¶???☻☻☻♥?♦§5
5t?$

> ??X?♫♫N♀XL?L????♂?►T????¤??♂?Q‼RS??
>
> Does anybody have any idea why I am receiving this result?
>
> Thank you for your help.
>
> Gareth
>
> --
> Gareth Hall
> Mobile: +44 (0) 7971037081



--
Gareth Hall
Mobile: +44 (0) 7971037081
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Michael Beddow-2
Gareth Hall wrote:

>  Another eXist user has advised me that he is experiencing the same
problem
> and was unable to resolve the problem - he did however find out that there
> has to be a version
> conflict between the xmldb.jar of eXist and the various versions of
> cocoon.
>  Is this a possibility?

Given that you say you do not see the problem when accessing the same data
via the Java client, I would say some sort of encoding-related conflict or
mismatch with Cocoon (or, less likely, Tomcat) is more or less a certainty.

It may be something that can be resolved by changing Cocoon or Tomcat
configuration settings, rather than a full-blown version conflict.

If you deploy a recent complete eXist build (i.e. using Cocoon and servlet
exactly as shipped in the eXist install package, rather than your existing
ones) do you get the same corruption when you run your code? If you do, we
may need to see a sample of your data, if there are no confidentiality
issues. If you don't, you will need to take a look at what exactly is in the
classpaths of the two installations, as well as inspecting all
encoding-related config and property settings, including default and
user-specified locales.

Beyond that I'm afraid I have no suggestions, because as I've said here
before, I gave up on Cocoon some time ago because of repeated (and sometimes
regressive) encoding problems (not just with eXist).

Michael Beddow



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Wolfgang Meier-2
> > and was unable to resolve the problem - he did however find out that
> > there has to be a version
> > conflict between the xmldb.jar of eXist and the various versions of
> > cocoon.

I remember someone else posted this kind of error some time ago, but I can't
find the message in the archive. Anyway, the hint about xmldb.jar is correct:
eXist uses a cvs build of the xmldb library. Please remove the xmldb jars
that come with cocoon and use only eXist's xmldb.jar instead.

Wolfgang


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Gareth Hall
I have now installed the latest possible CVS version of eXist ( eXist-20050805). I have replaced all JAR files where applicable with the JAR files distributed with the latest version of eXist.
 
I am still experiencing the same encoding issue.
 
To be clear - I'm running my application from within Tomcat 5.5.
 
The XML stored in the exist is:
 
<?xml version="1.0" encoding="UTF-8"?>
<ADMIN id="1127228503375" created="20/09/2005 at 04:01" type="normal">
    <NAME first="Gareth" family="Hall"/>
    <EMAIL>[hidden email]</EMAIL>
    <PASSWORD>f93fe2b182c016d7cb9b08981a3e26bc</PASSWORD>
</ADMIN>
 
The result of retrieving this document from eXist using a class executing within Tomcat is: -
 
<ADMIN id="1127228503375" created="20/09/2005 at 04:01" t??T??????(?????9♣5¶????
???↔????????????!??????(???☻♥?T?¶???v↨&WF??▬??♠▬66V?GW&R?6????T?¶???☻☻☻♥?♦§55t?$
??X?♫♫N♀XL?L????♂?►T????☼??♂?Q‼RS??
 
I've no idea how to progress this so any other thoughts or ideas would be very much appreciated.
 
Gareth
 
 


 
On 9/20/05, Gareth Hall <[hidden email]> wrote:
I have replaced all occurences of the xmldb.jar file within my Tomcat installation with the version distributed with eXist.
 
This has not resolved the issue.
 
I do not understand why I don't see this issue with version 0.9 of exist running with the same version of Tomcat.


 
On 9/20/05, Wolfgang Meier <[hidden email]> wrote:
> > and was unable to resolve the problem - he did however find out that
> > there has to be a version
> > conflict between the xmldb.jar of eXist and the various versions of
> > cocoon.

I remember someone else posted this kind of error some time ago, but I can't
find the message in the archive. Anyway, the hint about xmldb.jar is correct:
eXist uses a cvs build of the xmldb library. Please remove the xmldb jars
that come with cocoon and use only eXist's xmldb.jar instead.

Wolfgang


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://sourceforge.net/geronimo.php" target="_blank">http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://lists.sourceforge.net/lists/listinfo/exist-open" target="_blank"> https://lists.sourceforge.net/lists/listinfo/exist-open



--

Gareth Hall
Mobile: +44 (0) 7971037081



--
Gareth Hall
Mobile: +44 (0) 7971037081
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

golgoth14@nonlimit.ch
Hi,
   
    Do you dump the content of the data into a tomcat log file or into a
console (Eclipse or JBuilder)  ?

    In debug mode, try this and put a breakpoint in this line :
   
    String content = (String)((XMLResource) result.getResource((long)
i)).getContent();
   
    Next, watch the content data and try to copy/paste into an editor
(like crimson).

    In java, all strings are in Unicode. If eXist works correctly, the
"content" variable must contains the right data.
   


Gareth Hall wrote:

> I have now installed the latest possible CVS version of eXist
> ( eXist-20050805). I have replaced all JAR files where applicable with
> the JAR files distributed with the latest version of eXist.
>  
> I am still experiencing the same encoding issue.
>  
> To be clear - I'm running my application from within Tomcat 5.5.
>  
> The XML stored in the exist is:
>  
> <?xml version="1.0" encoding="UTF-8"?>
> <ADMIN id="1127228503375" created="20/09/2005 at 04:01" type="normal">
>     <NAME first="Gareth" family="Hall"/>
>     <EMAIL>[hidden email] <mailto:[hidden email]></EMAIL>
>     <PASSWORD>f93fe2b182c016d7cb9b08981a3e26bc</PASSWORD>
> </ADMIN>
>  
> The result of retrieving this document from eXist using a class
> executing within Tomcat is: -
>  
> <ADMIN id="1127228503375" created="20/09/2005 at 04:01"
> t??T??????(?????9♣5¶????
> ???↔????????????!??????(???☻♥?T?¶???v↨&WF??▬??♠▬66V?GW&R?6????T?¶???☻☻☻♥?♦§55t?$
> ??X?♫♫N♀XL?L????♂?►T????☼??♂?Q‼RS??
>  
> I've no idea how to progress this so any other thoughts or ideas would
> be very much appreciated.
>  
> Gareth
>  
>  
>
>
>  
> On 9/20/05, *Gareth Hall* <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     I have replaced all occurences of the xmldb.jar file within my
>     Tomcat installation with the version distributed with eXist.
>      
>     This has not resolved the issue.
>      
>     I do not understand why I don't see this issue with version 0.9 of
>     exist running with the same version of Tomcat.
>
>
>      
>     On 9/20/05, *Wolfgang Meier* <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>> > and was unable to resolve the problem - he did however find
>         out that
>> > there has to be a version
>> > conflict between the xmldb.jar of eXist and the various
>         versions of
>> > cocoon.
>
>         I remember someone else posted this kind of error some time
>         ago, but I can't
>         find the message in the archive. Anyway, the hint about
>         xmldb.jar is correct:
>         eXist uses a cvs build of the xmldb library. Please remove the
>         xmldb jars
>         that come with cocoon and use only eXist's xmldb.jar instead.
>
>         Wolfgang
>
>
>         -------------------------------------------------------
>         SF.Net email is sponsored by:
>         Tame your development challenges with Apache's Geronimo App
>         Server. Download
>         it for free - -and be entered to win a 42" plasma tv or your
>         very own
>         Sony(tm)PSP.  Click here to play:
>         http://sourceforge.net/geronimo.php
>         _______________________________________________
>         Exist-open mailing list
>         [hidden email]
>         <mailto:[hidden email]>
>         https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
>
>     --
>
>     Gareth Hall
>     Mobile: +44 (0) 7971037081
>
>
>
>
> --
> Gareth Hall
> Mobile: +44 (0) 7971037081




-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

wolfgangmm
Hi,

If nothing else helps, it would be nice if you could prepare a short
example class or test with which we can reproduce the problem. I never
saw this strange error myself. It looks like the serializer is running
out of bounds somehow.

>     <EMAIL>[hidden email] <mailto:[hidden email]></EMAIL>

Btw, the above is illegal. The < should be replaced by &lt;. The
parser should complain about this.

Wolfgang


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Gareth Hall
In reply to this post by golgoth14@nonlimit.ch
I've run the code in Debug mode (using Netbeans) and get the following: -
 
"<ADMIN id=\"1127228503375\" created=\"20/09/2005 at 04:01\" t��T􉹽ɵ����(�����95��������ɕѠ���������!������(����T����v&WF����66V�GW&R�6����T�����55t�$C�َLٙL��N\f��\fM�\r�؎X�N\fXL�L���� �T���ԑ�� �QRS��
 
I was previously outputting to the Tomcat console.
 


 
On 9/20/05, Golgoth 14 <[hidden email]> wrote:
Hi,

   Do you dump the content of the data into a tomcat log file or into a
console (Eclipse or JBuilder)  ?

   In debug mode, try this and put a breakpoint in this line :

   String content = (String)((XMLResource) result.getResource((long)
i)).getContent();

   Next, watch the content data and try to copy/paste into an editor
(like crimson).

   In java, all strings are in Unicode. If eXist works correctly, the
"content" variable must contains the right data.



Gareth Hall wrote:

> I have now installed the latest possible CVS version of eXist
> ( eXist-20050805). I have replaced all JAR files where applicable with
> the JAR files distributed with the latest version of eXist.
>
> I am still experiencing the same encoding issue.
>
> To be clear - I'm running my application from within Tomcat 5.5.

>
> The XML stored in the exist is:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ADMIN id="1127228503375" created="20/09/2005 at 04:01" type="normal">
>     <NAME first="Gareth" family="Hall"/>
>     <EMAIL>[hidden email] <mailto:[hidden email]></EMAIL>
>     <PASSWORD>f93fe2b182c016d7cb9b08981a3e26bc</PASSWORD>
> </ADMIN>
>
> The result of retrieving this document from eXist using a class
> executing within Tomcat is: -
>
> <ADMIN id="1127228503375" created="20/09/2005 at 04:01"
> t??T??????(?????9♣5¶????
> ???↔????????????!??????(???☻♥?T?¶???v↨&WF??▬??♠▬66V?GW&R?6????T?¶???☻☻☻♥?♦§55t?$
> ??X?♫♫N♀XL?L????♂?►T????☼??♂?Q‼RS??
>
> I've no idea how to progress this so any other thoughts or ideas would
> be very much appreciated.
>
> Gareth
>
>
>
>
>

> On 9/20/05, *Gareth Hall* <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     I have replaced all occurences of the xmldb.jar file within my
>     Tomcat installation with the version distributed with eXist.
>
>     This has not resolved the issue.
>
>     I do not understand why I don't see this issue with version 0.9 of
>     exist running with the same version of Tomcat.
>
>
>
>     On 9/20/05, *Wolfgang Meier* <[hidden email]
>     <mailto: [hidden email]>> wrote:
>
>> > and was unable to resolve the problem - he did however find
>         out that
>> > there has to be a version
>> > conflict between the xmldb.jar of eXist and the various
>         versions of
>> > cocoon.
>
>         I remember someone else posted this kind of error some time
>         ago, but I can't
>         find the message in the archive. Anyway, the hint about
>         xmldb.jar is correct:
>         eXist uses a cvs build of the xmldb library. Please remove the
>         xmldb jars
>         that come with cocoon and use only eXist's xmldb.jar instead.
>
>         Wolfgang
>
>
>         -------------------------------------------------------
>         SF.Net email is sponsored by:
>         Tame your development challenges with Apache's Geronimo App
>         Server. Download
>         it for free - -and be entered to win a 42" plasma tv or your
>         very own
>         Sony(tm)PSP.  Click here to play:
>         http://sourceforge.net/geronimo.php
>         _______________________________________________
>         Exist-open mailing list
>         [hidden email]
>         <mailto:[hidden email]>
>         https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
>
>     --
>
>     Gareth Hall
>     Mobile: +44 (0) 7971037081
>
>
>
>
> --
> Gareth Hall
> Mobile: +44 (0) 7971037081





--
Gareth Hall
Mobile: +44 (0) 7971037081
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Michael Beddow-2


> I've run the code in Debug mode (using Netbeans) and get the following: -
>  "<ADMIN id=\"1127228503375\" created=\"20/09/2005 at 04:01\"
>
t��T􉹽ɵ����(�����95��������ɕѠ���������!������(����T����v&WF����66V
�GW&R�6����T�����55t�$C�َLٙL��N\f��\fM�\r�؎X�N\fXL�L����
> �T���ԑ�� �QRS��
>  I was previously outputting to the Tomcat console.

Now that we've seen your source data, this doesn't look like an encoding
error after all. I'd say something was going wrong at a pretty low level.
You seem to be being handed a buffer which has been partly populated from
the wrong area of memory altogether. Reminds me more of  C debugging output
than Java.

Since you get the correct behaviour with the Java client, I'm not confident
the problem will be reproducible on other setups, but obviously it's worth a
try.

Michael Beddow





-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

golgoth14@nonlimit.ch
In reply to this post by Gareth Hall
Could you certify your source XML file is really in UTF-8 encoding ?

To do that, open your file with Crimson Editor and use the menu
"Document -> Encoding Type".
Try all the encoding and check the result.


Gareth Hall wrote:

> I've run the code in Debug mode (using Netbeans) and get the following: -
>  
> "<ADMIN id=\"1127228503375\" created=\"20/09/2005 at
> 04:01\"
> t��T􉹽ɵ����(�����95��������ɕѠ���������!������(����T����v&WF����66V�GW&R�6����T�����55t�$C�َLٙL��N\f��\fM�\r�؎X�N\fXL�L����
> �T���ԑ�� �QRS��
>  
> I was previously outputting to the Tomcat console.
>  
>
>
>  
> On 9/20/05, *Golgoth 14* <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Hi,
>
>        Do you dump the content of the data into a tomcat log file or
>     into a
>     console (Eclipse or JBuilder)  ?
>
>        In debug mode, try this and put a breakpoint in this line :
>
>        String content = (String)((XMLResource) result.getResource((long)
>     i)).getContent();
>
>        Next, watch the content data and try to copy/paste into an editor
>     (like crimson).
>
>        In java, all strings are in Unicode. If eXist works correctly, the
>     "content" variable must contains the right data.
>
>
>
>     Gareth Hall wrote:
>
>     > I have now installed the latest possible CVS version of eXist
>     > ( eXist-20050805). I have replaced all JAR files where
>     applicable with
>     > the JAR files distributed with the latest version of eXist.
>     >
>     > I am still experiencing the same encoding issue.
>     >
>     > To be clear - I'm running my application from within Tomcat 5.5.
>     >
>     > The XML stored in the exist is:
>     >
>     > <?xml version="1.0" encoding="UTF-8"?>
>     > <ADMIN id="1127228503375" created="20/09/2005 at 04:01"
>     type="normal">
>     >     <NAME first="Gareth" family="Hall"/>
>     >     <EMAIL>[hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email] <mailto:[hidden email]>></EMAIL>
>     >     <PASSWORD>f93fe2b182c016d7cb9b08981a3e26bc</PASSWORD>
>     > </ADMIN>
>     >
>     > The result of retrieving this document from eXist using a class
>     > executing within Tomcat is: -
>     >
>     > <ADMIN id="1127228503375" created="20/09/2005 at 04:01"
>     > t??T??????(?????9♣5¶????
>     >
>     ???↔????????????!??????(???☻♥?T?¶???v↨&WF??▬??♠▬66V?GW&R?6????T?¶???☻☻☻♥?♦§55t?$
>
>     > ??X?♫♫N♀XL?L????♂?►T????☼??♂?Q‼RS??
>     >
>     > I've no idea how to progress this so any other thoughts or ideas
>     would
>     > be very much appreciated.
>     >
>     > Gareth
>     >
>     >
>     >
>     >
>     >
>     > On 9/20/05, *Gareth Hall* <[hidden email]
>     <mailto:[hidden email]>
>     > <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>     >
>     >     I have replaced all occurences of the xmldb.jar file within my
>     >     Tomcat installation with the version distributed with eXist.
>     >
>     >     This has not resolved the issue.
>     >
>     >     I do not understand why I don't see this issue with version
>     0.9 of
>     >     exist running with the same version of Tomcat.
>     >
>     >
>     >
>     >     On 9/20/05, *Wolfgang Meier* <[hidden email]
>     <mailto:[hidden email]>
>     >     <mailto: [hidden email]
>     <mailto:[hidden email]>>> wrote:
>     >
>     >> > and was unable to resolve the problem - he did however find
>     >         out that
>     >> > there has to be a version
>     >> > conflict between the xmldb.jar of eXist and the various
>     >         versions of
>     >> > cocoon.
>     >
>     >         I remember someone else posted this kind of error some time
>     >         ago, but I can't
>     >         find the message in the archive. Anyway, the hint about
>     >         xmldb.jar is correct:
>     >         eXist uses a cvs build of the xmldb library. Please
>     remove the
>     >         xmldb jars
>     >         that come with cocoon and use only eXist's xmldb.jar
>     instead.
>     >
>     >         Wolfgang
>     >
>     >
>     >         -------------------------------------------------------
>     >         SF.Net email is sponsored by:
>     >         Tame your development challenges with Apache's Geronimo App
>     >         Server. Download
>     >         it for free - -and be entered to win a 42" plasma tv or your
>     >         very own
>     >         Sony(tm)PSP.  Click here to play:
>     >         http://sourceforge.net/geronimo.php
>     >         _______________________________________________
>     >         Exist-open mailing list
>     >         [hidden email]
>     <mailto:[hidden email]>
>     >         <mailto:[hidden email]
>     <mailto:[hidden email]>>
>     >         https://lists.sourceforge.net/lists/listinfo/exist-open
>     <https://lists.sourceforge.net/lists/listinfo/exist-open>
>     >
>     >
>     >
>     >
>     >     --
>     >
>     >     Gareth Hall
>     >     Mobile: +44 (0) 7971037081
>     >
>     >
>     >
>     >
>     > --
>     > Gareth Hall
>     > Mobile: +44 (0) 7971037081
>
>
>
>
>
> --
> Gareth Hall
> Mobile: +44 (0) 7971037081




-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Michael Beddow-2
> Could you certify your source XML file is really in UTF-8 encoding ?

Gareth assured us right at the start that he can retrieve this file
uncorrupted via the Java client (and that he can retrieve it via his app in
older eXist builds). So the data itself is OK. And comparing that data, now
weve seen it in Gareth's source, with the garbage returned reveals none of
classical symptoms of  encoding errors. In particular, the garbage values
seem to begin at an arbitrary point in a thus far intact string. That's why
I think we need to look for something at a much lower level, involving
buffer addressing

Michael Beddow



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Gareth Hall
Further to your previous mail regarding writing a class to demonstrate this behaviour - is this worth pursuing given that I would expect to the same behaviour as with the Java client in an independent class that I had written.
 
I would expect the only way to replicate this issue is run the code within Tomcat.

Any suggestions on how I can help the resolution?
 
Is it of any significance that if I run the exact same code within the same version of Tomcat against eXist 0.9 I do not experience this problem?
 

 
On 9/21/05, Michael Beddow <[hidden email]> wrote:
> Could you certify your source XML file is really in UTF-8 encoding ?

Gareth assured us right at the start that he can retrieve this file
uncorrupted via the Java client (and that he can retrieve it via his app in
older eXist builds). So the data itself is OK. And comparing that data, now
weve seen it in Gareth's source, with the garbage returned reveals none of
classical symptoms of  encoding errors. In particular, the garbage values
seem to begin at an arbitrary point in a thus far intact string. That's why
I think we need to look for something at a much lower level, involving
buffer addressing

Michael Beddow



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open



--
Gareth Hall
Mobile: +44 (0) 7971037081
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Gareth Hall
I do not experience this problem when executing a stand-alone class.

The only way of replicating this is to run my class within a servlet engine.

Rgrds,
Gareth

On 9/21/05, Gareth Hall <[hidden email]> wrote:
Further to your previous mail regarding writing a class to demonstrate this behaviour - is this worth pursuing given that I would expect to the same behaviour as with the Java client in an independent class that I had written.
 
I would expect the only way to replicate this issue is run the code within Tomcat.

Any suggestions on how I can help the resolution?
 
Is it of any significance that if I run the exact same code within the same version of Tomcat against eXist 0.9 I do not experience this problem?
 

 
On 9/21/05, Michael Beddow <[hidden email]> wrote:
> Could you certify your source XML file is really in UTF-8 encoding ?

Gareth assured us right at the start that he can retrieve this file
uncorrupted via the Java client (and that he can retrieve it via his app in
older eXist builds). So the data itself is OK. And comparing that data, now
weve seen it in Gareth's source, with the garbage returned reveals none of
classical symptoms of  encoding errors. In particular, the garbage values
seem to begin at an arbitrary point in a thus far intact string. That's why
I think we need to look for something at a much lower level, involving
buffer addressing

Michael Beddow



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: <a href="http://sourceforge.net/geronimo.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
<a href="https://lists.sourceforge.net/lists/listinfo/exist-open" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> https://lists.sourceforge.net/lists/listinfo/exist-open



--

Gareth Hall
Mobile: +44 (0) 7971037081



--
Gareth Hall
Mobile: +44 (0) 7971037081
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Gareth Hall
This is clearly a bug - a bug which I believe exists with eXist as this issue only begins to appear in more recent versions of eXist.

Please can you advise how I raise this bug for someone to investigate?

Thank you,
Gareth

On 9/23/05, Gareth Hall <[hidden email]> wrote:
I do not experience this problem when executing a stand-alone class.

The only way of replicating this is to run my class within a servlet engine.

Rgrds,
Gareth


On 9/21/05, Gareth Hall <[hidden email]> wrote:
Further to your previous mail regarding writing a class to demonstrate this behaviour - is this worth pursuing given that I would expect to the same behaviour as with the Java client in an independent class that I had written.
 
I would expect the only way to replicate this issue is run the code within Tomcat.

Any suggestions on how I can help the resolution?
 
Is it of any significance that if I run the exact same code within the same version of Tomcat against eXist 0.9 I do not experience this problem?
 

 
On 9/21/05, Michael Beddow <[hidden email]> wrote:
> Could you certify your source XML file is really in UTF-8 encoding ?

Gareth assured us right at the start that he can retrieve this file
uncorrupted via the Java client (and that he can retrieve it via his app in
older eXist builds). So the data itself is OK. And comparing that data, now
weve seen it in Gareth's source, with the garbage returned reveals none of
classical symptoms of  encoding errors. In particular, the garbage values
seem to begin at an arbitrary point in a thus far intact string. That's why
I think we need to look for something at a much lower level, involving
buffer addressing

Michael Beddow



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: <a href="http://sourceforge.net/geronimo.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
<a href="https://lists.sourceforge.net/lists/listinfo/exist-open" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> https://lists.sourceforge.net/lists/listinfo/exist-open



--

Gareth Hall
Mobile: +44 (0) 7971037081



--
Gareth Hall
Mobile: +44 (0) 7971037081



--
Gareth Hall
Mobile: +44 (0) 7971037081
Reply | Threaded
Open this post in threaded view
|

Re: eXist-1.0b2-build-1107 - XML corruption whenretr ieving XML documents

Michael Beddow-2
Gareth Hall wrote:

> This is clearly a bug - a bug which I believe exists with eXist as this
> issue only begins to appear in more recent versions of eXist.

> Please can you advise how I raise this bug for someone to investigate?

Wolfgang has already taken note of this (it was his suggestion that you
produce a test class that would reproduce it, not mine, though I expect he
will have seen the point of your reponse that you see this only when running
within Tomcat).

But it can't be investigated until you can provide some means by which it
can be reproduced, since no-one else has reported anything like it, although
a lot of users run eXist code under Tomcat (the other apparently similar
instances you have found seem to have been encoding issues, but yours almost
certainly isn't)

What I actually suggested is that you do a sandboxed install of a fresh
eXist build and test your code under Tomcat running within that sandbox,
rather than deploying eXist within your production servlet. If the same
symptoms occur in that sandbox, it will be easy for others to reproduce and
investigate. If they don't, you will need to scrutinize the contents of the
two classpaths in search of differences that could account for the problem.

Michael Beddow



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open