Thanks a lot for the info, it worked. I saw a Struts bean definition
like that somewhere that led me to believe that that was how it was
done, but as you said, it appears that the accessor never actually gets
registered that way. As for the wisdom of doing thisin my view the
real pain is
My guess, and it is just a guess, is that your bean is being
instantiated by the Struts2 container but it's not being injected anywhere.
Based on my almost-non-existent understanding of OGNL, the OgnlRuntime
contains a static synchronized map of Class->PropertyAccessor which you
can see being
ling List
> Date: Tue, 5 Feb 2008 13:11:57 -0800 (PST)
> To: Struts Users Mailing List
> Subject: Re: Custom OGNL PropertyAccessor
>
> FWIW, OGNL itself is in the ognl.* package.
>
> Dave
>
> --- Randy Burgess <[EMAIL PROTECTED]> wrote:
>
>> I use stand
xwork2.interceptor.LoggingInterceptor"/>
> >
> > looking for clues on OGNL logging???
> > Anyone?
> >
> > HTH
> > Martin
> > - Original Message -
> > Wrom: QBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCA
> > To: "Struts Users Maili
;
> Reply-To: Struts Users Mailing List
> Date: Tue, 5 Feb 2008 15:38:12 -0500
> To: Struts Users Mailing List
> Subject: Re: Custom OGNL PropertyAccessor
>
> you can configure the xwork LoggingInterceptor into your stack..
> class="com.opensymphony.xwork2.interceptor
--- [EMAIL PROTECTED] wrote:
> you can configure the xwork LoggingInterceptor into your stack..
> class="com.opensymphony.xwork2.interceptor.LoggingInterceptor"/>
>
> looking for clues on OGNL logging???
Set the level on the OGNL classes to DEBUG via whatever mechanism is being
used underneath
Re: Custom OGNL PropertyAccessor
> No I haven't. How do I go about doing that?
>
> Dave Newton wrote:
> > --- Tommy Becker <[EMAIL PROTECTED]> wrote:
> >
> >> If there were a better description, I'd be happy to give it. As far as
> >> I can t
No I haven't. How do I go about doing that?
Dave Newton wrote:
--- Tommy Becker <[EMAIL PROTECTED]> wrote:
If there were a better description, I'd be happy to give it. As far as
I can tell, our custom PropertyAccessor is not being used. What we want
is to be able to say "property" in an
--- Tommy Becker <[EMAIL PROTECTED]> wrote:
> If there were a better description, I'd be happy to give it. As far as
> I can tell, our custom PropertyAccessor is not being used. What we want
> is to be able to say "property" in an OGNL expression and have it call
> getPropertyValue("property")
If there were a better description, I'd be happy to give it. As far as
I can tell, our custom PropertyAccessor is not being used. What we want
is to be able to say "property" in an OGNL expression and have it call
getPropertyValue("property"), not getProperty(). It seems it's
continuing to t
Tommy Becker wrote:
I have a question about using OGNL PropertyAccessors. We have an object
on the value stack that we expose to JSP pages that does not have
standard JavaBeans getter/setter methods. From what I can tell, this
leaves us 2 options. We can either call the getter methods explic
I have a question about using OGNL PropertyAccessors. We have an object on the
value stack that we expose to JSP pages that does not have standard JavaBeans
getter/setter methods. From what I can tell, this leaves us 2 options. We can
either call the getter methods explicitly via OGNL method
12 matches
Mail list logo
