XSP pages processed forever

[Joel Hughes <jo...@redknee.com>]

Any page with a PI of type xsp are processed forever. Cocoon completes
compilation, but some process continues to run forever.  
The Tomcat log file indicates that it is repeatedly asked to get the same
file.
Following entry repeated until tomcat shutdown.
2000-09-26 10:48:04 - Ctx(  ): Get real path /ovoms/ai/login.xml
C:\workspace\www\htdocs\ovoms\ai\login.xml C:\workspace\www\htdocs

problem senarios:  
cocoon 1.7.4/1.8 tomcat 3.1
cocoon 1.8 tomcat 3.2b4

working senario:
cocoon 1.7.2 tomcat 3.1

I've compared my xsp page layout with supplied examples in cocoon-1.8.
Nothing looks unsual.

Suggestions?

File snippets below.

Thanks.
Joel


head of login.xml:
Only xml in this file.
<?xml version="1.0"?>

<?cocoon-process type="xslt"?>
<?xml-stylesheet href="xsp/ai.xsp" type="text/xsl"?>

head of ai.xsp:
xsl, xsp, and sql in this page.
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>

<!-- $Id: ai.xsp,v 1.46 2000/09/20 05:56:42 joel Exp $ -->

<xsl:stylesheet version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:xsp="http://www.apache.org/1999/XSP/Core"
  xmlns:sql="http://www.apache.org/XSP/SQL"
  xmlns:session="http://www.apache.org/XSP/Session"
  xmlns:request="http://www.apache.org/XSP/Request"
>

  <xsl:include href="../../../rk/xsp/rk.sxsp"/>

  <xsl:preserve-space elements="/"/>

  <xsl:template match="/">

      <!-- Processing Instuctions -->
      <!-- WARNING: order is important -->
    <xsl:processing-instruction
name="cocoon-process">type="xsp"</xsl:processing-instruction>
    <xsl:processing-instruction
name="cocoon-process">type="sql"</xsl:processing-instruction>
    <xsl:processing-instruction
name="cocoon-process">type="xslt"</xsl:processing-instruction>
    <xsl:processing-instruction
name="xml-stylesheet">href="xsl/ai-xml-html.xsl"
type="text/xsl"</xsl:processing-
instruction>

    <xsp:page
      language="java"
      xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      xmlns:xsp="http://www.apache.org/1999/XSP/Core"
      xmlns:session="http://www.apache.org/XSP/Session"
      xmlns:request="http://www.apache.org/XSP/Request"
>

    <xsp:structure>
      <xsp:include>java.text.SimpleDateFormat</xsp:include>
      <xsp:include>java.sql.*</xsp:include>
      <xsp:include>org.log4j.*</xsp:include>
      <xsp:include>com.redknee.base.*</xsp:include>
      <xsp:include>com.redknee.util.Env</xsp:include>
      <xsp:include>com.redknee.oam.log.*</xsp:include>
 
<xsp:include>com.redknee.apps.synaxis2200.MultiBatchActivator</xsp:include>
      <xsp:include>com.redknee.apps.synaxis2200.JobMgr</xsp:include>
      <xsp:include>com.redknee.apps.synaxis2200.AIMgr</xsp:include>
    </xsp:structure>

    <page>
    <xsp:logic>
	...


Joël Hughes
joel@redknee.com 
ph: +1 905 625 8235
fax: +1 905 625 6485

Re: XSP pages processed forever

[Donald Ball <ba...@webslingerZ.com>]

On Wed, 27 Sep 2000, Joel Hughes wrote:

> I've compared my xsp page layout with supplied examples in cocoon-1.8.
> Nothing looks unsual.

actually, your file layout differs considerably from the examples, at
least to my eye (or my examples). you start off with an xslt process which
results in a page which is processed by xsp, sql, and xslt again. so
you're doing xslt, xsp, sql, then xslt again. that's needlessly complex.
why not just do xsp, then xslt? it's much simpler and more efficient.

note that you _can_ use xslt in the preparation of an xsp page, but you
should do so by applying logicsheets, either by declaring a magic
namespace prefix (request, session, esql) or by a <?xml-logicsheet
href="esql.xsl"?> PI (the latter are applied in reactor fashion, then the
namespace logicsheets are applied in the order in which they're declared).

in all candor, you've probably found a bug - probably due to some internal
threading problem, and i reckon we could and perhaps should send someone
to track it down. however, i think you'll be able to work around it in the
mean time by reorganizing your processor pipeline.

if i might ask, which example (or lack thereof) led you to your choice of
processor pipelines?

- donald