Hi Bart, I am using version 1.2.13. After your question I switched to version 1.2.15.1 and I tried the same store action with the XML file containing the .dtd file.
Guess what: you're right. No complaints about the XML structure now. Very helpful; thanks. By the way, where can I take a look at the defined extractors you're talking about? Sooner or later I will need to define my own extractor for the specified XML file. Regards, Yomo On Thu, Jun 19, 2008 at 2:02 PM, Bart van der Schans <[EMAIL PROTECTED]> wrote: > Hi Yomo, > > Which version of the repository are you using? Iirc I have disabled dtd > checking in most extractors. The log message is a bit deceptive. the problem > you encounter is that the repository cannot find the specified DTD. > > Regards, > bart > > > > Yomo Guiamo wrote: > >> Hello Bart & Jeroen, >> >> Thank you for your replies. >> >> The problem is solved. The roadmap to the solution was to look at the log >> files, in particular the slide log file. >> >> The slide log shows: >> WARN 2008-06-19 13:44:01 [fortress.slide.domain] Exception while >> parsing content. XML document must be wellformed. >> >> Although many XML tool programs determined that my XML file was valid and >> well-formed, a line in my XML that said: >> <!DOCTYPE MyMessage SYSTEM "products.dtd"> >> >> caused the error in the slide log file for the Hippo Repo, therefore >> resulting in a 406 HTTP Status code. By the way, I wasn't using an empty >> XML >> file. >> >> When I removed this particular .dtd line, the Hippo Repo accepted my XML >> file. >> >> Although I'm happy with the final result, I do wonder why a general valid >> and well-formed XML - with a .dtd line - isn't accepted by Hippo. >> >> Thanks. >> >> >> >> >> On Thu, Jun 19, 2008 at 12:52 PM, Jeroen Reijn <[EMAIL PROTECTED]> >> wrote: >> >> > The XML can't be empty upon creation. That's what's causing the error. >> > >> > Regards, >> > >> > Jeroen >> > >> > On Thu, 2008-06-19 at 12:27 +0200, Bart van der Schans wrote: >> > > Hi Yomo, >> > > >> > > It is not a limitation. Probably the xml file triggers an extractor >> > > which fails. Did you look in the repository logs for any errors? >> > > >> > > Regards, >> > > >> > > Bart >> > > >> > > Yomo Guiamo wrote: >> > > > Hello, >> > > > >> > > > As I was trying to store a valid XML document onto a Hippo >> repository >> > > > (through a Java Class or directly on the Repository itself with vi) >> I >> > > > encountered a rather unexpected problem. For some reason it's not >> > possible >> > > > to create a new .xml file on the Hippo Repository in the >> > > > files/default.preview/content/documents even if you create your own >> > folder >> > > > (collection) in either the content or the documents folder. >> > > > >> > > > The workaround I used was to create a .html with the XML contents >> in >> > that >> > > > .html file and then rename it to a .xml file. Weird eh? >> > > > >> > > > My question is: what is the reason for this limitation? The >> limitation >> > for >> > > > directly creating.xml files is the case in the 'files' directory >> and >> > its >> > > > subdirectories (other dirs like 'history' and 'workingresource' >> face >> > the >> > > > same problem). Should one set specific properties first when >> trying to >> > > > create a .xml file on the repository - through the commandline or a >> > Java >> > > > Class - or is something else going on? >> > > > >> > > > I access the repository with the root account by the way. >> > > > >> > > > Regards, >> > > > Yomo >> > > > ******************************************** >> > > > Hippocms-dev: Hippo CMS development public mailinglist >> > > > >> > > > Searchable archives can be found at: >> > > > <a href="http://hippocms-dev.markmail.org/";>MarkMail</a> and <a >> > > > href="http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>. >> > > > >> > > >> > > >> > ******************************************** >> > Hippocms-dev: Hippo CMS development public mailinglist >> > >> > Searchable archives can be found at: >> > <a href="http://hippocms-dev.markmail.org/";>MarkMail</a> and <a href=" >> > http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>. >> > >> > >> ******************************************** >> Hippocms-dev: Hippo CMS development public mailinglist >> >> Searchable archives can be found at: >> <a href="http://hippocms-dev.markmail.org/";>MarkMail</a> and <a >> href="http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>. >> >> > > -- > Hippo B.V. - Amsterdam > Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 > > Hippo USA Inc. - San Francisco > 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 > ----------------------------------------------------------------- > http://www.onehippo.com - [EMAIL PROTECTED] > ----------------------------------------------------------------- > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > <a href="http://hippocms-dev.markmail.org/";>MarkMail</a> and <a href=" > http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>. > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: <a href="http://hippocms-dev.markmail.org/";>MarkMail</a> and <a href="http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>.
