Navigation bar links
I am looking to produce the following mark up: ul lia href=/Home/a/li li class=current About/li lia href=contactContact us/a/li ul the problem is I can not add a conditionally to li. I am using ListView to populate the Items. Can someone give me a hint about how to achieve this ?? Thank you in advance.
Fix for WICKET-3947 and WICKET-4700
Hi! I have a fix/patch for two wicket bugs: https://issues.apache.org/jira/browse/WICKET-3947 https://issues.apache.org/jira/browse/WICKET-3947 and https://issues.apache.org/jira/browse/WICKET-4700 https://issues.apache.org/jira/browse/WICKET-4700 This fix causes three of the junit tests to fail and I could use some help on figuring them out. First two are in org.apache.wicket.markup.html.border.ComponentBorderTest where both of tests cause error. I don't understand what these tests do so I've had problems on locating the problem. Third is in org.apache.wicket.markup.html.internal.InlineEnclosureTest where testInlineEnclosurePage_1 causes error. This test I understand but what I don't understand is why my patch causes this error? If someone could take a look of this patch and could help me locate my problem I would appreciate it. http://apache-wicket.1842946.n4.nabble.com/file/n4651386/Patch_for_WICKET-3947.zip Patch_for_WICKET-3947.zip -Veikko -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Fix-for-WICKET-3947-and-WICKET-4700-tp4651386.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Navigation bar links
You can use a disabled link, which will render as a span. Sven On 08/21/2012 08:10 AM, Mansour Al Akeel wrote: I am looking to produce the following mark up: ul lia href=/Home/a/li li class=current About/li lia href=contactContact us/a/li ul the problem is I can not add a conditionally to li. I am using ListView to populate the Items. Can someone give me a hint about how to achieve this ?? Thank you in advance. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Fix for WICKET-3947 and WICKET-4700
One more thing: Wicket 1.4.x is frozen. Only security related fixes may go in. If we find a fix for these problems we will apply them only in 1.5.x and 6.x On Tue, Aug 21, 2012 at 10:31 AM, Martin Grigorov mgrigo...@apache.org wrote: Hi, Thanks for your contribution! The .zip that you attached is not really a patch :-/ It contains modified (I guess) complete files which I have to diff with the original ones to see what changes you have made... One thing that bothers me a lot is that (Inline)Enclosure functionality requires changes in o.a.w. Component and MarkupContainer. I really don't like Component.java to have logic/knowledge about (Inline)Enclosure. I agree that the bug is annoying but for now I find my workaround as the best solution - just add a dummy WebMarkupContainer in the hierarchy and the bug disappears. On Tue, Aug 21, 2012 at 9:13 AM, Veikko Törmänen veikko.torma...@hotmail.com wrote: Hi! I have a fix/patch for two wicket bugs: https://issues.apache.org/jira/browse/WICKET-3947 https://issues.apache.org/jira/browse/WICKET-3947 and https://issues.apache.org/jira/browse/WICKET-4700 https://issues.apache.org/jira/browse/WICKET-4700 This fix causes three of the junit tests to fail and I could use some help on figuring them out. First two are in org.apache.wicket.markup.html.border.ComponentBorderTest where both of tests cause error. I don't understand what these tests do so I've had problems on locating the problem. Third is in org.apache.wicket.markup.html.internal.InlineEnclosureTest where testInlineEnclosurePage_1 causes error. This test I understand but what I don't understand is why my patch causes this error? If someone could take a look of this patch and could help me locate my problem I would appreciate it. http://apache-wicket.1842946.n4.nabble.com/file/n4651386/Patch_for_WICKET-3947.zip Patch_for_WICKET-3947.zip -Veikko -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Fix-for-WICKET-3947-and-WICKET-4700-tp4651386.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Fix for WICKET-3947 and WICKET-4700
Thank you for the information. I had missed the correct patch protocol and wasn't aware that the 1.4.x was frozen. Apologies. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Fix-for-WICKET-3947-and-WICKET-4700-tp4651386p4651395.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
Use StatelessForm instead. On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote: Hello Recently I found wicket tree control http://wicket-tree.appspot.com/nested and one there is a thing I can't understand: while the page contains Form it looks like not versioned. I mean there are no version number in a url. How does it work then? Is there any clear way to build pages containing Form without explicit version number in url except some black magic involved ( modified MountedMapper ) -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
They are using FormVoid form = new FormVoid(form); and still no version in url on round-trips. Also, FilterForm from Wicket API doesn't extends StatelessForm while your answer states that must be the case. On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote: Use StatelessForm instead. On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote: Hello Recently I found wicket tree control http://wicket-tree.appspot.com/nested and one there is a thing I can't understand: while the page contains Form it looks like not versioned. I mean there are no version number in a url. How does it work then? Is there any clear way to build pages containing Form without explicit version number in url except some black magic involved ( modified MountedMapper ) -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
The deployed examples use Wicket 1.4. http://wicket-tree.appspot.com/?wicket:interface=:0:1::: On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote: They are using FormVoid form = new FormVoid(form); and still no version in url on round-trips. Also, FilterForm from Wicket API doesn't extends StatelessForm while your answer states that must be the case. On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote: Use StatelessForm instead. On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote: Hello Recently I found wicket tree control http://wicket-tree.appspot.com/nested and one there is a thing I can't understand: while the page contains Form it looks like not versioned. I mean there are no version number in a url. How does it work then? Is there any clear way to build pages containing Form without explicit version number in url except some black magic involved ( modified MountedMapper ) -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modal Window set focus
On Aug 20, 2012, at 12:00 PM, Martin Grigorov wrote:
Only form elements can be focused in HTML by default.
To make a normal div focusable you need to add 'tabindex' attribute to it.
I set the focus to the ModalWindow by adding the following attribute:
body onload=window.focus()
...
...
/body
It work. Thanks for your help.
Experiment with Firebug/DevTools first. Find the JS that can focus
your modal window and then just add it in your Java code.
On Mon, Aug 20, 2012 at 12:54 PM, Marco Di Sabatino Di Diodoro
marco.disabat...@tirasa.net wrote:
I add target.appendJavaScript(document.getElementById(' +
editModalWin.getMarkupId() + ').focus(););
But not work...
Here you can found my code:
final AjaxLink createLink = new IndicatingAjaxLink(createLink) {
private static final long serialVersionUID =
-7978723352517770644L;
@Override
public void onClick(final AjaxRequestTarget target) {
editModalWin.setPageCreator(new ModalWindow.PageCreator() {
private static final long serialVersionUID =
-7834632442532690940L;
@Override
public Page createPage() {
return new
EditUserModalPage(Users.this.getPageReference(), editModalWin, new UserTO());
}
});
target.appendJavaScript(document.getElementById(' +
editModalWin.getMarkupId() + ').focus(););
editModalWin.show(target);
}
};
On Aug 20, 2012, at 10:49 AM, Martin Grigorov wrote:
Hi,
You open it with modal.show(target), right ?
Since you have the 'target' you can use it to execute an arbitrary
JavaScript after opening the modal: target.append(someJsToFocus).
The JS should look like: document.getElementById(
+modal.getMarkupId()+ ).focus();
On Mon, Aug 20, 2012 at 11:44 AM, Marco Di Sabatino Di Diodoro
marco.disabat...@tirasa.net wrote:
Hi all,
I want to set the focus to a ModalWindow when it is opened. This allows me
to close the ModalWIndow with the esc key without having to click on it
before.
suggestions?
Thanks
M
--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570
Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net
Apache Syncope PPMC Member
http://people.apache.org/~mdisabatino
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570
Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net
Apache Syncope PPMC Member
http://people.apache.org/~mdisabatino
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570
Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net
Apache Syncope PPMC Member
http://people.apache.org/~mdisabatino
Re: page version and forms
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
If someone wonder how to determine why his page is stateful here is
the solution:
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitorComponent,
Component() {
@Override
public void component(Component component,
IVisitComponent iVisit) {
if (!component.isStateless()) {
LOGGER.info(Stateful component found [
+ component.getClass().getName() + :
+ component.getMarkupId() + ]);
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov mgrigo...@apache.org wrote:
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com
wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail:
Re: page version and forms
The tree node selections are fully handled by ajax requests, so they will (obviously) never change the url of the page. Change the selection of e.g. the dropdown for Content, and you will see that the url changes. There are ways to have forms without version/id information in the URL. Search this list for e.g. NoVersionMount. Such solutions do change how Wicket behaves with the back-button/page-refresh, since a new version of the page will always be returned in that case. On Tue, Aug 21, 2012, at 13:16, Alex Shubert wrote: [...] Anyway: what does your answer has to do with my question? One more time: how that example manage not to increase page version shown in url on every tree node selection? thanks [...] On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote: The deployed examples use Wicket 1.4. http://wicket-tree.appspot.com/?wicket:interface=:0:1::: On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote: They are using FormVoid form = new FormVoid(form); and still no version in url on round-trips. Also, FilterForm from Wicket API doesn't extends StatelessForm while your answer states that must be the case. On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote: Use StatelessForm instead. On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote: Hello Recently I found wicket tree control http://wicket-tree.appspot.com/nested and one there is a thing I can't understand: while the page contains Form it looks like not versioned. I mean there are no version number in a url. How does it work then? Is there any clear way to build pages containing Form without explicit version number in url except some black magic involved ( modified MountedMapper ) -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
It's obvious that selection of leafs (implemented as BookmarcableLinks) is NOT handled by Ajax. BookmarkableFolderContent.java : 62 PageParameters parameters = new PageParameters(); parameters.add(foo, foo.getId()); return new BookmarkablePageLinkVoid(id, tree.getPage() .getClass(), parameters); Or you can take a look at FB console and see network activity. On 21 August 2012 16:48, Pointbreak pointbreak+wicketst...@ml1.net wrote: The tree node selections are fully handled by ajax requests, so they will (obviously) never change the url of the page. Change the selection of e.g. the dropdown for Content, and you will see that the url changes. There are ways to have forms without version/id information in the URL. Search this list for e.g. NoVersionMount. Such solutions do change how Wicket behaves with the back-button/page-refresh, since a new version of the page will always be returned in that case. On Tue, Aug 21, 2012, at 13:16, Alex Shubert wrote: [...] Anyway: what does your answer has to do with my question? One more time: how that example manage not to increase page version shown in url on every tree node selection? thanks [...] On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote: The deployed examples use Wicket 1.4. http://wicket-tree.appspot.com/?wicket:interface=:0:1::: On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote: They are using FormVoid form = new FormVoid(form); and still no version in url on round-trips. Also, FilterForm from Wicket API doesn't extends StatelessForm while your answer states that must be the case. On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote: Use StatelessForm instead. On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote: Hello Recently I found wicket tree control http://wicket-tree.appspot.com/nested and one there is a thing I can't understand: while the page contains Form it looks like not versioned. I mean there are no version number in a url. How does it work then? Is there any clear way to build pages containing Form without explicit version number in url except some black magic involved ( modified MountedMapper ) -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Best regards Alexandr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
The Google Code repo contains 1.5 but the deployed app is using pre-1.5 version.
I can bet on this.
On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
Is there a reason why you don't trust me ? :-)
wicket:interface is no more used in 1.5+, unless the application adds
it explicitly. Wicket (the framework) doesn't use it anymore.
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
Most of them are actually still valid.
There are new pages labeled with wicket15 and wicket6 which refer
to the new features in 1.5 and 6.0 respect.
If someone wonder how to determine why his page is stateful here is
the solution:
There is StatelessChecker in wicket-devutils for this task.
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitorComponent,
Component() {
@Override
public void component(Component component,
IVisitComponent iVisit) {
if (!component.isStateless()) {
LOGGER.info(Stateful component found [
+ component.getClass().getName() + :
+ component.getMarkupId() + ]);
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov mgrigo...@apache.org wrote:
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com
wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: page version and forms
Martin,
does it really makes any difference? Lack of stateless navigation does
( https://issues.apache.org/jira/browse/WICKET-1086 )
Anyway, I explained solution in my prev letter. Thanks!
On 21 August 2012 16:59, Martin Grigorov mgrigo...@apache.org wrote:
The Google Code repo contains 1.5 but the deployed app is using pre-1.5
version.
I can bet on this.
On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
Is there a reason why you don't trust me ? :-)
wicket:interface is no more used in 1.5+, unless the application adds
it explicitly. Wicket (the framework) doesn't use it anymore.
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
Most of them are actually still valid.
There are new pages labeled with wicket15 and wicket6 which refer
to the new features in 1.5 and 6.0 respect.
If someone wonder how to determine why his page is stateful here is
the solution:
There is StatelessChecker in wicket-devutils for this task.
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitorComponent,
Component() {
@Override
public void component(Component component,
IVisitComponent iVisit) {
if (!component.isStateless()) {
LOGGER.info(Stateful component found [
+ component.getClass().getName() + :
+ component.getMarkupId() + ]);
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov mgrigo...@apache.org wrote:
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com
wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
Re: page version and forms
On Tue, Aug 21, 2012 at 4:11 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin,
does it really makes any difference? Lack of stateless navigation does
( https://issues.apache.org/jira/browse/WICKET-1086 )
I'm not sure what you mean by referring to this ticket. I guess you
just found out that your page is stateful because you use
PagingNavigator. I believe it is quite easy to make a stateless
version of the navigator.
Maybe the topic of Wicket 7 should be Stateless.
Anyway, I explained solution in my prev letter. Thanks!
On 21 August 2012 16:59, Martin Grigorov mgrigo...@apache.org wrote:
The Google Code repo contains 1.5 but the deployed app is using pre-1.5
version.
I can bet on this.
On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
Is there a reason why you don't trust me ? :-)
wicket:interface is no more used in 1.5+, unless the application adds
it explicitly. Wicket (the framework) doesn't use it anymore.
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
Most of them are actually still valid.
There are new pages labeled with wicket15 and wicket6 which refer
to the new features in 1.5 and 6.0 respect.
If someone wonder how to determine why his page is stateful here is
the solution:
There is StatelessChecker in wicket-devutils for this task.
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitorComponent,
Component() {
@Override
public void component(Component component,
IVisitComponent iVisit) {
if (!component.isStateless()) {
LOGGER.info(Stateful component found [
+ component.getClass().getName() + :
+ component.getMarkupId() + ]);
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov mgrigo...@apache.org wrote:
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com
wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com
wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
BreadCrumb and page parameters
Hi,
I have the following scenario:
Page A
It's the home page without any params.
Calls page B.
Page B
Calls Page C with a modelobject.
Link teljlink = new Link(beosztottak) {
@Override
public void onClick() {
HRPortalWebSession.getSession().setCurrentPage(BeosztottjaimPage.class);
setResponsePage(new
BeosztottjaimPage(model.getObject()));
// storing the next page in session and calling it with
a modelobject.
}
};
add(teljlink);
Page C
Calls Page D with two params.
Link Blink = new Link(kerdoivkitoltes) {
@Override
public void onClick() {
HRPortalWebSession.getSession().setCurrentPage(KerdoivKitoltesPage.class);
setResponsePage(new
KerdoivKitoltesPage(model.getObject(),entity));
// storing the next page in session and calling it with
a modelobject and an entity param.
}
};
add(Blink);
Page D
My goal is when users click on the breadcrumb path _anywhere_ (eg. Page B)
the page should be called with the appropriate parameters. I store the
current page in my session. Is it possible somehow ?
Thank you in advance!
Regards, Sandor
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/BreadCrumb-and-page-parameters-tp4651412.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Wicket tags in output markup may change styles
Hi!
I was creating a website with Wicket and the CSS styles were fine.
Then I decided to replace some texts with wicket:message / and it
changed the formatting.
I know setStripWicketTags(true), but I prefer to have it working with
setStripWicketTags(false) in dev. mode.
The html is actually a XHTML transitional. The affected style is related
to body * { ... }.
I tried things like body *:* { ... } and it fixed the problem, but
introduced another ones. I'm even not sure this is a valid CSS syntax.
Has anyone have a hint on a good way to solve this problem?
Sorry to not create a quickstart, maybe this is well know thing, but it
never happened to me till now.
Adriano
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Navigation bar links
Thank you a lot.
Both methods did the trick. One last question in the same context. This is
the code I am working with:
list.add(new BookmarkablePageLinkWebPage(link, HomePage.class));
list.add(new BookmarkablePageLinkWebPage(link, About.class));
list.add(new BookmarkablePageLinkWebPage(link,
ContactUs.class));
@SuppressWarnings(unchecked)
ListView listview = new ListView(listview, list) {
protected void populateItem(ListItem item) {
BookmarkablePageLinkWebPage lnk =
(BookmarkablePageLinkWebPage) item
.getModelObject();
String requestedUrl = getRequest().getUrl().getPath();
String linkUrl = getRequestCycle().urlFor(
lnk.getPageClass() , new PageParameters()).toString().substring(2);
logger.debug(requested : + requestedUrl);
logger.debug(current link : + linkUrl);
Label label = new Label(lbl, lnk.getId());
lnk.add(label);
item.add(lnk);
if (linkUrl.equals(requestedUrl)) {
logger.debug(matched link with requested url);
// lnk.setRenderBodyOnly(true);
lnk.setEnabled(false);
}
}
};
add(listview);
I am trying to compare the requested URL to the link url. I need to obtain
the link url. It's no clear to me how to do it in clean way.
I am using:
String linkUrl = getRequestCycle().urlFor(
lnk.getPageClass() , new PageParameters()).toString().substring(2);
This introduced a problem. It works fine if the page is mounted on some
path. But if the link url is something like:
wicket/bookmarkable/com.example.MyPage
Then it breaks. Is there a better way to obtain the url for each link ??
Thank you.
On Tue, Aug 21, 2012 at 2:55 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Or you can do link.setRenderBodyOnly(true);
On Tue, Aug 21, 2012 at 9:30 AM, Sven Meier s...@meiers.net wrote:
You can use a disabled link, which will render as a span.
Sven
On 08/21/2012 08:10 AM, Mansour Al Akeel wrote:
I am looking to produce the following mark up:
ul
lia href=/Home/a/li
li class=current About/li
lia href=contactContact us/a/li
ul
the problem is I can not add a conditionally to li. I am using
ListView
to populate the Items.
Can someone give me a hint about how to achieve this ??
Thank you in advance.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
And the winner is ... Martin!
On AppEngine I still have Wicket 1.4.x running.
Sven
On 08/21/2012 02:59 PM, Martin Grigorov wrote:
The Google Code repo contains 1.5 but the deployed app is using pre-1.5 version.
I can bet on this.
On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
Is there a reason why you don't trust me ? :-)
wicket:interface is no more used in 1.5+, unless the application adds
it explicitly. Wicket (the framework) doesn't use it anymore.
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
Most of them are actually still valid.
There are new pages labeled with wicket15 and wicket6 which refer
to the new features in 1.5 and 6.0 respect.
If someone wonder how to determine why his page is stateful here is
the solution:
There is StatelessChecker in wicket-devutils for this task.
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitorComponent,
Component() {
@Override
public void component(Component component,
IVisitComponent iVisit) {
if (!component.isStateless()) {
LOGGER.info(Stateful component found [
+ component.getClass().getName() + :
+ component.getMarkupId() + ]);
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov mgrigo...@apache.org wrote:
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com wrote:
Martin
with all my respect but their build script uses
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
${wicket.version} derived from parent pom where
wicket.version1.5.0/wicket.version
So,
1. no stateless form
2. it is 1.5
3. it's pretty easy to ensure yourself just by looking into code
http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
can't be compiled under 1.4
Anyway: what does your answer has to do with my question? One more
time: how that example manage not to increase page version shown in
url on every tree node selection?
thanks
On 21 August 2012 14:39, Martin Grigorov mgrigo...@apache.org wrote:
The deployed examples use Wicket 1.4.
http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote:
They are using
FormVoid form = new FormVoid(form);
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states that
must be the case.
On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote:
Hello
Recently I found wicket tree control
http://wicket-tree.appspot.com/nested
and one there is a thing I can't understand: while the page contains
Form it looks like not versioned. I mean there are no version number
in a url.
How does it work then? Is there any clear way to build pages
containing Form without explicit version number in url except some
black magic involved ( modified MountedMapper )
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Best regards
Alexandr
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training,
redirectToInterceptPage and string
Hi, is possible to redirect page like this: redirectToInterceptPage(myPage.html) ? I can do it: redirectToInterceptPage(new MyPage()); But I know only myPage.html and I do not know what Page class it is. So is it any way how to use string and redirectToInterceptPage? Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/redirectToInterceptPage-and-string-tp4651417.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket tags in output markup may change styles
You should at least escape your ':', i.e. something like: BODY
WICKET\:MESSAGE * { }
But I doubt it will work on any browser. If you really want to keep the
wicket:message tags (imho you're better of without them), you could wrap
them in another container (div/span) and use that conatiner as a css
scope to style your messages.
On Tue, Aug 21, 2012, at 17:55, Adriano dos Santos Fernandes wrote:
Hi!
I was creating a website with Wicket and the CSS styles were fine.
Then I decided to replace some texts with wicket:message / and it
changed the formatting.
I know setStripWicketTags(true), but I prefer to have it working with
setStripWicketTags(false) in dev. mode.
The html is actually a XHTML transitional. The affected style is related
to body * { ... }.
I tried things like body *:* { ... } and it fixed the problem, but
introduced another ones. I'm even not sure this is a valid CSS syntax.
Has anyone have a hint on a good way to solve this problem?
Sorry to not create a quickstart, maybe this is well know thing, but it
never happened to me till now.
Adriano
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: redirectToInterceptPage and string
Hi, I don't think there's a direct way to achieve what you want. However, you could instead find the page class mapping to the url and use that in the exception. I'm not too familiar with it, but have a look at Application#getRootRequestMapper() and its mapHandler method. You could perhaps use a MockWebRequest with your url to find out which IPageClassRequestHandler maps to your page. Bertrand On 21/08/2012 1:43 PM, Dan12321 wrote: Hi, is possible to redirect page like this: redirectToInterceptPage(myPage.html) ? I can do it: redirectToInterceptPage(new MyPage()); But I know only myPage.html and I do not know what Page class it is. So is it any way how to use string and redirectToInterceptPage? Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/redirectToInterceptPage-and-string-tp4651417.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Which RENDER_STRATEGY is best for clustered setup?
Hello, We are currently using Apache Wicket 1.5.6 in a clustered setup. We have a custom built distributed session management based on memcached. Due to infrastructure limitations, we cannot use sticky sessions. So I am wondering whether 'ONE_PASS_RENDER' render strategy is the best solution for my use case. Its mentioned below that this still has double submit problem, http://wicket.apache.org/apidocs/1.4/org/apache/wicket/settings/IRequestCycleSettings.html Are there any other knows issues with 'ONE_PASS_RENDER' render strategy? Also what is the use of the below API? getRequestCycleSettings().setBufferResponse(false); Does it make any difference to the render strategy? I guess it makes some difference to 'REDIRECT_TO_BUFFER'. Thanks, Suresh -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
