Keith Sader wrote:
I've got a form that will be included in one of three pages.
Essentially this form captures the same data at different levels in an
inventory of rolling stock. The grouping is as follows:
1.) Inventory Defaults - applies to all inventory
2.) Fleet level defaults - applies to a group of inventory items
3.) Equipment defaults - applies to one piece of rolling stock.
The order of precedence is 3, 2, 1 i.e. attribute data at the
equipment level over-rides defaults set at the fleet level, defaults
set at the fleet level over-ride inventory defaults.
I've got a tile defined that captures the common data, and I was
wondering if it was advisable to pass in the action to call on submit
as a tile parameter? What I'd like ideally is polymorphism off of a
submit. Is there an object friendly-way to do this?
I'm not sure exactly what you meant by 'polymorphism off of a submit' so
this might be completely off-base but... Passing the action into the
tile definition may be one option, depending on how your tiles and
actions are set up. Another option may be to wait for the Struts 1.3
release that's coming up. 1.3 lets you have 'extends' relationships
between various configuration elements. I'm not sure, but I think this
includes tiles definitions, in which case you can have a tile for each
of your 'precedence levels' with each extending the higer-level one.
If that doesn't sound like it might be useful, I probably haven't
understood what you want to achieve properly.
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
