hi udo, there are different approaches to it... :) ...
you can configure the view using blocks ... i do it by defining some Blocks that are then composed using certain rules through my pimped BeanEditor component. eg. a new Dealer has at least one employee. Therefore when a new Dealer is created i get the input fields to create a new employee as well. when i edit a Dealer i only get a select option where i can select the main employee. which block is displayed is controlled by a service that has some rules contributed. so all i have to do is to define the rules ( fine granular: uses the beantype, propertytype, the current page, and a state) and pass in my bean to my pimped BeanEditor component. The contributed rules have a reference to the current bean and therefore can excute some logic and control the displayed block respectively. i hope this helps :) g, kris "Udo Abel" <[EMAIL PROTECTED]> 23.06.2008 10:26 Bitte antworten an "Tapestry users" <users@tapestry.apache.org> An users@tapestry.apache.org Kopie Thema programmatic component rendering Hi, we're planning a highly dynamic web app, where it is necessary to display certain components depending of the application state. E.g., in an address detail view there should be a paragraph which contains different details for a "customer" and a "supplier". Or if the balance of an account is greater than a certain amnout, another component should be redered on the current page (or within the current component, respectively). Since there are many such situations and combinations, we can't build static tml files for all of them. So, is it possible to render an arbitrary component based on a programmatic choice from within the rendering of a component? Thanks, Udo. -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
