For the core, I believe the external dependencies are Freemarker,
OGNL, XWork, and Commons Logging. Of course, adding plugins adds
dependencies, but that's another matter.
My heuristic is to stay current with the latest production release,
unless there is a problem. Otherwise, people using the
On 1/23/07, Ted Husted [EMAIL PROTECTED] wrote:
For the core, I believe the external dependencies are Freemarker,
OGNL, XWork, and Commons Logging. Of course, adding plugins adds
dependencies, but that's another matter.
My heuristic is to stay current with the latest production release,
On 1/23/07, Joe Germuska [EMAIL PROTECTED] wrote:
In the case of commons-logging, we should stay current with Struts
1.x, since we are encouraging people to use 1.x and 2.x in the same
application, and this is the one dependency we share.
-T.
On this subject, what about commons-logging 1.1?
I'm also going to run my local development with a dependency on FM 2.3.8. I
reviewed the release notes and there are no obvious compatibility issues,
plus, of course, a handful of bug fixes. It seems to have been stable for
almost six months, so it seems safe for us to move to it.
Do we have
We've been running against freemarker 2.3.4. Has anyone tried using 2.3.8?
Should we update our dependency from 2.3.4 to 2.3.8 ?
* http://freemarker.org/docs/app_versions.html
It's been out since July. I'm updating some training materials, and
I'll try it here locally.
-Ted.
On 1/20/07, Joe
I've ran into an odd problem of my own and while I'm troubleshooting it, I'm
hitting some problems or confusion with Freemarker as it is used for the S2
UI tags. Can anyone help me understand this better?
I was getting a big yellow and red Freemarker trace in my rendered page
because an
Joe,
${error} being null would imply that you have an item in the action
errors Collection that is null. (e.g. {Error1, Error2, null,
Error4}) It seems like that would be an issue that occurs as the
errors are being populated. (I can't think of a valid use case where
you would have a null
Tom:
Thanks for your help... I see now that the syntax I was trying to use was
added in Freemarker 2.3.7
http://freemarker.sourceforge.net/docs/versions_2_3_7.html
Now... is an empty string the right result? maybe ${error?default(!--
null error --)} ?
is that overkill?
Joe
On 1/20/07, Tom
No, not overkill at all. I like that better than my empty string. (The
select tag should probably be updated to output something like that for
null keys and null values)
Tom
Joe Germuska wrote:
Tom:
Thanks for your help... I see now that the syntax I was trying to use
was
added in
