Just to reiterate what I saw mentioned on this thread.... OGNL is _not_
involved in interpreting the 'type' attribute of
<property-specification>. It is an actual Java class name that you
could pass to Class.forName(), for example.
Erik
On Apr 19, 2005, at 12:11 PM, Kemkes, Andreas wrote:
Thanks for the answers.
I believe that I've tried about every combination of "@" and "." that I
could think of. It's also more a question of what OGNL supports and I
couldn't find anything in their specification.
It would be nice to have for typesafe enums, which are often
implemented
as nested classes.
Also, as far as I know, the syntax OuterClass$InnerClass has been
deprecated in favor of OuterClass.InnerClass (I don't remember in which
JDK version), but maybe that's what OGNL wants.
Andreas
-----Original Message-----
From: Thomas Meier [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 19, 2005 2:10 AM
To: Tapestry users
Subject: Re: <property-specification
type="a.public.static.member.class" ...>: ApplicationRuntimeException
If you want to access static member in OGNL you use the
expression @[EMAIL PROTECTED]
But this applies only to variables not classes.
If I understand you correct you want to use an internal class
as a type in a property specification. I'm not sure if that
works in Tapestry but in Java you would usually use
OuterClass$InnerClass for this So you'd use something like
<property-specification name="blah"
type="com.myPackage.MyClass$MyInnerClass"/>
Cheers
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
