SAXParseException in Cocoon 1.8.2 with WebSphere 3.5.4

2001-09-06 Thread Jack Hirasawa

Hi There!

I've recently installed Cocoon on WebSphere 3.5.4 using the install script 
and when I try to display the index.xml file in the samples directory I get 
the following:

org.xml.sax.SAXParseException: The markup in the document following the root 
element must be well-formed.
at org.xml.sax.SAXException.(SAXException.java:78)
at 
org.apache.cocoon.parser.AbstractParser.fatalError(AbstractParser.java:105)
at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1037)
at 
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
at 
org.apache.xerces.framework.XMLDocumentScanner.abortMarkup(XMLDocumentScanner.java:679)
at 
org.apache.xerces.framework.XMLDocumentScanner$TrailingMiscDispatcher.dispatch(XMLDocumentScanner.java(Compiled
 
Code))
at 
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java(Compiled
 
Code))
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at org.apache.cocoon.parser.XercesParser.parse(XercesParser.java:85)
at org.apache.cocoon.parser.AbstractParser.parse(AbstractParser.java:83)
at 
org.apache.cocoon.producer.ProducerFromFile.getDocument(ProducerFromFile.java:78)
at org.apache.cocoon.Engine.handle(Engine.java:359)
at org.apache.cocoon.Cocoon.service(Cocoon.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:626)
at 
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:160)
at 
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:287)
at 
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:105)
at 
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:360)
at 
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:775)
at 
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:701)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:478)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:234)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:138)
at 
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:77)
at 
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at 
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:155)
at 
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)
at 
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQEventListenerImp.java:230)
at 
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventListenerImp.java:104)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQEventSource.java:212)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.notifyService(SQWrapperEventSource.java:353)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.run(SQWrapperEventSource.java:220)
at 
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

I noticed in the archives that others have encountered the same problem, but 
I didn't see a resolution.

Any help would be appreciatedThanks!

Jack



_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>




SAXParseException in C1.8.2 using Websphere 3.5.4

2001-09-07 Thread Jack Hirasawa

Hi cocoon-users!

I recently installed cocoon 1.8.2 on Websphere 3.5.4 using the install 
script.  I had to fix cocoon.java so it would get the file cocoon.properties 
instead of a resource.  I was able to successfully get the Cocoon.xml page 
to display.  When I tried to display the index.xml page, I got the exception 
below.  Any help would be greatly appreciated!!! Thanks in advance...

org.xml.sax.SAXParseException: The markup in the document following the root 
element must be well-formed.
at org.apache.cocoon.Engine.handle(Engine.java:313)
at org.apache.cocoon.Cocoon.service(Cocoon.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:626)
at 
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:160)
at 
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:287)
at 
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:105)
at 
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:360)
at 
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:775)
at 
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:701)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:478)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:234)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:138)
at 
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:77)
at 
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at 
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:155)
at 
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)
at 
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQEventListenerImp.java:230)
at 
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventListenerImp.java:104)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQEventSource.java:212)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.notifyService(SQWrapperEventSource.java:353)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.run(SQWrapperEventSource.java:220)
at 
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)



_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>




Re: SAXParseException in C1.8.2 using Websphere 3.5.4

2001-09-07 Thread Jack Hirasawa

Berin,

Thanks for your reply, much appreciated...

I tried adding the xerces jar as the first entry in the

com.ibm.ejs.sm.adminserver.classpath property

in c:\WebSphere\AppServer\bin\admin.config

but it didn't make any difference.

Was this the WebSphere properties file that you were refering to?

Thanks

Jack


>From: Berin Loritsch <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: SAXParseException in C1.8.2 using Websphere 3.5.4
>Date: Fri, 07 Sep 2001 11:18:26 -0400
>
>Jack Hirasawa wrote:
> >
> > Hi cocoon-users!
> >
> > I recently installed cocoon 1.8.2 on Websphere 3.5.4 using the install
> > script.  I had to fix cocoon.java so it would get the file 
>cocoon.properties
> > instead of a resource.  I was able to successfully get the Cocoon.xml 
>page
> > to display.  When I tried to display the index.xml page, I got the 
>exception
> > below.  Any help would be greatly appreciated!!! Thanks in advance...
>
>The only time I have received this message is when the source XML was not
>well formed.  It is possible that Websphere is still referencing an older
>XML parser that doesn't accept namespaces.  In that case, you must make 
>sure
>that Xerces is before all other jars (including the WebSphere jars).
>
>You may have to edit your websphere property files that specify classpath
>information (you know the one where they tell you to edit for hot fixes?).
>I have examined the contents of the websphere jars trying to figure out why
>I was having issues with Cocoon 2 a few months ago.  The embed class files
>for Xerces in there.
>
>-
>Please check that your question has not already been answered in the
>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
>To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>For additional commands, e-mail: <[EMAIL PROTECTED]>
>


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>




Re: SAXParseException in C1.8.2 using Websphere 3.5.4

2001-09-07 Thread Jack Hirasawa

Berin,

Thanks again for your reply...

I'm stumped.

The index.xml file is the one that came with the distribution (unmodified).

I've tried the other samples as well, but no luck

Any other ideas? It must be a configuration issue, but I can't figure out 
what it is

Thanks,

Jack

>From: Berin Loritsch <[EMAIL PROTECTED]>
>To: Jack Hirasawa <[EMAIL PROTECTED]>
>Subject: Re: SAXParseException in C1.8.2 using Websphere 3.5.4
>Date: Fri, 07 Sep 2001 13:08:46 -0400
>
>Jack Hirasawa wrote:
> >
> > Berin,
> >
> > Thanks for your reply, much appreciated...
> >
> > I tried adding the xerces jar as the first entry in the
> >
> > com.ibm.ejs.sm.adminserver.classpath property
> >
> > in c:\WebSphere\AppServer\bin\admin.config
> >
> > but it didn't make any difference.
> >
> > Was this the WebSphere properties file that you were refering to?
>
>Yes, that was the one.
>
>Check your XML file to see if there is some sort of encoding
>problem with it.
>
> >
> > Thanks
> >
> > Jack
> >
> > >From: Berin Loritsch <[EMAIL PROTECTED]>
> > >Reply-To: [EMAIL PROTECTED]
> > >To: [EMAIL PROTECTED]
> > >Subject: Re: SAXParseException in C1.8.2 using Websphere 3.5.4
> > >Date: Fri, 07 Sep 2001 11:18:26 -0400
> > >
> > >Jack Hirasawa wrote:
> > > >
> > > > Hi cocoon-users!
> > > >
> > > > I recently installed cocoon 1.8.2 on Websphere 3.5.4 using the 
>install
> > > > script.  I had to fix cocoon.java so it would get the file
> > >cocoon.properties
> > > > instead of a resource.  I was able to successfully get the 
>Cocoon.xml
> > >page
> > > > to display.  When I tried to display the index.xml page, I got the
> > >exception
> > > > below.  Any help would be greatly appreciated!!! Thanks in 
>advance...
> > >
> > >The only time I have received this message is when the source XML was 
>not
> > >well formed.  It is possible that Websphere is still referencing an 
>older
> > >XML parser that doesn't accept namespaces.  In that case, you must make
> > >sure
> > >that Xerces is before all other jars (including the WebSphere jars).
> > >
> > >You may have to edit your websphere property files that specify 
>classpath
> > >information (you know the one where they tell you to edit for hot 
>fixes?).
> > >I have examined the contents of the websphere jars trying to figure out 
>why
> > >I was having issues with Cocoon 2 a few months ago.  The embed class 
>files
> > >for Xerces in there.
> > >
> > >-
> > >Please check that your question has not already been answered in the
> > >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> > >
> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > >For additional commands, e-mail: <[EMAIL PROTECTED]>
> > >
> >
> > _
> > Get your FREE download of MSN Explorer at 
>http://explorer.msn.com/intl.asp


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>




WebSphere/Cocoon Gurus - Help!!!!

2001-09-08 Thread Jack Hirasawa

(A desperate plea for understanding in a mechanized ethos)

Has anyone successfully installed Cocoon 1.8.2 on Websphere 3.5.4?

I downloaded cocoon 1.8.2, and ran the install script.

I got an exception Error accessing the resource cocoon.properties

I changed cocoon.java to access it as a file instead of a resource.

I was successful in getting http://localhost/cocoon/Cocoon.xml to display.

When I try to display the samples using http://localhost/cocoon/index.xml I 
get the exception below...

I have tried putting the jar files into the classpath in the admin.config 
file (and I did put the sax-bugfix.jar and xerces.jar in front)

Any ideas? ... Anyone? ... I'm stumped.

here's the exception...

Error found handling the request.
org.xml.sax.SAXParseException: The markup in the document following the root 
element must be well-formed.
at org.apache.cocoon.Engine.handle(Engine.java:313)
at org.apache.cocoon.Cocoon.service(Cocoon.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:626)
at 
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:160)
at 
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:287)
at 
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:105)
at 
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:360)
at 
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:775)
at 
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:701)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:478)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:234)
at 
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:138)
at 
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:77)
at 
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at 
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at 
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:160)
at 
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)
at 
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQEventListenerImp.java:230)
at 
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventListenerImp.java:104)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQEventSource.java:212)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.notifyService(SQWrapperEventSource.java:353)
at 
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.run(SQWrapperEventSource.java:220)
at 
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)




_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>




Re: WebSphere/Cocoon Gurus - Help!!!!

2001-09-10 Thread Jack Hirasawa

Hi fellow cocoon-users

I was able to successfully get Cocoon 1.8.2 working under WebSphere, but 
only after I back-levelled WebSphere to 3.5.2 (I was trying to get it 
running under 3.5.4).  Does anyone know what might have changed between the 
two releases that causes Cocoon 1.8.2 to break?

Cheers...

Jack


>From: "Jack Hirasawa" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: WebSphere/Cocoon Gurus -  Help
>Date: Sat, 08 Sep 2001 21:44:00 -0400
>MIME-Version: 1.0
>X-Originating-IP: [64.229.42.233]
>Received: from [64.125.133.20] by hotmail.com (3.2) with ESMTP id 
>MHotMailBD64147F002440043188407D85140BE90; Sat, 08 Sep 2001 18:44:32 -0700
>Received: (qmail 36370 invoked by uid 500); 9 Sep 2001 01:44:21 -
>Received: (qmail 36359 invoked from network); 9 Sep 2001 01:44:20 -
>From cocoon-users-return-23514-jackhirasawa Sat, 08 Sep 2001 18:46:11 -0700
>Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
>Precedence: bulk
>list-help: <mailto:[EMAIL PROTECTED]>
>list-unsubscribe: <mailto:[EMAIL PROTECTED]>
>list-post: <mailto:[EMAIL PROTECTED]>
>Delivered-To: mailing list [EMAIL PROTECTED]
>Message-ID: <[EMAIL PROTECTED]>
>X-OriginalArrivalTime: 09 Sep 2001 01:44:01.0130 (UTC) 
>FILETIME=[E64DDCA0:01C138D0]
>X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
>
>(A desperate plea for understanding in a mechanized ethos)
>
>Has anyone successfully installed Cocoon 1.8.2 on Websphere 3.5.4?
>
>I downloaded cocoon 1.8.2, and ran the install script.
>
>I got an exception Error accessing the resource cocoon.properties
>
>I changed cocoon.java to access it as a file instead of a resource.
>
>I was successful in getting http://localhost/cocoon/Cocoon.xml to display.
>
>When I try to display the samples using http://localhost/cocoon/index.xml I
>get the exception below...
>
>I have tried putting the jar files into the classpath in the admin.config
>file (and I did put the sax-bugfix.jar and xerces.jar in front)
>
>Any ideas? ... Anyone? ... I'm stumped.
>
>here's the exception...
>
>Error found handling the request.
>org.xml.sax.SAXParseException: The markup in the document following the 
>root
>element must be well-formed.
>   at org.apache.cocoon.Engine.handle(Engine.java:313)
>   at org.apache.cocoon.Cocoon.service(Cocoon.java:184)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>   at
>com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:626)
>   at
>com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:160)
>   at
>com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:287)
>   at
>com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:105)
>   at
>com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:360)
>   at
>com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:775)
>   at
>com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:701)
>   at
>com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:478)
>   at
>com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:234)
>   at
>com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:138)
>   at
>com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:77)
>   at
>com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
>   at
>com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
>   at
>com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:160)
>   at
>com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)
>   at
>com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQEventListenerImp.java:230)
>   at
>com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventListenerImp.java:104)
>   at
>com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQEventSource.java:212)
>   at
>com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.notifyService(SQWrapperEventSource.java:353)
>   at
>com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.run(SQWrapperEventSource.java:220)
>   at
>com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run(O