@Lance - the names are pulled from our database and will vary from grid to
grid as we allow dynamic building of the table so it wouldn't be viable or
predictable to add them to a message catalog I'm afraid!
@Thiago - this is just the issue in that the PropertyModelImpl source looks
like this;
public PropertyModelImpl(BeanModel model, String name, PropertyConduit
conduit, Messages messages) {
-- snip --
id = TapestryInternalUtils.extractIdFromPropertyExpression(name);
label = TapestryInternalUtils.defaultLabel(id, messages, name);
-- snip --
}
We have two strings here - the id and the label - and both are stripped
down. It seems like we might be expected to pass in a package/class at some
point given the extra work done on defaultLabel (strips to the last
dot-separated token, removes punctuation etc).
I would have assumed that id would store the field/method name while label
would store our customized user presentable name.
In that case I wonder whether it might be an option to arbitrarily name the
columns (given that there will be a variable number of them with variable
names) and add the actual column names as the first row. This would then
mean perhaps hacking my grid-based table to move first row values into
column names and then delete the first row (sounds like the job of a
mixin).
Thanks as ever for your feedback guys!
Peter
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/PropertyModelImpl-Stripping-Non-Word-Characters-From-Its-Label-tp5716383p5716391.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
