Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Mon, 17 Mar 2003 19:48:13 +0100
Subject: Re: Java PetStore sample - alternative view
Content-Type: text/plain; delsp=yes; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
From: leo leonid <tek@leonid.de>
To: cocoon-dev@xml.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <3E7607A1.7060701@verizon.net>
Message-Id: <01A6F442-58A9-11D7-9AA6-003065A89D34@leonid.de>


On Montag, M=E4rz 17, 2003, at 06:36  Uhr, Christopher Oliver wrote:

> leo leonid wrote:
>> excellent! so I can go on with checkout, order, shiping, etc...
>>> Does Xsp have some way of doing number formatting? The numeric =20
>>> values you receive from JavaScript are of type java.lang.Double.
>> Yes probably there is already a logicsheet for this, I try to avoid =20=

>> <xsp:logic/>. Number formating is also possible with XSL =20
>> <xsl:value-of select=3D"format-number (aNumber, '###,###.##')"/>
>
> Do you think it makes sense to add xsl functions to the JXPath context =
=20
> used by the jpath logic sheet, so that you can call them directly from =
=20
> jpath, e.g <jpath:value-of select =3D"format-number(/totalCost, =20
> '###,###.##')"/> ?

no, not necessarily, numbers can be formated already with the =20
generator, using a logicsheet or later
with the xsl-tranformermation step.
>
>> But something really ugly - where I really can't imagine an elegant =20=

>> solution with XSP or XSL - is HTML in the DB. The only reasonable =20
>> solution would be restructuring the DB, but then it isn't THE =20
>> petstore anymore. hm?? so where should we solve this problem?
>
> I think the original author was trying to make a direct comparison to =20=

> the M$ Petshop example, which has html in the DB. I think we can and =20=

> should remove that. IIRC IBatis JPetstore version 1
> http://prdownloads.sourceforge.net/ibatisjpetstore/jpetstore-src-1-2-=20=

> 3.zip?download
> has the proper design.
>

I'm not so good in history, but I thought the original petstore has =20
always been a part of SUN's blueprint program, teaching design patterns =20=

(obviously not DB-Design). I looked on my old ULTRA1 and actually found =20=

a petstore v.1.1 from early 2001. The data for populating the DB is =20
pretty much the same as in our example (you can see it on my server =20
'oracle.sql'). So for traditional reasons I'd say we should keep it, no?

>
> Regards,
>
> Chris
>
>