Re: Question about Resource Management changes in Wicket 8

[Chris Colman]

When you mentioned overriding renderHead it triggered a memory of a 
change to the API from Wicket <= 6 to Wicket >=7:


"org.apache.wicket.Component#renderHead(HtmlHeaderContainer) is renamed 
to Component#internalRenderHead(HtmlHeaderContainer) WICKET-4964
Component#renderHead(HtmlHeaderContainer) was very similar to the 
usually used Component#renderHead(IHeaderResponse). So it has been 
renamed to avoid any confusions."


I'm not sure if it's related to your issue but if you were previously 
overriding the renderHead that takes a HtmlHeaderContainer as a 
parameter 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 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 to my wicket
pages.

In my project there are helper classes where a number of resources are
defined. Examples of these helper classes are as follows:

public class JS {

public static final JavaScriptResourceReference JQUERY_UI = jquery(
JS.class, "jquery-ui.min.js" );

public static final JavaScriptResourceReference D3 = new
JavaScriptResourceReference( JS.class, "d3.min.js" );


public static void initChartJSBundle( Application wicketApp ) {

return wicketApp.getResourceBundles().addJavaScriptBundle(
JS.class, "chart.js", JQUERY_UI, D3);

}
}

public class CSS {

public static final CssResourceReference ICONS = css( "icons/icons.css" );

public static void initCSSResources( WebApplication wicketApp ) {

wicketApp.mountResource( "css/icons.css", CSS.ICONS );

}
}

Normally, widely used resources are added to my Wicket Application by
making calls to these helper classes in the init():

public abstract class MyApplication extends WebApplication {

public MyApplication() { }


@Override

public void init() {

JS.initChartJSBundle( this );

CSS.initCSSResources( this );

  }

}

I'm aware that resources are typically added to pages/components by
overriding the renderHead() method. I am in fact doing this for resources
that are specific to particular pages. However, for widely used resources,
the above example is all that was required for my Wicket 6 project to make
resources available and automatically included as headers on my Wicket
Pages. This does not seem to be the case with Wicket 8 as my resources are
not being included on any rendered pages. I have scoured the changelogs for
Wicket 8 and haven't found anything referring to the changes with resource
management.
Is there something I'm missing? Is the Wicket 6 behaviour something that
was removed over a preferred method for resource management? If so, what is
this method?

Thanks,

--
Regards,

Chris Colman
*Feezily*,
A product of /Step Ahead/ *Software* Pty Ltd
Web: feezily.com.au <http://feezily.com.au> Em: chr...@stepahead.com.au 
Ph: 02 9656 1278

Re: Question about Resource Management changes in Wicket 8

[Bas Gooren]

Hi Kyle,

I’ve been using for Wicket for a long time and have never seen anything
like what you describe (auto-adding of resources).

Just to check my assumptions I had a look again at the source code of
wicket’s application, webapplication and page classes for the 6.21 tag, and
don’t see any code that would do this for you.

Having said that, this should be rather easy to do yourself: just add a
component initialization listener to your app, check if the component is a
page, and then add a behavior which contributes your resources and/or
bundles to the head section on render.

Met 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 8, my javascript/CSS resources that are added to my
WicketApplication are no longer being automatically added to my wicket
pages.

In my project there are helper classes where a number of resources are
defined. Examples of these helper classes are as follows:

public class JS {

public static final JavaScriptResourceReference JQUERY_UI = jquery(
JS.class, "jquery-ui.min.js" );

public static final JavaScriptResourceReference D3 = new
JavaScriptResourceReference( JS.class, "d3.min.js" );


public static void initChartJSBundle( Application wicketApp ) {

return wicketApp.getResourceBundles().addJavaScriptBundle(
JS.class, "chart.js", JQUERY_UI, D3);

}
}

public class CSS {

public static final CssResourceReference ICONS = css( "icons/icons.css" );

public static void initCSSResources( WebApplication wicketApp ) {

wicketApp.mountResource( "css/icons.css", CSS.ICONS );

}
}

Normally, widely used resources are added to my Wicket Application by
making calls to these helper classes in the init():

public abstract class MyApplication extends WebApplication {

public MyApplication() { }


@Override

public void init() {

JS.initChartJSBundle( this );

CSS.initCSSResources( this );

}

}

I'm aware that resources are typically added to pages/components by
overriding the renderHead() method. I am in fact doing this for resources
that are specific to particular pages. However, for widely used resources,
the above example is all that was required for my Wicket 6 project to make
resources available and automatically included as headers on my Wicket
Pages. This does not seem to be the case with Wicket 8 as my resources are
not being included on any rendered pages. I have scoured the changelogs for
Wicket 8 and haven't found anything referring to the changes with resource
management.
Is there something I'm missing? Is the Wicket 6 behaviour something that
was removed over a preferred method for resource management? If so, what is
this method?

Thanks,
-- 
*Kyle Bibby**|* Software Tester | Avema Corporation
370 King Street West, Suite 604, Toronto, ON M5V 1J9
T: (416) 348-7286 <+14163487286> | E: kbi...@avemacorp.com


www.avema.com <https://www.facebook.com/AvemaCorporation>

This message is directed in confidence solely to the person named
above. The information in this message, and any attachment, may be
proprietary, confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any use, distribution, copying
or disclosure is prohibited. If you have received this message in
error, please notify us immediately by telephone or by e-mail and
delete this message, without making a copy. Thank you for your
cooperation.

-- 

Le présent message est destiné exclusivement à la personne dont le nom
figure ci-dessus. L’information qu’il contient peut être privée,
confidentielle, privilégiée et exempte de divulgation aux termes des
lois applicables. Si vous n’êtes pas le destinataire visé par ce
message, veuillez noter que l’utilisation, la distribution, la
reproduction ou la divulgation de ce message est interdite. Si vous
avez reçu le présent message par erreur, veuillez nous en aviser
immédiatement par téléphone ou par courriel et supprimer ce message,
sans en faire de copie. Merci de votre

Question about Resource Management changes in Wicket 8

[Kyle Bibby]

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 to my wicket
pages.

In my project there are helper classes where a number of resources are
defined. Examples of these helper classes are as follows:

public class JS {

public static final JavaScriptResourceReference JQUERY_UI = jquery(
JS.class, "jquery-ui.min.js" );

public static final JavaScriptResourceReference D3 = new
JavaScriptResourceReference( JS.class, "d3.min.js" );


public static void initChartJSBundle( Application wicketApp ) {

   return wicketApp.getResourceBundles().addJavaScriptBundle(
JS.class, "chart.js", JQUERY_UI, D3);

   }
}

public class CSS {

public static final CssResourceReference ICONS = css( "icons/icons.css" );

public static void initCSSResources( WebApplication wicketApp ) {

   wicketApp.mountResource( "css/icons.css", CSS.ICONS );

   }
}

Normally, widely used resources are added to my Wicket Application by
making calls to these helper classes in the init():

public abstract class MyApplication extends WebApplication {

public MyApplication() { }


@Override

public void init() {

JS.initChartJSBundle( this );

CSS.initCSSResources( this );

 }

}

I'm aware that resources are typically added to pages/components by
overriding the renderHead() method. I am in fact doing this for resources
that are specific to particular pages. However, for widely used resources,
the above example is all that was required for my Wicket 6 project to make
resources available and automatically included as headers on my Wicket
Pages. This does not seem to be the case with Wicket 8 as my resources are
not being included on any rendered pages. I have scoured the changelogs for
Wicket 8 and haven't found anything referring to the changes with resource
management.
Is there something I'm missing? Is the Wicket 6 behaviour something that
was removed over a preferred method for resource management? If so, what is
this method?

Thanks,
-- 
*Kyle Bibby**|* Software Tester | Avema Corporation
370 King Street West, Suite 604, Toronto, ON M5V 1J9
T: (416) 348-7286 <+14163487286> | E: kbi...@avemacorp.com


 www.avema.com <https://www.facebook.com/AvemaCorporation>

This message is directed in confidence solely to the person named
above. The information in this message, and any attachment, may be
proprietary, confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any use, distribution, copying
or disclosure is prohibited. If you have received this message in
error, please notify us immediately by telephone or by e-mail and
delete this message, without making a copy. Thank you for your
cooperation.

--

Le présent message est destiné exclusivement à la personne dont le nom
figure ci-dessus. L’information qu’il contient peut être privée,
confidentielle, privilégiée et exempte de divulgation aux termes des
lois applicables. Si vous n’êtes pas le destinataire visé par ce
message, veuillez noter que l’utilisation, la distribution, la
reproduction ou la divulgation de ce message est interdite. Si vous
avez reçu le présent message par erreur, veuillez nous en aviser
immédiatement par téléphone ou par courriel et supprimer ce message,
sans en faire de copie. Merci de votre

Re: migration from wicket 8 to 9 -> PageManagerProvider

[Sven Meier]

Indeed, flush-before-detach (WICKET-6831) was a huge performance 
improvement.


Sven


On 11.11.21 08:55, Korbinian Bachl wrote:

Hi Sven,

thanks a lot!

I've looked into that GaePageManagerProvider and adapted it myself. However, 
during test I somehow observed that the reason why I did use the HTTPSession 
store some long time ago (wicket 1.5/6?) doesn't seem to be existing anymore. 
Reason was that the underlying storage of our prod server has the typical small 
cloud latency. Now with wicket 9 all doing async I didnt see any benefit after 
all with having or not having the custom provider. I even suspect the 
HTTPSession solution to be a tad slower (1 to 10ms) from observation, but cant 
really pinpoint it down.

Its really nice to see how good wicket got here so that speed is quite well 
without the need for custom optimisation.

If you have any idea how to even speed 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. I'm very impressed!

thanks, glad to hear that.

You application is persisting pages in the Http session instead of disk.
Essentially what the wicketstuff's gae-initializer does too:

https://github.com/wicketstuff/core/blob/master/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaePageManagerProvider.java

InsessionPageStore has a maxBytes constructor too.
Watch out for the override of the #getKey() method - I'm not happy with
that, but your question triggers me to look into that once again.

Have fun
Sven


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();


setPageManagerProvider(new DefaultPageManagerProvider(this) {
  protected IDataStore newDataStore() {
  return new HttpSessionDataStore(getPageManagerContext(),
  new MemorySizeEvictionStrategy(Bytes.megabytes(24)));
  }
  });
getStoreSettings().setInmemoryCacheSize(0);



I honestly dont know from when this originated but I had to disable it as it
doesnt seem to exist anymore accorting to the migration guide.

So I just let de default settings now apply. The original solution was aimed at
maximum page delivery speed and didnt care much about RAM as we got plenty of
it. Any idea if I should let the default or can I squeeze out some milliseconds
by going pure in memory again?

Best,

KB

-
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

-
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: migration from wicket 8 to 9 -> PageManagerProvider

[Korbinian Bachl]

Hi Sven,

thanks a lot!

I've looked into that GaePageManagerProvider and adapted it myself. However, 
during test I somehow observed that the reason why I did use the HTTPSession 
store some long time ago (wicket 1.5/6?) doesn't seem to be existing anymore. 
Reason was that the underlying storage of our prod server has the typical small 
cloud latency. Now with wicket 9 all doing async I didnt see any benefit after 
all with having or not having the custom provider. I even suspect the 
HTTPSession solution to be a tad slower (1 to 10ms) from observation, but cant 
really pinpoint it down.

Its really nice to see how good wicket got here so that speed is quite well 
without the need for custom optimisation.

If you have any idea how to even speed 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. I'm very impressed!
> 
> thanks, glad to hear that.
> 
> You application is persisting pages in the Http session instead of disk.
> Essentially what the wicketstuff's gae-initializer does too:
> 
> https://github.com/wicketstuff/core/blob/master/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaePageManagerProvider.java
> 
> InsessionPageStore has a maxBytes constructor too.
> Watch out for the override of the #getKey() method - I'm not happy with
> that, but your question triggers me to look into that once again.
> 
> Have fun
> Sven
> 
> 
> 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();
>>
>>
>> setPageManagerProvider(new DefaultPageManagerProvider(this) {
>>  protected IDataStore newDataStore() {
>>  return new HttpSessionDataStore(getPageManagerContext(),
>>  new 
>> MemorySizeEvictionStrategy(Bytes.megabytes(24)));
>>  }
>>  });
>> getStoreSettings().setInmemoryCacheSize(0);
>>
>>
>>
>> I honestly dont know from when this originated but I had to disable it as it
>> doesnt seem to exist anymore accorting to the migration guide.
>>
>> So I just let de default settings now apply. The original solution was aimed 
>> at
>> maximum page delivery speed and didnt care much about RAM as we got plenty of
>> it. Any idea if I should let the default or can I squeeze out some 
>> milliseconds
>> by going pure in memory again?
>>
>> Best,
>>
>> KB
>>
>> -
>> 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

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: migration from wicket 8 to 9 -> PageManagerProvider

[Sven Meier]

Hi Korbinian,

> it was a real breeze. I'm very impressed!

thanks, glad to hear that.

You application is persisting pages in the Http session instead of disk. 
Essentially what the wicketstuff's gae-initializer does too:


https://github.com/wicketstuff/core/blob/master/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaePageManagerProvider.java

InsessionPageStore has a maxBytes constructor too.
Watch out for the override of the #getKey() method - I'm not happy with 
that, but your question triggers me to look into that once again.


Have fun
Sven


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();


setPageManagerProvider(new DefaultPageManagerProvider(this) {
 protected IDataStore newDataStore() {
 return new HttpSessionDataStore(getPageManagerContext(),
 new MemorySizeEvictionStrategy(Bytes.megabytes(24)));
 }
 });
getStoreSettings().setInmemoryCacheSize(0);



I honestly dont know from when this originated but I had to disable it as it 
doesnt seem to exist anymore accorting to the migration guide.

So I just let de default settings now apply. The original solution was aimed at 
maximum page delivery speed and didnt care much about RAM as we got plenty of 
it. Any idea if I should let the default or can I squeeze out some milliseconds 
by going pure in memory again?

Best,

KB

-
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

migration from wicket 8 to 9 -> PageManagerProvider

[Korbinian Bachl]

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(this) {
protected IDataStore newDataStore() {
return new HttpSessionDataStore(getPageManagerContext(),
new MemorySizeEvictionStrategy(Bytes.megabytes(24)));
}
});
getStoreSettings().setInmemoryCacheSize(0);



I honestly dont know from when this originated but I had to disable it as it 
doesnt seem to exist anymore accorting to the migration guide.

So I just let de default settings now apply. The original solution was aimed at 
maximum page delivery speed and didnt care much about RAM as we got plenty of 
it. Any idea if I should let the default or can I squeeze out some milliseconds 
by going pure in memory again?

Best,

KB

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 + 9 on jdk17?

[Ernesto Reinaldo Barreiro]

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 handle
> code
> > compiled with JDK17, but this was easily fixed by upgrading those
> > libraries.
> >
> > What helps is that the Wicket team periodically runs the entire test
> suite
> > against JDK release candidates and communicates their findings with the
> JDK
> > team.
> >
>
> I even use JDK 18 EA for some of my projects.
> But my apps are not so important. It is not like I'd lose few billions $$$
> if something breaks for few hours :-)
>
> > >
>

In a fair world maybe you, Sven and some other folks deserve some part of
those billions of $$$. But that's another story :-(

-- 
Regards - Ernesto Reinaldo Barreiro

Re: Wicket 8 + 9 on jdk17?

[Martin Grigorov]

On Thu, Oct 7, 2021 at 9:57 AM Jeroen Steenbeeke 
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 handle code
> compiled with JDK17, but this was easily fixed by upgrading those
> libraries.
>
> What helps is that the Wicket team periodically runs the entire test suite
> against JDK release candidates and communicates their findings with the JDK
> team.
>

I even use JDK 18 EA for some of my projects.
But my apps are not so important. It is not like I'd lose few 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 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 are some nice bits added
> > to the track from 11 to 17 I wonder if anyone has some experience with
> > higher version of java and wicket 8 or 9 running under it...
> >
> > Best,
> >
> > KB
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
> --
> Jeroen Steenbeeke
>

Re: Wicket 8 + 9 on jdk17?

[Jeroen Steenbeeke]

My personal Wicket apps (Wicket 9) are all running on JDK17 now. No
problems so far, other than certain libraries not being able to handle code
compiled with JDK17, but this was easily fixed by upgrading those libraries.

What helps is that the Wicket team periodically runs the entire test suite
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 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 are some nice bits added
> to the track from 11 to 17 I wonder if anyone has some experience with
> higher version of java and wicket 8 or 9 running under it...
>
> Best,
>
> KB
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Jeroen Steenbeeke

Wicket 8 + 9 on jdk17?

[Korbinian Bachl]

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 are some nice bits added to 
the track from 11 to 17 I wonder if anyone has some experience with higher 
version of java and wicket 8 or 9 running under it...

Best,

KB

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8.x Migration Issues with AjaxFallBackLink

[Johannes Renoth]

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
>
> 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-request-8.11.0.jar
> wicket-util-8.11.0.jar
> wicketstuff-inmethod-grid-8.11.0.jar
>
> Addressed the compilation issues related to AjaxFallBackLink onClick() method 
> .
> Changed the method signature to public void 
> onClick(Optional target).
>
> We have a Html page
>
> SettingsPanel.html
>
> 
>  xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd"; 
> lang="en">
>
> 
>wicket:id="saveIcon" />
>
>
> 
>
> 
>
> SettingsPanel.java
>
> AjaxFallbackLink settingsLink = new 
> AjaxFallbackLink("saveSettingsLink") {
>   private static final long serialVersionUID = 1L;
>
>   @Override
>   public void onClick(Optional target) {
> //some logic
> target.get().add(feedback);
>
>   }
> };
> Image img = new Image("saveIcon", new Model() {
>   private static final long serialVersionUID = 1L;
>
>   @Override
>   public Serializable getObject() {
> return new 
> PackageResourceReference(SettingsPanel.class,"save.png");
>   }
> });
> img.add(new AttributeModifier("title", new 
> StringResourceModel("saveTitle", ColumnSettingsLinkPanel.this,
> new Model(;
> settingsLink.add(img);
>
> With the above code, in Wicket 6.30, save image (save.png) gets displayed on 
> the page and when user clicks on the image link, onlick(AjaxRequestTarget 
> target) gets triggered.
> Post migrating to Wicket 8.11.0, image is not displaying on the page and when 
> user clicks on the image link, onClick(Optional target) 
> getting triggered, but the target value is always Empty.
>
> Below is the stack trace
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> java.util.NoSuchElementException: No value present
> at java.base/java.util.Optional.get(Optional.java:148)
> at com.csc.pts.web.ui.ColumnSettingsLinkPanel$3.onClick(SettingsPanel.java:98)
> at 
> org.apache.wicket.ajax.markup.html.AjaxFallbackLink.onClick(AjaxFallbackLink.java:122)
> at org.apache.wicket.markup.html.link.Link.onRequest(Link.java:189)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:255)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:215)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
> at 
> org.apache.wicket.core.request.handler.RequestSettingRequestHandler.respond(RequestSettingRequestHandler.java:78)
> at 
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)
> at 
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
> at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)
> at 
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
> at 
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
> at org.apache.catalina

Re: Wicket 8.x Migration Issues with AjaxFallBackLink

[Martin Grigorov]

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 in the classpath.
>
> wicket-auth-roles-8.11.0.jar
> wicket-core-8.11.0.jar
> wicket-datetime-8.0.0-M7.jar
>

better use
https://github.com/wicketstuff/core/tree/master/wicket-datetime-parent ,
https://search.maven.org/artifact/org.wicketstuff/wicketstuff-datetime-yui/8.11.0/jar


> wicket-extensions-8.11.0.jar
> wicket-request-8.11.0.jar
> wicket-util-8.11.0.jar
> wicketstuff-inmethod-grid-8.11.0.jar
>
> Addressed the compilation issues related to AjaxFallBackLink onClick()
> method .
> Changed the method signature to public void
> onClick(Optional target).
>
> We have a Html page
>
> SettingsPanel.html
>
> 
> http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd"; lang="en">
>
> 
>wicket:id="saveSettingsLink">
>
>
> 
>
> 
>
> SettingsPanel.java
>
> AjaxFallbackLink settingsLink = new
> AjaxFallbackLink("saveSettingsLink") {
>   private static final long serialVersionUID = 1L;
>
>   @Override
>   public void onClick(Optional target) {
> //some logic
> target.get().add(feedback);
>

replace it with: target.ifPresent(t -> t.add(feedback));

I am not sure what is the reason to still use AjaxFallback** components but
if your users really disable JavaScript in their browsers then you have to
check that the Optional brings AjaxRequestTarget before trying to use it.


>
>   }
> };
> Image img = new Image("saveIcon", new Model() {
>   private static final long serialVersionUID = 1L;
>
>   @Override
>   public Serializable getObject() {
> return new
> PackageResourceReference(SettingsPanel.class,"save.png");
>   }
> });
> img.add(new AttributeModifier("title", new
> StringResourceModel("saveTitle", ColumnSettingsLinkPanel.this,
> new Model(;
> settingsLink.add(img);
>
> With the above code, in Wicket 6.30, save image (save.png) gets displayed
> on the page and when user clicks on the image link,
> onlick(AjaxRequestTarget target) gets triggered.
> Post migrating to Wicket 8.11.0, image is not displaying on the page and
> when user clicks on the image link, onClick(Optional
> target) getting triggered, but the target value is always Empty.
>
> Below is the stack trace
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> java.util.NoSuchElementException: No value present
> at java.base/java.util.Optional.get(Optional.java:148)
> at
> com.csc.pts.web.ui.ColumnSettingsLinkPanel$3.onClick(SettingsPanel.java:98)
> at
> org.apache.wicket.ajax.markup.html.AjaxFallbackLink.onClick(AjaxFallbackLink.java:122)
> at org.apache.wicket.markup.html.link.Link.onRequest(Link.java:189)
> at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
> at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:255)
> at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:215)
> at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
> at
> org.apache.wicket.core.request.handler.RequestSettingRequestHandler.respond(RequestSettingRequestHandler.java:78)
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)
> at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
> at
> org.

Wicket 8.x Migration Issues with AjaxFallBackLink

[Satyavathi Iynaparthi]

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-request-8.11.0.jar
wicket-util-8.11.0.jar
wicketstuff-inmethod-grid-8.11.0.jar

Addressed the compilation issues related to AjaxFallBackLink onClick() method .
Changed the method signature to public void onClick(Optional 
target).

We have a Html page

SettingsPanel.html


http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd"; 
lang="en">


  






SettingsPanel.java

AjaxFallbackLink settingsLink = new 
AjaxFallbackLink("saveSettingsLink") {
  private static final long serialVersionUID = 1L;

  @Override
  public void onClick(Optional target) {
//some logic
target.get().add(feedback);

  }
};
Image img = new Image("saveIcon", new Model() {
  private static final long serialVersionUID = 1L;

  @Override
  public Serializable getObject() {
return new 
PackageResourceReference(SettingsPanel.class,"save.png");
  }
});
img.add(new AttributeModifier("title", new 
StringResourceModel("saveTitle", ColumnSettingsLinkPanel.this,
new Model(;
settingsLink.add(img);

With the above code, in Wicket 6.30, save image (save.png) gets displayed on 
the page and when user clicks on the image link, onlick(AjaxRequestTarget 
target) gets triggered.
Post migrating to Wicket 8.11.0, image is not displaying on the page and when 
user clicks on the image link, onClick(Optional target) 
getting triggered, but the target value is always Empty.

Below is the stack trace
ERROR - DefaultExceptionMapper - Unexpected error occurred
java.util.NoSuchElementException: No value present
at java.base/java.util.Optional.get(Optional.java:148)
at com.csc.pts.web.ui.ColumnSettingsLinkPanel$3.onClick(SettingsPanel.java:98)
at 
org.apache.wicket.ajax.markup.html.AjaxFallbackLink.onClick(AjaxFallbackLink.java:122)
at org.apache.wicket.markup.html.link.Link.onRequest(Link.java:189)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:255)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:215)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
at 
org.apache.wicket.core.request.handler.RequestSettingRequestHandler.respond(RequestSettingRequestHandler.java:78)
at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)
at 
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803)
at 
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at 
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459)
at 
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at 
java.base/java.util.concurrent.ThreadPoolExecutor

Re: Wicket 8: Content-Security-Policy header

[Francesco Chicchiriccò]

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 extends AuthenticatedWebApplication so, when accessing the 
> root page, I receive an HTTP 302 redirect to
> 
> /login;jsessionid=
> 
> which is expected.
> 
> Unfortunately, as far as I can tell, the Content-Security-Policy header is 
> included in the initial request to the root page but missing when I am 
> getting the login page, following the redirect.

Further information: with -Dwicket.configuration=deployment

GET / returns

HTTP/1.1 302 
Set-Cookie: JSESSIONID=31A285C6E9F7B7F238F58B7DFC3DBD2B; Path=/syncope-console; 
Secure; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src https:
X-Content-Type-Options: nosniff
Date: Wed, 25 Nov 2020 09:04:18 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Location: ./login;jsessionid=31A285C6E9F7B7F238F58B7DFC3DBD2B
Content-Length: 0

GET ./login;jsessionid=31A285C6E9F7B7F238F58B7DFC3DBD2B returns

HTTP/1.1 302 
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src https:
X-Content-Type-Options: nosniff
Date: Wed, 25 Nov 2020 09:05:22 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Location: ./login;jsessionid=31A285C6E9F7B7F238F58B7DFC3DBD2B?1
Content-Length: 0

and finally GET ./login;jsessionid=31A285C6E9F7B7F238F58B7DFC3DBD2B?1 returns

HTTP/1.1 200 
Date: Wed, 25 Nov 2020 09:06:14 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Content-Type: text/html;charset=UTF-8
Transfer-Encoding: chunked




I am observing that with -Dwicket.configuration=development even the last GET 
returns the expected headers.

Regards.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Wicket 8: Content-Security-Policy header

[Francesco Chicchiriccò]

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 receive an HTTP 302 redirect to

/login;jsessionid=

which is expected.

Unfortunately, as far as I can tell, the Content-Security-Policy header is 
included in the initial request to the root page but missing when I am getting 
the login page, following the redirect.

Is there anything obvious I am missing here?
Thanks in advance.

Regards.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

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

[Andrea Del Bene]

...or just use javadoc.io :-). Select the desired version and click
"download". For example:

https://www.javadoc.io/doc/org.apache.wicket/wicket-core/8.7.0/index.html

The only drawback is that you have to download JavaDoc per single module
(wicket-core, wicket-util, etc..)

On Mon, Mar 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 code.
> 4. The generated Javadocs can then be found in the `./target/site/apidocs/`
> directory.
>
> On Mon, Mar 2, 2020 at 8:01 AM SB  wrote:
>
> > 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?
> >
>


-- 
Andrea Del Bene.
Apache Wicket committer.

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

[SB]

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/site/apidocs/`
directory.

On Mon, Mar 2, 2020 at 8:01 AM SB  wrote:

> 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: Where to download Javadoc for Wicket 8.x?

[Martin Terra]

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.com/questions/310720/get-source-jar-files-attached-to-eclipse-for-maven-managed-dependencies

**
Martin


>
> 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 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 there a
> > > place where I can download Wicket's Javadocs for offline use?
> > >
> >
>

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

[SB]

> ... 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 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 there a
> > place where I can download Wicket's Javadocs for offline use?
> >
>

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

[Martin Terra]

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 there a
> place where I can download Wicket's Javadocs for offline use?
>

Where to download Javadoc for Wicket 8.x?

[SB]

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.

[Andrea Del Bene]

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 (wicket 8.X based). So, before any
> new milestone releases of 9.x I can use it to test if everything still
> works and hopefully provide some feedback to Wicket developers.
>
> Thanks again to Wicket team!
>
>
> On Fri, May 3, 2019 at 9:34 AM nino martinez wael <
> nino.martinez.w...@gmail.com> wrote:
>
> > 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 boot :)
> >
> >
> >
> > On Fri, May 3, 2019 at 8:45 AM Ernesto Reinaldo Barreiro <
> > reier...@gmail.com>
> > wrote:
> >
> > > 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 combination with wicket AJAX/Web sockets.
> Also
> > >
> > >
> > >- some home grown bootstrap modal wizard
> > >- wicket wrapper fro *https://github.com/fronteed/iCheck
> > ><https://github.com/fronteed/iCheck>*
> > >
> > > *And maybe some other home ground components. But this doesn't depend
> on
> > > me.*
> > >
> > > --
> > > Regards - Ernesto Reinaldo Barreiro
> > >
> >
> >
> > --
> > Best regards / Med venlig hilsen
> > Nino Martinez
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: thanks for wonderful work with Wicket 8.

[Ernesto Reinaldo Barreiro]

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 and hopefully provide some feedback to Wicket developers.

Thanks again to Wicket team!


On Fri, May 3, 2019 at 9:34 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:

> 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 boot :)
>
>
>
> On Fri, May 3, 2019 at 8:45 AM Ernesto Reinaldo Barreiro <
> reier...@gmail.com>
> wrote:
>
> > 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 combination with wicket AJAX/Web sockets. Also
> >
> >
> >- some home grown bootstrap modal wizard
> >- wicket wrapper fro *https://github.com/fronteed/iCheck
> ><https://github.com/fronteed/iCheck>*
> >
> > *And maybe some other home ground components. But this doesn't depend on
> > me.*
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>
>
> --
> Best regards / Med venlig hilsen
> Nino Martinez
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: Wicket 8 rendering of components

[Ravi]

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 commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 rendering of components

[Sven Meier]

 
 
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 altogether - just let your 
#isTokenValid() query the request parameter directly:
 

 
 getRequest().getRequestParameters().getParameterValue(tokenId).toString()
 

 
Much simpler IMHO
 

 
Have fun
 
Sven
 

 
 

 
 
 
 
 
>  
> On 13.05.2019 at 09:26,wrote:
>  
>  
>  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 
> - To 
> unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional 
> commands, e-mail: users-h...@wicket.apache.org 
>  
 

Re: Wicket 8 rendering of components

[Ravi]

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

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 rendering of components

[Sven Meier]

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
Sven


Am 10.05.19 um 09:39 schrieb Ravi:

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 programatically add the markup of a hidden input in
onComponentTagBody( markup, tag) of the Form.
This hidden input was added to the component tree in onInitialize.
In onBeforeRender we mark the component as rendered.

Worked fine so far.

What seems to be happening is that onBeforeRender ist called in
ComponentRenderingRequestHandler.beforeRender before component.renderPart
ist called.
RenderPart resets the renderedComponents in the Page - throwing away our
hidden input that was added in onBeforeRender.
Leaving us with an exception that ist thrown during Page.checkRendering.

Is this the expected behavior and if so how would I go about marking
components as rendered?

Thanks for any hint,

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 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

Wicket 8 rendering of components

[Ravi]

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 programatically add the markup of a hidden input in
onComponentTagBody( markup, tag) of the Form.
This hidden input was added to the component tree in onInitialize.
In onBeforeRender we mark the component as rendered.

Worked fine so far.

What seems to be happening is that onBeforeRender ist called in
ComponentRenderingRequestHandler.beforeRender before component.renderPart
ist called.
RenderPart resets the renderedComponents in the Page - throwing away our
hidden input that was added in onBeforeRender.
Leaving us with an exception that ist thrown during Page.checkRendering.

Is this the expected behavior and if so how would I go about marking
components as rendered?

Thanks for any hint,

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 commands, e-mail: users-h...@wicket.apache.org

Re: thanks for wonderful work with Wicket 8.

[nino martinez wael]

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 boot :)



On Fri, May 3, 2019 at 8:45 AM Ernesto Reinaldo Barreiro 
wrote:

> 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 combination with wicket AJAX/Web sockets. Also
>
>
>- some home grown bootstrap modal wizard
>- wicket wrapper fro *https://github.com/fronteed/iCheck
>*
>
> *And maybe some other home ground components. But this doesn't depend on
> me.*
>
> --
> Regards - Ernesto Reinaldo Barreiro
>


-- 
Best regards / Med venlig hilsen
Nino Martinez

Re: thanks for wonderful work with Wicket 8.

[Ernesto Reinaldo Barreiro]

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 combination with wicket AJAX/Web sockets. Also


   - some home grown bootstrap modal wizard
   - wicket wrapper fro *https://github.com/fronteed/iCheck
   *

*And maybe some other home ground components. But this doesn't depend on
me.*

-- 
Regards - Ernesto Reinaldo Barreiro

Re: thanks for wonderful work with Wicket 8.

[nino martinez wael]

I could use the

 Or a wicket wrapper for
> http://bootstrap-notify.remabledesigns.com/.


:)

On Thu, Apr 11, 2019 at 10:58 AM Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Hi Andrea,
>
>
> > 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 :-)
>
>
> :-( 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, 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.x.
>
> Also our project have some home made components and wrappers around
> JavaScript libraries that I might try to convince my customer to "open
> source". E.g. I have rolled out a LESS resource class that on the spot
> compiles LESS into CSS, if you modify your less this class will discard
> cached less and recompiles it, when I created this component I was looking
> around and found nothing similar. Or a wicket wrapper for
> http://bootstrap-notify.remabledesigns.com/. And some other Wicket things
> that might benefit community. But this decisions do not depend on me,
>
> --
> Regards - Ernesto Reinaldo Barreiro
>


-- 
Best regards / Med venlig hilsen
Nino Martinez

Re: thanks for wonderful work with Wicket 8.

[Ernesto Reinaldo Barreiro]

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-bootstrap/tree/wicket-8.x/bootstrap-less
> For Bootstrap 4.x we have it for Sass/Scss:
>
> https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x-bootstrap-4.x/bootstrap-sass
>

Hum... I didn't know about this. My implementation seems to bet simpler:
just an Interface to make LESS for compiler plugable +  Resource +
ResourceReference (for package served resources). No need for a cache. But
for our use case it works well.

-- 
Regards - Ernesto Reinaldo Barreiro

Re: thanks for wonderful work with Wicket 8.

[Martin Grigorov]

Hi Ernesto,

On Thu, Apr 11, 2019 at 11:58 AM Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Hi Andrea,
>
>
> > 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 :-)
>
>
> :-( 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, 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.x.
>

Already done: https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-9.x
I use it for my Wicket trainings application.


>
> Also our project have some home made components and wrappers around
> JavaScript libraries that I might try to convince my customer to "open
> source". E.g. I have rolled out a LESS resource class that on the spot
> compiles LESS into CSS, if you modify your less this class will discard
> cached less and recompiles it, when I created this component I was looking
> around and found nothing similar. Or a wicket wrapper for
>

There is something similar here:
https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x/bootstrap-less
For Bootstrap 4.x we have it for Sass/Scss:
https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x-bootstrap-4.x/bootstrap-sass


> http://bootstrap-notify.remabledesigns.com/. And some other Wicket things
> that might benefit community. But this decisions do not depend on me,


> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: thanks for wonderful work with Wicket 8.

[Ernesto Reinaldo Barreiro]

Hi Andrea,


> 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 :-)


:-( 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, 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.x.

Also our project have some home made components and wrappers around
JavaScript libraries that I might try to convince my customer to "open
source". E.g. I have rolled out a LESS resource class that on the spot
compiles LESS into CSS, if you modify your less this class will discard
cached less and recompiles it, when I created this component I was looking
around and found nothing similar. Or a wicket wrapper for
http://bootstrap-notify.remabledesigns.com/. And some other Wicket things
that might benefit community. But this decisions do not depend on me,

-- 
Regards - Ernesto Reinaldo Barreiro

Re: thanks for wonderful work with Wicket 8.

[Ernesto Reinaldo Barreiro]

It's been a pleasure using Wicket all these years. Thanks again!

On Thu, Apr 11, 2019 at 11:22 AM Martin Grigorov 
wrote:

> I am glad to read this small success story, Ernesto!
>
> I want to thank you for using Wicket all these years, for all the bug
> reports and the suggested 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 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 the removal of Form on
> > onSubmit and onError (on AJAX submitting components) and our derived
> > codebase depending on that) and fixed all warnings (most of them because
> of
> > depreciation of AbstractReadOnlyModel). Today, early in the morning,
> > application was already compiling! Then I ran Wicket based tests... Most
> of
> > them were failing :-( Our fault: one component (some home backed wrapper
> > around bootstrap modal) was missing calling super.onConfig()). Fixed that
> > line and all tests passed! I run the application and started to do some
> > manual testing (some of our features are very complex and use lots of
> > advanced low level Wicket JavaScript and even WebSockets). Again
> everything
> > seems to work flawlessly. Wow!
> >
> > Many thanks again to Wicket team!
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: thanks for wonderful work with Wicket 8.

[Andrea Del Bene]

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, 2019 at 10:22 AM Martin Grigorov 
wrote:

> I am glad to read this small success story, Ernesto!
>
> I want to thank you for using Wicket all these years, for all the bug
> reports and the suggested 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 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 the removal of Form on
> > onSubmit and onError (on AJAX submitting components) and our derived
> > codebase depending on that) and fixed all warnings (most of them because
> of
> > depreciation of AbstractReadOnlyModel). Today, early in the morning,
> > application was already compiling! Then I ran Wicket based tests... Most
> of
> > them were failing :-( Our fault: one component (some home backed wrapper
> > around bootstrap modal) was missing calling super.onConfig()). Fixed that
> > line and all tests passed! I run the application and started to do some
> > manual testing (some of our features are very complex and use lots of
> > advanced low level Wicket JavaScript and even WebSockets). Again
> everything
> > seems to work flawlessly. Wow!
> >
> > Many thanks again to Wicket team!
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>


-- 
Andrea Del Bene.
Apache Wicket committer.

Re: thanks for wonderful work with Wicket 8.

[Martin Grigorov]

I am glad to read this small success story, Ernesto!

I want to thank you for using Wicket all these years, for all the bug
reports and the suggested 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 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 the removal of Form on
> onSubmit and onError (on AJAX submitting components) and our derived
> codebase depending on that) and fixed all warnings (most of them because of
> depreciation of AbstractReadOnlyModel). Today, early in the morning,
> application was already compiling! Then I ran Wicket based tests... Most of
> them were failing :-( Our fault: one component (some home backed wrapper
> around bootstrap modal) was missing calling super.onConfig()). Fixed that
> line and all tests passed! I run the application and started to do some
> manual testing (some of our features are very complex and use lots of
> advanced low level Wicket JavaScript and even WebSockets). Again everything
> seems to work flawlessly. Wow!
>
> Many thanks again to Wicket team!
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

thanks for wonderful work with Wicket 8.

[Ernesto Reinaldo Barreiro]

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 to the removal of Form on
onSubmit and onError (on AJAX submitting components) and our derived
codebase depending on that) and fixed all warnings (most of them because of
depreciation of AbstractReadOnlyModel). Today, early in the morning,
application was already compiling! Then I ran Wicket based tests... Most of
them were failing :-( Our fault: one component (some home backed wrapper
around bootstrap modal) was missing calling super.onConfig()). Fixed that
line and all tests passed! I run the application and started to do some
manual testing (some of our features are very complex and use lots of
advanced low level Wicket JavaScript and even WebSockets). Again everything
seems to work flawlessly. Wow!

Many thanks again to Wicket team!

-- 
Regards - Ernesto Reinaldo Barreiro

RE: Exception handling wicket 8

[HOPPAN Matúš]

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

Hi,

Sounds like a bug in Wicket.
If you can reproduce it in a quickstart (mini) application then please attach 
it to a ticket in JIRA!
Thanks!

On Mon, Feb 18, 2019 at 2:45 PM HOPPAN Matúš  wrote:

> 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
> MyRequestCycleListener());
> 
>
>
> MyRequestCycleListener implements IRequestCycleListener and override
> method
>
>  
> @Override
> public IRequestHandler onException(RequestCycle cycle, Exception ex) {}
>   Optional target = cycle.find(AjaxRequestTarget.class);
>   //this part stopped working since it return Optional.empty(),
> because active RequestHandler
>   //and RequestHandlerScheduledAfterCurrent are both null
> if (target.isPresent()) {
> return target.get();
> }
> IPageRequestHandler last =
> PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
> WebPage page = (WebPage) (last.getPage());
>return new RenderPageRequestHandler(new
> PageProvider(currentPage));
>}
> 
>
> Is this a wicket bug or it was intention to work like this? If it was
> intentended, is there any workaround to get the AjaxRequestTarget? Or
> the approach has changed in wicket 8? Any other ideas?
>
>
> Matus
>
> 
>
> Táto správa je určená iba pre uvedeného príjemcu a môže obsahovať
> dôverné alebo interné informácie. Ak ste ju omylom obdržali,
> upovedomte o tom prosím odosielateľa a vymažte ju. Akýkoľvek iný
> spôsob použitia tohto e-mailu je zakázaný.
>
> This message is for the designated recipient only and may contain
> confidential or internal information. If you have received it in
> error, please notify the sender immediately and delete the original.
> Any other use of the e-mail by you is prohibited.
>



Táto správa je určená iba pre uvedeného príjemcu a môže obsahovať dôverné alebo 
interné informácie. Ak ste ju omylom obdržali, upovedomte o tom prosím 
odosielateľa a vymažte ju. Akýkoľvek iný spôsob použitia tohto e-mailu je 
zakázaný.

This message is for the designated recipient only and may contain confidential 
or internal information. If you have received it in error, please notify the 
sender immediately and delete the original. Any other use of the e-mail by you 
is prohibited.

Re: Exception handling wicket 8

[Martin Grigorov]

Hi,

Sounds like a bug in Wicket.
If you can reproduce it in a quickstart (mini) application then please
attach it to a ticket in JIRA!
Thanks!

On Mon, Feb 18, 2019 at 2:45 PM HOPPAN Matúš  wrote:

> 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
> MyRequestCycleListener());
> 
>
>
> MyRequestCycleListener implements IRequestCycleListener and override method
>
>  
> @Override
> public IRequestHandler onException(RequestCycle cycle, Exception ex) {}
>   Optional target = cycle.find(AjaxRequestTarget.class);
>   //this part stopped working since it return Optional.empty(), because
> active RequestHandler
>   //and RequestHandlerScheduledAfterCurrent are both null
> if (target.isPresent()) {
> return target.get();
> }
> IPageRequestHandler last =
> PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
> WebPage page = (WebPage) (last.getPage());
>return new RenderPageRequestHandler(new
> PageProvider(currentPage));
>}
> 
>
> Is this a wicket bug or it was intention to work like this? If it was
> intentended, is there
> any workaround to get the AjaxRequestTarget? Or the approach has changed
> in wicket 8? Any other ideas?
>
>
> Matus
>
> 
>
> Táto správa je určená iba pre uvedeného príjemcu a môže obsahovať dôverné
> alebo interné informácie. Ak ste ju omylom obdržali, upovedomte o tom
> prosím odosielateľa a vymažte ju. Akýkoľvek iný spôsob použitia tohto
> e-mailu je zakázaný.
>
> This message is for the designated recipient only and may contain
> confidential or internal information. If you have received it in error,
> please notify the sender immediately and delete the original. Any other use
> of the e-mail by you is prohibited.
>

Exception handling wicket 8

[HOPPAN Matúš]

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 MyRequestCycleListener());



MyRequestCycleListener implements IRequestCycleListener and override method

 
@Override
public IRequestHandler onException(RequestCycle cycle, Exception ex) {}
  Optional target = cycle.find(AjaxRequestTarget.class);
  //this part stopped working since it return Optional.empty(), because active 
RequestHandler
  //and RequestHandlerScheduledAfterCurrent are both null
if (target.isPresent()) {
return target.get();
}
IPageRequestHandler last = 
PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
WebPage page = (WebPage) (last.getPage());
   return new RenderPageRequestHandler(new 
PageProvider(currentPage));
   }


Is this a wicket bug or it was intention to work like this? If it was 
intentended, is there
any workaround to get the AjaxRequestTarget? Or the approach has changed in 
wicket 8? Any other ideas?


Matus



Táto správa je určená iba pre uvedeného príjemcu a môže obsahovať dôverné alebo 
interné informácie. Ak ste ju omylom obdržali, upovedomte o tom prosím 
odosielateľa a vymažte ju. Akýkoľvek iný spôsob použitia tohto e-mailu je 
zakázaný.

This message is for the designated recipient only and may contain confidential 
or internal information. If you have received it in error, please notify the 
sender immediately and delete the original. Any other use of the e-mail by you 
is prohibited.

Re: Wicket 8 and Edge : Known compatibilities problem ?

[Martin Grigorov]

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, 2019 at 8:02 PM andre seame  wrote:

> 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 network administrator that would say "Edge is not
> allowed on internal intranet network" ?
>
> Thanks,
>
>

Wicket 8 and Edge : Known compatibilities problem ?

[andre seame]

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 network administrator that would say "Edge is not 
allowed on internal intranet network" ?

Thanks,

Re: Wicket 8 CsrfPrevention issue

[Shengche Hsiao]

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:
>
>> 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-address-forwarding="true" to the http-
>> listener. This will instruct Undertow to read the headers passed by the
>> proxy.
>>
>> On your proxy you will want to set these headers (this is nginx config):
>> proxy_set_header X-Real-IP $remote_addr;
>> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>> proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
>> proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
>>
>> Best regards,
>> Emond Papegaaij
>>
>> On Sat, Dec 22, 2018 at 7:31 PM 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
>> > >
>> > > 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 attack, request URL: http://
>> > > etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw
>> ,
>> > > action: aborted with error 400 Origin does not correspond to request
>> > >
>> > > How can i conquer this?
>> > > 
>> > > --->
>> > > To boldly go where no man has gone before.
>> > > 
>> > > --->
>> > > We do this not because it is easy. We do this because it is hard.
>> > > -
>> > > -->
>> > > If I have seen further it is by standing on the shoulders of giants.
>> > > --
>> > > ->
>> > > front...@gmail.com
>> > >
>> ->
>> >
>> >
>> >
>> > --
>> > Chris Turchin 
>> >
>> > -
>> > 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
>>
>>
>
> --
>
> --->
> We do this not because it is easy. We do this because it is hard.
> --->
> ShengChe Hsiao
> --->
> front...@gmail.com
> front...@tc.edu.tw
> --->
> VoIP : 070-910-2450
> --->
>


-- 

--->
We do this not because it is easy. We do this because it is hard.
--->
ShengChe Hsiao
--->
front...@gmail.com
front...@tc.edu.tw
--->
VoIP : 070-910-2450
--->

Re: Wicket 8 CsrfPrevention issue

[Shengche Hsiao]

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 application and you application
> needs
> to use these headers.
>
> For WildFly, you need to add proxy-address-forwarding="true" to the http-
> listener. This will instruct Undertow to read the headers passed by the
> proxy.
>
> On your proxy you will want to set these headers (this is nginx config):
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
> proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
>
> Best regards,
> Emond Papegaaij
>
> On Sat, Dec 22, 2018 at 7:31 PM 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
> > >
> > > 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 attack, request URL: http://
> > > etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw,
> > > action: aborted with error 400 Origin does not correspond to request
> > >
> > > How can i conquer this?
> > > 
> > > --->
> > > To boldly go where no man has gone before.
> > > 
> > > --->
> > > We do this not because it is easy. We do this because it is hard.
> > > -
> > > -->
> > > If I have seen further it is by standing on the shoulders of giants.
> > > --
> > > ->
> > > front...@gmail.com
> > >
> ->
> >
> >
> >
> > --
> > Chris Turchin 
> >
> > -
> > 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
>
>

-- 

--->
We do this not because it is easy. We do this because it is hard.
--->
ShengChe Hsiao
--->
front...@gmail.com
front...@tc.edu.tw
--->
VoIP : 070-910-2450
--->

Re: Wicket 8 CsrfPrevention issue

[Emond Papegaaij]

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-address-forwarding="true" to the http-
listener. This will instruct Undertow to read the headers passed by the proxy.

On your proxy you will want to set these headers (this is nginx config):
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;

Best regards,
Emond Papegaaij

On zaterdag 22 december 2018 12:46:11 CET 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
> > 
> > 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 attack, request URL: http://
> > etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw,
> > action: aborted with error 400 Origin does not correspond to request
> > 
> > How can i conquer this?
> > 
> > --->
> > To boldly go where no man has gone before.
> > 
> > --->
> > We do this not because it is easy. We do this because it is hard.
> > -
> > -->
> > If I have seen further it is by standing on the shoulders of giants.
> > --
> > ->
> > front...@gmail.com
> > --
> > --->





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 CsrfPrevention issue

[Emond Papegaaij]

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-address-forwarding="true" to the http-
listener. This will instruct Undertow to read the headers passed by the proxy.

On your proxy you will want to set these headers (this is nginx config):
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;

Best regards,
Emond Papegaaij

On Sat, Dec 22, 2018 at 7:31 PM 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
> >
> > 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 attack, request URL: http://
> > etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw,
> > action: aborted with error 400 Origin does not correspond to request
> >
> > How can i conquer this?
> > 
> > --->
> > To boldly go where no man has gone before.
> > 
> > --->
> > We do this not because it is easy. We do this because it is hard.
> > -
> > -->
> > If I have seen further it is by standing on the shoulders of giants.
> > --
> > ->
> > front...@gmail.com
> > ->
>
>
>
> --
> Chris Turchin 
>
> -
> 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: Wicket 8 CsrfPrevention issue

[Shengche Hsiao]

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
> >
> > 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 attack, request URL: http://
> > etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw,
> > action: aborted with error 400 Origin does not correspond to request
> >
> > How can i conquer this?
> > 
> > --->
> > To boldly go where no man has gone before.
> > 
> > --->
> > We do this not because it is easy. We do this because it is hard.
> > -
> > -->
> > If I have seen further it is by standing on the shoulders of giants.
> > --
> > ->
> > front...@gmail.com
> >
> ->
>
>
>
> --
> Chris Turchin 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 

--->
We do this not because it is easy. We do this because it is hard.
--->
ShengChe Hsiao
--->
front...@gmail.com
front...@tc.edu.tw
--->
VoIP : 070-910-2450
--->

Re: Wicket 8 CsrfPrevention issue

[Chris Turchin]

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, when i add CsrfPreventionRequestCycleListener to
> my application , it showd error message:
>
> [org.apache.wicket.protocol.http.CsrfPreventionRequestCycleListener]
> (default task-48) Possible CSRF attack, request URL: http://
> etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw,
> action: aborted with error 400 Origin does not correspond to request
>
> How can i conquer this?
> 
> --->
> To boldly go where no man has gone before.
> 
> --->
> We do this not because it is easy. We do this because it is hard.
> -
> -->
> If I have seen further it is by standing on the shoulders of giants.
> --
> ->
> front...@gmail.com
> ->



-- 
Chris Turchin 

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Wicket 8 CsrfPrevention issue

[ShengChe Hsiao]

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 attack, request URL: http://
etalking.chc.edu.tw/agency/index, Origin: https://etalking.chc.edu.tw,
action: aborted with error 400 Origin does not correspond to request

How can i conquer this?

--->
To boldly go where no man has gone before.

--->
We do this not because it is easy. We do this because it is hard.
-
-->
If I have seen further it is by standing on the shoulders of giants.
--
->
front...@gmail.com
->

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

[nino martinez wael]

Sure, I was not so much thinking of me but other wicket users.. I've asked
around and at least here its not a "normal" wicket behavior that you could
break something by calling target.add(component).. And its not that I do
not want the error message, just to make it a little more clear to the
developer on whats wrong.. Not many would know that by calling target.add
you are breaking art because of internals of the tree..

A more pragmatic solution could also just to write in the java doc that
calling target.add + having expand in the  newContentComponent method are a
no go and will break runtime.

right now expand java doc are just "Expand the given node, tries to update
the affected branch if the change happens on an AjaxRequestTarget
<https://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/ajax/AjaxRequestTarget.html>
."


regards Nino

On Tue, Dec 11, 2018 at 10:02 PM Sven Meier  wrote:

> Hi Nino,
>
> I've expanded the error message for now.
>
> We could make that method on NestedTree lenient, i.e. catch the
> exception and log the message instead.
> But you could do that for yourself in your code too.
>
> Have fun
> Sven
>
> Am 10.12.18 um 11:16 schrieb nino martinez wael:
> > I agree, i just find the error message strange.. Normally if i add an
> > component with target.add it does not break.. If it breaks and we know it
> > breaks maybe an warning or error message should come from the tree that
> it
> > cannot have expand in new component on ajax requests..
> >
> >
> >
> > Ps typing iæon phone
> >
> > On Mon, 10 Dec 2018, 11:04 Sven Meier,  wrote:
> >
> >> Hi,
> >>
> >> found it:
> >>
> >> - since WICKET-6335 the node content is created in #onInitialize() only
> >> - at this moment the node is already inside the component hierarchy
> >> - #updateBranch() finds the branch of the currently rendered node and
> >> tries to add it to the ART
> >> -> "Components can no  longer be added"
> >>
> >> Compare this with 7.x:
> >>
> >> - the node content is created directly from the constructor
> >> - at this moment the node (and its parental branch) is not in the
> >> 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 ignored.
> >>
> >> You can achieve the same in Wicket 8.x with the following:
> >>
> >>   protected Component newContentComponent(String id,
> >> IModel node) {
> >>   if(haveClicked){
> >>   // #expand() can not be used, since it tries to
> add
> >> the branch
> >>   // to the ART, which is not allowed during
> rendering
> >>   getModelObject().add(node.getObject());
> >>   }
> >>   return super.newContentComponent(id, node);
> >>   }
> >>
> >> Have fun
> >> Sven
> >>
> >> Am 10.12.18 um 08:41 schrieb nino martinez wael:
> >>> I have replicated it here, I found the error a little counter
> intuitive:
> >>>
> >>>
> >>
> https://github.com/nmwael/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/tree/BeginnersTreePage.java
> >>> On Fri, Dec 7, 2018 at 5:48 PM Sven Meier  wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> the stacktrace shows clearly that you add a component to the ART while
> >>>> it is already rendering the response.
> >>>> This is not allowed, and this wasn't allowed in previous version.
> >>>>
> >>>> You'll have to provide a quickstart to prove that it worked
> previously.
> >>>>
> >>>> Regards
> >>>> Sven
> >>>>
> >>>> Am 06.12.18 um 13:50 schrieb nino martinez wael:
> >>>>> @svenme...@apache.com  what/how do I need to
> >> check
> >>>>> during the call? For now I have a breakpoint the place in the code
> >> where
> >>>> it
> >>>>> fails, but I need to figure out what closes the request target..
> >>>>>
> >>>>> On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
> >>>>> nino.martinez.w...@gmail.com> wrote:
> >

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

[Sven Meier]

Hi Nino,

I've expanded the error message for now.

We could make that method on NestedTree lenient, i.e. catch the 
exception and log the message instead.

But you could do that for yourself in your code too.

Have fun
Sven

Am 10.12.18 um 11:16 schrieb nino martinez wael:

I agree, i just find the error message strange.. Normally if i add an
component with target.add it does not break.. If it breaks and we know it
breaks maybe an warning or error message should come from the tree that it
cannot have expand in new component on ajax requests..



Ps typing iæon phone

On Mon, 10 Dec 2018, 11:04 Sven Meier,  wrote:


Hi,

found it:

- since WICKET-6335 the node content is created in #onInitialize() only
- at this moment the node is already inside the component hierarchy
- #updateBranch() finds the branch of the currently rendered node and
tries to add it to the ART
-> "Components can no  longer be added"

Compare this with 7.x:

- the node content is created directly from the constructor
- at this moment the node (and its parental branch) is not in the
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 ignored.

You can achieve the same in Wicket 8.x with the following:

  protected Component newContentComponent(String id,
IModel node) {
  if(haveClicked){
  // #expand() can not be used, since it tries to add
the branch
  // to the ART, which is not allowed during rendering
  getModelObject().add(node.getObject());
  }
  return super.newContentComponent(id, node);
  }

Have fun
Sven

Am 10.12.18 um 08:41 schrieb nino martinez wael:

I have replicated it here, I found the error a little counter intuitive:



https://github.com/nmwael/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/tree/BeginnersTreePage.java

On Fri, Dec 7, 2018 at 5:48 PM Sven Meier  wrote:


Hi,

the stacktrace shows clearly that you add a component to the ART while
it is already rendering the response.
This is not allowed, and this wasn't allowed in previous version.

You'll have to provide a quickstart to prove that it worked previously.

Regards
Sven

Am 06.12.18 um 13:50 schrieb nino martinez wael:

@svenme...@apache.com  what/how do I need to

check

during the call? For now I have a breakpoint the place in the code

where

it

fails, but I need to figure out what closes the request target..

On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


I've debugged a lot further. But still unable to pinpoint it.. For now
I've switched to rendering the full page instead, which of course

works.

We are a couple of things in conjunction with TREE, like wicket jquery

ui

draggable and droppable.. We also have a custom loading mechanism that

pops

a veil if the request are too long to load.. And some custom form

handling

aswell (auto show an marker for error'd form fields)..

PS writing this for other to see, if they hit  this challenge..

-Regards Nino


On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


currently unable to reproduce in examples, something must be wrong in

my

code..

I'll comeback if it turns out otherwise..

Thanks for helping :)

On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


Yes I understand.. Let me see if it breaks in wicket examples, or I

can

make it so.. Do you know another way to make a node/folder expand

during

construction time? Feels like the expand method are meant for ajax

calls

only.

-regards Nino

On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:


Hi Nino,



during rendering of components no additional components can be

added

to

the ART any more.

I surprised that your code worked in 6.x, can you build a

quickstart

demonstrating the problem?



Have fun

Sven










On 28.11.2018 at 14:38,wrote:


Hi In wicket 6 this worked, there are another input field (ajax

activated) that triggers the update : ChildAwareNestedTree
profilePartitionTree = new ChildAwareNestedTree("skillsetSelect",

provider,

sharedExpansionState) { @Override protected Component
newContentComponent(String id, IModel model) { TreeNode node =
model.getObject(); if (node instanceof

TreeNodeProvider.PartitionNode) {

Partition partition = ((TreeNodeProvider.PartitionNode)
node).getPartition(); if
(getPartitionsWithProfiles().containsKey(partition.getId())) {*
expand(node);* } } else if (node instanceof
TreeNodeProvider.NoPartitionNode  &&

isNoPartitionProfilesPresent()) {*

expand(node);* } } The triggering field: searchTerm.add(new
AjaxFormComponentUpdatingBehavior("keydown

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

[nino martinez wael]

I agree, i just find the error message strange.. Normally if i add an
component with target.add it does not break.. If it breaks and we know it
breaks maybe an warning or error message should come from the tree that it
cannot have expand in new component on ajax requests..



Ps typing iæon phone

On Mon, 10 Dec 2018, 11:04 Sven Meier,  wrote:

> Hi,
>
> found it:
>
> - since WICKET-6335 the node content is created in #onInitialize() only
> - at this moment the node is already inside the component hierarchy
> - #updateBranch() finds the branch of the currently rendered node and
> tries to add it to the ART
> -> "Components can no  longer be added"
>
> Compare this with 7.x:
>
> - the node content is created directly from the constructor
> - at this moment the node (and its parental branch) is not in the
> 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 ignored.
>
> You can achieve the same in Wicket 8.x with the following:
>
>  protected Component newContentComponent(String id,
> IModel node) {
>  if(haveClicked){
>  // #expand() can not be used, since it tries to add
> the branch
>  // to the ART, which is not allowed during rendering
>  getModelObject().add(node.getObject());
>  }
>  return super.newContentComponent(id, node);
>  }
>
> Have fun
> Sven
>
> Am 10.12.18 um 08:41 schrieb nino martinez wael:
> > I have replicated it here, I found the error a little counter intuitive:
> >
> >
> https://github.com/nmwael/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/tree/BeginnersTreePage.java
> >
> > On Fri, Dec 7, 2018 at 5:48 PM Sven Meier  wrote:
> >
> >> Hi,
> >>
> >> the stacktrace shows clearly that you add a component to the ART while
> >> it is already rendering the response.
> >> This is not allowed, and this wasn't allowed in previous version.
> >>
> >> You'll have to provide a quickstart to prove that it worked previously.
> >>
> >> Regards
> >> Sven
> >>
> >> Am 06.12.18 um 13:50 schrieb nino martinez wael:
> >>> @svenme...@apache.com  what/how do I need to
> check
> >>> during the call? For now I have a breakpoint the place in the code
> where
> >> it
> >>> fails, but I need to figure out what closes the request target..
> >>>
> >>> On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
> >>> nino.martinez.w...@gmail.com> wrote:
> >>>
> >>>> I've debugged a lot further. But still unable to pinpoint it.. For now
> >>>> I've switched to rendering the full page instead, which of course
> works.
> >>>>
> >>>> We are a couple of things in conjunction with TREE, like wicket jquery
> >> ui
> >>>> draggable and droppable.. We also have a custom loading mechanism that
> >> pops
> >>>> a veil if the request are too long to load.. And some custom form
> >> handling
> >>>> aswell (auto show an marker for error'd form fields)..
> >>>>
> >>>> PS writing this for other to see, if they hit  this challenge..
> >>>>
> >>>> -Regards Nino
> >>>>
> >>>>
> >>>> On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
> >>>> nino.martinez.w...@gmail.com> wrote:
> >>>>
> >>>>> currently unable to reproduce in examples, something must be wrong in
> >> my
> >>>>> code..
> >>>>>
> >>>>> I'll comeback if it turns out otherwise..
> >>>>>
> >>>>> Thanks for helping :)
> >>>>>
> >>>>> On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
> >>>>> nino.martinez.w...@gmail.com> wrote:
> >>>>>
> >>>>>> Yes I understand.. Let me see if it breaks in wicket examples, or I
> >> can
> >>>>>> make it so.. Do you know another way to make a node/folder expand
> >> during
> >>>>>> construction time? Feels like the expand method are meant for ajax
> >> calls
> >>>>>> only.
> >>>>>>
> >>>>

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

[Sven Meier]

Hi,

found it:

- since WICKET-6335 the node content is created in #onInitialize() only
- at this moment the node is already inside the component hierarchy
- #updateBranch() finds the branch of the currently rendered node and 
tries to add it to the ART

-> "Components can no  longer be added"

Compare this with 7.x:

- the node content is created directly from the constructor
- at this moment the node (and its parental branch) is not in the 
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 ignored.


You can achieve the same in Wicket 8.x with the following:

    protected Component newContentComponent(String id, 
IModel node) {

    if(haveClicked){
                    // #expand() can not be used, since it tries to add 
the branch

                    // to the ART, which is not allowed during rendering
        getModelObject().add(node.getObject());
    }
    return super.newContentComponent(id, node);
    }

Have fun
Sven

Am 10.12.18 um 08:41 schrieb nino martinez wael:

I have replicated it here, I found the error a little counter intuitive:

https://github.com/nmwael/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/tree/BeginnersTreePage.java

On Fri, Dec 7, 2018 at 5:48 PM Sven Meier  wrote:


Hi,

the stacktrace shows clearly that you add a component to the ART while
it is already rendering the response.
This is not allowed, and this wasn't allowed in previous version.

You'll have to provide a quickstart to prove that it worked previously.

Regards
Sven

Am 06.12.18 um 13:50 schrieb nino martinez wael:

@svenme...@apache.com  what/how do I need to check
during the call? For now I have a breakpoint the place in the code where

it

fails, but I need to figure out what closes the request target..

On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


I've debugged a lot further. But still unable to pinpoint it.. For now
I've switched to rendering the full page instead, which of course works.

We are a couple of things in conjunction with TREE, like wicket jquery

ui

draggable and droppable.. We also have a custom loading mechanism that

pops

a veil if the request are too long to load.. And some custom form

handling

aswell (auto show an marker for error'd form fields)..

PS writing this for other to see, if they hit  this challenge..

-Regards Nino


On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


currently unable to reproduce in examples, something must be wrong in

my

code..

I'll comeback if it turns out otherwise..

Thanks for helping :)

On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


Yes I understand.. Let me see if it breaks in wicket examples, or I

can

make it so.. Do you know another way to make a node/folder expand

during

construction time? Feels like the expand method are meant for ajax

calls

only.

-regards Nino

On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:


Hi Nino,



during rendering of components no additional components can be added

to

the ART any more.

I surprised that your code worked in 6.x, can you build a quickstart
demonstrating the problem?



Have fun

Sven










On 28.11.2018 at 14:38,wrote:


   Hi In wicket 6 this worked, there are another input field (ajax

activated) that triggers the update : ChildAwareNestedTree
profilePartitionTree = new ChildAwareNestedTree("skillsetSelect",

provider,

sharedExpansionState) { @Override protected Component
newContentComponent(String id, IModel model) { TreeNode node =
model.getObject(); if (node instanceof

TreeNodeProvider.PartitionNode) {

Partition partition = ((TreeNodeProvider.PartitionNode)
node).getPartition(); if
(getPartitionsWithProfiles().containsKey(partition.getId())) {*
expand(node);* } } else if (node instanceof
TreeNodeProvider.NoPartitionNode  &&

isNoPartitionProfilesPresent()) {*

expand(node);* } } The triggering field: searchTerm.add(new
AjaxFormComponentUpdatingBehavior("keydown") { @Override protected

void

onUpdate(AjaxRequestTarget target) { if (searchTermModel.getObject()

!=

null  &&  !searchTermModel.getObject().isEmpty()) {
profilePartitionTree.rebuildExpandedPartitions(); } else {
profilePartitionTree.getP
artitionsWithProfiles().clear(); }*

target.add(profilePartitionTree);*

} @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 wicket 8, my line

below:

2018-11-2

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

[nino martinez wael]

I have replicated it here, I found the error a little counter intuitive:

https://github.com/nmwael/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/tree/BeginnersTreePage.java

On Fri, Dec 7, 2018 at 5:48 PM Sven Meier  wrote:

> Hi,
>
> the stacktrace shows clearly that you add a component to the ART while
> it is already rendering the response.
> This is not allowed, and this wasn't allowed in previous version.
>
> You'll have to provide a quickstart to prove that it worked previously.
>
> Regards
> Sven
>
> Am 06.12.18 um 13:50 schrieb nino martinez wael:
> > @svenme...@apache.com  what/how do I need to check
> > during the call? For now I have a breakpoint the place in the code where
> it
> > fails, but I need to figure out what closes the request target..
> >
> > On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
> > nino.martinez.w...@gmail.com> wrote:
> >
> >> I've debugged a lot further. But still unable to pinpoint it.. For now
> >> I've switched to rendering the full page instead, which of course works.
> >>
> >> We are a couple of things in conjunction with TREE, like wicket jquery
> ui
> >> draggable and droppable.. We also have a custom loading mechanism that
> pops
> >> a veil if the request are too long to load.. And some custom form
> handling
> >> aswell (auto show an marker for error'd form fields)..
> >>
> >> PS writing this for other to see, if they hit  this challenge..
> >>
> >> -Regards Nino
> >>
> >>
> >> On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
> >> nino.martinez.w...@gmail.com> wrote:
> >>
> >>> currently unable to reproduce in examples, something must be wrong in
> my
> >>> code..
> >>>
> >>> I'll comeback if it turns out otherwise..
> >>>
> >>> Thanks for helping :)
> >>>
> >>> On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
> >>> nino.martinez.w...@gmail.com> wrote:
> >>>
> >>>> Yes I understand.. Let me see if it breaks in wicket examples, or I
> can
> >>>> make it so.. Do you know another way to make a node/folder expand
> during
> >>>> construction time? Feels like the expand method are meant for ajax
> calls
> >>>> only.
> >>>>
> >>>> -regards Nino
> >>>>
> >>>> On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:
> >>>>
> >>>>>
> >>>>> Hi Nino,
> >>>>>
> >>>>>
> >>>>>
> >>>>> during rendering of components no additional components can be added
> to
> >>>>> the ART any more.
> >>>>>
> >>>>> I surprised that your code worked in 6.x, can you build a quickstart
> >>>>> demonstrating the problem?
> >>>>>
> >>>>>
> >>>>>
> >>>>> Have fun
> >>>>>
> >>>>> Sven
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On 28.11.2018 at 14:38,wrote:
> >>>>>>
> >>>>>>
> >>>>>>   Hi In wicket 6 this worked, there are another input field (ajax
> >>>>> activated) that triggers the update : ChildAwareNestedTree
> >>>>> profilePartitionTree = new ChildAwareNestedTree("skillsetSelect",
> provider,
> >>>>> sharedExpansionState) { @Override protected Component
> >>>>> newContentComponent(String id, IModel model) { TreeNode node =
> >>>>> model.getObject(); if (node instanceof
> TreeNodeProvider.PartitionNode) {
> >>>>> Partition partition = ((TreeNodeProvider.PartitionNode)
> >>>>> node).getPartition(); if
> >>>>> (getPartitionsWithProfiles().containsKey(partition.getId())) {*
> >>>>> expand(node);* } } else if (node instanceof
> >>>>> TreeNodeProvider.NoPartitionNode  &&
> isNoPartitionProfilesPresent()) {*
> >>>>> expand(node);* } } The triggering field: searchTerm.add(new
> >>>>> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected
> void
> >>>>> onUpdate(AjaxRequ

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

[Sven Meier]

Hi,

the stacktrace shows clearly that you add a component to the ART while 
it is already rendering the response.

This is not allowed, and this wasn't allowed in previous version.

You'll have to provide a quickstart to prove that it worked previously.

Regards
Sven

Am 06.12.18 um 13:50 schrieb nino martinez wael:

@svenme...@apache.com  what/how do I need to check
during the call? For now I have a breakpoint the place in the code where it
fails, but I need to figure out what closes the request target..

On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


I've debugged a lot further. But still unable to pinpoint it.. For now
I've switched to rendering the full page instead, which of course works.

We are a couple of things in conjunction with TREE, like wicket jquery ui
draggable and droppable.. We also have a custom loading mechanism that pops
a veil if the request are too long to load.. And some custom form handling
aswell (auto show an marker for error'd form fields)..

PS writing this for other to see, if they hit  this challenge..

-Regards Nino


On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


currently unable to reproduce in examples, something must be wrong in my
code..

I'll comeback if it turns out otherwise..

Thanks for helping :)

On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:


Yes I understand.. Let me see if it breaks in wicket examples, or I can
make it so.. Do you know another way to make a node/folder expand during
construction time? Feels like the expand method are meant for ajax calls
only.

-regards Nino

On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:



Hi Nino,



during rendering of components no additional components can be added to
the ART any more.

I surprised that your code worked in 6.x, can you build a quickstart
demonstrating the problem?



Have fun

Sven










On 28.11.2018 at 14:38,wrote:


  Hi In wicket 6 this worked, there are another input field (ajax

activated) that triggers the update : ChildAwareNestedTree
profilePartitionTree = new ChildAwareNestedTree("skillsetSelect", provider,
sharedExpansionState) { @Override protected Component
newContentComponent(String id, IModel model) { TreeNode node =
model.getObject(); if (node instanceof TreeNodeProvider.PartitionNode) {
Partition partition = ((TreeNodeProvider.PartitionNode)
node).getPartition(); if
(getPartitionsWithProfiles().containsKey(partition.getId())) {*
expand(node);* } } else if (node instanceof
TreeNodeProvider.NoPartitionNode  &&  isNoPartitionProfilesPresent()) {*
expand(node);* } } The triggering field: searchTerm.add(new
AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void
onUpdate(AjaxRequestTarget target) { if (searchTermModel.getObject() !=
null  &&  !searchTermModel.getObject().isEmpty()) {
profilePartitionTree.rebuildExpandedPartitions(); } else {
profilePartitionTree.getP
artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);*
} @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 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 occurred
org.apache.wicket.WicketRuntimeException: Error attaching this container
for rendering: [Subtree [Component id = subtree]] at
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
at org.apache.wicket.MarkupContai
ner.onBeforeRenderChildren(MarkupContainer.java:1753)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
at
dk.netdesign.XXX.frontend.tree.ChildAwareNestedTree.onBeforeRender(ChildAwareNestedTree.java:41)[106:XXX-frontend:1.0.4.RC_01]
at
org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.page.PartialPageUpdate.prepareComponent(PartialPageUpdate.java:322)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:250)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxRequestHandler.java:384)[136:org.apache.wicket.core:8.1.0]
at
org.apache.wicket.r

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

[nino martinez wael]

@svenme...@apache.com  what/how do I need to check
during the call? For now I have a breakpoint the place in the code where it
fails, but I need to figure out what closes the request target..

On Mon, Dec 3, 2018 at 10:55 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:

> I've debugged a lot further. But still unable to pinpoint it.. For now
> I've switched to rendering the full page instead, which of course works.
>
> We are a couple of things in conjunction with TREE, like wicket jquery ui
> draggable and droppable.. We also have a custom loading mechanism that pops
> a veil if the request are too long to load.. And some custom form handling
> aswell (auto show an marker for error'd form fields)..
>
> PS writing this for other to see, if they hit  this challenge..
>
> -Regards Nino
>
>
> On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
> nino.martinez.w...@gmail.com> wrote:
>
>> currently unable to reproduce in examples, something must be wrong in my
>> code..
>>
>> I'll comeback if it turns out otherwise..
>>
>> Thanks for helping :)
>>
>> On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
>> nino.martinez.w...@gmail.com> wrote:
>>
>>> Yes I understand.. Let me see if it breaks in wicket examples, or I can
>>> make it so.. Do you know another way to make a node/folder expand during
>>> construction time? Feels like the expand method are meant for ajax calls
>>> only.
>>>
>>> -regards Nino
>>>
>>> On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:
>>>
>>>>
>>>>
>>>> Hi Nino,
>>>>
>>>>
>>>>
>>>> during rendering of components no additional components can be added to
>>>> the ART any more.
>>>>
>>>> I surprised that your code worked in 6.x, can you build a quickstart
>>>> demonstrating the problem?
>>>>
>>>>
>>>>
>>>> Have fun
>>>>
>>>> Sven
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> >
>>>> > On 28.11.2018 at 14:38,wrote:
>>>> >
>>>> >
>>>> >  Hi In wicket 6 this worked, there are another input field (ajax
>>>> activated) that triggers the update : ChildAwareNestedTree
>>>> profilePartitionTree = new ChildAwareNestedTree("skillsetSelect", provider,
>>>> sharedExpansionState) { @Override protected Component
>>>> newContentComponent(String id, IModel model) { TreeNode node =
>>>> model.getObject(); if (node instanceof TreeNodeProvider.PartitionNode) {
>>>> Partition partition = ((TreeNodeProvider.PartitionNode)
>>>> node).getPartition(); if
>>>> (getPartitionsWithProfiles().containsKey(partition.getId())) {*
>>>> expand(node);* } } else if (node instanceof
>>>> TreeNodeProvider.NoPartitionNode  &&  isNoPartitionProfilesPresent()) {*
>>>> expand(node);* } } The triggering field: searchTerm.add(new
>>>> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void
>>>> onUpdate(AjaxRequestTarget target) { if (searchTermModel.getObject() !=
>>>> null  &&  !searchTermModel.getObject().isEmpty()) {
>>>> profilePartitionTree.rebuildExpandedPartitions(); } else {
>>>> profilePartitionTree.getP
>>>> artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);*
>>>> } @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 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 occurred
>>>> org.apache.wicket.WicketRuntimeException: Error attaching this container
>>>> for rendering: [Subtree [Component id = subtree]] at
>>>> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]
>>>> at
>>>> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
>>>> at
>>>> org.apache.wicket.Component.beforeRender(Compone

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

[nino martinez wael]

I've debugged a lot further. But still unable to pinpoint it.. For now I've
switched to rendering the full page instead, which of course works.

We are a couple of things in conjunction with TREE, like wicket jquery ui
draggable and droppable.. We also have a custom loading mechanism that pops
a veil if the request are too long to load.. And some custom form handling
aswell (auto show an marker for error'd form fields)..

PS writing this for other to see, if they hit  this challenge..

-Regards Nino


On Thu, Nov 29, 2018 at 8:50 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:

> currently unable to reproduce in examples, something must be wrong in my
> code..
>
> I'll comeback if it turns out otherwise..
>
> Thanks for helping :)
>
> On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
> nino.martinez.w...@gmail.com> wrote:
>
>> Yes I understand.. Let me see if it breaks in wicket examples, or I can
>> make it so.. Do you know another way to make a node/folder expand during
>> construction time? Feels like the expand method are meant for ajax calls
>> only.
>>
>> -regards Nino
>>
>> On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:
>>
>>>
>>>
>>> Hi Nino,
>>>
>>>
>>>
>>> during rendering of components no additional components can be added to
>>> the ART any more.
>>>
>>> I surprised that your code worked in 6.x, can you build a quickstart
>>> demonstrating the problem?
>>>
>>>
>>>
>>> Have fun
>>>
>>> Sven
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> >
>>> > On 28.11.2018 at 14:38,wrote:
>>> >
>>> >
>>> >  Hi In wicket 6 this worked, there are another input field (ajax
>>> activated) that triggers the update : ChildAwareNestedTree
>>> profilePartitionTree = new ChildAwareNestedTree("skillsetSelect", provider,
>>> sharedExpansionState) { @Override protected Component
>>> newContentComponent(String id, IModel model) { TreeNode node =
>>> model.getObject(); if (node instanceof TreeNodeProvider.PartitionNode) {
>>> Partition partition = ((TreeNodeProvider.PartitionNode)
>>> node).getPartition(); if
>>> (getPartitionsWithProfiles().containsKey(partition.getId())) {*
>>> expand(node);* } } else if (node instanceof
>>> TreeNodeProvider.NoPartitionNode  &&  isNoPartitionProfilesPresent()) {*
>>> expand(node);* } } The triggering field: searchTerm.add(new
>>> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void
>>> onUpdate(AjaxRequestTarget target) { if (searchTermModel.getObject() !=
>>> null  &&  !searchTermModel.getObject().isEmpty()) {
>>> profilePartitionTree.rebuildExpandedPartitions(); } else {
>>> profilePartitionTree.getP
>>> artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);* }
>>> @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 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 occurred
>>> org.apache.wicket.WicketRuntimeException: Error attaching this container
>>> for rendering: [Subtree [Component id = subtree]] at
>>> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]
>>> at
>>> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
>>> at
>>> org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
>>> at org.apache.wicket.MarkupContai
>>> ner.onBeforeRenderChildren(MarkupContainer.java:1753)[136:org.apache.wicket.core:8.1.0]
>>> at
>>> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
>>> at
>>> dk.netdesign.XXX.frontend.tree.ChildAwareNestedTree.onBeforeRender(ChildAwareNestedTree.java:41)[106:XXX-frontend:1.0.4.RC_01]
>>> at
>>> org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
>>> at
>>> org.apache.wicket.page.PartialPageUpdate.prepa

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

[nino martinez wael]

currently unable to reproduce in examples, something must be wrong in my
code..

I'll comeback if it turns out otherwise..

Thanks for helping :)

On Thu, Nov 29, 2018 at 6:54 AM nino martinez wael <
nino.martinez.w...@gmail.com> wrote:

> Yes I understand.. Let me see if it breaks in wicket examples, or I can
> make it so.. Do you know another way to make a node/folder expand during
> construction time? Feels like the expand method are meant for ajax calls
> only.
>
> -regards Nino
>
> On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:
>
>>
>>
>> Hi Nino,
>>
>>
>>
>> during rendering of components no additional components can be added to
>> the ART any more.
>>
>> I surprised that your code worked in 6.x, can you build a quickstart
>> demonstrating the problem?
>>
>>
>>
>> Have fun
>>
>> Sven
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> >
>> > On 28.11.2018 at 14:38,wrote:
>> >
>> >
>> >  Hi In wicket 6 this worked, there are another input field (ajax
>> activated) that triggers the update : ChildAwareNestedTree
>> profilePartitionTree = new ChildAwareNestedTree("skillsetSelect", provider,
>> sharedExpansionState) { @Override protected Component
>> newContentComponent(String id, IModel model) { TreeNode node =
>> model.getObject(); if (node instanceof TreeNodeProvider.PartitionNode) {
>> Partition partition = ((TreeNodeProvider.PartitionNode)
>> node).getPartition(); if
>> (getPartitionsWithProfiles().containsKey(partition.getId())) {*
>> expand(node);* } } else if (node instanceof
>> TreeNodeProvider.NoPartitionNode  &&  isNoPartitionProfilesPresent()) {*
>> expand(node);* } } The triggering field: searchTerm.add(new
>> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void
>> onUpdate(AjaxRequestTarget target) { if (searchTermModel.getObject() !=
>> null  &&  !searchTermModel.getObject().isEmpty()) {
>> profilePartitionTree.rebuildExpandedPartitions(); } else {
>> profilePartitionTree.getP
>> artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);* }
>> @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 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 occurred
>> org.apache.wicket.WicketRuntimeException: Error attaching this container
>> for rendering: [Subtree [Component id = subtree]] at
>> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
>> at org.apache.wicket.MarkupContai
>> ner.onBeforeRenderChildren(MarkupContainer.java:1753)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
>> at
>> dk.netdesign.XXX.frontend.tree.ChildAwareNestedTree.onBeforeRender(ChildAwareNestedTree.java:41)[106:XXX-frontend:1.0.4.RC_01]
>> at
>> org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.page.PartialPageUpdate.prepareComponent(PartialPageUpdate.java:322)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:250)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxRequestHandler.java:384)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)[136:org.apa
>> che.wicket.core:8.1.0] at
>> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)[139:org.apache.wicket.request:8.1.0]
>> at
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)[136:org.apache.wicket.core:8.1.0]
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(Requ

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

[nino martinez wael]

Yes I understand.. Let me see if it breaks in wicket examples, or I can
make it so.. Do you know another way to make a node/folder expand during
construction time? Feels like the expand method are meant for ajax calls
only.

-regards Nino

On Wed, Nov 28, 2018 at 4:16 PM sven  wrote:

>
>
> Hi Nino,
>
>
>
> during rendering of components no additional components can be added to
> the ART any more.
>
> I surprised that your code worked in 6.x, can you build a quickstart
> demonstrating the problem?
>
>
>
> Have fun
>
> Sven
>
>
>
>
>
>
>
>
>
> >
> > On 28.11.2018 at 14:38,wrote:
> >
> >
> >  Hi In wicket 6 this worked, there are another input field (ajax
> activated) that triggers the update : ChildAwareNestedTree
> profilePartitionTree = new ChildAwareNestedTree("skillsetSelect", provider,
> sharedExpansionState) { @Override protected Component
> newContentComponent(String id, IModel model) { TreeNode node =
> model.getObject(); if (node instanceof TreeNodeProvider.PartitionNode) {
> Partition partition = ((TreeNodeProvider.PartitionNode)
> node).getPartition(); if
> (getPartitionsWithProfiles().containsKey(partition.getId())) {*
> expand(node);* } } else if (node instanceof
> TreeNodeProvider.NoPartitionNode  &&  isNoPartitionProfilesPresent()) {*
> expand(node);* } } The triggering field: searchTerm.add(new
> AjaxFormComponentUpdatingBehavior("keydown") { @Override protected void
> onUpdate(AjaxRequestTarget target) { if (searchTermModel.getObject() !=
> null  &&  !searchTermModel.getObject().isEmpty()) {
> profilePartitionTree.rebuildExpandedPartitions(); } else {
> profilePartitionTree.getP
> artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);* }
> @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 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 occurred
> org.apache.wicket.WicketRuntimeException: Error attaching this container
> for rendering: [Subtree [Component id = subtree]] at
> org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
> at org.apache.wicket.MarkupContai
> ner.onBeforeRenderChildren(MarkupContainer.java:1753)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
> at
> dk.netdesign.XXX.frontend.tree.ChildAwareNestedTree.onBeforeRender(ChildAwareNestedTree.java:41)[106:XXX-frontend:1.0.4.RC_01]
> at
> org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.page.PartialPageUpdate.prepareComponent(PartialPageUpdate.java:322)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:250)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxRequestHandler.java:384)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)[136:org.apa
> che.wicket.core:8.1.0] at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)[139:org.apache.wicket.request:8.1.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)[136:org.apache.wicket.core:8.1.0]
> at
> org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322.CGLIB$processRequestCycle$6()[jar:bundle://128.0:0/!/:]
> at
> org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322$$FastClassByCGLIB$$c4e730b8.invoke()[jar:bundle://128.0:0/!/:]
> at
> net.sf.cglib.p

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

[sven]

 
 
Hi Nino,
 

 
during rendering of components no additional components can be added to the ART 
any more.
 
I surprised that your code worked in 6.x, can you build a quickstart 
demonstrating the problem?
 

 
Have fun
 
Sven
 

 

 
 
 
 
 
>  
> On 28.11.2018 at 14:38,wrote:
>  
>  
>  Hi In wicket 6 this worked, there are another input field (ajax activated) 
> that triggers the update : ChildAwareNestedTree profilePartitionTree = new 
> ChildAwareNestedTree("skillsetSelect", provider, sharedExpansionState) { 
> @Override protected Component newContentComponent(String id, IModel model) { 
> TreeNode node = model.getObject(); if (node instanceof 
> TreeNodeProvider.PartitionNode) { Partition partition = 
> ((TreeNodeProvider.PartitionNode) node).getPartition(); if 
> (getPartitionsWithProfiles().containsKey(partition.getId())) {* 
> expand(node);* } } else if (node instanceof TreeNodeProvider.NoPartitionNode  
> &&  isNoPartitionProfilesPresent()) {* expand(node);* } } The triggering 
> field: searchTerm.add(new AjaxFormComponentUpdatingBehavior("keydown") { 
> @Override protected void onUpdate(AjaxRequestTarget target) { if 
> (searchTermModel.getObject() != null  &&  
> !searchTermModel.getObject().isEmpty()) { 
> profilePartitionTree.rebuildExpandedPartitions(); } else { 
> profilePartitionTree.getP
artitionsWithProfiles().clear(); }* target.add(profilePartitionTree);* } 
@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 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 occurred 
org.apache.wicket.WicketRuntimeException: Error attaching this container for 
rendering: [Subtree [Component id = subtree]] at 
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
 at org.apache.wicket.MarkupContai
ner.onBeforeRenderChildren(MarkupContainer.java:1753)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]
 at 
dk.netdesign.XXX.frontend.tree.ChildAwareNestedTree.onBeforeRender(ChildAwareNestedTree.java:41)[106:XXX-frontend:1.0.4.RC_01]
 at 
org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.page.PartialPageUpdate.prepareComponent(PartialPageUpdate.java:322)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:250)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxRequestHandler.java:384)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)[136:org.apa
che.wicket.core:8.1.0] at 
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)[139:org.apache.wicket.request:8.1.0]
 at 
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)[136:org.apache.wicket.core:8.1.0]
  at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322.CGLIB$processRequestCycle$6()[jar:bundle://128.0:0/!/:]
 at 
org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322$$FastClassByCGLIB$$c4e730b8.invoke()[jar:bundle://128.0:0/!/:]
 at 
net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)[128:org.apache.servic
emix.bundles.cglib:2.2.2.1] at 
org.ops4j.pax.wicket.internal.servlet.PAXWicketServlet$WicketFilterCallback.intercept(PAXWicketServlet.java:236)[147:org.ops4j.pax.wicket.service:5.0.0]
 at 
org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322.processRequestCycle()[jar:bundle://128.0:0/!/:]
 at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)[136:org.apache.wicket.core:8.1.0]
 at 
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)[136:

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

[nino martinez wael]

Hi
In wicket 6 this worked, there are another input field (ajax activated)
that triggers the update :

   ChildAwareNestedTree profilePartitionTree = new
ChildAwareNestedTree("skillsetSelect", provider, sharedExpansionState)
{

@Override
protected Component newContentComponent(String id,
IModel model) {

TreeNode node = model.getObject();

if (node instanceof TreeNodeProvider.PartitionNode) {
Partition partition =
((TreeNodeProvider.PartitionNode) node).getPartition();
if
(getPartitionsWithProfiles().containsKey(partition.getId())) {*
expand(node);*
}
} else if (node instanceof
TreeNodeProvider.NoPartitionNode && isNoPartitionProfilesPresent()) {*
   expand(node);*
}

}

The triggering field:

searchTerm.add(new AjaxFormComponentUpdatingBehavior("keydown") {

@Override
protected void onUpdate(AjaxRequestTarget target) {
if (searchTermModel.getObject() != null &&
!searchTermModel.getObject().isEmpty()) {
profilePartitionTree.rebuildExpandedPartitions();
} else {
profilePartitionTree.getPartitionsWithProfiles().clear();
}*target.add(profilePartitionTree);*

}

@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 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 occurred

org.apache.wicket.WicketRuntimeException: Error attaching this container
for rendering: [Subtree [Component id = subtree]]

 at
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1753)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.Component.onBeforeRender(Component.java:3788)[136:org.apache.wicket.core:8.1.0]

 at
dk.netdesign.XXX.frontend.tree.ChildAwareNestedTree.onBeforeRender(ChildAwareNestedTree.java:41)[106:XXX-frontend:1.0.4.RC_01]

 at
org.apache.wicket.Component.beforeRender(Component.java:937)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.page.PartialPageUpdate.prepareComponent(PartialPageUpdate.java:322)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:250)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxRequestHandler.java:384)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)[139:org.apache.wicket.request:8.1.0]

 at
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)[136:org.apache.wicket.core:8.1.0]

 at
org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322.CGLIB$processRequestCycle$6()[jar:bundle://128.0:0/!/:]

 at
org.apache.wicket.protocol.http.WicketFilter$$EnhancerByCGLIB$$a4862322$$FastClassByCGLIB$$c4e730b8.invoke()[jar:bundle://128.0:0/!/:]

 at
net.sf.cglib.proxy.MethodPr

Re: Wicket 8 ModalWindow autosizing problem

[daniel]

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 additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 ModalWindow autosizing problem

[daniel]

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 additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 ModalWindow autosizing problem

[Martin Grigorov]

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 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.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Wicket 8 ModalWindow autosizing problem

[daniel]

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.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 8 ModalWindow autosizing problem

[Martin Grigorov]

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 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
> scrollbar or excessive window size. I've been trying to play around with
> various combinations of set/useInitial/Minimal/Height() and setAutoSize()
> without any luck so far.
>
> Any help is appreciated, thank you.
>
> Daniel
>
> --
> Sent from:
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Wicket 8 ModalWindow autosizing problem

[daniel]

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
scrollbar or excessive window size. I've been trying to play around with
various combinations of set/useInitial/Minimal/Height() and setAutoSize()
without any luck so far.

Any help is appreciated, thank you.

Daniel

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WebSocket tests fail after migration to Wicket 8

[Manfred Bergmann]

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 commands, e-mail: users-h...@wicket.apache.org

Re: WebSocket tests fail after migration to Wicket 8

[Andrea Del Bene]

Hi,

you probably found an issue with we recently fixed : 
https://issues.apache.org/jira/browse/WICKET-6588


Could you test your code using 8.2.0-SNAPSHOT version?

Thank you.


On 29/09/2018 16:58, Manfred Bergmann wrote:


Hi.

I’m using a WebSocket on a component of a page based on WebSocketBehavior.
It’s working fine when running the app.

But the tests of the Panel fail, in contrast to Wicket 7 with:

Caused by: java.lang.NullPointerException
at 
org.apache.wicket.protocol.ws.api.BaseWebSocketBehavior.getSessionId(BaseWebSocketBehavior.java:176)
 ~[wicket-native-websocket-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





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WebSocket tests fail after migration to Wicket 8

[Manfred Bergmann]

Hi.

I’m using a WebSocket on a component of a page based on WebSocketBehavior.
It’s working fine when running the app.

But the tests of the Panel fail, in contrast to Wicket 7 with:

Caused by: java.lang.NullPointerException
at 
org.apache.wicket.protocol.ws.api.BaseWebSocketBehavior.getSessionId(BaseWebSocketBehavior.java:176)
 ~[wicket-native-websocket-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

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

[SUBRA]

Investigated the issue, the fix provided in 

https://issues.apache.org/jira/browse/WICKET-6509 is not resolving the
problem. 

Still In the generated manifest file the packages are present as it is
previously with out resolution : optional

Instead of setting the resolution:optional in the 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 specified above

It resolves the problem, that means setting the resolution optional in the
manifest file





--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

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

[SUBRA]

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.wiring.package=junit.framework)




--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

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

[Martin Grigorov]

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 is not.
>

This issue has been tested successfully by its reporter.

As it is explained in the comments none of the Wicket developers uses/knows
OSGi, so you will have to explain better what is the issue you face and to
suggest an improvement.
Thank you!


> https://issues.apache.org/jira/browse/WICKET-6509
> <https://issues.apache.org/jira/browse/WICKET-6509>
>
> Fixed version : *8.0.0-M9*
> Using wicket-core : *8.0.0*
>
> Please help me to resolve the issue
>
> --
> Sent from:
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Wicket 8 : OSGI wiring problem with junit framework.

[SUBRA]

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/jira/browse/WICKET-6509>  

Fixed version : *8.0.0-M9*
Using wicket-core : *8.0.0*

Please help me to resolve the issue

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Nice article on Wicket 8 by the New Stack

[Sebastien Briquet]

Very nice! Thanks for sharing! :)

Re: Nice article on Wicket 8 by the New Stack

[Andrea Del Bene]

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-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: Nice article on Wicket 8 by the New Stack

[Sven Meier]

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
>
>-
>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>For additional commands, e-mail: users-h...@wicket.apache.org

Nice article on Wicket 8 by the New Stack

[Martijn Dashorst]

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

[Korbinian Bachl]

Awesome! - I think I now got this. 

So, i need to use 
IRequestHandler mapRequest(Request request);
to handle the incoming request to "decode" the fake path/ part
and using 
Url mapHandler(IRequestHandler requestHandler);
I can put in any fake path/ part into the URL that goes to the 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:38:43
> Betreff: Re: wicket 8 / RootRequestMapper vs CompoundRequestMapper

> On Mon, Jun 11, 2018 at 1:33 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
> 
>> Hi,
>>
>> thanks a lot for the clarification. So say I want to do some kind of path
>> rewriting/ faking like the apache mod_rewrite does. I then would use a new
>> root mapper and have this one handle the request, fake the url and give it
>> to the "prior" mappers to resolve as in that case I need to make sure I'm
>> the first one in the hierarchy. But where would I then rewrite the
>> generated URLs?
>>
> 
> The request mappers are hierarchical.
> See how CryptoMapper does it.
> An encrypted url comes, CryptoMapper decrypts it, pass it to the underlying
> mappers, they handle the request, then produce readable urls for the
> links/redirect, and finally CryptoMapper encrypts those.
> 
> 
>>
>> Best,
>>
>> KB
>>
>> - Ursprüngliche Mail -
>> > 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!
>> >
>> > 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 -> compound ->
>> > mapper etc), the earlier it is called.
>> > Note that this is not that important, since the compound mapper works
>> with
>> > scores, but nevertheless if you want to do something like prefixing or
>> > postfixing urls, order does matter.
>> >
>> > This is also why, for example, the https mapper should be installed after
>> > all other mappers, and as the root mapper.
>> >
>> > If you just want to map some pages, just add the mapper and don’t worry
>> > about where in the hierarchy it is. As long as it returns a score higher
>> > than any other, it will be used.
>> >
>> > Met vriendelijke groet,
>> > Kind regards,
>> >
>> > Bas Gooren
>> >
>> > Op 11 juni 2018 bij 11:38:31, Korbinian Bachl (
>> > korbinian.ba...@whiskyworld.de) schreef:
>> >
>> > 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.:
>> >
>> > YourApplication#init():
>> > old = application.getRootRequestMapper()
>> > application.setRootRequestMapper(new CustomRequestMapper(old))
>> >
>> > or a CompoundRequestMapper e.g.:
>> >
>> > application.getRootRequestMapperAsCompound().add(new
>> > CustomRequestMapper(old));
>> >
>> > But what are the pros or cons of using either RootRequestMapper vs
>> > CompoundRequestMapper?
>> >
>> > From my point of view the only difference is that CompoundRequestMapper
>> > gets exectued based on score, where max score gets used first and lower
>> > scores later as long as the
>> >
>> > public IRequestHandler mapRequest(Request request)
>> >
>> > doesnt return null anymore; Did I miss something?
>> >
>> >
>> > Best,
>> >
>> > KB
>> >
>> > -
>> > 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
>>

-
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

[Martin Grigorov]

On Mon, Jun 11, 2018 at 1:33 PM, Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:

> Hi,
>
> thanks a lot for the clarification. So say I want to do some kind of path
> rewriting/ faking like the apache mod_rewrite does. I then would use a new
> root mapper and have this one handle the request, fake the url and give it
> to the "prior" mappers to resolve as in that case I need to make sure I'm
> the first one in the hierarchy. But where would I then rewrite the
> generated URLs?
>

The request mappers are hierarchical.
See how CryptoMapper does it.
An encrypted url comes, CryptoMapper decrypts it, pass it to the underlying
mappers, they handle the request, then produce readable urls for the
links/redirect, and finally CryptoMapper encrypts those.


>
> Best,
>
> KB
>
> - Ursprüngliche Mail -
> > 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!
> >
> > 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 -> compound ->
> > mapper etc), the earlier it is called.
> > Note that this is not that important, since the compound mapper works
> with
> > scores, but nevertheless if you want to do something like prefixing or
> > postfixing urls, order does matter.
> >
> > This is also why, for example, the https mapper should be installed after
> > all other mappers, and as the root mapper.
> >
> > If you just want to map some pages, just add the mapper and don’t worry
> > about where in the hierarchy it is. As long as it returns a score higher
> > than any other, it will be used.
> >
> > Met vriendelijke groet,
> > Kind regards,
> >
> > Bas Gooren
> >
> > Op 11 juni 2018 bij 11:38:31, Korbinian Bachl (
> > korbinian.ba...@whiskyworld.de) schreef:
> >
> > 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.:
> >
> > YourApplication#init():
> > old = application.getRootRequestMapper()
> > application.setRootRequestMapper(new CustomRequestMapper(old))
> >
> > or a CompoundRequestMapper e.g.:
> >
> > application.getRootRequestMapperAsCompound().add(new
> > CustomRequestMapper(old));
> >
> > But what are the pros or cons of using either RootRequestMapper vs
> > CompoundRequestMapper?
> >
> > From my point of view the only difference is that CompoundRequestMapper
> > gets exectued based on score, where max score gets used first and lower
> > scores later as long as the
> >
> > public IRequestHandler mapRequest(Request request)
> >
> > doesnt return null anymore; Did I miss something?
> >
> >
> > Best,
> >
> > KB
> >
> > -
> > 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: wicket 8 / RootRequestMapper vs CompoundRequestMapper

[Korbinian Bachl]

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 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/950403d5ccea5643e6005450c6b808ea72079d59/wicket-core/src/main/java/org/apache/wicket/protocol/http/WebApplication.java#L319
> https://github.com/apache/wicket/blob/950403d5ccea5643e6005450c6b808ea72079d59/wicket-core/src/main/java/org/apache/wicket/Application.java#L741-L750
> 
> On Mon, Jun 11, 2018 at 12:38 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
> 
>> 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.:
>>
>> YourApplication#init():
>> old = application.getRootRequestMapper()
>> application.setRootRequestMapper(new CustomRequestMapper(old))
>>
>> or a CompoundRequestMapper e.g.:
>>
>> application.getRootRequestMapperAsCompound().add(new
>> CustomRequestMapper(old));
>>
>> But what are the pros or cons of using either RootRequestMapper vs
>> CompoundRequestMapper?
>>
>> From my point of view the only difference is that CompoundRequestMapper
>> gets exectued based on score, where max score gets used first and lower
>> scores later as long as the
>>
>> public IRequestHandler mapRequest(Request request)
>>
>> doesnt return null anymore; Did I miss something?
>>
>>
>> Best,
>>
>> KB
>>
>> -
>> 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: wicket 8 / RootRequestMapper vs CompoundRequestMapper

[Korbinian Bachl]

Hi,

thanks a lot for the clarification. So say I want to do some kind of path 
rewriting/ faking like the apache mod_rewrite does. I then would use a new root 
mapper and have this one handle the request, fake the url and give it to the 
"prior" mappers to resolve as in that case I need 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
> Betreff: 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 -> compound ->
> mapper etc), the earlier it is called.
> Note that this is not that important, since the compound mapper works with
> scores, but nevertheless if you want to do something like prefixing or
> postfixing urls, order does matter.
> 
> This is also why, for example, the https mapper should be installed after
> all other mappers, and as the root mapper.
> 
> If you just want to map some pages, just add the mapper and don’t worry
> about where in the hierarchy it is. As long as it returns a score higher
> than any other, it will be used.
> 
> Met vriendelijke groet,
> Kind regards,
> 
> Bas Gooren
> 
> Op 11 juni 2018 bij 11:38:31, Korbinian Bachl (
> korbinian.ba...@whiskyworld.de) schreef:
> 
> 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.:
> 
> YourApplication#init():
> old = application.getRootRequestMapper()
> application.setRootRequestMapper(new CustomRequestMapper(old))
> 
> or a CompoundRequestMapper e.g.:
> 
> application.getRootRequestMapperAsCompound().add(new
> CustomRequestMapper(old));
> 
> But what are the pros or cons of using either RootRequestMapper vs
> CompoundRequestMapper?
> 
> From my point of view the only difference is that CompoundRequestMapper
> gets exectued based on score, where max score gets used first and lower
> scores later as long as the
> 
> public IRequestHandler mapRequest(Request request)
> 
> doesnt return null anymore; Did I miss something?
> 
> 
> Best,
> 
> KB
> 
> -
> 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: wicket 8 / RootRequestMapper vs CompoundRequestMapper

[Martin Grigorov]

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/950403d5ccea5643e6005450c6b808ea72079d59/wicket-core/src/main/java/org/apache/wicket/protocol/http/WebApplication.java#L319
https://github.com/apache/wicket/blob/950403d5ccea5643e6005450c6b808ea72079d59/wicket-core/src/main/java/org/apache/wicket/Application.java#L741-L750

On Mon, Jun 11, 2018 at 12:38 PM, Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:

> 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.:
>
> YourApplication#init():
> old = application.getRootRequestMapper()
> application.setRootRequestMapper(new CustomRequestMapper(old))
>
> or a CompoundRequestMapper e.g.:
>
> application.getRootRequestMapperAsCompound().add(new
> CustomRequestMapper(old));
>
> But what are the pros or cons of using either RootRequestMapper vs
> CompoundRequestMapper?
>
> From my point of view the only difference is that CompoundRequestMapper
> gets exectued based on score, where max score gets used first and lower
> scores later as long as the
>
> public IRequestHandler mapRequest(Request request)
>
> doesnt return null anymore; Did I miss something?
>
>
> Best,
>
> KB
>
> -
> 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

[Bas Gooren]

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 -> compound ->
mapper etc), the earlier it is called.
Note that this is not that important, since the compound mapper works with
scores, but nevertheless if you want to do something like prefixing or
postfixing urls, order does matter.

This is also why, for example, the https mapper should be installed after
all other mappers, and as the root mapper.

If you just want to map some pages, just add the mapper and don’t worry
about where in the hierarchy it is. As long as it returns a score higher
than any other, it will be used.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 11 juni 2018 bij 11:38:31, Korbinian Bachl (
korbinian.ba...@whiskyworld.de) schreef:

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.:

YourApplication#init():
old = application.getRootRequestMapper()
application.setRootRequestMapper(new CustomRequestMapper(old))

or a CompoundRequestMapper e.g.:

application.getRootRequestMapperAsCompound().add(new
CustomRequestMapper(old));

But what are the pros or cons of using either RootRequestMapper vs
CompoundRequestMapper?

>From my point of view the only difference is that CompoundRequestMapper
gets exectued based on score, where max score gets used first and lower
scores later as long as the

public IRequestHandler mapRequest(Request request)

doesnt return null anymore; Did I miss something?


Best,

KB

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

wicket 8 / RootRequestMapper vs CompoundRequestMapper

[Korbinian Bachl]

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.:

YourApplication#init():
old = application.getRootRequestMapper()
application.setRootRequestMapper(new CustomRequestMapper(old))

or a CompoundRequestMapper e.g.:

application.getRootRequestMapperAsCompound().add(new CustomRequestMapper(old));

But what are the pros or cons of using either RootRequestMapper vs 
CompoundRequestMapper?

>From my point of view the only difference is that CompoundRequestMapper gets 
>exectued based on score, where max score gets used first and lower scores 
>later as long as the 

public IRequestHandler mapRequest(Request request) 

doesnt return null anymore; Did I miss something?


Best,

KB

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: ChainingModel warnings in Wicket 8

[Thomas Heigl]

Hi Maxim,

Created https://issues.apache.org/jira/browse/WICKET-6560.

Thomas

On Sat, Jun 9, 2018 at 5:44 AM, Maxim Solodovnik 
wrote:

> Sounds like these 2 comments worth JIRA
> Or Jira+PR ;))
>
> On Thu, Jun 7, 2018 at 9:45 PM, Thomas Heigl  wrote:
> > Also the warning is logged for `null` objects, which probably shouldn't
> > happen.
> >
> > public ChainingModel(final Object modelObject)
> >> {
> >> if (modelObject instanceof Session)
> >> {
> >> LOG.warn("It is not a good idea to reference the .");
> >> } else if (modelObject instanceof Serializable == false)
> >> {
> >> LOG.warn("It is not a good idea to reference a non-serializable
> >> instance ");
> >> }
> >> target = modelObject;
> >> }
> >
> >
> > It should read something like:
> >
> > if (modelObject != null && modelObject 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 reference a
> >>> non-serializable instance in models directly as it may lead to
> >>> serialization problems
> >>
> >>
> >> The warning is OK, but it gives me absolutely no hint where to look for
> >> the issue. Could someone please add the (simple) class name of the model
> >> object to the warning message?
> >>
> >> Currently, the only way for me to find these issues is with a breakpoint
> >> in `ChainingModel` and clicking through my application until I hit the
> >> warning.
> >>
> >> Best,
> >>
> >> Thomas
> >>
>
>
>
> --
> WBR
> Maxim aka solomax
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ChainingModel warnings in Wicket 8

[Maxim Solodovnik]

Sounds like these 2 comments worth JIRA
Or Jira+PR ;))

On Thu, Jun 7, 2018 at 9:45 PM, Thomas Heigl  wrote:
> Also the warning is logged for `null` objects, which probably shouldn't
> happen.
>
> public ChainingModel(final Object modelObject)
>> {
>> if (modelObject instanceof Session)
>> {
>> LOG.warn("It is not a good idea to reference the .");
>> } else if (modelObject instanceof Serializable == false)
>> {
>> LOG.warn("It is not a good idea to reference a non-serializable
>> instance ");
>> }
>> target = modelObject;
>> }
>
>
> It should read something like:
>
> if (modelObject != null && modelObject 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 reference a
>>> non-serializable instance in models directly as it may lead to
>>> serialization problems
>>
>>
>> The warning is OK, but it gives me absolutely no hint where to look for
>> the issue. Could someone please add the (simple) class name of the model
>> object to the warning message?
>>
>> Currently, the only way for me to find these issues is with a breakpoint
>> in `ChainingModel` and clicking through my application until I hit the
>> warning.
>>
>> Best,
>>
>> Thomas
>>



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Release WiQuery for Wicket 8

[Emond Papegaaij]

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...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Release WiQuery for Wicket 8

[Martin Grigorov]

 >>
> > >> > > >>  0.023 s]
> > >> > > >>
> > >> > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT ..
> > >> > > >> SKIPPED
> > >> > > >> [INFO] --
> > >>
> > >> --
> > >>
> > >> > > >> 
> > >> > > >> [INFO] BUILD FAILURE
> > >> > > >> [INFO] --
> > >>
> > >> --
> > >>
> > >> > > >> 
> > >> > > >> [INFO] Total time: 3.720 s
> > >> > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00
> > >> > > >> [INFO] --
> > >>
> > >> --
> > >>
> > >> > > >> 
> > >> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui:
> Could
> > >>
> > >> not
> > >>
> > >> > > >> resolve dependencies for project org.wicketstuff.wiquery:
> > >> > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
> > >> > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
> > >> > > >> https://oss.sonatype.org/content/repositories/snapshots was
> > >>
> > >> cached in
> > >>
> > >> > > >> the local repository, resolution will not be reattempted until
> the
> > >> >
> > >> > update
> > >> >
> > >> > > >> interval of sonatype-nexus-snapshots has elapsed or updates are
> > >> >
> > >> > forced ->
> > >> >
> > >> > > >> [Help 1]
> > >> > > >> [ERROR]
> > >> > > >
> > >> > > > 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, Emond Papegaaij <
> > >> > > >
> > >> > > > emond.papega...@topicus.nl> wrote:
> > >> > > >> Hi Thomas,
> > >> > > >>
> > >> > > >> The easiest way is to just run 'mvn install' and depend on
> > >> >
> > >> > 8.0-SNAPSHOT.
> > >> >
> > >> > > >> I did
> > >> > > >> not do a release, as I cannot push to central. If you want to
> run
> > >>
> > >> your
> > >>
> > >> > > >> tests
> > >> > > >> on some CI server, you probably have to push the artifacts to a
> > >>
> > >> local
> > >>
> > >> > > >> repo
> > >> > > >> also.
> > >> > > >>
> > >> > > >> Best regards,
> > >> > > >> Emond
> > >> > > >>
> > >> > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
> > >> > > >> > Hi 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?
> > >> > > >> >
> > >> > > >> > Best,
> > >> > > >> >
> > >> > > >> > Thomas
> > >> > > >> >
> > >> > > >> > On 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
> > >> > > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more
> cleanu

Re: Release WiQuery for Wicket 8

[Emond Papegaaij]

 >> > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00
> >> > > >> [INFO] --
> >> 
> >> --
> >> 
> >> > > >> 
> >> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could
> >> 
> >> not
> >> 
> >> > > >> resolve dependencies for project org.wicketstuff.wiquery:
> >> > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
> >> > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
> >> > > >> https://oss.sonatype.org/content/repositories/snapshots was
> >> 
> >> cached in
> >> 
> >> > > >> the local repository, resolution will not be reattempted until the
> >> > 
> >> > update
> >> > 
> >> > > >> interval of sonatype-nexus-snapshots has elapsed or updates are
> >> > 
> >> > forced ->
> >> > 
> >> > > >> [Help 1]
> >> > > >> [ERROR]
> >> > > > 
> >> > > > 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, Emond Papegaaij <
> >> > > > 
> >> > > > emond.papega...@topicus.nl> wrote:
> >> > > >> Hi Thomas,
> >> > > >> 
> >> > > >> The easiest way is to just run 'mvn install' and depend on
> >> > 
> >> > 8.0-SNAPSHOT.
> >> > 
> >> > > >> I did
> >> > > >> not do a release, as I cannot push to central. If you want to run
> >> 
> >> your
> >> 
> >> > > >> tests
> >> > > >> on some CI server, you probably have to push the artifacts to a
> >> 
> >> local
> >> 
> >> > > >> repo
> >> > > >> also.
> >> > > >> 
> >> > > >> Best regards,
> >> > > >> Emond
> >> > > >> 
> >> > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
> >> > > >> > Hi 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?
> >> > > >> > 
> >> > > >> > Best,
> >> > > >> > 
> >> > > >> > Thomas
> >> > > >> > 
> >> > > >> > On 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
> >> > > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup
> >> 
> >> and
> >> 
> >> > > >> > > refactoring.
> >> > > >> > > Please test the changes in your project. The tests pass and
> >> > > >> > > the
> >> > 
> >> > demo
> >> > 
> >> > > >> runs
> >> > > >> 
> >> > > >> > > fine, but my project only uses a limited set of the UI
> >> 
> >> components.
> >> 
> >> > > >> > > Best regards,
> >> > > >> > > Emond
> >> > > >> > > 
> >> > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote:
> >> > > >> > > > I'm planning to upgrade jQuery UI to the latest version next
> >> > 
> >> > week.
> >> > 
> >> > > >> We
> >> > > >> 
> >> > > >> > > > are
> >> > > >> > > > currently migrating all

Re: ChainingModel warnings in Wicket 8

[Thomas Heigl]

Also the warning is logged for `null` objects, which probably shouldn't
happen.

public ChainingModel(final Object modelObject)
> {
> if (modelObject instanceof Session)
> {
> LOG.warn("It is not a good idea to reference the .");
> } else if (modelObject instanceof Serializable == false)
> {
> LOG.warn("It is not a good idea to reference a non-serializable
> instance ");
> }
> target = modelObject;
> }


It should read something like:

if (modelObject != null && modelObject 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 reference a
>> non-serializable instance in models directly as it may lead to
>> serialization problems
>
>
> The warning is OK, but it gives me absolutely no hint where to look for
> the issue. Could someone please add the (simple) class name of the model
> object to the warning message?
>
> Currently, the only way for me to find these issues is with a breakpoint
> in `ChainingModel` and clicking through my application until I hit the
> warning.
>
> Best,
>
> Thomas
>

Re: Release WiQuery for Wicket 8

[Martin Grigorov]

 >
>> > > > 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, Emond Papegaaij <
>> > > >
>> > > > emond.papega...@topicus.nl> wrote:
>> > > >> Hi Thomas,
>> > > >>
>> > > >> The easiest way is to just run 'mvn install' and depend on
>> > 8.0-SNAPSHOT.
>> > > >> I did
>> > > >> not do a release, as I cannot push to central. If you want to run
>> your
>> > > >> tests
>> > > >> on some CI server, you probably have to push the artifacts to a
>> local
>> > > >> repo
>> > > >> also.
>> > > >>
>> > > >> Best regards,
>> > > >> Emond
>> > > >>
>> > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
>> > > >> > Hi 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?
>> > > >> >
>> > > >> > Best,
>> > > >> >
>> > > >> > Thomas
>> > > >> >
>> > > >> > On 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
>> > > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup
>> and
>> > > >> > > refactoring.
>> > > >> > > Please test the changes in your project. The tests pass and the
>> > demo
>> > > >>
>> > > >> runs
>> > > >>
>> > > >> > > fine, but my project only uses a limited set of the UI
>> components.
>> > > >> > >
>> > > >> > > Best regards,
>> > > >> > > Emond
>> > > >> > >
>> > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote:
>> > > >> > > > I'm planning to upgrade jQuery UI to the latest version next
>> > week.
>> > > >>
>> > > >> We
>> > > >>
>> > > >> > > > are
>> > > >> > > > currently migrating all our applications to wicket 8 and also
>> > > >>
>> > > >> depend on
>> > > >>
>> > > >> > > > wiquery quite a lot. It does however seem that jQuery UI is
>> > mostly
>> > > >>
>> > > >> dead.
>> > > >>
>> > > >> > > > The rest of the world probably switched to yet another fancy
>> > > >>
>> > > >> JavaScript
>> > > >>
>> > > >> > > ui
>> > > >> > >
>> > > >> > > > library. At least the will make it easy to stay up to date
>> with
>> > the
>> > > >> > >
>> > > >> > > latest
>> > > >> > >
>> > > >> > > > version :)
>> > > >> > > >
>> > > >> > > > I can't push a release to central, but perhaps Martin can do
>> > that
>> > > >>
>> > > >> when
>> > > >>
>> > > >> > > I'm
>> > > >> > >
>> > > >> > > > done? For now you can use a snapshot build. It works, but
>> the UI
>> > > >> > > > API
>> > > >> > >
>> > > >> > > might
>> > > >> > >
>> > > >> > > > change a bit before the 8.0 release.
>> > > >> > > >
>> > > >> > > > Best regards,
>> > > >> > > > Emond Papegaaij
>> > > >> > > >
>> > > >> > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl <
>> > tho...@umschalt.com>:
>> > > >> > > > > Hi Ernesto,
>> > > >> > > > >
>> > > >> > > > > I'm not sure how many people are still using it. But as I
>> > said,
>> > > >> > > > > my
>> > > >> > >
>> > > >> > > project
>> > > >> > >
>> > > >> > > > > heavily depends on it.
>> > > >> > > > >
>> > > >> > > > > @papegaaij has resolved all the compile errors against
>> > 8.0.0-M9 (
>> > > >> > > > > https://github.com/wicketstuff/wiquery) and a simple
>> release
>> > of
>> > > >>
>> > > >> 8.0.0
>> > > >>
>> > > >> > > > > would
>> > > >> > > > > be enough for me.
>> > > >> > > > >
>> > > >> > > > > Best,
>> > > >> > > > >
>> > > >> > > > > Thomas
>> > > >> > > > >
>> > > >> > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
>> > > >> > > > >
>> > > >> > > > > reier...@gmail.com> wrote:
>> > > >> > > > > > Hi,
>> > > >> > > > > >
>> > > >> > > > > > I do not know who is actually using this project. I use
>> to
>> > > >> > >
>> > > >> > > contribute to
>> > > >> > >
>> > > >> > > > > it
>> > > >> > > > >
>> > > >> > > > > > a few years ago. I haven't used it for ages..
>> > > >> > > > > >
>> > > >> > > > > > On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl <
>> > > >>
>> > > >> tho...@umschalt.com>
>> > > >>
>> > > >> > > > > wrote:
>> > > >> > > > > > > Hi,
>> > > >> > > > > > >
>> > > >> > > > > > > Following the release of Wicket 8.0.0 and WicketStuff
>> > 8.0.0,
>> > > >>
>> > > >> could
>> > > >>
>> > > >> > > > > > somebody
>> > > >> > > > > >
>> > > >> > > > > > > please cut a release of WiQuery compatible with the new
>> > > >>
>> > > >> version?
>> > > >>
>> > > >> > > > > > > Our application still heavily relies on WiQuery and we
>> > can't
>> > > >>
>> > > >> move
>> > > >>
>> > > >> > > to
>> > > >> > >
>> > > >> > > > > > Wicket
>> > > >> > > > > >
>> > > >> > > > > > > 8 without it.
>> > > >> > > > > > >
>> > > >> > > > > > > Best,
>> > > >> > > > > > >
>> > > >> > > > > > > Thomas
>> > > >> > > > > >
>> > > >> > > > > > --
>> > > >> > > > > > Regards - Ernesto Reinaldo Barreiro
>> > > >> > >
>> > > >> > > 
>> > -
>> > > >> > > 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
>> >
>> >
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>> >
>>
>
>

ChainingModel warnings in Wicket 8

[Thomas Heigl]

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 it gives me absolutely no hint where to look for the
issue. Could someone please add the (simple) class name of the model object
to the warning message?

Currently, the only way for me to find these issues is with a breakpoint in
`ChainingModel` and clicking through my application until I hit the warning.

Best,

Thomas

Re: Release WiQuery for Wicket 8

[Martin Grigorov]

OK. I will make a release!

On Thu, Jun 7, 2018 at 3:25 PM, Thomas Heigl  wrote:

> Hi Emond,
>
> I did some exploratory testing against the current build. I checked Dialog,
> Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be
> working at first glance.
>
> All my tests pass as well.
>
> Best,
>
> Thomas
>
> On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij <
> emond.papega...@topicus.nl>
> wrote:
>
> > I've fixed the problem. The setup currently used is discouraged and
> broken
> > in
> > m2e, but I don't feel like restructuring the whole thing to get rid of
> > this
> > test-jar.
> >
> > Emond
> >
> > On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote:
> > > The culprit is:
> > >
> > > https://github.com/wicketstuff/wiquery/commit/
> > 0235691174ceeede22b588d2f67868
> > > b940d9be3a
> > > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl 
> > wrote:
> > > > `mvn clean install` fails for me because no test-jar is built for the
> > core
> > > > module:
> > > >
> > > > [INFO] WiQuery Parent 8.0-SNAPSHOT  SUCCESS [
> > > >
> > > >>  0.353 s]
> > > >>
> > > >> [INFO] WiQuery Core Project ...
> SUCCESS [
> > > >>
> > > >>  2.673 s]
> > > >>
> > > >> [INFO] WiQuery jQuery UI Project .. FAILURE
> [
> > > >>
> > > >>  0.023 s]
> > > >>
> > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED
> > > >> [INFO] 
> > > >> 
> > > >> [INFO] BUILD FAILURE
> > > >> [INFO] 
> > > >> 
> > > >> [INFO] Total time: 3.720 s
> > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00
> > > >> [INFO] 
> > > >> 
> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could
> not
> > > >> resolve dependencies for project org.wicketstuff.wiquery:
> > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
> > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
> > > >> https://oss.sonatype.org/content/repositories/snapshots was cached
> in
> > > >> the local repository, resolution will not be reattempted until the
> > update
> > > >> interval of sonatype-nexus-snapshots has elapsed or updates are
> > forced ->
> > > >> [Help 1]
> > > >> [ERROR]
> > > >
> > > > 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, Emond Papegaaij <
> > > >
> > > > emond.papega...@topicus.nl> wrote:
> > > >> Hi Thomas,
> > > >>
> > > >> The easiest way is to just run 'mvn install' and depend on
> > 8.0-SNAPSHOT.
> > > >> I did
> > > >> not do a release, as I cannot push to central. If you want to run
> your
> > > >> tests
> > > >> on some CI server, you probably have to push the artifacts to a
> local
> > > >> repo
> > > >> also.
> > > >>
> > > >> Best regards,
> > > >> Emond
> > > >>
> > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
> > > >> > Hi 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?
> > > >> >
> > > >> > Best,
> > > >> >
> > > >> > Thomas
> > > >> >
> > > >> > On 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
> > > >&g

Re: Release WiQuery for Wicket 8

[Thomas Heigl]

Hi Emond,

I did some exploratory testing against the current build. I checked Dialog,
Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be
working at first glance.

All my tests pass as well.

Best,

Thomas

On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij 
wrote:

> I've fixed the problem. The setup currently used is discouraged and broken
> in
> m2e, but I don't feel like restructuring the whole thing to get rid of
> this
> test-jar.
>
> Emond
>
> On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote:
> > The culprit is:
> >
> > https://github.com/wicketstuff/wiquery/commit/
> 0235691174ceeede22b588d2f67868
> > b940d9be3a
> > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl 
> wrote:
> > > `mvn clean install` fails for me because no test-jar is built for the
> core
> > > module:
> > >
> > > [INFO] WiQuery Parent 8.0-SNAPSHOT  SUCCESS [
> > >
> > >>  0.353 s]
> > >>
> > >> [INFO] WiQuery Core Project ... SUCCESS [
> > >>
> > >>  2.673 s]
> > >>
> > >> [INFO] WiQuery jQuery UI Project .. FAILURE [
> > >>
> > >>  0.023 s]
> > >>
> > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED
> > >> [INFO] 
> > >> 
> > >> [INFO] BUILD FAILURE
> > >> [INFO] 
> > >> 
> > >> [INFO] Total time: 3.720 s
> > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00
> > >> [INFO] 
> > >> 
> > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not
> > >> resolve dependencies for project org.wicketstuff.wiquery:
> > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
> > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
> > >> https://oss.sonatype.org/content/repositories/snapshots was cached in
> > >> the local repository, resolution will not be reattempted until the
> update
> > >> interval of sonatype-nexus-snapshots has elapsed or updates are
> forced ->
> > >> [Help 1]
> > >> [ERROR]
> > >
> > > 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, Emond Papegaaij <
> > >
> > > emond.papega...@topicus.nl> wrote:
> > >> Hi Thomas,
> > >>
> > >> The easiest way is to just run 'mvn install' and depend on
> 8.0-SNAPSHOT.
> > >> I did
> > >> not do a release, as I cannot push to central. If you want to run your
> > >> tests
> > >> on some CI server, you probably have to push the artifacts to a local
> > >> repo
> > >> also.
> > >>
> > >> Best regards,
> > >> Emond
> > >>
> > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
> > >> > Hi 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?
> > >> >
> > >> > Best,
> > >> >
> > >> > Thomas
> > >> >
> > >> > On 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
> > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and
> > >> > > refactoring.
> > >> > > Please test the changes in your project. The tests pass and the
> demo
> > >>
> > >> runs
> > >>
> > >> > > fine, but my project only uses a limited set of the UI components.
> > >> > >
> > >> > > Best regards,
> > >> > > Emond
> > >> > >
> > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote:
> > >> > > > I'm planning to upgrade jQuery

Re: Release WiQuery for Wicket 8

[Emond Papegaaij]

I've fixed the problem. The setup currently used is discouraged and broken in 
m2e, but I don't feel like restructuring the whole thing to get rid of this 
test-jar.

Emond

On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote:
> The culprit is:
> 
> https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868
> b940d9be3a
> On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl  wrote:
> > `mvn clean install` fails for me because no test-jar is built for the core
> > module:
> > 
> > [INFO] WiQuery Parent 8.0-SNAPSHOT  SUCCESS [
> > 
> >>  0.353 s]
> >> 
> >> [INFO] WiQuery Core Project ... SUCCESS [
> >> 
> >>  2.673 s]
> >> 
> >> [INFO] WiQuery jQuery UI Project .. FAILURE [
> >> 
> >>  0.023 s]
> >> 
> >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED
> >> [INFO] 
> >> 
> >> [INFO] BUILD FAILURE
> >> [INFO] 
> >> 
> >> [INFO] Total time: 3.720 s
> >> [INFO] Finished at: 2018-06-06T11:48:16+02:00
> >> [INFO] 
> >> 
> >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not
> >> resolve dependencies for project org.wicketstuff.wiquery:
> >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
> >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
> >> https://oss.sonatype.org/content/repositories/snapshots was cached in
> >> the local repository, resolution will not be reattempted until the update
> >> interval of sonatype-nexus-snapshots has elapsed or updates are forced ->
> >> [Help 1]
> >> [ERROR]
> > 
> > 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, Emond Papegaaij <
> > 
> > emond.papega...@topicus.nl> wrote:
> >> Hi Thomas,
> >> 
> >> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT.
> >> I did
> >> not do a release, as I cannot push to central. If you want to run your
> >> tests
> >> on some CI server, you probably have to push the artifacts to a local
> >> repo
> >> also.
> >> 
> >> Best regards,
> >> Emond
> >> 
> >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
> >> > Hi 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?
> >> > 
> >> > Best,
> >> > 
> >> > Thomas
> >> > 
> >> > On 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
> >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and
> >> > > refactoring.
> >> > > Please test the changes in your project. The tests pass and the demo
> >> 
> >> runs
> >> 
> >> > > fine, but my project only uses a limited set of the UI components.
> >> > > 
> >> > > Best regards,
> >> > > Emond
> >> > > 
> >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote:
> >> > > > I'm planning to upgrade jQuery UI to the latest version next week.
> >> 
> >> We
> >> 
> >> > > > are
> >> > > > currently migrating all our applications to wicket 8 and also
> >> 
> >> depend on
> >> 
> >> > > > wiquery quite a lot. It does however seem that jQuery UI is mostly
> >> 
> >> dead.
> >> 
> >> > > > The rest of the world probably switched to yet another fancy
> >> 
> >> JavaScript
> >> 
> >> > > ui
> >> > > 
> >> > > > library. At least the will make it easy to stay up to date with the
> >> > > 
> >> > > latest
> >> > > 
> >> >

Re: Release WiQuery for Wicket 8

[Emond Papegaaij]

You are right, I still had the artifacts in my local repo. The old 
configuration did not build anymore due to changes in the jar-plugin. I'll 
look into it.

Emond

On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote:
> The culprit is:
> 
> https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868
> b940d9be3a
> On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl  wrote:
> > `mvn clean install` fails for me because no test-jar is built for the core
> > module:
> > 
> > [INFO] WiQuery Parent 8.0-SNAPSHOT  SUCCESS [
> > 
> >>  0.353 s]
> >> 
> >> [INFO] WiQuery Core Project ... SUCCESS [
> >> 
> >>  2.673 s]
> >> 
> >> [INFO] WiQuery jQuery UI Project .. FAILURE [
> >> 
> >>  0.023 s]
> >> 
> >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED
> >> [INFO] 
> >> 
> >> [INFO] BUILD FAILURE
> >> [INFO] 
> >> 
> >> [INFO] Total time: 3.720 s
> >> [INFO] Finished at: 2018-06-06T11:48:16+02:00
> >> [INFO] 
> >> 
> >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not
> >> resolve dependencies for project org.wicketstuff.wiquery:
> >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
> >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
> >> https://oss.sonatype.org/content/repositories/snapshots was cached in
> >> the local repository, resolution will not be reattempted until the update
> >> interval of sonatype-nexus-snapshots has elapsed or updates are forced ->
> >> [Help 1]
> >> [ERROR]
> > 
> > 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, Emond Papegaaij <
> > 
> > emond.papega...@topicus.nl> wrote:
> >> Hi Thomas,
> >> 
> >> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT.
> >> I did
> >> not do a release, as I cannot push to central. If you want to run your
> >> tests
> >> on some CI server, you probably have to push the artifacts to a local
> >> repo
> >> also.
> >> 
> >> Best regards,
> >> Emond
> >> 
> >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
> >> > Hi 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?
> >> > 
> >> > Best,
> >> > 
> >> > Thomas
> >> > 
> >> > On 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
> >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and
> >> > > refactoring.
> >> > > Please test the changes in your project. The tests pass and the demo
> >> 
> >> runs
> >> 
> >> > > fine, but my project only uses a limited set of the UI components.
> >> > > 
> >> > > Best regards,
> >> > > Emond
> >> > > 
> >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote:
> >> > > > I'm planning to upgrade jQuery UI to the latest version next week.
> >> 
> >> We
> >> 
> >> > > > are
> >> > > > currently migrating all our applications to wicket 8 and also
> >> 
> >> depend on
> >> 
> >> > > > wiquery quite a lot. It does however seem that jQuery UI is mostly
> >> 
> >> dead.
> >> 
> >> > > > The rest of the world probably switched to yet another fancy
> >> 
> >> JavaScript
> >> 
> >> > > ui
> >> > > 
> >> > > > library. At least the will make it easy to stay up to date with the
> >> > > 
> >> > > latest
> >> > > 
> >> > > >

Re: Release WiQuery for Wicket 8

[Thomas Heigl]

The culprit is:

https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868b940d9be3a

On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl  wrote:

> `mvn clean install` fails for me because no test-jar is built for the core
> module:
>
> [INFO] WiQuery Parent 8.0-SNAPSHOT  SUCCESS [
>>  0.353 s]
>> [INFO] WiQuery Core Project ... SUCCESS [
>>  2.673 s]
>> [INFO] WiQuery jQuery UI Project .. FAILURE [
>>  0.023 s]
>> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 3.720 s
>> [INFO] Finished at: 2018-06-06T11:48:16+02:00
>> [INFO] 
>> 
>> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not
>> resolve dependencies for project org.wicketstuff.wiquery:
>> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find
>> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in
>> https://oss.sonatype.org/content/repositories/snapshots was cached in
>> the local repository, resolution will not be reattempted until the update
>> interval of sonatype-nexus-snapshots has elapsed or updates are forced ->
>> [Help 1]
>> [ERROR]
>
>
> 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, Emond Papegaaij <
> emond.papega...@topicus.nl> wrote:
>
>> Hi Thomas,
>>
>> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT.
>> I did
>> not do a release, as I cannot push to central. If you want to run your
>> tests
>> on some CI server, you probably have to push the artifacts to a local
>> repo
>> also.
>>
>> Best regards,
>> Emond
>>
>> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote:
>> > Hi 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?
>> >
>> > Best,
>> >
>> > Thomas
>> >
>> > On 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
>> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and
>> > > refactoring.
>> > > Please test the changes in your project. The tests pass and the demo
>> runs
>> > > fine, but my project only uses a limited set of the UI components.
>> > >
>> > > Best regards,
>> > > Emond
>> > >
>> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote:
>> > > > I'm planning to upgrade jQuery UI to the latest version next week.
>> We
>> > > > are
>> > > > currently migrating all our applications to wicket 8 and also
>> depend on
>> > > > wiquery quite a lot. It does however seem that jQuery UI is mostly
>> dead.
>> > > > The rest of the world probably switched to yet another fancy
>> JavaScript
>> > >
>> > > ui
>> > >
>> > > > library. At least the will make it easy to stay up to date with the
>> > >
>> > > latest
>> > >
>> > > > version :)
>> > > >
>> > > > I can't push a release to central, but perhaps Martin can do that
>> when
>> > >
>> > > I'm
>> > >
>> > > > done? For now you can use a snapshot build. It works, but the UI API
>> > >
>> > > might
>> > >
>> > > > change a bit before the 8.0 release.
>> > > >
>> > > > Best regards,
>> > > > Emond Papegaaij
>> > > >
>> > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl :
>> > > > > Hi Ernesto,
>> > > > >
>> > > > > I'm not sure how many people are still using it. But as I said, my
>> > >
>> > > project
>> > >
>> > > > > heavily depends on it.
>> > > > >
>> > > > > @p