On Wed, Apr 28, 2010 at 4:54 AM, Christophe Cordenier <[email protected]> wrote: > Hi, > > To avoid some cumbersome hacking or use of ognl, i finally decided to > automatically generate one getter for each know activity type. This was the > opportunity to test the brand new Component Class Transformation API. > > Thanks to Howard for this great changes, no BodyBuilder anymore.
Yes, though the cost seems to be an explosion of classes taking up a big chunk of permgen space. This has me a bit concerned. > > Best Regards, > Christophe Cordenier. > > 2010/4/28 Christophe Cordenier <[email protected]> > >> Hi >> >> Currently property conduit are created when the page template is parsed, i >> guess there is good reasons for that (performance, template validation) >> But what about a property binding that would be able to get informations >> from the returned type and note the type of the accessor. >> >> In my case, i have different blocks that display different type of >> activities. Every activity extends a base one, but each activity has >> specific attributes. >> My first implementation was to define one component per activity and put >> all the generics stuff in base component class. >> >> But i thought it would be more elegant to do it the 'PropertyDisplayBlocks' >> way, i mean create a context that contain the datas to display and let a >> service decide which block to display in function of the activity type. But >> doing this i am still stuck to my specific attributes problem. >> >> Any idea ? >> >> -- >> Regards, >> Christophe Cordenier. >> >> Developer of wooki @wookicentral.com >> > > > > -- > Regards, > Christophe Cordenier. > > Developer of wooki @wookicentral.com > -- 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: [email protected] For additional commands, e-mail: [email protected]
