It's unfortunate, but that would be another strategy that would make
your life easier.
> -Original Message-
> From: Brian Buckley [mailto:[EMAIL PROTECTED]
>
> David,
>
> Thanks for your help.
>
> Perhaps my convention of naming objects using their fully-qualified
> package
> names ough
David,
Thanks for your help.
Perhaps my convention of naming objects using their fully-qualified package
names ought to be changed to avoid having dots in the names.
Brian
> I can only see one way to do this, and it's not simple.
>
> You'd have to write a custom tag that would create a page-sco
> Does work?
Good guess but, no, that gives me a JasperException.
Brian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I can only see one way to do this, and it's not simple.
You'd have to write a custom tag that would create a page-scoped
variable which is a single map variable that has been merged from the
following maps, in order: application, session, request, and page. Then
you could reference your dotted va
Brian wrote:
> if a value with the name "a.b" could be in either request or
> session scope, neither
> or
> by themselves would work.
> Is there syntax to do this?
Does work?
--
Wendy Smoak
