Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Bernhard Huber" <bh22351@i-one.at>
To: Damian Kwok <damian@acm.org>,cocoon-dev@xml.apache.org
Message-ID: <28d2626108.2610828d26@i-one.at>
Date: Tue, 16 Oct 2001 17:24:45 GMT
MIME-Version: 1.0
Content-Language: de
Subject: Re: Cocoon 2 Jsp Generator and Weblogic 6.1
Content-Type: multipart/mixed; boundary="--7215febd1b2dd8"

----7215febd1b2dd8
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi
As I=27m a bit remote my answere here a bit theortically=2E
As you wrote issue 3 promises to be most hopeful solution=2E
This would be some how the most correct way to invoke any
servlet from Cocoon2=2E

I think there should be some other solution than subclassing
ServletResponseImpl=2E I was implementing that way as it=27s the
easiest way=2E Anyway it=27s somehow not the best
that the complete jsp response is stored into a buffer=2C and
than piped to Cocoon2=2C perhaps the best way - regarding
performance - is to have some pipe piping jsp response more
seamlessly to Cocoon2=2E
 =

I think you may have to set the output stream before calling
the RequestDispatcher=2E I=27m not 100=25 sure how to do do it by heart=2E=


Another point it=27s quite okay to use the RequestDispatcher
as the servlet-container can handle resources quite alright=2E

After JSP processing you should pipe
the output to Cocoon=2E
I=27m sorry for the quick incomplete answer=2C but I=27m a bit busy

Just one remark I don=27t mind being emailed directly=2C but
posting to cocoon2-dev=40xml=2Eapache=2Eorg will help others too=2E=2E=2E=
=2E =3A-)
So if it=27s okay for you forward this message to cocoon2-dev
mailing list=2E

bye

=3E Hi Bernhard=2C
=3E I apologise for writing directly to you=2C but we=27re hoping that =

=3E maybe you can
=3E give us some pointers in getting Cocoon 2 to use the JSP engine in =

=3E WLS6=2E1=2EWe got the JSP generator adaptor (JSPEngineImplWLS) from t=
he =

=3E candidaterelease=2C and have spent some time getting that to work on =

=3E 6=2E1=2E  Basically=3A
=3E =

=3E 1=2E Our first attempt was to use weblogic=2Eservlet=2EJSPServlet as-=
is =

=3E (i=2Ee=2EPlain vanilla JSPEngineImpl to invoke the service() method o=
n =

=3E JSPServlet)=2ESome twiddling in JSPEngineImpl was required to keep =

=3E weblogic happy=2C but
=3E weblogic=27s JSPServlet code doesn=27t seem to do very much - at leas=
t =

=3E it didn=27t
=3E seem to do anything to the response object=2E  So perhaps it=27s the =

=3E wrong class
=3E we=27re invoking=2C or it=27s the wrong entry point=2E
=3E =

=3E 2=2E Next we tried JSPEngineImplWLS - unfortunately Weblogic=27s =

=3E implementationseems to have changed quite a bit in 6=2E1 - for =

=3E example ServletRequestImpl no
=3E longer has a public constructor=2C and ServletResponseImpl is now =

=3E marked final
=3E so cannot be subclassed at all=2E
=3E =

=3E 3=2E Finally we went for the generic named dispatcher approach - =

=3E which seems
=3E to hold some promises=2E  We managed to get weblogic to compile and =

=3E executethe JSP without errors=2C by passing weblogic=C2=B9s =

=3E RequestDispatcherImpl the
=3E request/response objects as they are (they already are
=3E ServletRequestImpl/ServletResponseImpl instances)=2E  But now we are =

=3E not sure
=3E how to convert the output of the response object into a byte array as=

=3E required by Cocoon=2E  The fact that both =03 and
=3E ServletOutputStreamImpl are marked final now means that the old =

=3E weblogichack can=27t be done=2E
=3E =

=3E Any pointers will be much appreciated=2E
=3E Thanks a lot=2C
=3E Damian =

=3E 

----7215febd1b2dd8
Content-Type: text/x-vcard; name="bh22351.vcf"; charset=us-ascii
Content-Disposition: attachment; filename="bh22351.vcf
Content-Description: Card for <bh22351@i-one.at>
Content-Transfer-Encoding: 7bit

begin:vcard
n:Huber;Bernhard
fn:Bernhard Huber
version:2.1
email;internet:bh22351@i-one.at
end:vcard


----7215febd1b2dd8
Content-Type: text/plain; charset=us-ascii

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
----7215febd1b2dd8--