Ok, so I solved my problem. The problem was actually Ultra-Edit adding BOM headers to all UTF-8 files automatically. This was nasty as this configuration is the default one... The header was 2 characters placed before <?xml...?>
En réponse à Jaq Marit <[EMAIL PROTECTED]>: > I had a similar experience. Being a sax exception, there must be > something > wrong with one of the xml files (mostly config files). My observation > is that > jetspeed tries to process and possibly write to config files causing the > xml > files to be modified. At some point, my apps server did crash or did > not exit > gracefully and I encountered 'Content is not allowed in prolog' errors. > So I > had to look at the xml files, and I saw an empty xml (config) file. > Your > problem may not be similar to mine but you could consider checking each > xml > file again. > > Quoting Xavier Lawrence <[EMAIL PROTECTED]>: > > > Well, I continued getting these 'org.xml.sax.SAXParseException: > Content is > > not > > allowed in prolog' this morning :( > > > > However, I might have spotted something: > > I took the struts-demo application which is working fine. The war file > for > > this > > application was created by using 'maven quickstart' and is the one > deployed > > into JetSpeed. > > I then went into the root directory of the struts-demo application > and > > deleted > > the target directory. I then typed 'maven war' and replaced the > original file > > > > deployed into jetspeed by this one (after correctly undeploying it). > Guess > > what ? > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
