pdate. It appears this is happening when
calling ValueStack#findValue(java.lang.String) from the interceptor.
I have time to work on a patch, if this issue is valid.
--
With Regards,
Andrew Carr
e. andrewlanec...@gmail.com
w. andrew.c...@openlogic.com
h. 4235255668
c. 4239489852
a. 101 Fra
ork2/util/TextParseUtil.java?view=markup#l170
>
> points to comment ;-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/12/19 Andrew Carr :
>> Hello team,
>>
>> I started to post this as a bug, but thought better of it. I figured
ten ;-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/12/20 Andrew Carr :
>> Used the latest xwork. Am I missing something?
>>
>> On Fri, Dec 20, 2013 at 2:15 AM, Lukasz Lenart
>> wrote:
>>> Be sure yo
Sure
On Wed, Jan 8, 2014 at 10:35 AM, Lukasz Lenart wrote:
> Can you check against version 2.3.16 and post the stacktrace again?
>
> 2013/12/20 Lukasz Lenart :
>> Looks ok :/
>>
>> 2013/12/20 Andrew Carr :
>>> My apologies for missing this email. I pasted
://pastebin.com/gb1ANUM5
-Andrew Carr
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
elements are used to construct a
> >>>>>>>>>>> font.
> >>>>>>>>>>> How does this font look like? It does not seem to follow all of
> >>>>>>>>>>> the
> >>>>>>>>>
gt; >>
> > >> > Is this a bug? I cannot use an EL expression to set the "value"
> > >> attribute.
> > >> > I don't understand why such a restriction exists. Thoughts?
> > >> >
> > >> > Cheers,
> > >
