> <param name="file" value="{{URL HERE}}">
Put some wicket:id on that, then add a WebComponent for it that you add
an AttributeModifier to, which sets the "value" attribute.
> When I try to do the obvious, replace the {{URL_HERE}} part
> with <span wicket:id="downloadMsf"></span> it complains
> about non-valid XML and such.
There are basically two groups of web frameworks:
The "strict" group parses the HTML in the templates and (if they use
their own tags) requires the templates to conform to XHTML syntax. Tags
and attributes specific to the framework form parts of "proper" XML
namespaces. Wicket, Facelets and Tapestry belong to this group as far as
I know. These are the more powerfuil since they can manipulate the DOM
at render time while maintaining a designer-friendly template without
too much mess.
The "lenient" group only bothers with its own tags/commands etc. and
treats the rest of the template as just text that should be outputted to
the stream without a question about structure. JSP, Velocity, Webmacro
and many others belong to this group, which is large because it is far
easier to write parsers for this approach, for some definitions of
"easier" :). This is the reason you can do e.g. <a href="<%= url %>"> in
JSP because JSP turns that into outputting of the string "<a href=\"",
the value of url, then the string "\">". It never "sees" the a element.
However, since it deals with JSP and JSTL tags in the same step, you
cannot do e.g. <c:if test="<%= somevariable %>"> but need to use EL
instead.
(Did I mention that JSP is a horrid mess and EL is just mascara on a
pig? Well, consider it mentioned. :) )
- Tor Iver
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
