cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Gentry" <>
Subject Re: Cayenne web application tutorial
Date Mon, 09 Apr 2007 14:04:58 GMT
I haven't tried out Click (yet), but if it looks interesting to you,
definitely give it a shot since they are including Cayenne support as part
of the out-of-the-box experience.

I've used Cayenne inside Tapestry apps and it'll work there, too, but I
wouldn't call it seamless.  Especially with the newer Tapestry 4.x releases
where it wants to serialize your Cayenne DataObjects into the HTML it
renders as HIDDEN form elements.  This causes deserialization errors.  If
you go the suggested route of using a DataSqueezer, you'll be OK.  Both of
these options, though, introduce security concerns.  As does including the
primary key as part of the form data.  I'm not sure how Click handles these
issues, but with Tapestry, you have to be careful to not expose internal
data if you care about security.  (Never trust the user to send you the
"correct" HTML back to the server -- I can edit the FORM data in my browser
and change PKs/etc and mess you up.)


On 4/9/07, Reid Thompson <> wrote:
> Malcolm Edgar wrote:
> > Hi Reid,
> >
> > Beyond this tutuorial you get into the realm of web application
> > frameworks and their capabilities to support Cayenne.
> >
> > Click Framework provides extensive support for the Cayenne ORM
> > framework. You can see examples online at:
> >
> >
> >
> > regards Malcolm Edgar
> >
> >
> > On 4/9/07, Reid Thompson <> wrote:
> >> Is there a more advance web application tutorial available than the one
> >> at ??
> >>
> Thanks,
> I saw the reference to Click ( and others ) in the wiki and noted it for
> further investigation ( a quick glance piqued my interest pretty good
> ).  I've also looked over SiteMesh a bit.  I was thinking of perhaps
> trying to implement an application utilizing these two tools.  Anyone
> know of any issue that would make that a bad direction?
> reid

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message