On 5/16/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
what is by the way "${basep}"  ?
that looks like the context path of the app.

I was thinking about the context path. I can think of other use cases, but then it may be more appropriate to just modify attributes.
 

This is already done by wicket.

Thanks - I'll check it out.

johan



On 5/15/06, Yuri Magrisso <[EMAIL PROTECTED]> wrote:
Thanks for the answers!

Filters seem to be exaclty what I had in mind. Do you know how can I register a custom filter? Looks like I have to use MarkupParser.appendMarkupFilter, but how do I get the markup parser?

Yuri


On 5/15/06, Johan Compagner < [EMAIL PROTECTED]> wrote:
you could also use a Filter for that to find replace stuff.

johan



On 5/15/06, Bruno Borges <[EMAIL PROTECTED] > wrote:
I don't think wicket has support for what you are asking for, but I can think in one possibility which is the use of Velocity to pre-render the html before wicket.



On 5/14/06, Yuri Magrisso <[EMAIL PROTECTED]> wrote:
Hi,

Is there a way to define a parameter in the HTML markup, which is not specific for a component and is replaced when the markup tree is rendered. Consider for example the following HTML:

<html>
<header>
<script src="" ... />
<link href="" ... />
</header>
<body>
  <table>
    <tr><td><img src="" /></td><td>Some Text A</td></tr>
    <tr><td><img src="" /></td><td>Some Text B</td></tr>
    <tr><td><img src="" /></td><td>Some Text C</td></tr>
     ....
  </table>
</body>
</html>

I want to be able to replace ${basep} without declaring a component. In the given example it seams better to just declare a component inside a repeater, but In more complex scenarios where the same text (base path) is repeated across variety of tags, which are not repetitive it seams simpler to just declare a markup variable and have it replaced without writing / declaring componets just for the purpose.

Thanks,
Yuri



--
Bruno Borges
Summa Technologies




Reply via email to