Re: [S2] Inappropriate Error Message

2007-05-23 Thread Roger Varley
Usually this means that there is something other than the BOM before your This is repeatable by using a bogus class name, so that suggests that Struts/Spring is the root cause. Regards Roger - To unsubscribe, e-mail: [EMAIL P

Re: [S2] Inappropriate Error Message

2007-05-23 Thread Martin Gainty
. - Original Message - From: "Roger Varley" <[EMAIL PROTECTED]> To: Sent: Wednesday, May 23, 2007 9:07 AM Subject: [S2] Inappropriate Error Message I'm developing using Struts 2 with the Spring plugin within Netbeans 5.5 using the embedded Tomcat as the servlet eng

Re: [S2] Inappropriate Error Message

2007-05-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roger, Roger Varley wrote: > SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in > prolog. > org.xml.sax.SAXParseException: Content is not allowed in prolog. Usually this means that there is something other than the BOM before you

Re: [S2] Inappropriate Error Message

2007-05-23 Thread Musachy Barroso
That's a generic SAX exception, and I think in this case is coming from Spring, right? musachy On 5/23/07, Roger Varley <[EMAIL PROTECTED]> wrote: I'm developing using Struts 2 with the Spring plugin within Netbeans 5.5 using the embedded Tomcat as the servlet engine. If I screw up my Spring a

[S2] Inappropriate Error Message

2007-05-23 Thread Roger Varley
I'm developing using Struts 2 with the Spring plugin within Netbeans 5.5 using the embedded Tomcat as the servlet engine. If I screw up my Spring applicationContext.xml by incorrectly specifying the path to the class in a bean element, then when I try to deploy the project I get the error message