I haven't read any of this thread, so forgive me if I'm totally off base
here. If we're talking about a velocity view, $someMethod() won't work
afaik. Anything in the form $foo is considered a property, not a method,
and can't accept parameters. $foo looks for getFoo() in the context. This
came up
Yes, these are velocity views I'm using w/ WW actions.
I haven't read any of this thread, so forgive me if I'm totally off
base
here. If we're talking about a velocity view, $someMethod() won't work
afaik. Anything in the form $foo is considered a property, not a
method,
and can't accept
Title: Message
I
think this should just be
ww:url page="smallImageURL"/
I
think.
Most
all of the attribute values are evaluated, so this will try to get the
smallImageURL property from the ValueStack.
Can
someone verify?
-Original Message-From: Andre Mermegas
All,
We are currently evaluting the framework to use for our new CRM product. I'm
bias towards webwork and really like many of the features plan for webwork 2.0
( I've been using webwork and are not entirely happy with the current version
).
So, my concern now is the schedule of webwork 2.0 and
Low,
I don't know about anyone else's dates, but I'm giving a presentation on
WebWork 2 at The Server Side's Symposium in mid June, so it will be stable,
tested and released by then ;)
And as for WW + Velocity + Hibernate + SiteMesh, yes that is a killer
combination of tools.
Cheers,
Mike
On
What sort of design pattern would you recommend for using/glue the four library
together ? Or may be all this can be use in a very loose couple manner and it
just fall in place nicely ? I think I've heard many time that the combination
of the four tool together are great but haven't come across
