Hello all,
I've to upgrade a web application built on Wikcet 1.3.6 to wicket 1.4.13.
In my webapp I have a class which extends
WicketMessageResolver.MessageLabel.
When I updated my Maven dependency to wicket 1.4.13 I noticed that
MessageLabel was no more in the Wicket API.
What class replaced
Hi Igor, thanks for your answer, but I think it doesn't fit my situation.
To explain better, I post the code similar to the class that must be changed
in order to be upgraded to 1.4.13.
---
import
What if I try to extend org.apache.wicket.markup.html.basic.Label?
Will it work when I extended MessageLabel?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/MessageLabel-vanished-in-Wicket-1-4-x-tp3050632p3053186.html
Sent from the Users forum mailing list archive
hello all,
in the process og upgrading from Wicket 1.3.x to 1.4.x a lot of my markup
model raise some exception.
One that often occurr is this one:
WicketMessage: close tag not found for tag: . Component: [MarkupContainer
[Component id = toolbar]]
I don't understand what that means, since it
Sorry, I didn't paste all the code :(
Here is the correct one where the span with is toolbar appears
wicket:panel
caption class=tableCaption
/caption
thead class=rowH
/thead
tbody
tr wicket:id=rows
td wicket:id=cells
[cell]
/td
/tr
/tbody
tfoot
I am very sorry, but it seems like a portion of the code I paste is being
stripped when I post it.
This is the code that's nested inside the thead tag
span wicket:id = topToolbars
span wicket:id = toolbar / span
Hope it's readable now (all those whitespaces are not in the original
Hi Andrea, thank you.
In the original code the span tags are properly closed.
Is it possible that in the 1.4.x versions nested span tags are not allowed
(at least the ones with a wicket:id?
Andrea Del Bene-2 wrote:
Hi Andrea,
maybe have you just missed close tag for topToolbars
Matt, thank you, but original code has no whitespaces.
To add, more the html markup worked perfectly in my app with Wicket 1.3.6
while all seems to break when I upgrade to Wicket 1.4.13
--
View this message in context:
Basically, it is a (supposed) bug in version 1.4.13, something very similar
to this
https://issues.apache.org/jira/browse/WICKET-2620
Downgrading to 1.4.5 solved my issue.
--
View this message in context:
Hi, here's a new episode of my Wicket upgrade saga.
Hope I'm not disturbing anyone :D
In my application developed with Wicket 1.3.6 I have a
CarMessages.properties file which was sort of shared by two classes
CarListPage and CarDetail, since they use the same messages.
When I upgraded to 1.4 all
Hi,
Martin Grigorov-4 wrote:
What is the relation between CarMessages.java (if there is such file)
and CarDetail.java
?
Does the one extend/implement the other ?
On Thu, Nov 25, 2010 at 10:11 AM, adam.gibbons
adam.s.gibb...@gmail.comwrote:
There's no CarMessages.java, just the two
One thing that I just noticed is that in every class I have this problem I
had to change the invocation of the method getModel() to getDefaultModel(),
according to the migration guide to 1.4.
Can the problem be there (honestly, I don't think so but, who knows, I'm
just a Wicket newbie)
Andrea
Hi everybody,
I'd like to implement a mechanism of ETags in my wicket application.
What I would like to achieve is to avoid rendering of wicket model
components if it's not necessary.
In order to do this I'll keep a registry of modified elements and render
them only if they are changed.
What
13 matches
Mail list logo
