2008/4/16, JRD <[EMAIL PROTECTED]>: > > > I don't really see it that way. To me this is the exact intention of > Tiles. > From my perspective you have two ways of building a UI that has both > dataEntry & readOnly views of the same data. You can have struts make the > call which one to show or you can leave it to Tiles. I think the tiles > approach is far superior.
Well... you are not too much wrong :-D Anyway Struts 2 gives you a lot of ways for customizing your components, even with parameters and little tricks. See: http://www.vitarara.org/cms/struts_2_cookbook/creating_a_ui_component I was able to get what I wanted by making my own tag. I'm not happy doing > it as now I need to be careful with Tiles if I want to upgrade but not > having this feature is sort of a show-stopper. > > public class TilesAttributesTag extends AttributeTagSupport { > ... Uh wait, you can use the <tiles:importAttribute> tag without the "name" parameter for this: http://tiles.apache.org/2.0/framework/tiles-jsp/tlddoc/tiles/importAttribute.html I read that > you were working on cascading properties which sounds like it would solve > my > problem depending on the implementation. If you just took everything out > of > the parents attributeContext and put it into the new attributeContext it > should be ok. You can play with cascading attributes right now, I published a snapshot of Tiles 2.1.0: http://people.apache.org/repo/m2-snapshot-repository/ HTH Antonio
