I'm trying to develop a standard approach to CRUD that is made of highly
decoupled HiveMind services, but have not got much together yet, as there
are many technologies to consider. :(

If you use Hibernate and Eclipse, you may find that this
http://www.eclipse.org/jsr220orm/ is helpful for developing the persistence
layer.

Getting the form data into your page classes is very easy with Tapestry 4,
but I suggest you read up a little first, maybe start with these free
chapters http://www.agileskills2.org/EWDT/chapters1-4.pdf of Kent Tongs
book.

John

----- Original Message ----- 
From: "albartell" <[EMAIL PROTECTED]>
To: <tapestry-user@jakarta.apache.org>
Sent: Wednesday, December 28, 2005 10:41 PM
Subject: Tapestry 4.0 CRUD application


> Hi everyone,
>
> I am new to Tapestry (jumping over the fence from MyFaces) and am having
> trouble with all the different ways to do the same thing.  I was initially
> attracted to Tapestry because of it's mission statement "The simplest
choice
> should be the correct choice."  I think what I am struggling with right
now
> is half of the documentation at http://jakarta.apache.org/tapestry is for
> 3.0 and I am going down the 4.0 route (I like the idea of less xml config
> files :-)
>
> Anyway, what this post boils down to is my need to see just a basic
Tapestry
> 4.0 CRUD (Create, Read, Update, Delete) application (doesn't even need to
be
> tied to a database, BTW I use Hibernate).  I downloaded the
> tapestry-examples-4.0-rc-2.tar.gz file and attempted to install it only to
> have it puke (is it available in .war form so I can load it into Tomcat
> 5.x?).
>
> If anybody has a small CRUD app they could share that would be much
> appreciated as I am hitting the "new technology frustration stage" being
on
> my 2nd full day of Tapestry and I only have a small mess of an application
> running.
>
> Thanks,
> Aaron Bartell
> http://mowyourlawn.com
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to