I've given some thought to a declarative persistance model. Interestingly,
I've also learned the bytecode tricks necessary to fill in abstract methods,
much like a CMP Entity EJB. But this isn't even on the radar yet ... your
IDE can create your getters and setters and you can fill in the extra (if
necesasary, I think Spindle can even do that for you).
----- Original Message -----
From: "julien viet" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, November 24, 2002 11:55 AM
Subject: suggestion
> Hello howard,
>
> I've been playing aroud with tapestry and I was
> wondering :
>
> a page use properties that are setup when it's used
> and removed after (with detach method)
>
> that would be possible to use the same kind of things
> that are used in EJBs impl. : abstract setters and getters.
>
> instead of :
>
> private Object property;
> public Object getProperty() { return property; }
> public void setProperty(Object property) { this.property = property; }
> public void detach() { super.detach(); property = null; }
>
> have that :
>
> public Object getProperty();
> public void setProperty(Object property);
>
> and have subclass taking care of all.
>
> I believe that would simplify pages.
>
> any thoughts ?
>
> --
> Best regards,
> julien mailto:[EMAIL PROTECTED]
>
> ___________________________________________________________
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
> Yahoo! Mail : http://fr.mail.yahoo.com
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
