In this way there is not bad pratice visible.
Imagine the situation:
<sometaglib:sometag var="result"/>
<s:hidden name="property" value="${result}”/>
<s:hidden name="anotherProperty" value="#anotherResult#CameFromValueStack”/>
<s:hidden name="anotherProperty" value="%{anotherResult.dosomething()}”/>
I'm not an OGNL expert, but from what I know, there is a lot of things you
have to do using OGNL and not just JSTL EL. So, the point is, when to use
what? Trying and fixing?
How about juniors developers? It could really confuse theirs heads.
Maybe in small projects it doesn't matter, I agree, but for big projects
with lots and lots of developers, or where another team maintain the app,
could represent some documentation.
And not considering the security problem. Some Architect could define to use
the struts-dangerous, but the developers don't even know why
struts-dangerous is dangerous.
Of course, it is just my opinion.
Felipe Rodrigues
Andrea Vettori wrote:
>
> Hi,
>
> can someone explain why it's bad practice to do something like this in
> a jsp page :
>
> <sometaglib:sometag var="result"/>
> <s:hidden name="property" value="${result}”/>
>
>
> ??
>
> Thanks !
>
>
>
>> The 2 point is the most important, from my view.
>> Use JSP EL in Struts2 tag is not a best pratice. Match these kind of
>> languages could make the code confuse to be maintained. Sometimes
>> you use
>> OGNL, othertimes you use JSTL EL.
>
>>
>>> Is 2. really a problem? Sorry, I didn't really understand.
>>>> The second problem is keep feeding this pratice (use JSTL EL).
>>>>
>>>
>
> --
> Ing. Andrea Vettori
> Consulente per l'Information Technology
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Issue-WW-2107-question---Is-JSTL-disable-or-not--tp15830208p15877164.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
