Re: [Exist-open] does eXist remove xml declaration and doc-type declaration?

[Matteo C. <cat...@gm...>]

Ok, it seems a found a solution.
Before retrieving your Resource by yourCollection.getResource("id"),
give yourCollection.setProperty(EXistOutputKeys.OUTPUT_DOCTYPE, "yes");
and yourCollection.setProperty(OutputKeys.OMIT_XML_DECLARATION, "no");

Matteo

On Wed, Apr 11, 2012 at 11:07 PM, Matteo Catena <cat...@gm...>wrote:

> I've just downloaded and installed 2.0 (because i can't find 1.4.2 on the
> website, just 1.4.1). Uploading and downloading documents from the web
> interface works as expected (xml declaration and doctype declaration are
> preserved). However, the problem persist uploading and downloading
> resources from my java client (i'm using xmldb apis).
>
> Matteo
>
>
> On Wed, Apr 11, 2012 at 10:51 PM, Casey Jordan <cas...@jo...>wrote:
>
>> You should upgrade to 1.4.2 (Or latest 1.4.x release) there have been
>> many fixes from 1.4.0 to the most current 1.4 release.
>>
>> Make sure you completely backup your database, then restore it to the new
>> codebase as 1.4.0 and 1.4.2 use slightly different data storage models.
>>
>> Cheers,
>>
>> Casey
>>
>>
>>
>>
>> On Wed, Apr 11, 2012 at 4:31 PM, Matteo Catena <cat...@gm...>wrote:
>>
>>> eXist Version:1.4.0 eXist Build:20091111eXist Home:/opt/eXistSVN
>>> Revision:10440Operating System: Linux 2.6.32-40-generic amd64File
>>> encoding:UTF-8
>>>
>>> On Wed, Apr 11, 2012 at 10:26 PM, Casey Jordan <cas...@jo...>wrote:
>>>
>>>> What version of eXist are you using? Older versions did not always
>>>> preserve doctype declarations.
>>>>
>>>> I know that 1.4.x does, but perhaps this did not make it into trunk.
>>>> Dmitriy fixed this so perhaps he can comment further.
>>>>
>>>>
>>>> On Wed, Apr 11, 2012 at 4:14 PM, Matteo Catena <cat...@gm...
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>> i've loaded some xml files on eXist via the web interface. All of them
>>>>> had the xml declaration. Some of them have also a doc-type declaration.
>>>>> However, when i download those documents from the db, every declaration
>>>>> disappears. The same applies if i access eXist via a java client.
>>>>> Can I avoid this behaviour? I'd like to have my declarations when i
>>>>> retrive my documents.
>>>>>
>>>>> Thank you,
>>>>> Matteo
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Better than sec? Nothing is better than sec when it comes to
>>>>> monitoring Big Data applications. Try Boundary one-second
>>>>> resolution app monitoring today. Free.
>>>>> http://p.sf.net/sfu/Boundary-dev2dev
>>>>> _______________________________________________
>>>>> Exist-open mailing list
>>>>> Exi...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Casey Jordan
>>>> easyDITA a product of Jorsek LLC
>>>> "CaseyDJordan" on LinkedIn, Twitter & Facebook
>>>> (585) 348 7399
>>>> easydita.com
>>>>
>>>>
>>>> This message is intended only for the use of the Addressee(s) and may
>>>> contain information that is privileged, confidential, and/or exempt from
>>>> disclosure under applicable law.  If you are not the intended recipient,
>>>> please be advised that any disclosure  copying, distribution, or use of
>>>> the information contained herein is prohibited.  If you have received
>>>> this communication in error, please destroy all copies of the message,
>>>> whether in electronic or hard copy format, as well as attachments, and
>>>> immediately contact the sender by replying to this e-mail or by phone.
>>>> Thank you.
>>>>
>>>>
>>>
>>
>>
>> --
>> --
>> Casey Jordan
>> easyDITA a product of Jorsek LLC
>> "CaseyDJordan" on LinkedIn, Twitter & Facebook
>> (585) 348 7399
>> easydita.com
>>
>>
>> This message is intended only for the use of the Addressee(s) and may
>> contain information that is privileged, confidential, and/or exempt from
>> disclosure under applicable law.  If you are not the intended recipient,
>> please be advised that any disclosure  copying, distribution, or use of
>> the information contained herein is prohibited.  If you have received
>> this communication in error, please destroy all copies of the message,
>> whether in electronic or hard copy format, as well as attachments, and
>> immediately contact the sender by replying to this e-mail or by phone.
>> Thank you.
>>
>>
>