Document chaining

[gr...@Cyveillance.com]

I'm trying to adopt the following architecture:

Complex.xml ---(xslt/xsp)----> Simple.xml ---(xslt)---> Final.html

I am using IIS/JRun.  I want the transform between Simple.xml and Final.html
to be real simple so that I can give it to our webmasters to spruce up.

There seem to be a number of choices for implementing this:

1) Modify the cocoon servlet using Java.
2) Write Java code in XSP to process the subsequent document.
3) Set up JRUN to do servlet chaining.
4) Use <xsl:include/> or <xsl:import/> to read in the documents.

Am I missing any choices here?  Any thoughts on the pros and cons of these
approaches?

	- Greg

_________________________________________________________________________

Greg Ross, Software Engineer
Cyveillance
"Minding your business on the Net"
1555 Wilson Blvd., Suite 404, Arlington, VA  22209
dir. line:  (703) 312-1243; fax:  (703) 312-0536
e-mail:  gross@cyveillance.com
www.cyveillance.com 

Solaris againe ......

[Taras Shumeyko <no...@humgat.kiev.ua>]

I run Cocoon without JIT compiler but ... but not have error line
number.
We still have this error.
-----------------------
java.lang.ArrayIndexOutOfBoundsException: -47330168
at org.apache.cocoon.processor.xsp.XSPPage.getDocument(Compiled Code)
at org.apache.cocoon.processor.xsp.XSPProcessor.process(Compiled Code)
at org.apache.cocoon.Engine.handle(Compiled Code)
at org.apache.cocoon.Cocoon.service(Compiled Code)
at javax.servlet.http.HttpServlet.service(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)
------------------------

Here is how it happens:

Let's suppose that after modification of .xsp source code we have "null
pointer exception" in some line.
This is really my mistake, and I correct this line. Then I'm requesting
this page and have right result without errors. After 3th or 4th
requests we have "java.lang.ArrayIndexOutOfBoundsException: -47330168"
error.
We tried turn on "log.level = debug" in cocoon.properties,
"wrapper.bin.parameters="-Xms16M -Djava.compiler=NONE -Xt" " in
jserv.properties,
but have not any error line number.


Cocoon very GOOD stuff, but with this bug it's not usable for us.
We run at : Solaris 7, Java 1.2.2_005, Jserv 1.1, Cocoon1.7.3-dev,Apache
3.12

P.S. on NT with same software configuration we don't have any problems.
please help with this trouble.

Re: Document chaining

[Stefano Mazzocchi <st...@apache.org>]

gross@Cyveillance.com wrote:
> 
> I'm trying to adopt the following architecture:
> 
> Complex.xml ---(xslt/xsp)----> Simple.xml ---(xslt)---> Final.html
> 
> I am using IIS/JRun.  I want the transform between Simple.xml and Final.html
> to be real simple so that I can give it to our webmasters to spruce up.
> 
> There seem to be a number of choices for implementing this:
> 
> 1) Modify the cocoon servlet using Java.
> 2) Write Java code in XSP to process the subsequent document.
> 3) Set up JRUN to do servlet chaining.
> 4) Use <xsl:include/> or <xsl:import/> to read in the documents.
> 
> Am I missing any choices here?  Any thoughts on the pros and cons of these
> approaches?

why don't you simply do document chaining in Cocoon?

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

just make sure your PIs are copied over in your stylesheets.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<st...@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------