The docs on useAttribute seem do not mention that it
will honour the "type" attribute.
Obviously it is not a string when placed as a put.
This would cause the class cast.
What is the cast exception. It should specify what it
thinks it is?
There is a getAsString method as well, but I don't
Thanks for the follow-up - I will try "String".
My problem really isn't with the attributes I'm specifying as
direct="true" or type="string", it's with the one (navNode from
my example) that I must specifically leave off the type/direct
attributes in order for it to work with the useAttribute tag:
Not sure if this is what you are after, but according
to the docs it says that tiles:get will respect the
"type" parameter. So maybe this is a bug.
>From the docs:
<--
If 'direct=true' content is 'string', if
'direct=false', content is 'page'
Specify content type: string, page, template or
def
I'm trying to use Tiles for a couple different things and seeing
some bizarre behavior. I've not looked into its source too
thoroughly at this point, but would be willing to do so to help
figure this out.
I use tile parameters in a couple different ways:
So you can see I
4 matches
Mail list logo
