You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Rob Parker <ro...@webcybernetics.com> on 2000/03/16 01:08:26 UTC

Order of XSP/SQL processing declarations gives different behaviour...

I've experienced the following feature with Cocoon 1.7

If my order is as follows, all works fine...

<?cocoon-process type="xsp"?>
<?cocoon-process type="sql"?>

If I reverse the order, all looks fine, except the next time I request the
page,
the query is not executed again and I just see old data.

Is this a bug or feature.

thanks
Rob


Re: Config problem on cocoon1.7

Posted by Thomas Krebs <tk...@attglobal.net>.
After commenting out the lines in the property file of cocoon, I managed to
get the proper return from cocoon.xml. However, I still have problems to
display XML files. I think the source of my problem is to force Apache to
properly forward XML files to tomcat. I know this was discussed several
times in this list, but it is still not clear to me what exactly I have to
put into the tomcat configuration file which is loaded by apache. I am using
Tomcat 3.1M1 and Cocoon 1.7. I have defined a context 'cocoon' in which I
have cocoon defined as a servlet. Access to
http://localhost/cocoon/servlets/Cocoon.xml returns the coocon status page,
but trying to access any other XML file returns an error. Any help would be
appreciated.

----- Original Message -----
From: "Thomas Krebs" <tk...@attglobal.net>
To: <co...@xml.apache.org>
Sent: Thursday, March 23, 2000 8:46 PM
Subject: Re: Config problem on cocoon1.7


> I had exactly the same problem which I posted some weeks ago. I still
> haven't got a solution.
> In my installation the files are in cocoon.jar which I put in the
classpath.
> I even extracted cocoon.jar into the servlet context for which I
configured
> cocoon, but I didn't get it to work.
> There was some discussion earlier in the list concerning class loader
> issues, which is the only lead I currently have.
>
>
> ----- Original Message -----
> From: "Donald Ball" <ba...@webslingerZ.com>
> To: <co...@xml.apache.org>
> Sent: Thursday, March 23, 2000 5:45 AM
> Subject: Re: Config problem on cocoon1.7
>
>
> > On Wed, 22 Mar 2000, Carlos Vinueza M. wrote:
> >
> > > Hi,
> > > I was using an old version of Cocoon, and I tried to update it to
> Cocoon1.7,
> > > but when I type
> > >
> > >             http://localhost/Cocoon.xml
> > >
> > > I get the next error
> > >
> > > java.lang.RuntimeException: Error loading logicsheet:
> > > resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl.
> > > java.io.IOException: Resource not found:
> > > resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl
> > >  at org.apache.cocoon.processor.xsp.XSPProcessor.init(Compiled Code)
> > >  at org.apache.cocoon.framework.Manager.create(Compiled Code)
> > >  at org.apache.cocoon.framework.Router.init(Compiled Code)
> > >  at org.apache.cocoon.framework.Manager.create(Compiled Code)
> > >  at org.apache.cocoon.Engine.(Compiled Code)
> > >  at org.apache.cocoon.Engine.getInstance(Compiled Code)
> > >  at org.apache.cocoon.Cocoon.init(Compiled Code)
> > >  at org.apache.jserv.JServServletManager.load_init(Compiled Code)
> > >  at org.apache.jserv.JServServletManager.loadServlet(Compiled Code)
> > >  at org.apache.jserv.JServConnection.processRequest(Compiled Code)
> > >  at org.apache.jserv.JServConnection.run(Compiled Code)
> > >  at java.lang.Thread.run(Compiled Code)
> > >
> > > Does anybody have any idea????????
> >
> > What JVM are you using? Does your cocoon jar file include these
> > stylesheets?
> >
> > - donald
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> > For additional commands, e-mail: cocoon-users-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>


Re: Config problem on cocoon1.7

Posted by Thomas Krebs <tk...@attglobal.net>.
I had exactly the same problem which I posted some weeks ago. I still
haven't got a solution.
In my installation the files are in cocoon.jar which I put in the classpath.
I even extracted cocoon.jar into the servlet context for which I configured
cocoon, but I didn't get it to work.
There was some discussion earlier in the list concerning class loader
issues, which is the only lead I currently have.


----- Original Message -----
From: "Donald Ball" <ba...@webslingerZ.com>
To: <co...@xml.apache.org>
Sent: Thursday, March 23, 2000 5:45 AM
Subject: Re: Config problem on cocoon1.7


> On Wed, 22 Mar 2000, Carlos Vinueza M. wrote:
>
> > Hi,
> > I was using an old version of Cocoon, and I tried to update it to
Cocoon1.7,
> > but when I type
> >
> >             http://localhost/Cocoon.xml
> >
> > I get the next error
> >
> > java.lang.RuntimeException: Error loading logicsheet:
> > resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl.
> > java.io.IOException: Resource not found:
> > resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl
> >  at org.apache.cocoon.processor.xsp.XSPProcessor.init(Compiled Code)
> >  at org.apache.cocoon.framework.Manager.create(Compiled Code)
> >  at org.apache.cocoon.framework.Router.init(Compiled Code)
> >  at org.apache.cocoon.framework.Manager.create(Compiled Code)
> >  at org.apache.cocoon.Engine.(Compiled Code)
> >  at org.apache.cocoon.Engine.getInstance(Compiled Code)
> >  at org.apache.cocoon.Cocoon.init(Compiled Code)
> >  at org.apache.jserv.JServServletManager.load_init(Compiled Code)
> >  at org.apache.jserv.JServServletManager.loadServlet(Compiled Code)
> >  at org.apache.jserv.JServConnection.processRequest(Compiled Code)
> >  at org.apache.jserv.JServConnection.run(Compiled Code)
> >  at java.lang.Thread.run(Compiled Code)
> >
> > Does anybody have any idea????????
>
> What JVM are you using? Does your cocoon jar file include these
> stylesheets?
>
> - donald
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>


Re: Config problem on cocoon1.7

Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 22 Mar 2000, Carlos Vinueza M. wrote:

> Hi,
> I was using an old version of Cocoon, and I tried to update it to Cocoon1.7,
> but when I type
> 
>             http://localhost/Cocoon.xml
> 
> I get the next error
> 
> java.lang.RuntimeException: Error loading logicsheet:
> resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl.
> java.io.IOException: Resource not found:
> resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl
>  at org.apache.cocoon.processor.xsp.XSPProcessor.init(Compiled Code)
>  at org.apache.cocoon.framework.Manager.create(Compiled Code)
>  at org.apache.cocoon.framework.Router.init(Compiled Code)
>  at org.apache.cocoon.framework.Manager.create(Compiled Code)
>  at org.apache.cocoon.Engine.(Compiled Code)
>  at org.apache.cocoon.Engine.getInstance(Compiled Code)
>  at org.apache.cocoon.Cocoon.init(Compiled Code)
>  at org.apache.jserv.JServServletManager.load_init(Compiled Code)
>  at org.apache.jserv.JServServletManager.loadServlet(Compiled Code)
>  at org.apache.jserv.JServConnection.processRequest(Compiled Code)
>  at org.apache.jserv.JServConnection.run(Compiled Code)
>  at java.lang.Thread.run(Compiled Code)
> 
> Does anybody have any idea????????

What JVM are you using? Does your cocoon jar file include these
stylesheets?

- donald


Config problem on cocoon1.7

Posted by "Carlos Vinueza M." <ca...@ecuadorexplorer.com>.
Hi,
I was using an old version of Cocoon, and I tried to update it to Cocoon1.7,
but when I type

            http://localhost/Cocoon.xml

I get the next error

java.lang.RuntimeException: Error loading logicsheet:
resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl.
java.io.IOException: Resource not found:
resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl
 at org.apache.cocoon.processor.xsp.XSPProcessor.init(Compiled Code)
 at org.apache.cocoon.framework.Manager.create(Compiled Code)
 at org.apache.cocoon.framework.Router.init(Compiled Code)
 at org.apache.cocoon.framework.Manager.create(Compiled Code)
 at org.apache.cocoon.Engine.(Compiled Code)
 at org.apache.cocoon.Engine.getInstance(Compiled Code)
 at org.apache.cocoon.Cocoon.init(Compiled Code)
 at org.apache.jserv.JServServletManager.load_init(Compiled Code)
 at org.apache.jserv.JServServletManager.loadServlet(Compiled Code)
 at org.apache.jserv.JServConnection.processRequest(Compiled Code)
 at org.apache.jserv.JServConnection.run(Compiled Code)
 at java.lang.Thread.run(Compiled Code)

Does anybody have any idea????????

Thank you

--
Computers let you make More mistakes faster
than any other invention in human history
with the possible exception of handguns and tequila.


cArLos  8-)



Re: Order of XSP/SQL processing declarations gives different behaviour...

Posted by Donald Ball <ba...@webslingerZ.com>.
On Thu, 16 Mar 2000, Rob Parker wrote:

> I've experienced the following feature with Cocoon 1.7
> 
> If my order is as follows, all works fine...
> 
> <?cocoon-process type="xsp"?>
> <?cocoon-process type="sql"?>
> 
> If I reverse the order, all looks fine, except the next time I request the
> page,
> the query is not executed again and I just see old data.
> 
> Is this a bug or feature.

Likely a bug, but possibly a feature - Stefano or Ricardo should be able
to answer with some more authority. However, might I suggest that you use
the SQL taglib since you've already made the XSP hurdle? Just add the
resource directive to the sql taglib in cocoon.properties, add the sql
namespace to your list of xsp namespaces in the xml file, and configure
the query using the sql namespace - options are just like those for SQL
processor, except instead of attributes the options are now elmeents:

<sql:execute-query>
	<sql:driver>org.gjt.mm.mysql.Driver</sql:driver>
	<sql:query>select * from foo_table</sql:query>
</sql:execute-query>

Gotta get some time to write docs...

- donald