https://cwiki.apache.org/WICKET/rendering-panel-to-a-string.html
2011/8/7 Joe Fawzy :
> Hi
> is there something equivelant to fragment caching in wicket?
> I mean , is there any way to cache the generated markup of a component, and
> on subsequent requests it just render this markup string?
> if
I'm just curious about this: are you having performance issues?
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Sat, Aug 6, 2011 at 9:01 PM, Joe Fawzy wrote:
> Hi
> is there something equivelant to fragment caching in wicket?
> I mean , is there any way to cache the generated markup
>
> As for your suggestion to attach the sources, well, often I use quite many
> libraries (Lucene, Hibernate..) and it would generally speaking get rather
> impractical to attach the sources of all of them. Also kind of defies the
> idea of a /library/..
>
I don't know what your development envir
Hi
it seems that
item.add(new TextField("itemId", new
PropertyModel(item.**getModel(),
"itemId")));
should be
item.add(new TextField("itemId", new
PropertyModel(item.**getModelObject(),
"itemId")));
Joe
On Mon, Aug 1, 2011 at 6:35 PM, Mike Mander wrote:
> Hi,
>
> i would like to build up a s
Hi
is there something equivelant to fragment caching in wicket?
I mean , is there any way to cache the generated markup of a component, and
on subsequent requests it just render this markup string?
if so, how one can store these fragments in external store? how that can be
configured or plugged in
What I meant with 'radical' changes is that there are many classes that for
example have disappeared from the API, or have become abstract where before
they were not, things like that.. in some cases these classes were not
marked 'deprecated' in 1.4 and yet they're gone in 1.5.
As a result, many o
On Sun, Aug 7, 2011 at 1:38 AM, heikki wrote:
> Yes, from looking at the code it certainly seems as if it should work..
>
> As for your suggestion to attach the sources, well, often I use quite many
> libraries (Lucene, Hibernate..) and it would generally speaking get rather
> impractical to attac
Yes, from looking at the code it certainly seems as if it should work..
As for your suggestion to attach the sources, well, often I use quite many
libraries (Lucene, Hibernate..) and it would generally speaking get rather
impractical to attach the sources of all of them. Also kind of defies the
id
sorry, did not escape html in my post. That should be:
with
# contact
in the HTML.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/URLs-without-counter-parameter-tp3724144p3724147.html
Sent from the Users forum mailing list archive at Nabble.com.
-
Hello,
I'm using Wicket 1.5M3 and I'm trying to have nice-looking URLs in my web
app.
The URLs produced by the code as below are almost perfect, except for one
detail: always, there is a counter appended, reflecting the number of
requests made in this session.
For example I get http://localhost
I tested in 1.4 and it worked. There's more error checking in 1.5, but it
essentially looks the same.
http://svn.apache.org/repos/asf/wicket/trunk/wicket-core/src/main/java/org/apache/wicket/markup/parser/filter/WicketMessageTagHandler.java
I recommend spending the time to attach the Wicket source
Hmm I don't have Wicket source at hand, just using the compiled libraries.
Could it be that it works differently in the Wicket version I'm using (1.5
M3) ?
I tested this:
and this (reversed order in comma-separated list):
and the resu
I'm pretty sure it's supposed to work as Martin described. Why don't you
breakpoint WicketMessageTagHandler.AttributeLocalizer.onComponentTag() and
see what's going on. It looks straight forward, expr.split(",") and all.
On Sat, Aug 6, 2011 at 9:05 AM, heikki wrote:
> hi,
>
> thanks, but that do
hi Dan,
you're right ! The translation as such is working fine, it's just the
preserved element that is also displayed in the page's
title.
Am I right that in non-development mode, the wicket elements are stripped
from the page? In that case I can live with them while developing, now that
it's c
hi,
thanks, but that doesn't work; only the first in the comma-separated list
gets translated.
Anyone have an idea how to do this ?
thanks
kind regards
Heikki Doeleman
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/i18n-for-more-than-attribute-tp3722544p3723525.ht
s/goes/goes away/ :)
On Sat, Aug 6, 2011 at 8:48 AM, Dan Retzlaff wrote:
> If I recall correctly, the string literal "" goes
> deployment mode. We haven't internationalized our site yet, so I can't speak
> to any potential bug with locale-specific resource lookups. You might try
>
> ...
>
> wit
If I recall correctly, the string literal "" goes deployment
mode. We haven't internationalized our site yet, so I can't speak to any
potential bug with locale-specific resource lookups. You might try
...
with a corresponding Label and ResourceModel. We did that just to get rid of
the in develop
it is something like:
wicket:message="title:translationkey,alt:altTranslationKey"
On Sat, Aug 6, 2011 at 3:47 AM, heikki wrote:
> Hello,
>
> I'm trying to make my site available in several languages, and mostly things
> work fine. But I'm wondering how to apply translations to more than one
> att
hi Martin,
thanks for your suggestion, but it made no difference. I tried
http://wicket.apache.org/";>
Bienvenue à
Braziland
and it's the same, no translated title shown, but instead the
appears as the title.
What am I doing wrong here? Surely it must be possible to use i18n for
heade
19 matches
Mail list logo
