I know your problems solved, but this is how I did it last night..
ec:column property=actions title=nbsp;
ww:url id=editUrl action=buildDefinition method=input
ww:param
name=projectGroupId${pageScope.buildDefinitionSummary.projectGroupId}/ww:param
Ok, the problem is resolved: I upgraded the web.xml to the 2.4
specification. Tomcat correctly uses the 1.0 jstl and applies other 2.3
behaviours if the web.xml is version 2.3, whereas jetty probably always
uses the 2.4 spec, which is why that works there (although jetty:run
doesn't work
The later is most definitely better. It allows you to keep your URLs
independent. For example, with the repository browse actions in Archiva,
the mapper will convert the action parameters into
/browse/group/artifact/version instead of
browse.action?group=...artifactId=... etc
- Brett
On
reason is in the other mail. use ww:url for getting action urls (for
which there is no standard equivalent).
I use c: forEach instead of ww:iterator and so on, though.
- Brett
On 17/8/06 2:59 AM, Carlos Sanchez wrote:
What's the advantage of using webwork ww:url and other ww tags when
me too.
Emmanuel
Brett Porter a écrit :
Since it's an action URL, I strong suggest using ww:url instead.
- Brett
On 16/08/2006 12:04 PM, Carlos Sanchez wrote:
i've seen this problem with tomcat. Works fine with jetty.
Please add a jira to put back the right url composition, your changes
