Re: Question about Resource Management changes in Wicket 8

ameter then it needs to be renamed to work as it did in Wicket 6.x (although the Wicket 7+ docs recommend not to override that method). Regards, Chrisco On 6/06/2024 11:28 pm, Kyle Bibby wrote: Hello, I have a large project that I am upgrading from Wicket 6 to Wicket 8. Yes, it's fairly o

Re: Question about Resource Management changes in Wicket 8

vriendelijke groet, Kind regards, Bas Gooren Op 6 juni 2024 bij 15:28:35, Kyle Bibby (kbi...@avemacorp.com) schreef: Hello, I have a large project that I am upgrading from Wicket 6 to Wicket 8. Yes, it's fairly old. As I am working through the various changes one issue has stumped me. With Wicket

Question about Resource Management changes in Wicket 8

Hello, I have a large project that I am upgrading from Wicket 6 to Wicket 8. Yes, it's fairly old. As I am working through the various changes one issue has stumped me. With Wicket 8, my javascript/CSS resources that are added to my WicketApplication are no longer being automatically added

Re: migration from wicket 8 to 9 -> PageManagerProvider

eed things more up I'm always happy to hear ;) Best, KB - Ursprüngliche Mail - Von: "Sven Meier" An: "users" Gesendet: Mittwoch, 10. November 2021 20:31:52 Betreff: Re: migration from wicket 8 to 9 -> PageManagerProvider Hi Korbinian, it was a real breeze

Re: migration from wicket 8 to 9 -> PageManagerProvider

; > An: "users" > Gesendet: Mittwoch, 10. November 2021 20:31:52 > Betreff: Re: migration from wicket 8 to 9 -> PageManagerProvider > Hi Korbinian, > > > it was a real breeze. I'm very impressed! > > thanks, glad to hear that. > > You application

Re: migration from wicket 8 to 9 -> PageManagerProvider

n On 10.11.21 12:05, Korbinian Bachl wrote: Hi, Im currently migrating our applications from wicket 8 to wicket 9.6 and so far it was a real breeze. I'm very impressed! One thing however that puzzles me is the following code I had in the application init(); set

migration from wicket 8 to 9 -> PageManagerProvider

Hi, Im currently migrating our applications from wicket 8 to wicket 9.6 and so far it was a real breeze. I'm very impressed! One thing however that puzzles me is the following code I had in the application init(); setPageManagerProvider(new DefaultPageManagerProvider

Re: Wicket 8 + 9 on jdk17?

Hi, On Thu, Oct 7, 2021 at 10:09 AM Martin Grigorov wrote: > On Thu, Oct 7, 2021 at 9:57 AM Jeroen Steenbeeke < > j.steenbeeke...@gmail.com> > wrote: > > > My personal Wicket apps (Wicket 9) are all running on JDK17 now. No > > problems so far, other than certain libraries not being able to hand

Re: Wicket 8 + 9 on jdk17?

billions $$$ if something breaks for few hours :-) > > Op do 7 okt. 2021 om 08:52 schreef Korbinian Bachl < > korbinian.ba...@whiskyworld.de>: > > > Hi, > > > > has anyone any details about using of wicket 8.x or 9.x under jdk 17? > > We currently just mig

Re: Wicket 8 + 9 on jdk17?

against JDK release candidates and communicates their findings with the JDK team. Op do 7 okt. 2021 om 08:52 schreef Korbinian Bachl < korbinian.ba...@whiskyworld.de>: > Hi, > > has anyone any details about using of wicket 8.x or 9.x under jdk 17? > We currently just migrated fro

Wicket 8 + 9 on jdk17?

Hi, has anyone any details about using of wicket 8.x or 9.x under jdk 17? We currently just migrated from jdk8 to jdk11 as runtime in production and wicket 8.x was fine under all things (still had some problems with third party libs however). Next we want to go to wicket 9.x but since there

Re: Wicket 8.x Migration Issues with AjaxFallBackLink

Hi, you have to use target.ifPresent(t -> t.add(feedback)); instead of target.get().add(feedback); Trying to get an O Optional with no value present results in the mentioned error. Greetings, Johannes Renoth On 2021-03-23 0:09, Satyavathi Iynaparthi wrote: > Classification: Confidential >

Re: Wicket 8.x Migration Issues with AjaxFallBackLink

Hi, On Tue, Mar 23, 2021 at 7:43 AM Satyavathi Iynaparthi wrote: > Classification: Confidential > I am not sure whether I am allowed to read further. > > Hi Team, > > We are in process of migration our Web application from Wicket 6.30 to > Wicket 8.11.0. > As a first step, placed below jars i

Wicket 8.x Migration Issues with AjaxFallBackLink

Classification: Confidential Hi Team, We are in process of migration our Web application from Wicket 6.30 to Wicket 8.11.0. As a first step, placed below jars in the classpath. wicket-auth-roles-8.11.0.jar wicket-core-8.11.0.jar wicket-datetime-8.0.0-M7.jar wicket-extensions-8.11.0.jar wicket-r

Re: Wicket 8: Content-Security-Policy header

On 2020/11/24 15:49:58, Francesco Chicchiricc�� wrote: > Hi, > in a Wicket 8.8.0 application, I am following what suggested in > > https://ci.apache.org/projects/wicket/guide/8.x/single.html#_external_security_checks > > to add Content-Security-Policy header into response. > > My application e

Wicket 8: Content-Security-Policy header

Hi, in a Wicket 8.8.0 application, I am following what suggested in https://ci.apache.org/projects/wicket/guide/8.x/single.html#_external_security_checks to add Content-Security-Policy header into response. My application extends AuthenticatedWebApplication so, when accessing the root page, I r

Re: Where to download Javadoc for Wicket 8.x?

ar 2, 2020 at 12:49 PM SB wrote: > Okay, I figured it out: > > 1. Download the Apache Wicket source code from > https://wicket.apache.org/start/wicket-8.x.html > 2. Unzip the downloaded file. > 3. To generate Javadocs, run `mvn javadoc:aggregate` at the root of the > source co

Re: Where to download Javadoc for Wicket 8.x?

Okay, I figured it out: 1. Download the Apache Wicket source code from https://wicket.apache.org/start/wicket-8.x.html 2. Unzip the downloaded file. 3. To generate Javadocs, run `mvn javadoc:aggregate` at the root of the source code. 4. The generated Javadocs can then be found in the `./target

Re: Where to download Javadoc for Wicket 8.x?

ma 2. maalisk. 2020 klo 13.43 SB (progscriptcl...@gmail.com) kirjoitti: > > ... plug in the libraries with maven together with the source option ... > > Sorry, I don't understand. Could you explain what you mean by this? > Depending on which IDE you use, try something like: https://stackoverflow.

Re: Where to download Javadoc for Wicket 8.x?

> ... plug in the libraries with maven together with the source option ... Sorry, I don't understand. Could you explain what you mean by this? On Mon, Mar 2, 2020 at 11:35 AM Martin Terra < martin.te...@koodaripalvelut.com> wrote: > I would recommend to plug in the libraries with maven together

Re: Where to download Javadoc for Wicket 8.x?

I would recommend to plug in the libraries with maven together with the source option, this way you have both the wicket source code and the javadoc. ** Martin ma 2. maalisk. 2020 klo 2.01 SB (progscriptcl...@gmail.com) kirjoitti: > I usually work offline, and I need to refer to the Javadocs. Is

Where to download Javadoc for Wicket 8.x?

I usually work offline, and I need to refer to the Javadocs. Is there a place where I can download Wicket's Javadocs for offline use?

Re: thanks for wonderful work with Wicket 8.

Thanks you Ernesto! On Fri, May 24, 2019, 9:03 AM Ernesto Reinaldo Barreiro wrote: > Hi, > > I just created a branch of or application based on 9.X-SNAPSHOT and > bootstrap 4.x-SNAPSHOT and I plan to keep it synchronized, at least once > per week, with our development branch (w

Re: thanks for wonderful work with Wicket 8.

Hi, I just created a branch of or application based on 9.X-SNAPSHOT and bootstrap 4.x-SNAPSHOT and I plan to keep it synchronized, at least once per week, with our development branch (wicket 8.X based). So, before any new milestone releases of 9.x I can use it to test if everything still works

Re: Wicket 8 rendering of components

I'll try that, Thank you for your quick response, Sven! -Ravi -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional comma

Re: Wicket 8 rendering of components

Hi, in Wicket 8.x an Ajax response prepares all components beforehand and only then renders all components afterwards. Simplest fix would be overwriting #onRender() and let it call rendered() on your fake input instead. I'd suggest to skip that unnecessary input altog

Re: Wicket 8 rendering of components

Hi Sven, sure thing, here it is. Thanks! Ravi secure-form-example1.zip -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html -

Re: Wicket 8 rendering of components

Hi, > how would I go about marking components as rendered? Wicket marks components as they are rendered, this isn't something you need/should do. Why aren't you just using a HiddenField? A quickstart would help to understand your problem, especially to compare it with Wicket 7.x. Regards S

Wicket 8 rendering of components

Hi all, I have a question regarding the rendering in Wicket 8.3.0. We have a Wicket 7.2.0 implementation of SecureForm for CSFR prevention similar to what shayy posted here http://apache-wicket.1842946.n4.nabble.com/Implementing-a-SecureForm-to-avoid-CSRF-attacks-td4666175.html Basically we prog

Re: thanks for wonderful work with Wicket 8.

Sounds great.. For minimal effort, I think the notify plugin would fit very well here: https://github.com/l0rdn1kk0n/wicket-bootstrap Under extensions, but it's not my repo.. And yes wicket are wonderful, even after all these years :) And I've been using it on, Guice, OSGI and now with spring bo

Re: thanks for wonderful work with Wicket 8.

Hi, On Fri, May 3, 2019 at 8:39 AM nino martinez wael < nino.martinez.w...@gmail.com> wrote: > I could use the > > Or a wicket wrapper for > > http://bootstrap-notify.remabledesigns.com/. > > I can try to convince my manager to open-source it. We are using it all over in our application in combi

Re: thanks for wonderful work with Wicket 8.

sed. If > > you have the chance to play with it we are looking forward for your > > feedback :-) > > > :-( Unfortunately My customer has a very tight schedule for delivering the > application I just migrated. Even jumping to Wicket 8.x was something we > had to consider very

Re: thanks for wonderful work with Wicket 8.

Hi, > Already done: > https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-9.x > I use it for my Wicket trainings application. > > Haha... It is difficult to beat you in speed :-) > There is something similar here: > > https://github.com/l0rdn1kk0n/wicket-b

Re: thanks for wonderful work with Wicket 8.

rward for your > > feedback :-) > > > :-( Unfortunately My customer has a very tight schedule for delivering the > application I just migrated. Even jumping to Wicket 8.x was something we > had to consider very carefully. All I can offer is if I start some side > personal project, w

Re: thanks for wonderful work with Wicket 8.

umping to Wicket 8.x was something we had to consider very carefully. All I can offer is if I start some side personal project, which sometimes I do, try to use Wicket 9.x. Or help migrating some of the satellite projects, like Wicket bootstrap, to wish I have contributed from time to time, to Wicket 9

Re: thanks for wonderful work with Wicket 8.

features! > > On Thu, Apr 11, 2019 at 11:13 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > I would like to thanks Wicket's development team for wonderful work done > > with wicket 8.x! > > > > Yesterday mid

Re: thanks for wonderful work with Wicket 8.

Thanks to you Ernesto for your support and kind words! I'm happy that the hard work done with Wicket 8 is paying off. PS: we are voting for the first milestone of Wicket 9 to be released. If you have the chance to play with it we are looking forward for your feedback :-) On Thu, Apr 11, 20

Re: thanks for wonderful work with Wicket 8.

thanks Wicket's development team for wonderful work done > with wicket 8.x! > > Yesterday mid morning I started to migrate the application of a customer of > mine to Wicket 8.4 (form WIcket 7.9). By the end of the day I had fixed > almost all compile errors (most of them due to th

thanks for wonderful work with Wicket 8.

Hi, I would like to thanks Wicket's development team for wonderful work done with wicket 8.x! Yesterday mid morning I started to migrate the application of a customer of mine to Wicket 8.4 (form WIcket 7.9). By the end of the day I had fixed almost all compile errors (most of them due t

RE: Exception handling wicket 8

Thanks for fast response, ive created quickstart and attached it to JIRA issue https://issues.apache.org/jira/browse/WICKET-6637 Matus -Original Message- From: Martin Grigorov Sent: Monday, February 18, 2019 1:49 PM To: users@wicket.apache.org Subject: Re: Exception handling wicket 8

Re: Exception handling wicket 8

.3.0. > With wicket 7 everything seemed to be fine, however in wicket 8 we have an > issue > with handling exception. > In Application we have in init() method: > > getRequestCycleListeners().add(new > MyRequestCycleListener()); > > > > MyRequestCycle

Exception handling wicket 8

Hi, recently we have upgraded our application, from wicket 7.11 to wicket 8.3.0. With wicket 7 everything seemed to be fine, however in wicket 8 we have an issue with handling exception. In Application we have in init() method: getRequestCycleListeners().add(new

Re: Wicket 8 and Edge : Known compatibilities problem ?

Hi, We are not aware of any issues with MS Edge. The error message is really strange though! Here is something that I've found: https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_store/youll-need-a-new-app-to-open-this-https/631579eb-4051-42d9-96cc-3909690421e5 On Thu, Jan 24, 2

Wicket 8 and Edge : Known compatibilities problem ?

Hello, I have a wicket application that is Ok with Mozilla. My company will to use windows 10 and Edge. I did some test and I have an error message : You need a new application to see this page. Is this a know bug for edge ? A bad configuration of my HTML code ? a New security option of the net

Re: Wicket 8 CsrfPrevention issue

I add custom original url, and it works! getRequestCycleListeners().add(new CsrfPreventionRequestCycleListener().addAcceptedOrigin("mydomain")); On Mon, Dec 24, 2018 at 9:26 AM Shengche Hsiao wrote: > Thanks Papegaaji, let me try. > > On Sun, Dec 23, 2018 at 8:32 PM Emond Papegaaij > wrote: >

Re: Wicket 8 CsrfPrevention issue

Thanks Papegaaji, let me try. On Sun, Dec 23, 2018 at 8:32 PM Emond Papegaaij wrote: > I checked the answers and comments on that post, and they are > incorrect. When you > place your application behind a reverse http proxy, you need to make sure > the > proxy passes the correct headers to your

Re: Wicket 8 CsrfPrevention issue

I checked the answers and comments on that post, and they are wrong. When you place your application behind a reverse http proxy, you need to make sure the proxy passes the correct headers to your application and you application needs to use these headers. For WildFly, you need to add proxy-add

Re: Wicket 8 CsrfPrevention issue

I checked the answers and comments on that post, and they are incorrect. When you place your application behind a reverse http proxy, you need to make sure the proxy passes the correct headers to your application and you application needs to use these headers. For WildFly, you need to add proxy-ad

Re: Wicket 8 CsrfPrevention issue

Thanks, I'll check it out. On Sun, Dec 23, 2018 at 2:31 AM Chris Turchin wrote: > This might help: > > https://stackoverflow.com/questions/46337253/apache-reverse-proxy-and-wicket-csrfpreventionrequestcyclelistener > > On Sat, Dec 22, 2018 at 3:28 AM ShengChe Hsiao wrote: > > > > Dear all > > >

Re: Wicket 8 CsrfPrevention issue

This might help: https://stackoverflow.com/questions/46337253/apache-reverse-proxy-and-wicket-csrfpreventionrequestcyclelistener On Sat, Dec 22, 2018 at 3:28 AM ShengChe Hsiao wrote: > > Dear all > > I use apache httpd as wildlfy's backend proxy server to redirect http > request to https request,

Wicket 8 CsrfPrevention issue

Dear all I use apache httpd as wildlfy's backend proxy server to redirect http request to https request, when i add CsrfPreventionRequestCycleListener to my application , it showd error message: [org.apache.wicket.protocol.http.CsrfPreventionRequestCycleListener] (default task-48) Possible CSRF a

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

gt;> component hierarchy yet > >> - #updateBranch() does not find any branch for the node's model and > >> doesn't add anything to the ART > >> > >> So yes, we have a change, but no bug. In 7.x adding of the branch to the > >> ART was just ignore

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

add anything to the ART So yes, we have a change, but no bug. In 7.x adding of the branch to the ART was just ignored. You can achieve the same in Wicket 8.x with the following: protected Component newContentComponent(String id, IModel node) { if(haveClicked){

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

y yet > - #updateBranch() does not find any branch for the node's model and > doesn't add anything to the ART > > So yes, we have a change, but no bug. In 7.x adding of the branch to the > ART was just ignored. > > You can achieve the same in Wicket 8.x with the fol

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

ART So yes, we have a change, but no bug. In 7.x adding of the branch to the ART was just ignored. You can achieve the same in Wicket 8.x with the following:     protected Component newContentComponent(String id, IModel node) {     if(haveClicked){                     // #e

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

tring id, IModel model) { TreeNode node = > >>>>> model.getObject(); if (node instanceof > TreeNodeProvider.PartitionNode) { > >>>>> Partition partition = ((TreeNodeProvider.PartitionNode) > >>>>> node).getPartition(); if > >>>>>

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

gSettings(new ThrottlingSettings(searchTerm.getMarkupId(), Duration.milliseconds(400), true)); } }); But I get an this error message in wicket 8, my line below: 2018-11-28 14:26:44,127 | ERROR | qtp938432184-652 | DefaultExceptionMapper | 136 - org.apache.wicket.core - 8.1.0 | Unexpected error o

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

eeNodeProvider.NoPartitionNode && isNoPartitionProfilesPresent()) {* >>>> expand(node);* } } The triggering field: searchTerm.add(new >>>> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void >>>> onUpdate(AjaxRequestTarget target) { if

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

titionNode && isNoPartitionProfilesPresent()) {* >>> expand(node);* } } The triggering field: searchTerm.add(new >>> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void >>> onUpdate(AjaxRequestTarget target) { if (searchTermModel.getO

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

) { if (searchTermModel.getObject() != >> null && !searchTermModel.getObject().isEmpty()) { >> profilePartitionTree.rebuildExpandedPartitions(); } else { >> profilePartitionTree.getP >> artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);*

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

e { > profilePartitionTree.getP > artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);* } > @Override protected void updateAjaxAttributes(AjaxRequestAttributes > attributes) { super.updateAjaxAttributes(attributes); > attributes.setThrottlingSettings(new > ThrottlingSettings(

Re: Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

rtitionTree);* } @Override protected void updateAjaxAttributes(AjaxRequestAttributes attributes) { super.updateAjaxAttributes(attributes); attributes.setThrottlingSettings(new ThrottlingSettings(searchTerm.getMarkupId(), Duration.milliseconds(400), true)); } }); But I get an this error message in wicke

Wicket 6.x -> Wicket 8.x extensions NestedTree expand fails ( Components can no longer be added)

AjaxAttributes(AjaxRequestAttributes attributes) { super.updateAjaxAttributes(attributes); attributes.setThrottlingSettings(new ThrottlingSettings(searchTerm.getMarkupId(), Duration.milliseconds(400), true)); } }); But I get an this error messa

Re: Wicket 8 ModalWindow autosizing problem

Thanks for the tip. https://issues.apache.org/jira/browse/WICKET-6613 -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additiona

Re: Wicket 8 ModalWindow autosizing problem

Thanks for the tip. https://issues.apache.org/jira/browse/WICKET-6613 -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additiona

Re: Wicket 8 ModalWindow autosizing problem

http://examples8x.wicket.apache.org/ajax/modal-window also loads fine but I think there is no auto-sizing there. Try to reproduce it in a quickstart application and attach it to a ticket in JIRA. On Wed, Nov 7, 2018 at 1:21 PM daniel wrote: > I updated the version and modal.css seems to load fin

Re: Wicket 8 ModalWindow autosizing problem

I updated the version and modal.css seems to load fine (modal-ver-154158884.css). -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.or

Re: Wicket 8 ModalWindow autosizing problem

Hi, Please update Wicket to 8.1.0. Then check whether there is any problem with the loading of modal.css in your browser Dev Tools > Network tab. On Wed, Nov 7, 2018 at 11:01 AM daniel wrote: > Hi, > > I've recently upgraded my project from Wicket version 6 to 8.0.0-M9 and > autosizing of Modal

Wicket 8 ModalWindow autosizing problem

Hi, I've recently upgraded my project from Wicket version 6 to 8.0.0-M9 and autosizing of ModalWindows suddenly stopped working. All ModalWindows are either too big or too small, in that case the scrollbar appears. I need my ModalWindows to be autosized so the content fits perfectly without any s

Re: WebSocket tests fail after migration to Wicket 8

Yes, I can confirm 8.2.0-SNAPSHOT works. Thank you, Manfred -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional command

Re: WebSocket tests fail after migration to Wicket 8

-core-8.1.0.jar:8.1.0] at org.apache.wicket.protocol.ws.api.BaseWebSocketBehavior.renderHead(BaseWebSocketBehavior.java:128) ~[wicket-native-websocket-core-8.1.0.jar:8.1.0] Is there something that must change for testing WebSocket behavior in Wicket 8? Regards, Manfred

WebSocket tests fail after migration to Wicket 8

testing WebSocket behavior in Wicket 8? Regards, Manfred

Re: Wicket 8 : OSGI wiring problem with junit framework.

pom.xml of wicket project https://github.com/apache/wicket/blob/wicket-8.x/pom.xml set the dependency for junit junit *true* provided as optional true as

Re: Wicket 8 : OSGI wiring problem with junit framework.

Is this issue has been tested successfully by its reporter. Did i miss anything? We are using junit : 4.12, on bundle start getting the BundleException Unresolved constraint in bundle org.apache.wicket.core [34]: Unable to resolve 34.0: missing requirement [34.0] osgi.wiring.package; (osgi.wirin

Re: Wicket 8 : OSGI wiring problem with junit framework.

Hi, On Tue, Aug 21, 2018 at 12:13 PM SUBRA wrote: > HI, > > I'm migrating to wicket-8, getting osgi wiring problem with junit framework > osgi.wiring.package=junit.framework > > Jira issue, created with similar issue, is in resolved state but > apparently > it i

Wicket 8 : OSGI wiring problem with junit framework.

HI, I'm migrating to wicket-8, getting osgi wiring problem with junit framework osgi.wiring.package=junit.framework Jira issue, created with similar issue, is in resolved state but apparently it is not. https://issues.apache.org/jira/browse/WICKET-6509 <https://issues.apache.org/jir

Re: Nice article on Wicket 8 by the New Stack

Very nice! Thanks for sharing! :)

Re: Nice article on Wicket 8 by the New Stack

Nice indeed! Thank you! On Tue, Jun 12, 2018 at 6:40 AM, Sven Meier wrote: > Many thanks, that's great! > > Sven > > Am 12. Juni 2018 00:20:53 MESZ schrieb Martijn Dashorst < > martijn.dasho...@gmail.com>: > >https://thenewstack.io/wicket-8-whats-new-and-wha

Re: Nice article on Wicket 8 by the New Stack

Many thanks, that's great! Sven Am 12. Juni 2018 00:20:53 MESZ schrieb Martijn Dashorst : >https://thenewstack.io/wicket-8-whats-new-and-whats-next-for-the-server-side-java-web-framework/ > >Martijn > >- >

Nice article on Wicket 8 by the New Stack

https://thenewstack.io/wicket-8-whats-new-and-whats-next-for-the-server-side-java-web-framework/ Martijn - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

he outside. Thanks a lot Martin! That saves me from doing any JCR/ Brix related hacking as I can now internally map the pages/ paths as I need it :) - Ursprüngliche Mail - > Von: "Martin Grigorov" > An: users@wicket.apache.org > Gesendet: Montag, 11. Juni 2018 12:

Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

gt; Von: "Bas Gooren" > > An: users@wicket.apache.org, "Korbinian Bachl" < > korbinian.ba...@whiskyworld.de> > > Gesendet: Montag, 11. Juni 2018 12:06:12 > > Betreff: Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper > > > Hi! > > >

Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

Thanks for pointing me to this! - Ursprüngliche Mail - > Von: "Martin Grigorov" > An: users@wicket.apache.org > Gesendet: Montag, 11. Juni 2018 12:11:32 > Betreff: Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper > Hi, > > The main method for m

Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

ed to make sure I'm the first one in the hierarchy. But where would I then rewrite the generated URLs? Best, KB - Ursprüngliche Mail - > Von: "Bas Gooren" > An: users@wicket.apache.org, "Korbinian Bachl" > > Gesendet: Montag, 11. Juni 2018 12:06:12

Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

Hi, The main method for mounting is WebApplication#mount(IRequestMapper). It uses getRootRequestMapperAsCompound().add(mapper);, i.e. no matter whether your root mapper is already compound or not, Wicket will make it compound by wrapping it in SystemMapper https://github.com/apache/wicket/blob/9

Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

Hi! The Compound mapper is merely a wrapper which can have many child mappers. The Root mapper is the mapper that wicket calls to do mapping and reverse mapping. For wicket itself it’s not important whether it is a mapper or compound mapper. The higher up in the mapper hierarchy (root -> compound

wicket 8 / RootRequestMapper vs CompoundRequestMapper

Hi, situation: I need to add some "special" URL handling for certain URLs to have product pages and catalog pages on root. As we also use brix we already have at least one compoundRequestMapper already in use. Now, wicket seems to have 2 places for that. A new RootRequestMapper e.g.: YourAppli

Re: ChainingModel warnings in Wicket 8

target = modelObject; > >> } > > > > > > It should read something like: > > > > if (modelObject != null && modelObject instanceof Serializable == false) > > > > > > Best, > > > > Thomas > > > > > > On Thu, Jun 7

Re: ChainingModel warnings in Wicket 8

le >> instance "); >> } >> target = modelObject; >> } > > > It should read something like: > > if (modelObject != null && modelObject instanceof Serializable == false) > > > Best, > > Thomas > > > On Thu, Jun 7, 2018

Re: Release WiQuery for Wicket 8

On donderdag 7 juni 2018 17:10:16 CEST Martin Grigorov wrote: > 8.0 is on its way to Maven Central! Thanks for the help with the release Martin, and Thomas thanks for testing! Emond - To unsubscribe, e-mail: users-unsubscr...@

Re: Release WiQuery for Wicket 8

; > > > >> > > > Did you change something about test-jar configuration? I do not > see > > >> > > > `test-jar` generation enabled in the POM file. > > >> > > > > > >> > > > On Wed, Jun 6, 2018 at 11:43 AM, Emo

Re: Release WiQuery for Wicket 8

t; > > > >> > > > emond.papega...@topicus.nl> wrote: > >> > > >> Hi Thomas, > >> > > >> > >> > > >> The easiest way is to just run 'mvn install' and depend on > >> > > >&g

Re: ChainingModel warnings in Wicket 8

instanceof Serializable == false) Best, Thomas On Thu, Jun 7, 2018 at 4:25 PM, Thomas Heigl wrote: > Hi all, > > After porting our app to Wicket 8, I'm getting these warnings on my test > environment: > > WAR o.a.w.model.ChainingModel It is not a good idea to refer

Re: Release WiQuery for Wicket 8

> > >> tests >> > > >> on some CI server, you probably have to push the artifacts to a >> local >> > > >> repo >> > > >> also. >> > > >> >> > > >> Best regards, >> > > >> E

ChainingModel warnings in Wicket 8

Hi all, After porting our app to Wicket 8, I'm getting these warnings on my test environment: WAR o.a.w.model.ChainingModel It is not a good idea to reference a > non-serializable instance in models directly as it may lead to > serialization problems The warning is OK, but

Re: Release WiQuery for Wicket 8

Emond, > > > >> > > > > >> > How can I test this? Did you do a milestone release or do I have > to > > > >> > > > >> build > > > >> > > > >> > from source and push to my local artifact repo? > > >

Re: Release WiQuery for Wicket 8

ut the UI > > >> > > > API > > >> > > > > >> > > might > > >> > > > > >> > > > change a bit before the 8.0 release. > > >> > > > > > >> > > > Best regards,

Re: Release WiQuery for Wicket 8

n Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < > >> > >> emond.papega...@topicus.nl> > >> > >> > wrote: > >> > > I've just pushed a massive upgrade of all components. Removed all > >> > > deprecated > >>

Re: Release WiQuery for Wicket 8

2018 at 3:01 PM, Emond Papegaaij < > >> > >> emond.papega...@topicus.nl> > >> > >> > wrote: > >> > > I've just pushed a massive upgrade of all components. Removed all > >> > > deprecated > >> > > part

Re: Release WiQuery for Wicket 8

cus.nl> >> > wrote: >> > > I've just pushed a massive upgrade of all components. Removed all >> > > deprecated >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and >> > > refactoring. >> > > Please test the cha

  1   2   >