I realize this is a very old thread but I'm facing something similar and
would like to point out that one may need to go deep into an object graph.
For example Adam is asking if tapestry can auto create the "address" object
for him, but what if the address object has other objects that needs to be
treated the same way ? To be auto initialized I mean. I can't initialized
all objects or initialized them when "get"ing them because thier null value
indicates that they weren't initialized.
Has anyone faced a similar case and would like to share how he solved it ?
On Wed, Apr 13, 2011 at 1:53 PM, Christophe Cordenier <
christophe.corden...@gmail.com> wrote:
> And what if we allowed to create defaultXxx method for persistent fields as
> we do for component parameters, does it make sense ?
>
> 2011/4/12 Howard Lewis Ship <hls...@gmail.com>
>
> > This wouldn't have to be an extension to the @Property annotation, it
> > could be a new annotation, (say) @AutoCreate, perhaps with a value to
> > say when (initialize, setup render, etc.). It could use the same kind
> > of logic that the BeanEditForm uses, one that supports the full
> > injection mechanism.
> >
> > On Tue, Apr 12, 2011 at 10:25 AM, Adam Zimowski <zimowsk...@gmail.com>
> > wrote:
> > > You have a point Thiago, I will try other init phases, I suppose just
> > > a habit, and it worked :)
> > >
> > > In regards to your comment on page pool.... Now that Tap isn't using
> > > it, would auto create property instance be an issue? Just curious..
> > >
> > > Adam
> > >
> > > On Tue, Apr 12, 2011 at 12:19 PM, Thiago H. de Paula Figueiredo
> > > <thiag...@gmail.com> wrote:
> > >> On Tue, 12 Apr 2011 13:34:17 -0300, Adam Zimowski <
> zimowsk...@gmail.com
> > >
> > >> wrote:
> > >>
> > >>> Maybe I'm over-thinking here... I find a lot of times I have to do
> > this:
> > >>>
> > >>> @Property
> > >>> private AddressUiBean address;
> > >>>
> > >>> @SetupRender
> > >>> void init() {
> > >>> if(address == null) address = new AddressUiBean();
> > >>> }
> > >>
> > >> Why not activate instead of @SetupRender? Or one of the prepare*
> events
> > of
> > >> Form? Not an easy decision. ;)
> > >>
> > >> --
> > >> Thiago H. de Paula Figueiredo
> > >> Independent Java, Apache Tapestry 5 and Hibernate consultant,
> developer,
> > and
> > >> instructor
> > >> Owner, Ars Machina Tecnologia da Informação Ltda.
> > >> http://www.arsmachina.com.br
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > >> For additional commands, e-mail: users-h...@tapestry.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > > For additional commands, e-mail: users-h...@tapestry.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
>
> --
> Regards,
> Christophe Cordenier.
>
> Committer on Apache Tapestry 5
> Co-creator of wooki @wookicentral.com
>
--
*Regards,*
*Muhammad Gelbana
Java Developer*
