Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 25427 invoked from network); 29 May 2000 12:18:31 -0000 Received: from news.ozonline.com.au (203.4.248.42) by locus.apache.org with SMTP; 29 May 2000 12:18:31 -0000 Received: from aegis (melb-pool-158-189.ozonline.com.au [203.23.158.189]) by news.ozonline.com.au (8.8.7/8.8.7) with SMTP id WAA08147 for ; Mon, 29 May 2000 22:18:00 +1000 Message-ID: <005f01bfc967$fd263fa0$bd9e17cb@webcybernetics.com> Reply-To: "Rob Parker" From: "Rob Parker" To: Subject: simple-page request creates two XSPGenerator instances Date: Mon, 29 May 2000 22:17:53 +1000 Organization: Web Cybernetics MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005C_01BFC9BB.BBB853B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_005C_01BFC9BB.BBB853B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Developers Unfortunately I don't have any further time to follow this through, but = I noticed the following behaviour with C2 on NT hosted by Apache 1.3.12 resin = 1.1.1 jdk 1.2.2 Each request to simple-page.xsp seems to create two instances of the = generated xsp class. For example, I added the following to the simple page = example... static int their_ctr=3D0; static int their_hitctr=3D0; =20 public _simple_page_xsp() { super(); their_ctr++; } Hence ctr is incremented by the constructor. When I output this value = with an in the page... I've been created their_ctr times and hit = ++their_hitctr times. I find that the hit count is correct, but that the instance count = increases by 2, except on the first request. Is this the anticipated behaviour? Whilst I'm on the subject, down the track, will you guys be adding an = instance pool mechnism so that instances get recycled. If that's the case, is it time to put an interface in the = instance creation areas? regards Rob ------=_NextPart_000_005C_01BFC9BB.BBB853B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Developers
 
Unfortunately I don't have any further = time to=20 follow this through, but I noticed
the following behaviour with C2 on NT = hosted by=20 Apache 1.3.12 resin 1.1.1 jdk 1.2.2
 
Each request to simple-page.xsp seems = to create two=20 instances of the generated
xsp class. For example, I added the = following to=20 the simple page example...
 
<xsp:logic>
  static int=20 their_ctr=3D0;
  static int their_hitctr=3D0;
  =
  public=20 _simple_page_xsp()
  {
   =20 super();
    their_ctr++;
 =20 }
</xsp:logic>
 
Hence ctr is incremented by the = constructor. When I=20 output this value with an <xsp:expr> in
the page...
 
I've been created <xsp:expr> = their_ctr=20 </xsp:expr> times and hit <xsp:expr> ++their_hitctr=20 </xsp:expr> times.
 
I find that the hit count is correct, = but that the=20 instance count increases by 2, except on the first request. Is = this
the anticipated behaviour?
 
Whilst I'm on the subject, down the = track, will you=20 guys be adding an instance pool mechnism so that instances
get recycled. If that's the case, is it = time to put=20 an interface in the instance creation areas?
 
regards
 
Rob
------=_NextPart_000_005C_01BFC9BB.BBB853B0--