Re: Sharing property files for resources across components

[Martin Grigorov]

Hi,

On Thu, Aug 29, 2024 at 4:02 PM mscoon  wrote:

> Hi all,
>
> We are considering the following implementation for
> a ComponentStringResourceLoader. The idea is not only to search for
> resources using the superclasses of the components, but also using
> interfaces implemented by the components.
> public class InterfaceAwareComponentStringResourceLoader extends
> ComponentStringResourceLoader {
> @Override
> public String loadStringResource(Class clazz, String key, Locale
> locale, String style, String variation) {
>
>String ret = super.loadStringResource(clazz, key, locale, style,
> variation);
>if (ret == null) {
>

while (ret == null) {
To look in the interfaces of the base classes too ?!


>   for (Class i : clazz.getInterfaces()) {
>  if (IResourceProvider.class.isAssignableFrom(i)) {
> ret = super.loadStringResource(i, key, locale, style,
> variation);
> if (ret != null) {
>break;
> }
>  }
>   }
>}
>return ret;
>
> }
> }
>
> What we want to do is have two different panels like this:
> public class PersonFormPanel extends BaseFormPanel implements
> PersonResources
> public class PersonOtherPanel extends BaseOtherPanel implements
> PersonResources
>
> and given
> public interface PersonResources implements IResourceProvider
> and a file PersonResources.utf8.properties
>
> we want that the two panels share the resources declared in
> PersonResources.utf8.properties.
>
> Do you see any problems with this idea/implementation?
>

It looks OK to me!
If it works as you want it then it is good enough!



>
> Thanks in advance!
> Marios
>

Re: Sort the header items

[Martin Grigorov]

Hi,

You may want to read
http://wicketinaction.com/2012/07/wicket-6-resource-management/
It is a 12 years old article but still valid!

Martin

On Fri, Aug 23, 2024 at 9:08 AM Stéphane V  wrote:

> The PanelPanel CSS is now on top and the parent..
> 
> De : Stéphane V 
> Envoyé : vendredi 23 août 2024 08:06
> À : users@wicket.apache.org 
> Objet : RE: Sort the header items
>
> Hello Bas, thank you for your reply.
>
> Sorry, but I don't understand.
>
> Below the resulting order after the first interaction on the ajax button
> adding the last PanelPanel CSS. My CSS and JS are always declared in the
> renderHead method of the component (pages and panels).
> I can understant the dependency order with an inheritage in Java, but
> about CSS and JS the reasons are different: the cascading from CSS is not
> rerspected because the parent is overiding the child and more specific
> declaration.
>
> 
> 
>  href="../wicket/resource/org.ma.dashboard.components.overview.panels.OverviewPanel/OverviewPanel-ver-1724044527323.css">
>  src="../wicket/resource/org.ma.dashboard.components.overview.panels.OverviewPanel/OverviewPanel-ver-1724354734488.js">
>  src="../wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-3.7.1-ver-1722411717821.js">
>  src="../wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1722411717821.js">
>
> 
> 
>  href="/dashboard/resources/theme/org.ma.dashboard.theme.preset/theme.css">
>  src="/dashboard/resources/theme/org.ma.dashboard.theme.preset/bootstrap.js">
>  href="../wicket/resource/org.ma.dashboard.AbstractDashboardPage/AbstractDashboardPage-ver-1723739558518.css">
>  href="../wicket/resource/org.ma.dashboard.pages.DashboardIndexPage/DashboardIndexPage-ver-1723824628472.css">
>
> 
>  href="../wicket/resource/org.ma.dashboard.components.overview.panels.PanelPanel/PanelPanel-ver-1724353849200.css">
>
> And now the result after the first refresh of the page:
>
> 
> 
>  href="../wicket/resource/org.ma.dashboard.components.overview.panels.PanelPanel/PanelPanel-ver-1724353849200.css">
>  href="../wicket/resource/org.ma.dashboard.components.overview.panels.OverviewPanel/OverviewPanel-ver-1724044527323.css">
>  src="../wicket/resource/org.ma.dashboard.components.overview.panels.OverviewPanel/OverviewPanel-ver-1724354734488.js">
>  src="../wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-3.7.1-ver-1722411717821.js">
>  src="../wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1722411717821.js">
>
> 
> 
>  href="/dashboard/resources/theme/org.ma.dashboard.theme.preset/theme.css">
>  src="/dashboard/resources/theme/org.ma.dashboard.theme.preset/bootstrap.js">
>  href="../wicket/resource/org.ma.dashboard.AbstractDashboardPage/AbstractDashboardPage-ver-1723739558518.css">
>  href="../wicket/resource/org.ma.dashboard.pages.DashboardIndexPage/DashboardIndexPage-ver-1723824628472.css">
>
> The PanelPanel CSS is not on top and the parent (OverviewPanel CSS) can
> override the CSS. For me, it's trange. And the theme (using Bootstrap) is
> overriding a style inside the PanelPanel.css and I have to add !important
> to be sure I can keep the style declared in PanelPanel.css.
>
> //Stef
> 
> De : Bas Gooren 
> Envoyé : mardi 20 août 2024 21:41
> À : users@wicket.apache.org 
> Objet : Re: Sort the header items
>
> Hi Stephane,
>
> The easiest way is to ensure you define the dependencies on the child
> items. Then wicket will always render the parent (dependencies) before the
> children.
>
> Sounds to me like the reason for wanting things rendered in a certain
> order is precisely that: dependencies.
>
> For Ajax rendered items it shouldn’t matter: any new JavaScript and css
> will always be added and evaluated at the end.
>
> // Bas
>
> Verstuurd vanaf mijn iPhone
>
> > Op 20 aug 2024 om 19:49 heeft Stéphane V  het
> volgende geschreven:
> >
> > Hello,
> >
> > I'm looking for a way to sort header items like CSS or JavaScript files.
> I'm using renderHead() to add items to the head section, and I'm also
> utilizing inheritance for my pages. The order is perfect for the pages: the
> parent items come first, followed by the children items.
> >
> > However, the problem arises with panels. Their header items are created
> before the page's items, whereas I would like them to appear after the page
> items. Additionally, if I add a panel using Ajax, its header items are
> added at the end.
> >
> > How can I control the order of these items? Specifically, I want the
> page items to appear first, followed by the panel items.
> >
> > Thank you.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: Sort the header items

[Stéphane V]

The PanelPanel CSS is now on top and the parent..

De : Stéphane V 
Envoyé : vendredi 23 août 2024 08:06
À : users@wicket.apache.org 
Objet : RE: Sort the header items

Hello Bas, thank you for your reply.

Sorry, but I don't understand.

Below the resulting order after the first interaction on the ajax button adding 
the last PanelPanel CSS. My CSS and JS are always declared in the renderHead 
method of the component (pages and panels).
I can understant the dependency order with an inheritage in Java, but about CSS 
and JS the reasons are different: the cascading from CSS is not rerspected 
because the parent is overiding the child and more specific declaration.


















And now the result after the first refresh of the page:
















The PanelPanel CSS is not on top and the parent (OverviewPanel CSS) can 
override the CSS. For me, it's trange. And the theme (using Bootstrap) is 
overriding a style inside the PanelPanel.css and I have to add !important to be 
sure I can keep the style declared in PanelPanel.css.

//Stef

De : Bas Gooren 
Envoyé : mardi 20 août 2024 21:41
À : users@wicket.apache.org 
Objet : Re: Sort the header items

Hi Stephane,

The easiest way is to ensure you define the dependencies on the child items. 
Then wicket will always render the parent (dependencies) before the children.

Sounds to me like the reason for wanting things rendered in a certain order is 
precisely that: dependencies.

For Ajax rendered items it shouldn’t matter: any new JavaScript and css will 
always be added and evaluated at the end.

// Bas

Verstuurd vanaf mijn iPhone

> Op 20 aug 2024 om 19:49 heeft Stéphane V  het volgende 
> geschreven:
>
> Hello,
>
> I'm looking for a way to sort header items like CSS or JavaScript files. I'm 
> using renderHead() to add items to the head section, and I'm also utilizing 
> inheritance for my pages. The order is perfect for the pages: the parent 
> items come first, followed by the children items.
>
> However, the problem arises with panels. Their header items are created 
> before the page's items, whereas I would like them to appear after the page 
> items. Additionally, if I add a panel using Ajax, its header items are added 
> at the end.
>
> How can I control the order of these items? Specifically, I want the page 
> items to appear first, followed by the panel items.
>
> Thank you.

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

RE: Sort the header items

[Stéphane V]

Hello Bas, thank you for your reply.

Sorry, but I don't understand.

Below the resulting order after the first interaction on the ajax button adding 
the last PanelPanel CSS. My CSS and JS are always declared in the renderHead 
method of the component (pages and panels).
I can understant the dependency order with an inheritage in Java, but about CSS 
and JS the reasons are different: the cascading from CSS is not rerspected 
because the parent is overiding the child and more specific declaration.


















And now the result after the first refresh of the page:
















The PanelPanel CSS is not on top and the parent (OverviewPanel CSS) can 
override the CSS. For me, it's trange. And the theme (using Bootstrap) is 
overriding a style inside the PanelPanel.css and I have to add !important to be 
sure I can keep the style declared in PanelPanel.css.

//Stef

De : Bas Gooren 
Envoyé : mardi 20 août 2024 21:41
À : users@wicket.apache.org 
Objet : Re: Sort the header items

Hi Stephane,

The easiest way is to ensure you define the dependencies on the child items. 
Then wicket will always render the parent (dependencies) before the children.

Sounds to me like the reason for wanting things rendered in a certain order is 
precisely that: dependencies.

For Ajax rendered items it shouldn’t matter: any new JavaScript and css will 
always be added and evaluated at the end.

// Bas

Verstuurd vanaf mijn iPhone

> Op 20 aug 2024 om 19:49 heeft Stéphane V  het volgende 
> geschreven:
>
> Hello,
>
> I'm looking for a way to sort header items like CSS or JavaScript files. I'm 
> using renderHead() to add items to the head section, and I'm also utilizing 
> inheritance for my pages. The order is perfect for the pages: the parent 
> items come first, followed by the children items.
>
> However, the problem arises with panels. Their header items are created 
> before the page's items, whereas I would like them to appear after the page 
> items. Additionally, if I add a panel using Ajax, its header items are added 
> at the end.
>
> How can I control the order of these items? Specifically, I want the page 
> items to appear first, followed by the panel items.
>
> Thank you.

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

Re: Sort the header items

[Maxim Solodovnik]

Maybe this 
https://nightlies.apache.org/wicket/guide/10.x/single.html#_header_contributors_positioning
can help in your case? :)

On Wed, 21 Aug 2024 at 02:41, Bas Gooren  wrote:
>
> Hi Stephane,
>
> The easiest way is to ensure you define the dependencies on the child items. 
> Then wicket will always render the parent (dependencies) before the children.
>
> Sounds to me like the reason for wanting things rendered in a certain order 
> is precisely that: dependencies.
>
> For Ajax rendered items it shouldn’t matter: any new JavaScript and css will 
> always be added and evaluated at the end.
>
> // Bas
>
> Verstuurd vanaf mijn iPhone
>
> > Op 20 aug 2024 om 19:49 heeft Stéphane V  het volgende 
> > geschreven:
> >
> > Hello,
> >
> > I'm looking for a way to sort header items like CSS or JavaScript files. 
> > I'm using renderHead() to add items to the head section, and I'm also 
> > utilizing inheritance for my pages. The order is perfect for the pages: the 
> > parent items come first, followed by the children items.
> >
> > However, the problem arises with panels. Their header items are created 
> > before the page's items, whereas I would like them to appear after the page 
> > items. Additionally, if I add a panel using Ajax, its header items are 
> > added at the end.
> >
> > How can I control the order of these items? Specifically, I want the page 
> > items to appear first, followed by the panel items.
> >
> > Thank you.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>


-- 
Best regards,
Maxim

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

Re: Sort the header items

[Bas Gooren]

Hi Stephane,

The easiest way is to ensure you define the dependencies on the child items. 
Then wicket will always render the parent (dependencies) before the children.

Sounds to me like the reason for wanting things rendered in a certain order is 
precisely that: dependencies.

For Ajax rendered items it shouldn’t matter: any new JavaScript and css will 
always be added and evaluated at the end.

// Bas

Verstuurd vanaf mijn iPhone

> Op 20 aug 2024 om 19:49 heeft Stéphane V  het volgende 
> geschreven:
> 
> Hello,
> 
> I'm looking for a way to sort header items like CSS or JavaScript files. I'm 
> using renderHead() to add items to the head section, and I'm also utilizing 
> inheritance for my pages. The order is perfect for the pages: the parent 
> items come first, followed by the children items.
> 
> However, the problem arises with panels. Their header items are created 
> before the page's items, whereas I would like them to appear after the page 
> items. Additionally, if I add a panel using Ajax, its header items are added 
> at the end.
> 
> How can I control the order of these items? Specifically, I want the page 
> items to appear first, followed by the panel items.
> 
> Thank you.

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

Re: ModalDialog - why no dialog?

[Maxim Solodovnik]

On Sat, 3 Aug 2024 at 21:34, Korbinian Bachl
 wrote:
>
> Hi,
>
> why is it that the new "ModalDialog" doesn't use the "" elemt? But a 
>  instead with the need of custom css?
>
> -> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dialog
>
> And why are the
> https://examples9x.wicket.apache.org/ajax/modal-dialog
> crashing (code 503) when I open a dozen stacked dialogs? or switch to nested 
> and back while opening?
>
> Anyone that can look into the server log files?
> 16:31 GMT+1

These examples are in docker, not sure if it possible to check logs :(
Maybe you can reproduce it locally? :))

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


-- 
Best regards,
Maxim

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

Re: Kendo UI - DataTable with checkboxes as CommandButtons and onClick

[Bergmann Manfred]

Yes, problem solved.
The ‚edit‘ mode using a simple IKendoEditor implementation that renders a 
checkbox works well.

This can be done using standard PropertyColumn, i.e.:

new PropertyColumn("active", "active", 50) {
  override def isEditable = true
  override def getField = "active" // this is important, it's used below as 
'options.field' and is the path to the checkbox value in the model
  override def getEditor = new IKendoEditor {
  override def toString: String = {
"function my-fun (container, options) { " // lf
  + "console.log(options);“
  + "jQuery('')" // lf
  + ".appendTo(container); " // lf
  + „}"
  }
}

Then this only requires ‚onUpdate‘ implementation of the DataTable itself.


Regards,
Manfred



> Am 05.08.2024 um 18:57 schrieb Ernesto Reinaldo Barreiro :
> 
> Thus, you solved your problem?
> 
> On Mon, Aug 5, 2024 at 10:26 AM Bergmann Manfred 
> wrote:
> 
>> Having written this, I’ve looked a bit further and discovered the
>> ‚IKendoEditor‘ interface.
>> As used like here:
>> 
>> https://github.com/sebfz1/wicket-jquery-ui/blob/wicket9.x/wicket-kendo-ui/src/main/java/com/googlecode/wicket/kendo/ui/datatable/editor/TextAreaEditor.java
>> 
>> Seems like this should be used to modify model when in an ‚edit‘ mode.
>> 
>> 
>> Manfred
>> 
>> 
>>> Am 05.08.2024 um 17:00 schrieb Bergmann Manfred >> :
>>> 
>>> Quickstart is difficult because it means a considerable additional
>> effort.
>>> But I’ve added a screenshot.
>>> The right-most column is a CommandColumn with CommandButtons. This works
>> well, onClick handler is called, all good.
>>> The columns with the checkboxes here are customized CommandColumns with
>> CommandButton.
>>> The CommandColumns override getTemplate with something like this:
>>> 
>>> override def getTemplate: String = {
>>>   s"""
>>>  |  > title="activeCheckbox" class="k-button w-icon-only" if($getField){#
>> ${checkboxAttributes.positiveClass} #} else
>> {#${checkboxAttributes.negativeClass}#}#/>
>>>  |""".stripMargin
>>> }
>>> 
>>> So this basically renders an checkbox form component. I honestly doubt
>> this is the right approach.
>>> With this the CommandButton's onClick handler doesn’t work, only the
>> DataTable's onClick handler fires, but the Checkbox doesn’t toggle.
>>> Probably this requires attaching a custom JavaScript to make that
>> happen. But that seems like a complex way to make this happen.
>>> 
>>> I’d think that the ’selectable’ approach using a CheckboxColumn is
>> probably the right thing here.
>>> But we can’t figure out how to achieve that a checkbox toggle immediate
>> fires a callback.
>>> 
>>> 
>>> Regards,
>>> Manfred
>>> 
>>> 
>>> 
>>> 
>>> 
 Am 02.08.2024 um 22:54 schrieb Ernesto Reinaldo Barreiro <
>> reier...@gmail.com>:
 
 Could you please share some more data? Maybe share a quickstart project
 illustrating what you want to do?
 
 On Fri, Aug 2, 2024 at 11:57 AM Bergmann Manfred <
>> m...@software-by-mabe.com>
 wrote:
 
> Hello.
> 
> We’re struggling to add (or actually we’re not sure of possible ways)
> checkboxes to a DataTable (Grid) column that will install onClick
>> handler
> similar as the CommandButtons do in CommandColumn, so that onClick is
> called on each checkbox toggle.
> We’re tried a few variations, i.e. using AbstractColumn with
>> CommandButton
> and use getTemplate to render checkbox form input, but this doesn’t
>> install
> an onClick handler, or at least onClick is not called.
> 
> Anyone with pointers of how this could work?
> 
> 
> Regards,
> Manfred
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 
 
 --
 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
>> 
>> 
> 
> -- 
> Regards - Ernesto Reinaldo Barreiro


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

Re: Image without page versioning

[Bas Gooren]

Hi all,

To prevent unnecessary requests for unchanged avatars, I recommend adding
the last-modified timestamp to the url; If you have it for the avatar, add
that, if not, add the last-modified of the user.

This way you can let the browser cache the avatar for a year. When it
doesn’t change, it will only get requested once.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 5 augustus 2024 bij 21:09:43, Ernesto Reinaldo Barreiro (
reier...@gmail.com) schreef:

Thanks for sharing. If your users can change the avatar maybe you want at
"client side" to add some request parameter with the timestamp when the
user updated the avatar. This way you might avoid browser caching the
avatar and displaying an outdated one.

On Mon, Aug 5, 2024 at 1:31 PM Stéphane V  wrote:

> Thank you Bas.
>
> Here my implementation: maybe it will help someone:
>
>
> public class AvatarResourceReference extends ResourceReference {
>
> private final IUserService userService;
>
> public AvatarResourceReference(IUserService userService) {
> super(AvatarResourceReference.class.getName());
> this.userService = userService;
> }
>
>
> @Override
> public IResource getResource() {
>
> return new AbstractResource() {
> @Override
> protected ResourceResponse newResourceResponse(Attributes
> attributes) {
>
> final ResourceResponse res = new ResourceResponse();
>
> // Check if the user has the role for the DASHBOARD
> // FIXME Add authorization with ROLES
> // if
> (!AuthenticatedWebSession.get().getRoles().contains("DASHBOARD")) {
> // res.setError(HttpServletResponse.SC_FORBIDDEN);
> // return res;
> // }
>
> // If the user PID est missing the request, return an HTTP
> error
> final StringValue userPidValue =
> attributes.getParameters().get("userPid");
> if (userPidValue.isEmpty()) {
> res.setError(HttpServletResponse.SC_NOT_FOUND);
> return res;
> }
>
> // Search the requested user. If not found, return an error
> final Optional userProfile =
> userService.findUserByPid(userPidValue.toString());
> if (userProfile.isEmpty()) {
> res.setError(HttpServletResponse.SC_NOT_FOUND);
> return res;
> }
>
> final UserProfile user = userProfile.get();
> if (user.getAvatar() != null) {
> res.setContentType(user.getAvatar().getContentType());
> } else {
> res.setContentType("image/png");
> }
> res.setWriteCallback(new WriteCallback() {
> @Override
> public void writeData(Attributes attributes) throws
> IOException {
>
> attributes.getResponse().write(getUserAvatar(user));
> }
> });
>
> return res;
> }
> };
> }
>
> private byte[] getUserAvatar(UserProfile userProfile) {
> if (userProfile.getAvatar() != null) {
> return userProfile.getAvatar().getData();
> } else {
> try {
> return
>
IOUtils.toByteArray(Objects.requireNonNull(UserListPanel.class.getResourceAsStream("avatar-unknown.png")));

> } catch (IOException e) {
> throw new RuntimeException(e);
> }
> }
> }
> }
>
> I'm using MarcGiffing framework. Here the initiailization of the resource
> reference:
>
>
> public void init(WebApplication webApplication) {
>
>
webApplication.mountResource(String.format("/dashboard/resources/%s/${userPid}",

> AvatarResourceReference.class.getName()), new
> AvatarResourceReference(userService));
> }
>
> Stef
> 
> De : Bas Gooren 
> Envoyé : dimanche 4 août 2024 13:29
> À : users@wicket.apache.org 
> Objet : Re: Image without page versioning
>
> Hi!
>
> Since you are using an image component with a component-local resource,
> this will always require the page to be versioned.
> The url that is generated for the image will be page-specific, to be able
> to let the image component call the byte array resource.
>
> If you wish to keep the page stateless, you’ll need to use a mounted
> resource for this.
>
> You can create a mounted resource that gets the active user from the
> session (or return a 404 when the user is not logged in); Or you can
build
> a stateless version which has some unique user identifier in the url.
>
> // Bas
>
> Verstuurd vanaf mijn iPhone
>
> > Op 4 aug 2024 om 12:52 heeft Stéphane V  het volgende
> geschreven:
> >
> > Hi,
> >
> > I'm using a NonCachingImage for the avatar image of my users. I was
> expecting the page will not be versioned, but it's versioned.
> >
> > I'm using this code:
> >
> > new NonCachingImage("avatar", new ByteArrayResource("image/png",
> getUserAvatar(userProfile)))
> >
> > How can I avoid to version the page ?
> >
> > Thank you.
> >
> > Stef
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Regards - Ernesto Reinaldo Barreiro

Re: Image without page versioning

[Ernesto Reinaldo Barreiro]

Thanks for sharing. If your users can change the avatar maybe you want at
"client side" to add some request parameter with the timestamp when the
user updated the avatar. This way  you might avoid browser caching the
avatar and displaying an outdated one.

On Mon, Aug 5, 2024 at 1:31 PM Stéphane V  wrote:

> Thank you Bas.
>
> Here my implementation: maybe it will help someone:
>
>
> public class AvatarResourceReference extends ResourceReference {
>
> private final IUserService userService;
>
> public AvatarResourceReference(IUserService userService) {
> super(AvatarResourceReference.class.getName());
> this.userService = userService;
> }
>
>
> @Override
> public IResource getResource() {
>
> return new AbstractResource() {
> @Override
> protected ResourceResponse newResourceResponse(Attributes
> attributes) {
>
> final ResourceResponse res = new ResourceResponse();
>
> // Check if the user has the role for the DASHBOARD
> // FIXME Add authorization with ROLES
> //if
> (!AuthenticatedWebSession.get().getRoles().contains("DASHBOARD")) {
> //res.setError(HttpServletResponse.SC_FORBIDDEN);
> //return res;
> //}
>
> // If the user PID est missing the request, return an HTTP
> error
> final StringValue userPidValue =
> attributes.getParameters().get("userPid");
> if (userPidValue.isEmpty()) {
> res.setError(HttpServletResponse.SC_NOT_FOUND);
> return res;
> }
>
> // Search the requested user. If not found, return an error
> final Optional userProfile =
> userService.findUserByPid(userPidValue.toString());
> if (userProfile.isEmpty()) {
> res.setError(HttpServletResponse.SC_NOT_FOUND);
> return res;
> }
>
> final UserProfile user = userProfile.get();
> if (user.getAvatar() != null) {
> res.setContentType(user.getAvatar().getContentType());
> } else {
> res.setContentType("image/png");
> }
> res.setWriteCallback(new WriteCallback() {
> @Override
> public void writeData(Attributes attributes) throws
> IOException {
>
> attributes.getResponse().write(getUserAvatar(user));
> }
> });
>
> return res;
> }
> };
> }
>
> private byte[] getUserAvatar(UserProfile userProfile) {
> if (userProfile.getAvatar() != null) {
> return userProfile.getAvatar().getData();
> } else {
> try {
> return
> IOUtils.toByteArray(Objects.requireNonNull(UserListPanel.class.getResourceAsStream("avatar-unknown.png")));
> } catch (IOException e) {
> throw new RuntimeException(e);
> }
> }
> }
> }
>
> I'm using MarcGiffing framework. Here the initiailization of the resource
> reference:
>
>
> public void init(WebApplication webApplication) {
>
> webApplication.mountResource(String.format("/dashboard/resources/%s/${userPid}",
> AvatarResourceReference.class.getName()), new
> AvatarResourceReference(userService));
> }
>
> Stef
> 
> De : Bas Gooren 
> Envoyé : dimanche 4 août 2024 13:29
> À : users@wicket.apache.org 
> Objet : Re: Image without page versioning
>
> Hi!
>
> Since you are using an image component with a component-local resource,
> this will always require the page to be versioned.
> The url that is generated for the image will be page-specific, to be able
> to let the image component call the byte array resource.
>
> If you wish to keep the page stateless, you’ll need to use a mounted
> resource for this.
>
> You can create a mounted resource that gets the active user from the
> session (or return a 404 when the user is not logged in); Or you can build
> a stateless version which has some unique user identifier in the url.
>
> // Bas
>
> Verstuurd vanaf mijn iPhone
>
> > Op 4 aug 2024 om 12:52 heeft Stéphane V  het volgende
> geschreven:
> >
> > Hi,
> >
> > I'm using a NonCachingImage for the avatar image of my users. I was
> expecting the page will not be versioned, but it's versioned.
> >
> > I'm using this code:
> >
> > new NonCachingImage("avatar", new ByteArrayResource("image/png",
> getUserAvatar(userProfile)))
> >
> > How can I avoid to version the page ?
> >
> > Thank you.
> >
> > Stef
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Regards - Ernesto Reinaldo Barreiro

RE: Image without page versioning

[Stéphane V]

Thank you Bas.

Here my implementation: maybe it will help someone:


public class AvatarResourceReference extends ResourceReference {

private final IUserService userService;

public AvatarResourceReference(IUserService userService) {
super(AvatarResourceReference.class.getName());
this.userService = userService;
}


@Override
public IResource getResource() {

return new AbstractResource() {
@Override
protected ResourceResponse newResourceResponse(Attributes 
attributes) {

final ResourceResponse res = new ResourceResponse();

// Check if the user has the role for the DASHBOARD
// FIXME Add authorization with ROLES
//if 
(!AuthenticatedWebSession.get().getRoles().contains("DASHBOARD")) {
//res.setError(HttpServletResponse.SC_FORBIDDEN);
//return res;
//}

// If the user PID est missing the request, return an HTTP error
final StringValue userPidValue = 
attributes.getParameters().get("userPid");
if (userPidValue.isEmpty()) {
res.setError(HttpServletResponse.SC_NOT_FOUND);
return res;
}

// Search the requested user. If not found, return an error
final Optional userProfile = 
userService.findUserByPid(userPidValue.toString());
if (userProfile.isEmpty()) {
res.setError(HttpServletResponse.SC_NOT_FOUND);
return res;
}

final UserProfile user = userProfile.get();
if (user.getAvatar() != null) {
res.setContentType(user.getAvatar().getContentType());
} else {
res.setContentType("image/png");
}
res.setWriteCallback(new WriteCallback() {
@Override
public void writeData(Attributes attributes) throws 
IOException {
attributes.getResponse().write(getUserAvatar(user));
}
});

return res;
}
};
}

private byte[] getUserAvatar(UserProfile userProfile) {
if (userProfile.getAvatar() != null) {
return userProfile.getAvatar().getData();
} else {
try {
return 
IOUtils.toByteArray(Objects.requireNonNull(UserListPanel.class.getResourceAsStream("avatar-unknown.png")));
} catch (IOException e) {
throw new RuntimeException(e);
}
}
}
}

I'm using MarcGiffing framework. Here the initiailization of the resource 
reference:


public void init(WebApplication webApplication) {

webApplication.mountResource(String.format("/dashboard/resources/%s/${userPid}",
 AvatarResourceReference.class.getName()), new 
AvatarResourceReference(userService));
}

Stef

De : Bas Gooren 
Envoyé : dimanche 4 août 2024 13:29
À : users@wicket.apache.org 
Objet : Re: Image without page versioning

Hi!

Since you are using an image component with a component-local resource, this 
will always require the page to be versioned.
The url that is generated for the image will be page-specific, to be able to 
let the image component call the byte array resource.

If you wish to keep the page stateless, you’ll need to use a mounted resource 
for this.

You can create a mounted resource that gets the active user from the session 
(or return a 404 when the user is not logged in); Or you can build a stateless 
version which has some unique user identifier in the url.

// Bas

Verstuurd vanaf mijn iPhone

> Op 4 aug 2024 om 12:52 heeft Stéphane V  het volgende 
> geschreven:
>
> Hi,
>
> I'm using a NonCachingImage for the avatar image of my users. I was expecting 
> the page will not be versioned, but it's versioned.
>
> I'm using this code:
>
> new NonCachingImage("avatar", new ByteArrayResource("image/png", 
> getUserAvatar(userProfile)))
>
> How can I avoid to version the page ?
>
> Thank you.
>
> Stef

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

Re: Kendo UI - DataTable with checkboxes as CommandButtons and onClick

[Ernesto Reinaldo Barreiro]

Thus, you solved your problem?

On Mon, Aug 5, 2024 at 10:26 AM Bergmann Manfred 
wrote:

> Having written this, I’ve looked a bit further and discovered the
> ‚IKendoEditor‘ interface.
> As used like here:
>
> https://github.com/sebfz1/wicket-jquery-ui/blob/wicket9.x/wicket-kendo-ui/src/main/java/com/googlecode/wicket/kendo/ui/datatable/editor/TextAreaEditor.java
>
> Seems like this should be used to modify model when in an ‚edit‘ mode.
>
>
> Manfred
>
>
> > Am 05.08.2024 um 17:00 schrieb Bergmann Manfred  >:
> >
> > Quickstart is difficult because it means a considerable additional
> effort.
> > But I’ve added a screenshot.
> > The right-most column is a CommandColumn with CommandButtons. This works
> well, onClick handler is called, all good.
> > The columns with the checkboxes here are customized CommandColumns with
> CommandButton.
> > The CommandColumns override getTemplate with something like this:
> >
> > override def getTemplate: String = {
> >s"""
> >   |   title="activeCheckbox" class="k-button w-icon-only" if($getField){#
> ${checkboxAttributes.positiveClass} #} else
> {#${checkboxAttributes.negativeClass}#}#/>
> >   |""".stripMargin
> >  }
> >
> > So this basically renders an checkbox form component. I honestly doubt
> this is the right approach.
> > With this the CommandButton's onClick handler doesn’t work, only the
> DataTable's onClick handler fires, but the Checkbox doesn’t toggle.
> > Probably this requires attaching a custom JavaScript to make that
> happen. But that seems like a complex way to make this happen.
> >
> > I’d think that the ’selectable’ approach using a CheckboxColumn is
> probably the right thing here.
> > But we can’t figure out how to achieve that a checkbox toggle immediate
> fires a callback.
> >
> >
> > Regards,
> > Manfred
> >
> >
> >
> >
> >
> >> Am 02.08.2024 um 22:54 schrieb Ernesto Reinaldo Barreiro <
> reier...@gmail.com>:
> >>
> >> Could you please share some more data? Maybe share a quickstart project
> >> illustrating what you want to do?
> >>
> >> On Fri, Aug 2, 2024 at 11:57 AM Bergmann Manfred <
> m...@software-by-mabe.com>
> >> wrote:
> >>
> >>> Hello.
> >>>
> >>> We’re struggling to add (or actually we’re not sure of possible ways)
> >>> checkboxes to a DataTable (Grid) column that will install onClick
> handler
> >>> similar as the CommandButtons do in CommandColumn, so that onClick is
> >>> called on each checkbox toggle.
> >>> We’re tried a few variations, i.e. using AbstractColumn with
> CommandButton
> >>> and use getTemplate to render checkbox form input, but this doesn’t
> install
> >>> an onClick handler, or at least onClick is not called.
> >>>
> >>> Anyone with pointers of how this could work?
> >>>
> >>>
> >>> Regards,
> >>> Manfred
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> For additional commands, e-mail: users-h...@wicket.apache.org
> >>>
> >>>
> >>
> >> --
> >> 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
>
>

-- 
Regards - Ernesto Reinaldo Barreiro

Re: Kendo UI - DataTable with checkboxes as CommandButtons and onClick

[Bergmann Manfred]

Having written this, I’ve looked a bit further and discovered the 
‚IKendoEditor‘ interface.
As used like here:
https://github.com/sebfz1/wicket-jquery-ui/blob/wicket9.x/wicket-kendo-ui/src/main/java/com/googlecode/wicket/kendo/ui/datatable/editor/TextAreaEditor.java

Seems like this should be used to modify model when in an ‚edit‘ mode.


Manfred


> Am 05.08.2024 um 17:00 schrieb Bergmann Manfred :
> 
> Quickstart is difficult because it means a considerable additional effort.
> But I’ve added a screenshot.
> The right-most column is a CommandColumn with CommandButtons. This works 
> well, onClick handler is called, all good.
> The columns with the checkboxes here are customized CommandColumns with 
> CommandButton.
> The CommandColumns override getTemplate with something like this:
> 
> override def getTemplate: String = {
>s"""
>   |   title="activeCheckbox" class="k-button w-icon-only" if($getField){# 
> ${checkboxAttributes.positiveClass} #} else 
> {#${checkboxAttributes.negativeClass}#}#/>
>   |""".stripMargin
>  }
> 
> So this basically renders an checkbox form component. I honestly doubt this 
> is the right approach.
> With this the CommandButton's onClick handler doesn’t work, only the 
> DataTable's onClick handler fires, but the Checkbox doesn’t toggle.
> Probably this requires attaching a custom JavaScript to make that happen. But 
> that seems like a complex way to make this happen.
> 
> I’d think that the ’selectable’ approach using a CheckboxColumn is probably 
> the right thing here.
> But we can’t figure out how to achieve that a checkbox toggle immediate fires 
> a callback.
> 
> 
> Regards,
> Manfred
> 
> 
> 
> 
> 
>> Am 02.08.2024 um 22:54 schrieb Ernesto Reinaldo Barreiro 
>> :
>> 
>> Could you please share some more data? Maybe share a quickstart project
>> illustrating what you want to do?
>> 
>> On Fri, Aug 2, 2024 at 11:57 AM Bergmann Manfred 
>> wrote:
>> 
>>> Hello.
>>> 
>>> We’re struggling to add (or actually we’re not sure of possible ways)
>>> checkboxes to a DataTable (Grid) column that will install onClick handler
>>> similar as the CommandButtons do in CommandColumn, so that onClick is
>>> called on each checkbox toggle.
>>> We’re tried a few variations, i.e. using AbstractColumn with CommandButton
>>> and use getTemplate to render checkbox form input, but this doesn’t install
>>> an onClick handler, or at least onClick is not called.
>>> 
>>> Anyone with pointers of how this could work?
>>> 
>>> 
>>> Regards,
>>> Manfred
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>> 
>>> 
>> 
>> -- 
>> 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

Re: Kendo UI - DataTable with checkboxes as CommandButtons and onClick

[Bergmann Manfred]

Quickstart is difficult because it means a considerable additional effort.
But I’ve added a screenshot.
The right-most column is a CommandColumn with CommandButtons. This works well, 
onClick handler is called, all good.
The columns with the checkboxes here are customized CommandColumns with 
CommandButton.
The CommandColumns override getTemplate with something like this:

override def getTemplate: String = {
s"""
   |  
   |""".stripMargin
  }

So this basically renders an checkbox form component. I honestly doubt this is 
the right approach.
With this the CommandButton's onClick handler doesn’t work, only the 
DataTable's onClick handler fires, but the Checkbox doesn’t toggle.
Probably this requires attaching a custom JavaScript to make that happen. But 
that seems like a complex way to make this happen.

I’d think that the ’selectable’ approach using a CheckboxColumn is probably the 
right thing here.
But we can’t figure out how to achieve that a checkbox toggle immediate fires a 
callback.


Regards,
Manfred





> Am 02.08.2024 um 22:54 schrieb Ernesto Reinaldo Barreiro :
> 
> Could you please share some more data? Maybe share a quickstart project
> illustrating what you want to do?
> 
> On Fri, Aug 2, 2024 at 11:57 AM Bergmann Manfred 
> wrote:
> 
>> Hello.
>> 
>> We’re struggling to add (or actually we’re not sure of possible ways)
>> checkboxes to a DataTable (Grid) column that will install onClick handler
>> similar as the CommandButtons do in CommandColumn, so that onClick is
>> called on each checkbox toggle.
>> We’re tried a few variations, i.e. using AbstractColumn with CommandButton
>> and use getTemplate to render checkbox form input, but this doesn’t install
>> an onClick handler, or at least onClick is not called.
>> 
>> Anyone with pointers of how this could work?
>> 
>> 
>> Regards,
>> Manfred
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>> 
>> 
> 
> -- 
> Regards - Ernesto Reinaldo Barreiro



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

Re: Image without page versioning

[Bas Gooren]

Hi!

Since you are using an image component with a component-local resource, this 
will always require the page to be versioned.
The url that is generated for the image will be page-specific, to be able to 
let the image component call the byte array resource.

If you wish to keep the page stateless, you’ll need to use a mounted resource 
for this.

You can create a mounted resource that gets the active user from the session 
(or return a 404 when the user is not logged in); Or you can build a stateless 
version which has some unique user identifier in the url.

// Bas

Verstuurd vanaf mijn iPhone

> Op 4 aug 2024 om 12:52 heeft Stéphane V  het volgende 
> geschreven:
> 
> Hi,
> 
> I'm using a NonCachingImage for the avatar image of my users. I was expecting 
> the page will not be versioned, but it's versioned.
> 
> I'm using this code:
> 
> new NonCachingImage("avatar", new ByteArrayResource("image/png", 
> getUserAvatar(userProfile)))
> 
> How can I avoid to version the page ?
> 
> Thank you.
> 
> Stef

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

Re: Bookmarkable ModalWindow

[Korbinian Bachl]

Ah the good'ol times where you need an extra workaround for anything :D

I never said the old ModalWindow was great, but its in so many places and for 
Jakarta one needs wicket 10 :S



- Ursprüngliche Mail -
> Von: "Ernesto Reinaldo Barreiro" 
> An: "users" 
> Gesendet: Samstag, 3. August 2024 15:53:43
> Betreff: Re: Bookmarkable ModalWindow

> From a previous life
> 
> https://cwiki.apache.org/confluence/display/WICKET/Modal+Windows
> 
> On Fri, Aug 2, 2024 at 7:18 PM Martin Terra <
> martin.te...@koodaripalvelut.com> wrote:
> 
>> Thanks. The question was formulated from the perspective of the old
>> Modal Window.
>>
>> However, maybe they are equivalent, and if not, what are the caveats?
>>
>> If any, what are the relevant differences between new and old in this
>> respect?
>>
>> **
>> Martin
>>
>> pe 2. elok. 2024 klo 19.06 Ernesto Reinaldo Barreiro (reier...@gmail.com)
>> kirjoitti:
>>
>> > Hi,
>> >
>> > Does this refer to the Old modal window or the new Modal window?
>> >
>> > On Fri, Aug 2, 2024 at 5:58 AM Martin Terra <
>> > martin.te...@koodaripalvelut.com> wrote:
>> >
>> > > Hi!
>> > >
>> > > Has anyone made a bookmarkable use case of ModalWindow, are there any
>> > > caveats?
>> > >
>> > > Basically the goal would be that refreshing the page retains its state
>> as
>> > > if it was a regular panel.
>> > >
>> > >
>> > > **
>> > > Martin
>> > >
>> >
>> >
>> > --
>> > Regards - Ernesto Reinaldo Barreiro
>> >
>>
> 
> 
> --
> Regards - Ernesto Reinaldo Barreiro

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

Re: Bookmarkable ModalWindow

[Martin]

Thanks. Pre-wicket-10 ModalWindows.

I am familiar with "Opening a modal window on page load", but I am looking
for a non ajax and non javascript solution so that the window is actually
open on render instead of "opened on render".

It might ofcourse be simpler to roll out a custom one.

**
Martin

la 3. elok. 2024 klo 16.54 Ernesto Reinaldo Barreiro (reier...@gmail.com)
kirjoitti:

> From a previous life
>
> https://cwiki.apache.org/confluence/display/WICKET/Modal+Windows
>
> On Fri, Aug 2, 2024 at 7:18 PM Martin Terra <
> martin.te...@koodaripalvelut.com> wrote:
>
> > Thanks. The question was formulated from the perspective of the old
> > Modal Window.
> >
> > However, maybe they are equivalent, and if not, what are the caveats?
> >
> > If any, what are the relevant differences between new and old in this
> > respect?
> >
> > **
> > Martin
> >
> > pe 2. elok. 2024 klo 19.06 Ernesto Reinaldo Barreiro (reier...@gmail.com
> )
> > kirjoitti:
> >
> > > Hi,
> > >
> > > Does this refer to the Old modal window or the new Modal window?
> > >
> > > On Fri, Aug 2, 2024 at 5:58 AM Martin Terra <
> > > martin.te...@koodaripalvelut.com> wrote:
> > >
> > > > Hi!
> > > >
> > > > Has anyone made a bookmarkable use case of ModalWindow, are there any
> > > > caveats?
> > > >
> > > > Basically the goal would be that refreshing the page retains its
> state
> > as
> > > > if it was a regular panel.
> > > >
> > > >
> > > > **
> > > > Martin
> > > >
> > >
> > >
> > > --
> > > Regards - Ernesto Reinaldo Barreiro
> > >
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: Bookmarkable ModalWindow

[Ernesto Reinaldo Barreiro]

>From a previous life

https://cwiki.apache.org/confluence/display/WICKET/Modal+Windows

On Fri, Aug 2, 2024 at 7:18 PM Martin Terra <
martin.te...@koodaripalvelut.com> wrote:

> Thanks. The question was formulated from the perspective of the old
> Modal Window.
>
> However, maybe they are equivalent, and if not, what are the caveats?
>
> If any, what are the relevant differences between new and old in this
> respect?
>
> **
> Martin
>
> pe 2. elok. 2024 klo 19.06 Ernesto Reinaldo Barreiro (reier...@gmail.com)
> kirjoitti:
>
> > Hi,
> >
> > Does this refer to the Old modal window or the new Modal window?
> >
> > On Fri, Aug 2, 2024 at 5:58 AM Martin Terra <
> > martin.te...@koodaripalvelut.com> wrote:
> >
> > > Hi!
> > >
> > > Has anyone made a bookmarkable use case of ModalWindow, are there any
> > > caveats?
> > >
> > > Basically the goal would be that refreshing the page retains its state
> as
> > > if it was a regular panel.
> > >
> > >
> > > **
> > > Martin
> > >
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: Bookmarkable ModalWindow

[Korbinian Bachl]

https://github.com/wicketstuff/core/issues/984

:)


- Ursprüngliche Mail -
> Von: "Ernesto Reinaldo Barreiro" 
> An: "users" 
> Gesendet: Freitag, 2. August 2024 18:06:04
> Betreff: Re: Bookmarkable ModalWindow

> Hi,
> 
> Does this refer to the Old modal window or the new Modal window?
> 
> On Fri, Aug 2, 2024 at 5:58 AM Martin Terra <
> martin.te...@koodaripalvelut.com> wrote:
> 
>> Hi!
>>
>> Has anyone made a bookmarkable use case of ModalWindow, are there any
>> caveats?
>>
>> Basically the goal would be that refreshing the page retains its state as
>> if it was a regular panel.
>>
>>
>> **
>> Martin
>>
> 
> 
> --
> Regards - Ernesto Reinaldo Barreiro

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

Re: Bookmarkable ModalWindow

[Martin Terra]

Thanks. The question was formulated from the perspective of the old
Modal Window.

However, maybe they are equivalent, and if not, what are the caveats?

If any, what are the relevant differences between new and old in this
respect?

**
Martin

pe 2. elok. 2024 klo 19.06 Ernesto Reinaldo Barreiro (reier...@gmail.com)
kirjoitti:

> Hi,
>
> Does this refer to the Old modal window or the new Modal window?
>
> On Fri, Aug 2, 2024 at 5:58 AM Martin Terra <
> martin.te...@koodaripalvelut.com> wrote:
>
> > Hi!
> >
> > Has anyone made a bookmarkable use case of ModalWindow, are there any
> > caveats?
> >
> > Basically the goal would be that refreshing the page retains its state as
> > if it was a regular panel.
> >
> >
> > **
> > Martin
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: Kendo UI - DataTable with checkboxes as CommandButtons and onClick

[Ernesto Reinaldo Barreiro]

Could you please share some more data? Maybe share a quickstart project
illustrating what you want to do?

On Fri, Aug 2, 2024 at 11:57 AM Bergmann Manfred 
wrote:

> Hello.
>
> We’re struggling to add (or actually we’re not sure of possible ways)
> checkboxes to a DataTable (Grid) column that will install onClick handler
> similar as the CommandButtons do in CommandColumn, so that onClick is
> called on each checkbox toggle.
> We’re tried a few variations, i.e. using AbstractColumn with CommandButton
> and use getTemplate to render checkbox form input, but this doesn’t install
> an onClick handler, or at least onClick is not called.
>
> Anyone with pointers of how this could work?
>
>
> Regards,
> Manfred
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Regards - Ernesto Reinaldo Barreiro

Re: Bookmarkable ModalWindow

[Ernesto Reinaldo Barreiro]

Hi,

Does this refer to the Old modal window or the new Modal window?

On Fri, Aug 2, 2024 at 5:58 AM Martin Terra <
martin.te...@koodaripalvelut.com> wrote:

> Hi!
>
> Has anyone made a bookmarkable use case of ModalWindow, are there any
> caveats?
>
> Basically the goal would be that refreshing the page retains its state as
> if it was a regular panel.
>
>
> **
> Martin
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: Full time remote Apache Wicket developer opportunity

[Ernesto Reinaldo Barreiro]

Thanks for sharing.

On Tue, Jul 30, 2024 at 8:05 AM Wayne W  wrote:

> Hello all,
>
> We are looking for the above, if anyone is interested or knows of anyone
> who might be interested.
>
> This is a long term position.
>
> Details of the job can be found here:  https://wellfound.com/l/2ArmgA
>
> Salary depends on experience and to be discussed one on one.
>
> Kind regards
> Wayne
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: ListItemModel is not detaching List-model

[Martin Terra]

to 11. heinäk. 2024 klo 16.54 Tobias Gierke
(tobias.gie...@voipfuture.com.invalid) kirjoitti:

>
> On 11.07.24 15:31, Emond Papegaaij wrote:
> > Op do 11 jul 2024 om 15:09 schreef Sven Meier :
> >
> >> the ListItemModel does not hold a reference to the model of the
> >> ListView, so it's not its responsibility to detach it.
> >>
> > IMHO, the implementation of ListItemModel is strange. It does not hold a
> > direct reference to the model of the ListView, but it holds a reference
> to
> > the ListView instead. It also has a dependency on the model object (and
> > hence the model of) the ListView. I don't think models should hold
> > references to components, it should be the other way around. I think
> > ListItemModel should be reworked to take a reference to the model of the
> > ListView.
> >
> > Rule of thumb: if you hold a reference to a model, you have to detach it.
> >
> >
> > I would say: if reading the object of model X requires reading the
> objects
> > of other models, the detach of model X should also detach those other
> > models.
> FWIW, I second this - I also recently came across this somewhat
> surprising behavior.
>

IMO ListItemModel is more of a Lense than a model ;) Rename perhaps?

**
Martin



>
> Regards,
> Tobias
> >
> > Best regards,
> > Emond
> >
> --
> Tobias Gierke
> Software Developer
>
> Voipfuture GmbH   Wendenstr. 4   20097 Hamburg   Germany
> Phone +49 40 688 9001 64   Fax +49 40 688 9001 99
> Managing Directors   Jan Bastian   Eyal Ullert
> Commercial Court AG Hamburg   HRB 109896   VAT ID DE263738086
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ListItemModel is not detaching List-model

[Tobias Gierke]

On 11.07.24 15:31, Emond Papegaaij wrote:

Op do 11 jul 2024 om 15:09 schreef Sven Meier :


the ListItemModel does not hold a reference to the model of the
ListView, so it's not its responsibility to detach it.


IMHO, the implementation of ListItemModel is strange. It does not hold a
direct reference to the model of the ListView, but it holds a reference to
the ListView instead. It also has a dependency on the model object (and
hence the model of) the ListView. I don't think models should hold
references to components, it should be the other way around. I think
ListItemModel should be reworked to take a reference to the model of the
ListView.

Rule of thumb: if you hold a reference to a model, you have to detach it.


I would say: if reading the object of model X requires reading the objects
of other models, the detach of model X should also detach those other
models.
FWIW, I second this - I also recently came across this somewhat 
surprising behavior.


Regards,
Tobias


Best regards,
Emond


--
Tobias Gierke
Software Developer

Voipfuture GmbH   Wendenstr. 4   20097 Hamburg   Germany
Phone +49 40 688 9001 64   Fax +49 40 688 9001 99
Managing Directors   Jan Bastian   Eyal Ullert
Commercial Court AG Hamburg   HRB 109896   VAT ID DE263738086



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

Re: ListItemModel is not detaching List-model

[Emond Papegaaij]

Op do 11 jul 2024 om 15:09 schreef Sven Meier :

> the ListItemModel does not hold a reference to the model of the
> ListView, so it's not its responsibility to detach it.
>

IMHO, the implementation of ListItemModel is strange. It does not hold a
direct reference to the model of the ListView, but it holds a reference to
the ListView instead. It also has a dependency on the model object (and
hence the model of) the ListView. I don't think models should hold
references to components, it should be the other way around. I think
ListItemModel should be reworked to take a reference to the model of the
ListView.

Rule of thumb: if you hold a reference to a model, you have to detach it.


I would say: if reading the object of model X requires reading the objects
of other models, the detach of model X should also detach those other
models.

Best regards,
Emond

Re: ListItemModel is not detaching List-model

[Sven Meier]

Hi,

the ListItemModel does not hold a reference to the model of the 
ListView, so it's not its responsibility to detach it.


Rule of thumb: if you hold a reference to a model, you have to detach it.

Hope this helps
Sven

On 11.07.24 14:51, Hannes Becker wrote:

Hi Johannes,

(and greetings, dear former colleague 😉)

As I said - it is not about Components detaching Models. At the end of the render 
cycle, the ListView detaches its Model, this is default & fine.

My point is, that the detaching of Models is not consistently implemented, if you 
take a look at ListItemModel vs. the implementations produced by (e.g.) 
IModel.map(...) or LambdaModel.of(IModel target,...).
The ListItemModel does not care about its dependencies, the latter do - which 
is correct in my humble opinion.

My very specific use case would be too long to post here, but I have a ListView 
A which renders a Component B, which is implemented in a separate class. 
Component B does not know anything about its parent (ListView) Component or the 
ListItemModel, which is passed as default model, as it is a reusable Component. 
But this example is not really important here. I just made me stumble over the 
inconsistent implementation (imho 😉) described in the paragraph above.
Using events would be possible to work around the problem but it would feel 
like a hack. I'd rather prefer a consistent implementation of detach().

Best regards,
Hannes

From: Johannes Renoth 
Sent: Thursday, July 11, 2024 14:01
To: users@wicket.apache.org 
Subject: Re: ListItemModel is not detaching List-model

Hi Hannes,

Shouldn't the detaching of the ListModel be handled by the ListView
itself? Why would you detach the complete ListModel from inside a
component in the ListView? You could always send an event to the parent
of the ListItem however ...

Greetings,

Johannes

On 11/07/2024 13:44, Hannes Becker wrote:

Hi!

Thanks for your feedback.

Maybe I need to elaborate my point a little bit more. It's not about Components 
detaching Models but about the detaching-responsibility of dependent models.

A detach on a (child) Model, which depends on another (parent) Model normally detaches 
also the parent Model. The most "prominent" example is the default 
implementation of IModel.map(...).

In opposition to that, ListItemModel.detach() has a (default) 
noop-implementation and I am wondering why it is not implemented as the 
following:


@Override
public void detach()
{
  listView.getModel().detach();
}


This is actually a problem for me, because I have a LoadableDetachableModel, which is the 
"parent" Model for the ListView. This LoadableDetachableModel needs to be 
detached but I don't have a reference to the LoadableDetachableModel in the Component 
which is rendered inside the ListView. If detach would be implemented in the way I 
proposed (and how it is implemented in IModel.map(...)), it would just work.
Thus, I suggest do implement detach as described above in ListItemModel.

Best regards,
Hannes


From: Martin Terra 
Sent: Wednesday, July 10, 2024 12:57
To: users@wicket.apache.org 
Subject: Re: ListItemModel is not detaching List-model

Normally it's the other way, a component detaches it's model.

The ListItemModel isn't really holding any data, it is relying on the
actual model held by listView.

**
Martin

ke 10. heinäk. 2024 klo 13.53 Hannes Becker (hannes.bec...@proxora.com)
kirjoitti:


Hi!

I am wondering why org.apache.wicket.markup.html.list.ListItemModel is not
detaching the ListView's model. Feels to me like a bug...or is there an
explanation?

Thanks for your help and best regards
Hannes



-
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: ListItemModel is not detaching List-model

[Hannes Becker]

Hi Johannes,

(and greetings, dear former colleague 😉)

As I said - it is not about Components detaching Models. At the end of the 
render cycle, the ListView detaches its Model, this is default & fine.

My point is, that the detaching of Models is not consistently implemented, if 
you take a look at ListItemModel vs. the implementations produced by (e.g.) 
IModel.map(...) or LambdaModel.of(IModel target,...).
The ListItemModel does not care about its dependencies, the latter do - which 
is correct in my humble opinion.

My very specific use case would be too long to post here, but I have a ListView 
A which renders a Component B, which is implemented in a separate class. 
Component B does not know anything about its parent (ListView) Component or the 
ListItemModel, which is passed as default model, as it is a reusable Component. 
But this example is not really important here. I just made me stumble over the 
inconsistent implementation (imho 😉) described in the paragraph above.
Using events would be possible to work around the problem but it would feel 
like a hack. I'd rather prefer a consistent implementation of detach().

Best regards,
Hannes

From: Johannes Renoth 
Sent: Thursday, July 11, 2024 14:01
To: users@wicket.apache.org 
Subject: Re: ListItemModel is not detaching List-model

Hi Hannes,

Shouldn't the detaching of the ListModel be handled by the ListView
itself? Why would you detach the complete ListModel from inside a
component in the ListView? You could always send an event to the parent
of the ListItem however ...

Greetings,

Johannes

On 11/07/2024 13:44, Hannes Becker wrote:
> Hi!
>
> Thanks for your feedback.
>
> Maybe I need to elaborate my point a little bit more. It's not about 
> Components detaching Models but about the detaching-responsibility of 
> dependent models.
>
> A detach on a (child) Model, which depends on another (parent) Model normally 
> detaches also the parent Model. The most "prominent" example is the default 
> implementation of IModel.map(...).
>
> In opposition to that, ListItemModel.detach() has a (default) 
> noop-implementation and I am wondering why it is not implemented as the 
> following:
>
> 
> @Override
> public void detach()
> {
>   listView.getModel().detach();
> }
> 
>
> This is actually a problem for me, because I have a LoadableDetachableModel, 
> which is the "parent" Model for the ListView. This LoadableDetachableModel 
> needs to be detached but I don't have a reference to the 
> LoadableDetachableModel in the Component which is rendered inside the 
> ListView. If detach would be implemented in the way I proposed (and how it is 
> implemented in IModel.map(...)), it would just work.
> Thus, I suggest do implement detach as described above in ListItemModel.
>
> Best regards,
> Hannes
>
> 
> From: Martin Terra 
> Sent: Wednesday, July 10, 2024 12:57
> To: users@wicket.apache.org 
> Subject: Re: ListItemModel is not detaching List-model
>
> Normally it's the other way, a component detaches it's model.
>
> The ListItemModel isn't really holding any data, it is relying on the
> actual model held by listView.
>
> **
> Martin
>
> ke 10. heinäk. 2024 klo 13.53 Hannes Becker (hannes.bec...@proxora.com)
> kirjoitti:
>
>> Hi!
>>
>> I am wondering why org.apache.wicket.markup.html.list.ListItemModel is not
>> detaching the ListView's model. Feels to me like a bug...or is there an
>> explanation?
>>
>> Thanks for your help and best regards
>> Hannes
>>
>>

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

Re: ListItemModel is not detaching List-model

[Johannes Renoth]

Hi Hannes,

Shouldn't the detaching of the ListModel be handled by the ListView 
itself? Why would you detach the complete ListModel from inside a 
component in the ListView? You could always send an event to the parent 
of the ListItem however ...


Greetings,

Johannes

On 11/07/2024 13:44, Hannes Becker wrote:

Hi!

Thanks for your feedback.

Maybe I need to elaborate my point a little bit more. It's not about Components 
detaching Models but about the detaching-responsibility of dependent models.

A detach on a (child) Model, which depends on another (parent) Model normally detaches 
also the parent Model. The most "prominent" example is the default 
implementation of IModel.map(...).

In opposition to that, ListItemModel.detach() has a (default) 
noop-implementation and I am wondering why it is not implemented as the 
following:


@Override
public void detach()
{
  listView.getModel().detach();
}


This is actually a problem for me, because I have a LoadableDetachableModel, which is the 
"parent" Model for the ListView. This LoadableDetachableModel needs to be 
detached but I don't have a reference to the LoadableDetachableModel in the Component 
which is rendered inside the ListView. If detach would be implemented in the way I 
proposed (and how it is implemented in IModel.map(...)), it would just work.
Thus, I suggest do implement detach as described above in ListItemModel.

Best regards,
Hannes


From: Martin Terra 
Sent: Wednesday, July 10, 2024 12:57
To: users@wicket.apache.org 
Subject: Re: ListItemModel is not detaching List-model

Normally it's the other way, a component detaches it's model.

The ListItemModel isn't really holding any data, it is relying on the
actual model held by listView.

**
Martin

ke 10. heinäk. 2024 klo 13.53 Hannes Becker (hannes.bec...@proxora.com)
kirjoitti:


Hi!

I am wondering why org.apache.wicket.markup.html.list.ListItemModel is not
detaching the ListView's model. Feels to me like a bug...or is there an
explanation?

Thanks for your help and best regards
Hannes




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

Re: ListItemModel is not detaching List-model

[Hannes Becker]

Hi!

Thanks for your feedback.

Maybe I need to elaborate my point a little bit more. It's not about Components 
detaching Models but about the detaching-responsibility of dependent models.

A detach on a (child) Model, which depends on another (parent) Model normally 
detaches also the parent Model. The most "prominent" example is the default 
implementation of IModel.map(...).

In opposition to that, ListItemModel.detach() has a (default) 
noop-implementation and I am wondering why it is not implemented as the 
following:


@Override
public void detach()
{
  listView.getModel().detach();
}


This is actually a problem for me, because I have a LoadableDetachableModel, 
which is the "parent" Model for the ListView. This LoadableDetachableModel 
needs to be detached but I don't have a reference to the 
LoadableDetachableModel in the Component which is rendered inside the ListView. 
If detach would be implemented in the way I proposed (and how it is implemented 
in IModel.map(...)), it would just work.
Thus, I suggest do implement detach as described above in ListItemModel.

Best regards,
Hannes


From: Martin Terra 
Sent: Wednesday, July 10, 2024 12:57
To: users@wicket.apache.org 
Subject: Re: ListItemModel is not detaching List-model

Normally it's the other way, a component detaches it's model.

The ListItemModel isn't really holding any data, it is relying on the
actual model held by listView.

**
Martin

ke 10. heinäk. 2024 klo 13.53 Hannes Becker (hannes.bec...@proxora.com)
kirjoitti:

> Hi!
>
> I am wondering why org.apache.wicket.markup.html.list.ListItemModel is not
> detaching the ListView's model. Feels to me like a bug...or is there an
> explanation?
>
> Thanks for your help and best regards
> Hannes
>
>

Re: ListItemModel is not detaching List-model

[Martin Terra]

Normally it's the other way, a component detaches it's model.

The ListItemModel isn't really holding any data, it is relying on the
actual model held by listView.

**
Martin

ke 10. heinäk. 2024 klo 13.53 Hannes Becker (hannes.bec...@proxora.com)
kirjoitti:

> Hi!
>
> I am wondering why org.apache.wicket.markup.html.list.ListItemModel is not
> detaching the ListView's model. Feels to me like a bug...or is there an
> explanation?
>
> Thanks for your help and best regards
> Hannes
>
>

Re: wicket and stateless ajax?

[Bas Gooren]

Hi Korbinian,

I don’t think you can make “dependent” stateless ajax components.

Due to the stateful nature, the page is built anew for each ajax request.
As such you cannot depend on visibility being controlled from an earlier
(stateless) ajax request.

My suggestion would be to either

a) do the visibility change purely client side (so all nested components
are always available on recreation of the page)
b) pull the functionality up into a behavior that you add to the page
itself; So a custom ajax behavior that you pass some params in the url,
which you extract when the behavior is called

… and if it’s not really statelessness you are after but clean urls …

c) map the page using a mapper which doesn’t put the page id in the url;
The public URL is clean, but ajax urls will refer to stateful urls.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 1 juli 2024 bij 10:14:31, Korbinian Bachl (
korbinian.ba...@whiskyworld.de.invalid) schreef:

Hi,

is there any guide or direct guidance on how to make complete stateless
ajax components?

For example on a simple AjaxEventBehaviour "onClick" its enought to supply
a unique ID thats reachable, but if you have an Ajaxified Panel that has
sub-"clicks" on it, I cant find a way to make the subcomponents stateless
since the parent is not visible all times (only after it hast been made
visible via an AJAX call) meaning the target ID is not existing in the DOM.

Best,

KB

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

Re: Variant changes not picked up in response to (Ajax) submit

[Johan Stuyts]

See https://github.com/jstuyts/variant-not-picked-up-directly

Op Fri, 28 Jun 2024 12:04:04 +0200 schreef Martin Grigorov 
:


Hi,

Please create a quickstart and share it with us so we can debug it!
You can share it as a Github project or attach it to a Jira issue.


--
Best regards / Met vriendelijke groet,

Johan Stuyts
Squins IT Solutions BV
Oranjestraat 30
2983 HS  Ridderkerk
The Netherlands
www.squins.com
Chamber of commerce Rotterdam: 24435103

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

Re: Variant changes not picked up in response to (Ajax) submit

[Martin Grigorov]

Hi,

Please create a quickstart and share it with us so we can debug it!
You can share it as a Github project or attach it to a Jira issue.

On Thu, Jun 27, 2024 at 10:22 AM Johan Stuyts 
wrote:

> Note that if a panel with variants is present in the page markup, the
> correct markup variant of the panel is used directly after the submit. So
> the 3rd line below becomes:
>
> - The page markup variant without the style is still displayed, but the
> panel markup variant with the style is correctly displayed.
>
> Op Wed, 26 Jun 2024 10:09:26 +0200 schreef Johan Stuyts <
> johanstu...@squins.com>:
>
> > Hello,
> >
> > If I make changes to the style, variation and/or locale during an (Ajax)
> submit, the changes are not picked up: the markup of the variant that was
> active at the start of the request is still used.
> >
> > For example:
> > - Load the page with the style not set.
> > - Click on an (Ajax) button to set the style (and do not set a response
> page).
> > - The markup variant without the style is still displayed.
> > - Refresh, or click the button again, and then the correct markup
> variant is displayed.
> >
> > Is it possible to tell Wicket to reload the markup after the style,
> variation and/or locale have changed?
> >
> > Thanks in advance for your answers.
> >
>
>
> --
> Best regards / Met vriendelijke groet,
>
> Johan Stuyts
> Squins IT Solutions BV
> Oranjestraat 30
> 2983 HS  Ridderkerk
> The Netherlands
> www.squins.com
> Chamber of commerce Rotterdam: 24435103
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Variant changes not picked up in response to (Ajax) submit

[Johan Stuyts]

Note that if a panel with variants is present in the page markup, the correct 
markup variant of the panel is used directly after the submit. So the 3rd line 
below becomes:

- The page markup variant without the style is still displayed, but the panel 
markup variant with the style is correctly displayed.

Op Wed, 26 Jun 2024 10:09:26 +0200 schreef Johan Stuyts 
:


Hello,

If I make changes to the style, variation and/or locale during an (Ajax) 
submit, the changes are not picked up: the markup of the variant that was 
active at the start of the request is still used.

For example:
- Load the page with the style not set.
- Click on an (Ajax) button to set the style (and do not set a response page).
- The markup variant without the style is still displayed.
- Refresh, or click the button again, and then the correct markup variant is 
displayed.

Is it possible to tell Wicket to reload the markup after the style, variation 
and/or locale have changed?

Thanks in advance for your answers.




--
Best regards / Met vriendelijke groet,

Johan Stuyts
Squins IT Solutions BV
Oranjestraat 30
2983 HS  Ridderkerk
The Netherlands
www.squins.com
Chamber of commerce Rotterdam: 24435103

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

Re: Advanced examples for Wicket

[Ernesto Reinaldo Barreiro]

Thank you very much!

On Thu, Jun 20, 2024 at 9:40 AM Andrea Del Bene  wrote:

> Hi,
>
> I've collected a set of tips and example to tackle some of the most
> advanced needs for a web application such as session clustering or styling
> with SCSS. You can find all here: https://github.com/bitstorm/moder
> n-webdev-wicket  <
> https://t.co/xbLS6q44vT>
>
> Have fun!
>
> Andrea Del Bene.
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: Advanced examples for Wicket

[Korbinian Bachl]

Hi Andrea, 

really nice! 

One thing I stumbled upon is the "Remove page id from URL". While its great to 
have it away from the page url itself, its still in the AJAX links 
e.g.: 

https://examples9x.wicket.apache.org/ajax/editable-label?5 
-> 
 
... 
Wicket.Ajax.ajax({"u":"./editable-label? 5 
-1.0-form-text1-label","c":"id28","e":"click"});; 
.. 
 

Now the problem is that modern spiders like googleBot take these Ajax URLs and 
use them (I can see it in search console). Is there any way to have the Ajax 
instead on the page URL and instead have it transported the necessary details 
via any request payload? Maybe as Post parameters? 

Best, 

KB 

> Von: "Andrea Del Bene" 
> An: "users" 
> Gesendet: Donnerstag, 20. Juni 2024 16:39:49
> Betreff: Advanced examples for Wicket

> Hi,

> I've collected a set of tips and example to tackle some of the most
> advanced needs for a web application such as session clustering or styling
> with SCSS. You can find all here: https://github.com/bitstorm/moder
> n-webdev-wicket 

> Have fun!

> Andrea Del Bene.

Re: Advanced examples for Wicket

[Andrea Del Bene]

Thank you for your kind words and for your text revision!

On Fri, Jun 21, 2024 at 7:17 AM Chris Colman 
wrote:

> Hey Andrea,
>
> Thanks for producing this Wicket example and explaining how to use Agile
> Coder's Bootstrap jars to make the sample app look modern and appealing
> - I think that will be more appealing to newcomers than the traditional
> "Times Roman" sample webapp.
>
> I learnt a lot (e.g. Hazelcast) but I also think it's great that we
> promote, by example, how productive and easy website development can be
> with Wicket by leveraging it's built in JS powered components i.e. To be
> able to achieve all the interactive, partial updating goodness that only
> comes with JS but not having to ever write a single line of JS!
>
> Like you say, a "single language" solution has so many advantages.
>
>
That's exactly the goal of this example 🙏


>
> While reading it I found a few typos. To help improve the readability
> for Wicket newcomers I have listed the typos here:
>
> Under "Page mounting heading":
>
> Typo: resurce-friendly -> resource-friendly
>
> Under "Manage CSS and JavaScript ...":
>
> Typo: CssHeaderItem using refernce class -> reference
>
> Under "Use Spring Boot and Hazelcast..":
>
> Possible typo: "which lay the foundation" could be "which lays the
> foundation"
>
> Under "Warning"
> Typo: "Please note that for sake of semplicity" -> simplicity?
> Typo:  enviorment -> environment
> Typo:  safier -> safer
> Typo:  PAgeManagerProvider ->  PageManagerProvider
>
>
> I don't have much time to contribute any Wicket code changes but if
> someone wants me to proof read any docs promoting Wicket I'm up for it!
>
> Regards,
> Chrisco
>
> On 21/06/2024 12:39 am, Andrea Del Bene wrote:
> > Hi,
> >
> > I've collected a set of tips and example to tackle some of the most
> > advanced needs for a web application such as session clustering or
> styling
> > with SCSS. You can find all here:https://github.com/bitstorm/moder
> > n-webdev-wicket
> >
> > Have fun!
> >
> > Andrea Del Bene.
> >
> --
> Regards,
>
> Chris Colman
> *Feezily*,
> A product of /Step Ahead/ *Software* Pty Ltd
> Web: feezily.com.au  Em: chr...@stepahead.com.au
> Ph: 02 9656 1278



-- 
Andrea Del Bene.
Apache Wicket committer.

Re: Advanced examples for Wicket

[Chris Colman]

Hey Andrea,

Thanks for producing this Wicket example and explaining how to use Agile 
Coder's Bootstrap jars to make the sample app look modern and appealing 
- I think that will be more appealing to newcomers than the traditional 
"Times Roman" sample webapp.


I learnt a lot (e.g. Hazelcast) but I also think it's great that we 
promote, by example, how productive and easy website development can be 
with Wicket by leveraging it's built in JS powered components i.e. To be 
able to achieve all the interactive, partial updating goodness that only 
comes with JS but not having to ever write a single line of JS!


Like you say, a "single language" solution has so many advantages.


While reading it I found a few typos. To help improve the readability 
for Wicket newcomers I have listed the typos here:


Under "Page mounting heading":

Typo: resurce-friendly -> resource-friendly

Under "Manage CSS and JavaScript ...":

Typo: CssHeaderItem using refernce class -> reference

Under "Use Spring Boot and Hazelcast..":

Possible typo: "which lay the foundation" could be "which lays the 
foundation"


Under "Warning"
Typo: "Please note that for sake of semplicity" -> simplicity?
Typo:  enviorment -> environment
Typo:  safier -> safer
Typo:  PAgeManagerProvider ->  PageManagerProvider


I don't have much time to contribute any Wicket code changes but if 
someone wants me to proof read any docs promoting Wicket I'm up for it!


Regards,
Chrisco

On 21/06/2024 12:39 am, Andrea Del Bene wrote:

Hi,

I've collected a set of tips and example to tackle some of the most
advanced needs for a web application such as session clustering or styling
with SCSS. You can find all here:https://github.com/bitstorm/moder
n-webdev-wicket

Have fun!

Andrea Del Bene.


--
Regards,

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

Re: Getting more details into the logs for Component warning

[Korbinian Bachl]

Hi Martin, 

thanks for help. 
A pull request is here as you asked:
https://github.com/apache/wicket/pull/894

My trouble is that I only get these warnings in production and couldnt find 
them in development, so the classic debug->breakpoint wont work but the 
messages will :)


- Ursprüngliche Mail -
> Von: "Martin Grigorov" 
> An: "users" 
> Gesendet: Dienstag, 18. Juni 2024 08:50:09
> Betreff: Re: Getting more details into the logs for Component warning

> Hi,
> 
> The easiest is to put a breakpoint at
> https://github.com/apache/wicket/blob/b2d55be7b06d736b2085387ecc29cdd22540b588/wicket-core/src/main/java/org/apache/wicket/Component.java#L2480
> Feel free to send a Pull Request with more details in the log message!
> 
> On Tue, Jun 18, 2024 at 9:32 AM Korbinian Bachl
>  wrote:
> 
>> Hi,
>>
>> it seems as I somewhere made a set MarkupId on a component that renders
>> body only. I got much like this:
>>
>> [[WARN  - Component  - Markup id set on a component that
>> renders its body only. Markup id: ida0ce, component id: body.]]
>>
>> The markup id seems a repeater generated one. Any idea how I can get more
>> details about the Component like maybe its class so I can spot it?
>>
>> 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: Getting more details into the logs for Component warning

[Martin Grigorov]

Hi,

The easiest is to put a breakpoint at
https://github.com/apache/wicket/blob/b2d55be7b06d736b2085387ecc29cdd22540b588/wicket-core/src/main/java/org/apache/wicket/Component.java#L2480
Feel free to send a Pull Request with more details in the log message!

On Tue, Jun 18, 2024 at 9:32 AM Korbinian Bachl
 wrote:

> Hi,
>
> it seems as I somewhere made a set MarkupId on a component that renders
> body only. I got much like this:
>
> [[WARN  - Component  - Markup id set on a component that
> renders its body only. Markup id: ida0ce, component id: body.]]
>
> The markup id seems a repeater generated one. Any idea how I can get more
> details about the Component like maybe its class so I can spot it?
>
> Best,
>
> KB
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

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

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: ApacheCon: Community Over Code Bratislava

[Ernesto Reinaldo Barreiro]

Thanks for the invitation!

On Mon, Jun 3, 2024 at 5:05 AM Tony Tkacik 
wrote:

>
>
> Hi everyone!
>
> Just reaching out to see if any of you are planning to hit up ApacheCon:
> Community Over Code in Bratislava ( [ https://eu.communityovercode.org/ |
> https://eu.communityovercode.org/ ] ).
>
> My colleague, Radovan Semancik, and I are part of a team based in
> Slovakia, where we use Wicket for our open-source product, midPoint.
> We thought it'd be cool to meet other Wicket developers and community
> members after the conference for a beer and a chat.
>
> If you're up for it, you can meet Radovan at the conference, or drop me a
> reply here.
>
> Thanks,
>
>
> --
> Anton Tkáčik
> Software Developer
> evolveum.com
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: Wicket 10 - not finding "el" properties

[mscoon]

Thanks for the reply Martin.

I also did some improvements in the file's contents. Here's the PR:
https://github.com/apache/wicket/pull/879. Do I need to post this in the
dev list as well?

On Mon, May 27, 2024 at 10:50 AM Martin Grigorov 
wrote:

> Hi Marios,
>
> On Mon, May 27, 2024 at 9:33 AM mscoon  wrote:
>
> > Hi all,
> >
> > We have an application in greek. We recently to wicket 10 and messages
> for
> > the build-in validators (e.g. Required) stopped appearing in greek and
> > started appearing in english.
> >
> > We noticed that the name of the properties file in wicket-core
> > (wicket-core\src\main\java\org\apache\wicket) is
> > Applcation_el.properties.utf8.properties (notice it has twice the word
> > "properties"), and this seems to be the culprit.
> >
> > Should I submit a PR for this?
> >
>
> Yes, please!
> Thank you!
>
>
>
> >
> > Thanks
> > Marios
> >
>

Re: Wicket 10 - not finding "el" properties

[Martin Grigorov]

Hi Marios,

On Mon, May 27, 2024 at 9:33 AM mscoon  wrote:

> Hi all,
>
> We have an application in greek. We recently to wicket 10 and messages for
> the build-in validators (e.g. Required) stopped appearing in greek and
> started appearing in english.
>
> We noticed that the name of the properties file in wicket-core
> (wicket-core\src\main\java\org\apache\wicket) is
> Applcation_el.properties.utf8.properties (notice it has twice the word
> "properties"), and this seems to be the culprit.
>
> Should I submit a PR for this?
>

Yes, please!
Thank you!



>
> Thanks
> Marios
>

Re: Apache Wicket 7.6.0 - filter status: REJECTED

[Emond Papegaaij]

Op di 9 apr 2024 om 17:16 schreef Mihir Chhaya :

> Thank you, Emond for sharing this. We had our JBoss Server patched up
> recently which broke the system. It was working fine before the server
> update.
>

The change came as a fix for CVE-2023-3171: WFCORE-6578 WildFly heap
exhaustion via deserialization
You can find more information here:
https://issues.redhat.com/browse/WFCORE-6578 or JBEAP-24964 (which I don't
have access to)

In the actual change (see the pull request), you can see the filter being
set to maxbytes=10485760;maxdepth=128;maxarray=10;maxrefs=30

Best regards,
Emond

Re: Apache Wicket 7.6.0 - filter status: REJECTED

[Mihir Chhaya]

Thank you, Emond for sharing this. We had our JBoss Server patched up
recently which broke the system. It was working fine before the server
update.

On Mon, Apr 8, 2024 at 1:11 PM Emond Papegaaij 
wrote:

> Op ma 8 apr 2024 18:16 schreef Mihir Chhaya :
>
> > We have the following configuration for one of the Apache Wicket
> projects.
> >
> > Apache Wicket: 7.6.0
> > OpenJDK Java Version: 1.8.402
> > JBoss Server: 7.4.13
> >
> > *Issue: Caused by: java.io.InvalidClassException: filter status:
> REJECTED*
> >
> > The application works fine when the number of records is around 100, but
> > throws above error when the number is increased.
> > My understanding is some Wicket class is being rejected from the
> > Serialization/Deserialization and this class comes into picture only when
> > the Page has more data.
> >
>
> This is likely not related to a specific class, but rather to the size of
> the page or the number of references in it. We hit the exact same issue
> some time ago after upgrading WildFly. In the recent releases a filter on
> serialization is enabled, that does not interact nicely with Wicket. On
> WildFly you can disable it with DISABLE_JDK_SERIAL_FILTER=true. It probably
> is the same on JBoss EAP. You can also try to tweak the settings if you
> want to keep the filter, but you will have to check with Red Hat for the
> exact settings.
>
> Best regards,
> Emond
>
> >
>

Re: Apache Wicket 7.6.0 - filter status: REJECTED

[Emond Papegaaij]

Op ma 8 apr 2024 18:16 schreef Mihir Chhaya :

> We have the following configuration for one of the Apache Wicket projects.
>
> Apache Wicket: 7.6.0
> OpenJDK Java Version: 1.8.402
> JBoss Server: 7.4.13
>
> *Issue: Caused by: java.io.InvalidClassException: filter status: REJECTED*
>
> The application works fine when the number of records is around 100, but
> throws above error when the number is increased.
> My understanding is some Wicket class is being rejected from the
> Serialization/Deserialization and this class comes into picture only when
> the Page has more data.
>

This is likely not related to a specific class, but rather to the size of
the page or the number of references in it. We hit the exact same issue
some time ago after upgrading WildFly. In the recent releases a filter on
serialization is enabled, that does not interact nicely with Wicket. On
WildFly you can disable it with DISABLE_JDK_SERIAL_FILTER=true. It probably
is the same on JBoss EAP. You can also try to tweak the settings if you
want to keep the filter, but you will have to check with Red Hat for the
exact settings.

Best regards,
Emond

>

Re: Wicket & Quarkus

[Martijn Dashorst]

Quarkus + Wicket and graalvm native image will probably not work because of
reflection use.

An intern also looked at CDI + Wicket + Quarkus and that will also not work
because Wicket components are not managed by the CDI container (we do a
non-contextual injection), so the compile time ARC resolving won't work.

But I'm quite interested to see this work in the future. Let us know if you
run into anything.

Martijn


On Fri, Mar 22, 2024 at 10:59 AM Robert Palm 
wrote:

>
> Hi list!
>
> I am looking into wicket 10 and wonder how to use it with quarkus.io
>
> Is there any "official integration" available ?
>
> Thanks
>
> Robert
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: Roadmap of Apache Wicket 2024 or is the project nearly dead?

[Andrea Del Bene]

FYI: version 4.0.0 based on Wicket 10.0.0 is out!

On Wed, Mar 13, 2024 at 1:32 PM Kyrindorx  wrote:

> oh nice! gz!
>
> How knows something about
> https://github.com/MarcGiffing/wicket-spring-boot and Apache Wicket 10.x?
>
> Greets
> Kyrindor
>
> Am 13.03.2024 um 10:25 schrieb Andrea Del Bene:
> > you missed the last news 😉
> >
> >
> https://news.apache.org/foundation/entry/apache-software-foundation-announces-apache-wicket-v10
> >
> > On Wed, Mar 13, 2024 at 10:21 AM Kyrindorx  wrote:
> >
> >> Hello everyone,
> >>
> >> what are the plans for Apache Wicket 2024? Migration to Java 17, 21?
> >> Upgrade to compatibility with spring-boot 3.x? Is there a roadmap and
> >> plan for the project somewhere?
> >>
> >> Thanks in advance for some information for further plans on Apache
> Wicket.
> >>
> >> Best regards
> >> Kyrindor
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
>


-- 
Andrea Del Bene.
Apache Wicket committer.

Re: Wicket & Quarkus

[Robert Palm]

Yes, thanks, found this, too.

Not sure if it supports all the features like hot reload when wicket  
components are changed and how well it will be maintained in the  
future...




Zitat von Martin Grigorov :


Hi,

I am not aware of anything "official".
You may take a look at https://github.com/brunoborges/wicket-with-quarkus
but it is rather an example than integration.

On Fri, Mar 22, 2024 at 11:59 AM Robert Palm 
wrote:



Hi list!

I am looking into wicket 10 and wonder how to use it with quarkus.io

Is there any "official integration" available ?

Thanks

Robert




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

[Martin Grigorov]

Hi,

I am not aware of anything "official".
You may take a look at https://github.com/brunoborges/wicket-with-quarkus
but it is rather an example than integration.

On Fri, Mar 22, 2024 at 11:59 AM Robert Palm 
wrote:

>
> Hi list!
>
> I am looking into wicket 10 and wonder how to use it with quarkus.io
>
> Is there any "official integration" available ?
>
> Thanks
>
> Robert
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: AbstractAjaxBehavior#getCallbackUrl returning HTTP URLs instead of HTTPS

[Martin Grigorov]

Hi,

Can you put a breakpoint at
https://github.com/apache/wicket/blob/wicket-9.x/wicket-core/src/main/java/org/apache/wicket/protocol/http/servlet/ServletWebResponse.java#L176
(#encodeURL(Url)) and see what is going on?
Wicket should return a relative url and let the browser resolve it to full.

On Mon, Mar 18, 2024 at 7:35 PM Tomasz Pluskiewicz 
wrote:

> Hello
>
> I’m troubleshooting a problem which suddenly appeared on my instance of
> INCEpTION [1]. It is using wicket 9.16
>
> I am running behind a reverse proxy and seemingly out of the blue page
> navigation goes over HTTPS-HTTP-HTTPS redirects [2]. Alone, that would not
> be an issue but the application sends some URLs constructed by wicket [2]
> to fetch and they fail security checks in the browser.
>
> I tracked them to AbstractAjaxBehavior#getCallbackUrl but am at a loss as
> to why the returned URLs are not HTTPS…
>
> The server is running a managed nginx on cloud66.com. It is doing SSL
> termination as expected, adding the X-Forwarded-* headers. I’ve been
> running a number of apps there and never had this kind of problems.
> Strangest part is that initially the app worked fine and this started
> happening only after some time, with no apparent reason that I con think of
> in terms of server reconfiguration etc.
>
> Thanks,
> Tom
>
> [1]: https://github.com/inception-project/inception
> [2]: https://github.com/inception-project/inception/issues/4630
> [3]:
> https://github.com/inception-project/inception/blob/inception-31.3/inception/inception-pdf-editor2/src/main/java/de/tudarmstadt/ukp/inception/pdfeditor2/view/PdfDocumentIFrameView.java#L165-L166
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: [ANNOUNCE] WicketStuff 10.0.0 Released

[Andrea Del Bene]

Thank you!

On Mon, Mar 18, 2024 at 11:25 AM Maxim Solodovnik 
wrote:

> WicketStuff core 10.0.0 based on Apache Wicket 10.0.0 is released
> and soon will be available at Maven Central!
>
> dependabot[bot] (50):
>   Bump org.springframework:spring-core from 6.0.10 to 6.0.15 (#760)
>   Bump org.springframework:spring-core from 6.0.15 to 6.0.16 (#761)
>   Bump com.hazelcast:hazelcast in
> /datastores-parent/datastore-hazelcast (#763)
>   Bump org.springframework:spring-web from 6.0.16 to 6.0.17 (#765)
>   Bump actions/checkout from 2 to 4 (#766)
>   Bump actions/setup-java from 2 to 4 (#768)
>   Bump actions/cache from 2 to 4 (#770)
>   Bump ch.qos.logback:logback-classic from 1.4.8 to 1.5.0 (#815)
>   Bump commons-logging:commons-logging from 1.2 to 1.3.0 (#814)
>   Bump org.apache.maven.plugins:maven-surefire-report-plugin (#813)
>   Bump org.apache.maven.plugins:maven-project-info-reports-plugin
> (#812)
>   Bump org.javassist:javassist from 3.29.2-GA to 3.30.2-GA (#811)
>   Bump org.apache.maven.archetype:archetype-packaging from 3.1.0
> to 3.2.1 (#805)
>   Bump org.apache.felix:org.apache.felix.webconsole from 3.1.8 to
> 5.0.0 (#802)
>   Bump com.datastax.cassandra:cassandra-driver-core from 3.6.0 to
> 3.11.5 (#801)
>   Bump org.apache.maven.plugins:maven-clean-plugin from 3.2.0 to
> 3.3.2 (#799)
>   Bump com.hazelcast:hazelcast from 5.3.5 to 5.3.6 (#798)
>   Bump org.webjars.bower:datatables from 1.10.19 to 1.10.21 (#796)
>   Bump org.ow2.asm:asm-util from 9.5 to 9.6 (#795)
>   Bump scala.version from 2.13.11 to 2.13.13 (#794)
>   Bump com.google.protobuf:protobuf-java from 3.19.6 to 3.25.3 (#787)
>   Bump redis.clients:jedis from 4.3.1 to 5.1.1 (#786)
>   Bump org.apache.maven.plugins:maven-jxr-plugin from 2.5 to 3.3.2
> (#783)
>   Bump
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib
> (#782)
>   Bump org.apache.ignite:ignite-core from 2.14.0 to 2.16.0 (#781)
>   Bump org.apache.maven.plugins:maven-checkstyle-plugin from 2.15
> to 3.3.1 (#776)
>   Bump spring.version from 6.0.17 to 6.1.4 (#773)
>   Bump net.javacrumbs.json-unit:json-unit from 2.17.0 to 3.2.7 (#769)
>   Bump org.apache.shiro:shiro-core from 1.11.0 to 1.13.0 (#759)
>   Bump org.glassfish.main.extras:glassfish-embedded-all from 4.0
> to 7.0.12 (#778)
>   Bump org.apache.shiro:shiro-web from 1.11.0 to 1.13.0 (#758)
>   Bump log4j.version from 2.20.0 to 2.23.0 (#797)
>   Bump org.codehaus.mojo:findbugs-maven-plugin from 3.0.1 to 3.0.5
> (#829)
>   Bump ch.qos.logback:logback-classic from 1.5.0 to 1.5.2 (#828)
>   Bump org.webjars.npm:tinymce from 6.8.2 to 6.8.3 (#827)
>   Bump org.codehaus.mojo:taglist-maven-plugin from 2.4 to 3.0.0 (#826)
>   Bump org.apache.maven.plugins:maven-archetype-plugin from 3.1.0
> to 3.2.1 (#825)
>   Bump org.apache.maven.plugins:maven-site-plugin (#824)
>   Bump jakarta.servlet.jsp:jakarta.servlet.jsp-api from 3.1.0 to
> 3.1.1 (#823)
>   Bump org.glassfish.main.extras:glassfish-embedded-all (#820)
>   Bump com.sun.xml.bind:jaxb-core from 2.3.0.1 to 4.0.4 (#819)
>   Bump org.mockito:mockito-core from 5.10.0 to 5.11.0 (#818)
>   Bump org.apache.maven.plugins:maven-toolchains-plugin from 1.1
> to 3.1.0 (#817)
>   Bump shiro.version from 1.13.0 to 2.0.0 (#816)
>   Bump slf4j.version from 2.0.7 to 2.0.12 (#779)
>   Bump org.clojure:clojure from 1.11.1 to 1.11.2 (#830)
>   Bump ch.qos.logback:logback-classic from 1.5.2 to 1.5.3 (#836)
>   Bump com.sun.xml.bind:jaxb-core from 4.0.4 to 4.0.5 (#835)
>   Bump com.fasterxml.jackson.core:jackson-databind from 2.14.3 to
> 2.16.2 (#833)
>   Bump redis.clients:jedis from 5.1.1 to 5.1.2 (#832)
>
> Maxim Solodovnik (15):
>   Switching to the next development version
>   schemaLocation for web.xml files is updated
>   Jetty DTD URL is updated
>   Dependencies are updated
>   Merge is fixed
>   Duplicate property removed
>   TinyMCE 3 and 4 are dropped
>   Modules for TinyMCE 3 and 4 are dropped
>   Dependencies are updated
>   Fixes issue #764: presense of 'getAttribute' function is being tested
>   Dependencies are updated
>   Dependencies are updated
>   Fast serializer is updated
>   GPG plugin is updated
>   wicketstuff-core-10.0.0 is released
>
> Johannes Renoth (1):
>   Add TinyMCE 6 module (#762)
>
> Martin Tzvetanov Grigorov (1):
>   Add dependabot config for updating the Java deps and Github Actions
>
> Silas Porth (1):
>   Update/partial rewrite of editable-grid (#756)
>
> The WicketStuff team
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Andrea Del Bene.
Apache Wicket committer.

Re: Roadmap of Apache Wicket 2024 or is the project nearly dead?

[Andrea Del Bene]

you missed the last news 😉

https://news.apache.org/foundation/entry/apache-software-foundation-announces-apache-wicket-v10

On Wed, Mar 13, 2024 at 10:21 AM Kyrindorx  wrote:

> Hello everyone,
>
> what are the plans for Apache Wicket 2024? Migration to Java 17, 21?
> Upgrade to compatibility with spring-boot 3.x? Is there a roadmap and
> plan for the project somewhere?
>
> Thanks in advance for some information for further plans on Apache Wicket.
>
> Best regards
> Kyrindor
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Andrea Del Bene.
Apache Wicket committer.

Re: Question about Wicket 10.0.0-M2

[Martin Grigorov]

Hi Tom,

It seems that you run your application with modulePath (JPMS) instead of
classpath.
But your application is not a JPMS module itself - "unnamed module".
I guess you just need to disable JPMS for Maven Surefire plugin -
https://stackoverflow.com/a/73654342/497381

On Tue, Feb 6, 2024 at 3:36 PM Tom Benjamins 
wrote:

> Hello,
>
> I was wondering whether this is the correct mailinglist to send a
> quiestion about upgrading a Wicket 9 application to
> Wicket 10.
> I have upgraded from Wicket 9.15 to 10.0.0-M2, Java 17 and Spring Boot 3.2
>
> I have a regression/ test which uses a CachingPageStore and during the
> adding of any page to the store
>
> I get the following exception:
>
> java.lang.reflect.InaccessibleObjectException: Unable to make static
> java.io.ObjectStreamClass
> java.io.ObjectStreamClass.lookup(java.lang.Class,boolean) accessible:
> module java.base does not "opens java.io" to unnamed module @21bcffb5
>
> at
>
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
>
> at
>
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
>
> at
> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
>
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
>
> at
>
> org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream.(CheckingObjectOutputStream.java:253)
>
> at
>
> org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:387)
>
> at
> java.base/java.io
> .ObjectOutputStream.writeObject(ObjectOutputStream.java:350)
>
> at
>
> org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:97)
>
> at
>
> org.apache.wicket.pageStore.SerializingPageStore.addPage(SerializingPageStore.java:80)
>
> at
>
> org.apache.wicket.pageStore.CachingPageStore.addPage(CachingPageStore.java:73)
>
> at
>
> org.apache.wicket.pageStore.RequestPageStore.detach(RequestPageStore.java:114)
>
> at org.apache.wicket.page.PageManager.detach(PageManager.java:91)
>
>
> Is this a error that anybody has seen before? Does this merit an issue?
>
> --
> Lost Lemon B.V.T: +31(0)85 489 
> Kennemerplein 1E:tombenjam...@lostlemon.nl
> 2011 MH HaarlemW:www.lostlemon.nl
>

Re: upgrading Wicket

[Martijn Dashorst]

If I was a consulting company I'd also suggest rewriting in React.

But upgrading to latest/greatest Wicket is not too bad, even if it is
Wicket 1.4 code. There are gotcha's, but since probably the whole Wicket
community upgraded their projects way before you guys, the issues are
pretty much well documented in the migration guides.

For now I'd suggest upgrading up to Wicket 9 at maximum, and see what
breaks. Wicket 10 has the javax - jakarta package rename IIRC, so that will
probably mean upgrading your complete stack.

I don't know how many pages and custom components you need to migrate. At
€dayjob we've upgraded our 3-4 major applications of in total 5M lines of
code consistently, and typically the upgrades from 1.4 to 1.5 to 6 were the
toughest. From there on it was not that hard (a couple of days for a major
upgrade). But at that time, Wicket was really in heavy development and we
did upgrade to betas all the time so there was usually some considerable
rework necessary at that time to even out the wrinkles.

Martijn


On Fri, Jan 26, 2024 at 2:58 PM Nelligan, Steven M 
wrote:

>
> Help,  I am new to Wicket...and have taken over a project with wicket
> version 1.4.18, which is way out of date.
> According to a consulting firm, this would be a multi-year project to
> update all of our projects to the latest version of Wicket; and they are
> recommending we just rewrite the front end code to React.
>
> Does anyone have a program or script which would help with the updating of
> wicket components to a new Version?
>
> Thanks,
> Steven M Nelligan
> SENIOR SOFTWARE DEVELOPER
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: upgrading Wicket

[Mihir Chhaya]

Hi Steven,

I undertook the Wicket Upgrade for a couple of 1.4/1.5 projects to Wicket
7/8 with Bootstrap. I don't have a script for upgrading it, but can share
my experiences and component changes by early next week.

If your 1.4 projects had multiple complex custom components written, then
it might be just easier to either create a new project with the latest
Apache Wicket and Wicket based UI libraries (which can replace some of your
custom components) to retain and reuse Wicket knowledge, or, use React (or
other Javascript framework).

Using React compared to Apache Wicket would be an architectural shift and
would need evaluating the pros/cons like budget, timeline,
ability/requirement to write test cases for UI behavior, Java v/s
JavaScript coding, overall testing, learning curve etc.

Creating a new project with the latest Apache Wicket and UI component
libraries might be easier than using React just with the fact that you
already have 1.4 code to copy/paste many if not most of the codebase.
In both cases, you can try to keep the UI leaner and push business to a
separate web services based project.

Best,
-Mihir


On Fri, Jan 26, 2024 at 8:58 AM Nelligan, Steven M 
wrote:

>
> Help,  I am new to Wicket...and have taken over a project with wicket
> version 1.4.18, which is way out of date.
> According to a consulting firm, this would be a multi-year project to
> update all of our projects to the latest version of Wicket; and they are
> recommending we just rewrite the front end code to React.
>
> Does anyone have a program or script which would help with the updating of
> wicket components to a new Version?
>
> Thanks,
> Steven M Nelligan
> SENIOR SOFTWARE DEVELOPER
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: upgrading Wicket

[Sven Meier]

Hi Steven,

I've send you a PM.

Sven


On 26.01.24 14:57, Nelligan, Steven M wrote:

Help,  I am new to Wicket...and have taken over a project with wicket version 
1.4.18, which is way out of date.
According to a consulting firm, this would be a multi-year project to update 
all of our projects to the latest version of Wicket; and they are recommending 
we just rewrite the front end code to React.

Does anyone have a program or script which would help with the updating of 
wicket components to a new Version?

Thanks,
Steven M Nelligan
SENIOR SOFTWARE DEVELOPER



-
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 9 + Jetty 12: Lots of exceptions due to modification of read-only response

[Martin Grigorov]

https://issues.apache.org/jira/browse/WICKET-7075
I will backport it to 9.x !

On Tue, Jan 23, 2024 at 10:26 AM Martin Grigorov 
wrote:

> Hi,
>
> On Mon, Jan 22, 2024 at 6:09 PM Martin Simons 
> wrote:
>
>> Hey everyone,
>>
>> I started a gnarly migration of a really old Wicket 6 application to
>> Wicket 9 last week. One of the objectives was to move away from a
>> .war-based deployment to a Tomcat app server, and instead go with an
>> embedded server which runs within a Docker file. The choice here fell on
>> Jetty 12 using the EE8 environment.
>>
>
> Are you still able to deploy to Tomcat ? If YES then it would be good to
> check whether your app will experience the same errors there too!
>
>
>>
>> So far, so good. After getting all the API changes sorted out, most
>> things work as expected. But what puzzles me is that I get the logs flooded
>> with exceptions because different pieces of code try to write to the web
>> response at a point in the web request cycle when it has already been
>> committed.
>>
>> For Wicket itself, this affects the COOP and COEP filters when handling
>> HEAD requests.
>>
>
> COOP and COEP are new in Wicket 9.x, so it is quite possible that they
> might have issues with HEAD requests.
> Please provide failing unit tests and/or a quickstart and/or at least
> stacktraces!
>
>
>>
>> My one code is affected (for example) when trying to set a cookie at the
>> end of a request cycle.
>>
>> So two questions:
>>
>>   1.  I am likely missing something obvious. Does anyone see what it
>> might be?
>>   2.  Regarding my own code: I get that I can’t write to a response
>> that’s been committed, but what’s “the Wicket way” to modify a response
>> header after the response has been processed but before it is written?
>> RequestCycleListener::onEndRequest() seems to be too late.
>
>
> RequestCycle[Listener]#onEndRequest() is called before
> HttpServletResponse#flush(), so it shouldn't be that late. But I need to
> debug the app to tell whether the response is buffering or not.
> See org.apache.wicket.protocol.http.HeaderBufferingWebResponse
>
>
> If you were using Wicket 10.x + servlet-api 6.x then you could use
> https://jakarta.ee/specifications/servlet/6.0/apidocs/jakarta.servlet/jakarta/servlet/http/httpservletresponse#setTrailerFields(java.util.function.Supplier)
>
>
>
>
>>
>> I found surprisingly little on this problem when googling, so I am almost
>> certain it’s my mistake. But after looking at it for days, I am sort of
>> stuck. I would greatly appreciate a few pointers.
>>
>> Thank you very much,
>> Martin
>>
>

Re: Wicket 9 + Jetty 12: Lots of exceptions due to modification of read-only response

[Martin Grigorov]

Hi,

On Mon, Jan 22, 2024 at 6:09 PM Martin Simons 
wrote:

> Hey everyone,
>
> I started a gnarly migration of a really old Wicket 6 application to
> Wicket 9 last week. One of the objectives was to move away from a
> .war-based deployment to a Tomcat app server, and instead go with an
> embedded server which runs within a Docker file. The choice here fell on
> Jetty 12 using the EE8 environment.
>

Are you still able to deploy to Tomcat ? If YES then it would be good to
check whether your app will experience the same errors there too!


>
> So far, so good. After getting all the API changes sorted out, most things
> work as expected. But what puzzles me is that I get the logs flooded with
> exceptions because different pieces of code try to write to the web
> response at a point in the web request cycle when it has already been
> committed.
>
> For Wicket itself, this affects the COOP and COEP filters when handling
> HEAD requests.
>

COOP and COEP are new in Wicket 9.x, so it is quite possible that they
might have issues with HEAD requests.
Please provide failing unit tests and/or a quickstart and/or at least
stacktraces!


>
> My one code is affected (for example) when trying to set a cookie at the
> end of a request cycle.
>
> So two questions:
>
>   1.  I am likely missing something obvious. Does anyone see what it might
> be?
>   2.  Regarding my own code: I get that I can’t write to a response that’s
> been committed, but what’s “the Wicket way” to modify a response header
> after the response has been processed but before it is written?
> RequestCycleListener::onEndRequest() seems to be too late.


RequestCycle[Listener]#onEndRequest() is called before
HttpServletResponse#flush(), so it shouldn't be that late. But I need to
debug the app to tell whether the response is buffering or not.
See org.apache.wicket.protocol.http.HeaderBufferingWebResponse


If you were using Wicket 10.x + servlet-api 6.x then you could use
https://jakarta.ee/specifications/servlet/6.0/apidocs/jakarta.servlet/jakarta/servlet/http/httpservletresponse#setTrailerFields(java.util.function.Supplier)




>
> I found surprisingly little on this problem when googling, so I am almost
> certain it’s my mistake. But after looking at it for days, I am sort of
> stuck. I would greatly appreciate a few pointers.
>
> Thank you very much,
> Martin
>

Re: Wicket 9 + Jetty 12: Lots of exceptions due to modification of read-only response

[Maxim Solodovnik]

Hello Martin,

On Mon, 22 Jan 2024 at 23:09, Martin Simons  wrote:
>
> Hey everyone,
>
> I started a gnarly migration of a really old Wicket 6 application to Wicket 9 
> last week. One of the objectives was to move away from a .war-based 
> deployment to a Tomcat app server, and instead go with an embedded server 
> which runs within a Docker file. The choice here fell on Jetty 12 using the 
> EE8 environment.

I believe you need Wicket10 for Jetty12 :)

>
> So far, so good. After getting all the API changes sorted out, most things 
> work as expected. But what puzzles me is that I get the logs flooded with 
> exceptions because different pieces of code try to write to the web response 
> at a point in the web request cycle when it has already been committed.
>
> For Wicket itself, this affects the COOP and COEP filters when handling HEAD 
> requests.
>
> My one code is affected (for example) when trying to set a cookie at the end 
> of a request cycle.
>
> So two questions:
>
>   1.  I am likely missing something obvious. Does anyone see what it might be?
>   2.  Regarding my own code: I get that I can’t write to a response that’s 
> been committed, but what’s “the Wicket way” to modify a response header after 
> the response has been processed but before it is written? 
> RequestCycleListener::onEndRequest() seems to be too late.
>
> I found surprisingly little on this problem when googling, so I am almost 
> certain it’s my mistake. But after looking at it for days, I am sort of 
> stuck. I would greatly appreciate a few pointers.
>
> Thank you very much,
> Martin



-- 
Best regards,
Maxim

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

Re: A simple Wicket component to render a Vue app

[Andrea Del Bene]

Thank you Kent!

On Sat, 20 Jan 2024, 12:31 Ernesto Reinaldo Barreiro, 
wrote:

> Thanks for sharing!
>
> On Sat, Jan 20, 2024 at 12:49 AM Kent Tong  wrote:
>
> > Hi,
> >
> > I have written a simple Wicket component that allows you to easily
> render a
> > Vue 3 app in Java. This component is implemented in about just 130 lines
> of
> > code (including Java, HTML and js), so there is no risk in using it.
> > How to use
> >
> > Suppose that you want a Vue app on an HTML page like below:
> >
> > https://.../vue.js";>
> > 
> > 
> > var app = Vue.createApp({
> > data() {
> > return {a: 4, b: "Hi"};
> > },
> > template: `{{a}} {{b}}`,
> > methods {
> > m1() {
> > console.log(this.a);
> > }
> > },
> > });
> > app.mount('#app1')
> > 
> >
> > And you want to generate this from a Wicket page. To do that, you can use
> > the WicketVueApp component provided by this project.
> >
> > First, add the dependency:
> >
> > 
> >com.ttdev
> >wicket-vue-app-core
> >1.0.2
> > 
> >
> > Your Wicket page should be like:
> >
> > import com.ttdev.WicketVueApp;
> > public class GetStartedDemo extends WebPage {
> >   public GetStartedDemo() {
> > HashMap state = new HashMap<>();
> > state.put("a", 4);
> > state.put("b", "Hi");
> > WicketVueApp vwa=new WicketVueApp("wva",
> > new Model(state),
> > "m1() {console.log(this.a);}");
> > add(vwa);
> >   }
> > }
> >
> > The template is provided in the HTML markup:
> >
> > 
> >{{a}} {{b}}
> >
> > The WicketVueApp component will generate the desired HTML and js code
> > inside the  automatically. Now, run your Wicket webapp as usual and
> > you will see the Vue app working on your Wicket page.
> > Handling Vue events in Wicket
> >
> > In the example above, suppose that you want to handle the click on the
> > server side (Wicket), all you need to do is to call a js method named
> "cb"
> > (standing for "call back") as shown below:
> >
> > 
> >{{a}} {{b}}
> >
> > This cb method will use Wicket's ajax mechanism to send the request to
> the
> > Wicket side, where you can handle it by overriding the OnVueEvent method:
> >
> > public class GetStartedDemo extends WebPage {
> >   public GetStartedDemo() {
> > HashMap state = new HashMap<>();
> > state.put("a", 4);
> > state.put("b", "Hi");
> > WicketVueApp vwa=new WicketVueApp("wva",
> > new Model(state)) {
> >   @Override
> >   public void onVueEvent(AjaxRequestTarget target, Map > Object> data) {
> > state.put("b", state.get("b")+"!");
> >   }
> > };
> > add(vwa);
> >   }
> > }
> >
> > The cb method will automatically send the current state of the Vue app
> back
> > to the WicketVueApp component on server, which will use the data to
> update
> > itself own state, before calling its onVueEvent method. This way you will
> > have access to the latest state of the Vue app in the browser.
> >
> > In this method you can further modify the state, which will be sent back
> to
> > the browser automatically to refresh the Vue app. Here, in this example,
> > the "b" variable's value will have an exclamation mark added to it.
> >
> > Note that the AjaxRequestTarget one of the parameters, you can add other
> > ajax Wicket components to the target to have them refreshed.
> > <
> >
> https://github.com/freemant2000/WicketVueApp#handling-vue-events-in-wicket
> > >
> >
> > --
> > Kent Tong
> > IT author and consultant, child education coach
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: A simple Wicket component to render a Vue app

[Ernesto Reinaldo Barreiro]

Thanks for sharing!

On Sat, Jan 20, 2024 at 12:49 AM Kent Tong  wrote:

> Hi,
>
> I have written a simple Wicket component that allows you to easily render a
> Vue 3 app in Java. This component is implemented in about just 130 lines of
> code (including Java, HTML and js), so there is no risk in using it.
> How to use
>
> Suppose that you want a Vue app on an HTML page like below:
>
> https://.../vue.js";>
> 
> 
> var app = Vue.createApp({
> data() {
> return {a: 4, b: "Hi"};
> },
> template: `{{a}} {{b}}`,
> methods {
> m1() {
> console.log(this.a);
> }
> },
> });
> app.mount('#app1')
> 
>
> And you want to generate this from a Wicket page. To do that, you can use
> the WicketVueApp component provided by this project.
>
> First, add the dependency:
>
> 
>com.ttdev
>wicket-vue-app-core
>1.0.2
> 
>
> Your Wicket page should be like:
>
> import com.ttdev.WicketVueApp;
> public class GetStartedDemo extends WebPage {
>   public GetStartedDemo() {
> HashMap state = new HashMap<>();
> state.put("a", 4);
> state.put("b", "Hi");
> WicketVueApp vwa=new WicketVueApp("wva",
> new Model(state),
> "m1() {console.log(this.a);}");
> add(vwa);
>   }
> }
>
> The template is provided in the HTML markup:
>
> 
>{{a}} {{b}}
>
> The WicketVueApp component will generate the desired HTML and js code
> inside the  automatically. Now, run your Wicket webapp as usual and
> you will see the Vue app working on your Wicket page.
> Handling Vue events in Wicket
>
> In the example above, suppose that you want to handle the click on the
> server side (Wicket), all you need to do is to call a js method named "cb"
> (standing for "call back") as shown below:
>
> 
>{{a}} {{b}}
>
> This cb method will use Wicket's ajax mechanism to send the request to the
> Wicket side, where you can handle it by overriding the OnVueEvent method:
>
> public class GetStartedDemo extends WebPage {
>   public GetStartedDemo() {
> HashMap state = new HashMap<>();
> state.put("a", 4);
> state.put("b", "Hi");
> WicketVueApp vwa=new WicketVueApp("wva",
> new Model(state)) {
>   @Override
>   public void onVueEvent(AjaxRequestTarget target, Map Object> data) {
> state.put("b", state.get("b")+"!");
>   }
> };
> add(vwa);
>   }
> }
>
> The cb method will automatically send the current state of the Vue app back
> to the WicketVueApp component on server, which will use the data to update
> itself own state, before calling its onVueEvent method. This way you will
> have access to the latest state of the Vue app in the browser.
>
> In this method you can further modify the state, which will be sent back to
> the browser automatically to refresh the Vue app. Here, in this example,
> the "b" variable's value will have an exclamation mark added to it.
>
> Note that the AjaxRequestTarget one of the parameters, you can add other
> ajax Wicket components to the target to have them refreshed.
> <
> https://github.com/freemant2000/WicketVueApp#handling-vue-events-in-wicket
> >
>
> --
> Kent Tong
> IT author and consultant, child education coach
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: wicket 10 production ready plan

[Thies Edeling]

Great work, thanks Martin and the rest of the team!

Thies

On Wed, Jan 10, 2024, 07:29 Martin Grigorov  wrote:

> Hi,
>
> We work on the non-technical tasks (press release, announcement, etc.).
> IMO it should be released in the next few weeks!
>
> Martin
>
> On Wed, Jan 10, 2024 at 7:13 AM any sdk  wrote:
>
> > Hello wicket team,
> >
> > May I ask you when the wicket 10 production ready version will be
> released?
> >
> >
> >
> https://stackoverflow.com/questions/77790782/apache-wicket-10-production-release-date
> >
>

Re: How to load JS resources in an orderly fashion ?

[Dirk Forchel]

Hi,
you can use ResourceReference#getDependencies() to return a list of 
HeaderItems your resource depends on. This means, these resources are 
included before your resource link.

Just a hint. Greetings.
Dirk

Am 12/01/2024 um 08:59 schrieb sundar saba:

Hi all,
 I am using wicket bootstrap in my Application. Bootstrap
resources are loaded automatically through the wicket-bootstrap library in
the init method of the WebApplication class like this:

  BootstrapSettings settings = new BootstrapSettings();
  Bootstrap.install(this, settings);
  BootstrapSass.install(this);

  I am using an Abstract page to load other JS resources and all
the other pages extend this page. I want one of my JS resources to load
after the bootstrap JS resources are loaded . Kindly advice how to achieve
this

Re: wicket 10 production ready plan

[Martin Grigorov]

Hi,

We work on the non-technical tasks (press release, announcement, etc.).
IMO it should be released in the next few weeks!

Martin

On Wed, Jan 10, 2024 at 7:13 AM any sdk  wrote:

> Hello wicket team,
>
> May I ask you when the wicket 10 production ready version will be released?
>
>
> https://stackoverflow.com/questions/77790782/apache-wicket-10-production-release-date
>

Re: Wicket 10 and wicket bootstrap 7.0.2-SNAPSHOT error in modal

[Andrea Patricelli]

Thanks again for the hints Martin. The issue was caused by a not well 
formed html returned by the ajax response and browser cache did not help 
too much to check the solution.


Best regards,
Andrea

On 09/01/24 09:04, Martin Grigorov wrote:

Hi Andrea,

Please use Wicket-Bootstrap's issues or StackOverflow for questions about
Wicket-Bootstrap. Or users@wicket.apache.org.
dev@wicket.a.o is about the development of Apache Wicket itself.

On Mon, Jan 8, 2024 at 6:57 PM Andrea Patricelli <
andreapatrice...@apache.org> wrote:


Hi all,

I've just upgraded a project to wicket-bootstrap 7.0.2-SNAPSHOT and
wicket 10.0.0-M2.

I'm getting as clear as cryptic error with a multivalued panel when
clicking the "+" button to add a new text field panel.

Basically the multivalued panel goal is to manage multivalued attributes
of an object, especially a list of strings, nothing too much complex.

The error is:

POST

http://localhost:9090/syncope-console/wicket/bookmarkable/org.apache.syncope.client.console.pages.Realms?3-1.0-body-content-body-container-content-tabbedPanel-panel-searchResult-outerObjectsRepeater-0-outer-form-content-form-view-plainSchemas-tabs-0-body-content-schemas-8-panel-multiValueContainer-innerForm-content-view-0-panelPlus-add&selectedIndex=1
400 (Bad Request)
Wicket.Ajax.Call.failure: Error while parsing response: Bad Request

The error occurs only when I'm in a boostrap modal window by
wicket-bootstrap-core. The very same panel outside the modal is working
fine.

The multivalued panel class structure is quite complex, but the button
that fires such AJAX behavior is here [1].

Moreover I've also reproduced the same structure (simplified) with the
wicket sample archetype, but no error occurs and I'm not able to
reproduce the issue.

I'd like to ask not a solution, but at least the most effective way to
debug and to find some more hints about the error (logs, whatever) and
why the request is returning 400 without any apparent wrong input.

I'm working in dev mode and using the chrome dev console, but did not
find any clue to solve the issue.


I'd compare the request url and parameters when using the modal and without
it. Is there any noticeable difference ?
The next step is to set a breakpoint at HttpServletResponse#sendError() and
see who calls it and the reason why it is being called.




Thanks and regards,
Andrea

[1]

https://github.com/apache/syncope/blob/master/client/idrepo/common-ui/src/main/java/org/apache/syncope/client/ui/commons/markup/html/form/AbstractMultiPanel.java#L94-L125

--
Andrea Patricelli

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope



--
Andrea Patricelli

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope


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

Re: Reg: Content security policy

[sundar saba]

Hi all,           I open a ticket in jira regarding my issue 'Nounces should only use the base64 charset'.ASF JIRAissues.apache.org

Re: Reg: Content security policy

[sundar saba]

Hi all, 
Again thanks for your quick reply. Shortly I open a ticket in JIRA 
regarding this issue with sufficient details.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Reg: Content security policy

[Martin Grigorov]

Could you please open a ticket in JIRA with this information ?
Thanks!

On Thu, Jan 4, 2024 at 9:46 AM sundar saba 
wrote:

> Hi all,
>   Thanks for your quick reply. This is the info message get from
> Kali Linux
>
> DirectiveValue
> script-src 'nonce-QmsK_uBjkJ84B3bGJIX'
> style-src   'nonce-QmsK_uBjkJ84B3bGJIX'
>
>

Re: Reg: Content security policy

[sundar saba]

Hi all, 
  Thanks for your quick reply. This is the info message get from Kali 
Linux 

DirectiveValue 
script-src 'nonce-QmsK_uBjkJ84B3bGJIX'   
style-src   'nonce-QmsK_uBjkJ84B3bGJIX'   


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

Re: Reg: Content security policy

[Martin Grigorov]

Hi,

https://github.com/apache/wicket/blob/e9461b0d115a7dbf4992596823521f6e038817d9/wicket-core/src/main/java/org/apache/wicket/core/random/ISecureRandomSupplier.java#L60

This is the relevant code. It looks OK to me.
Attachments are not allowed in the mailing list. Could you please
copy/paste a nonce instance which is non-base64 according to Kali Linux ?

Also please check that you don't use a custom NonceCreator -
https://github.com/apache/wicket/blob/e9461b0d115a7dbf4992596823521f6e038817d9/wicket-core/src/main/java/org/apache/wicket/csp/ContentSecurityPolicySettings.java#L102

Martin

On Thu, Jan 4, 2024 at 4:51 AM sundar saba 
wrote:

> Hi all,
>   I  applied a strict content security policy to my application
> using wicket after I tested my application using Kali Linux to check for
> vulnerabilities. The tool provides the report with an info message "Nonces
> should only use the base64 charset" regarding the info message needed to
> configure any properties in CSP. I attached the report screenshot . Can you
> all please give your suggestions.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org

Re: RangeValidator and BigDecimal

[Eric Hamel]

Sven,

Thanks I hit send by mistake. It became clear that it was a BigDecimal
instantiation issue and nothing to do with the RangeValidator.

Thanks all.

On Wed, Dec 20, 2023 at 9:25 AM Sven Meier  wrote:

> Hi Eric,
>
> you can read in the javadoc, why your first solution is 'unpredictable':
>
>
> https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/math/BigDecimal.html#%3Cinit%3E(double)
>
> Sven
>
> On 20.12.23 15:18, Eric Hamel wrote:
> > Hi Bas,
> >
> > Thanks for the response.
> >
> > I discovered the NumberTextField had its own RangeValidator 2 seconds
> after posting. With that said, I’m getting the same issue when using it.
> >
> > To be clear, I’m not getting any Exceptions, everything seems to work
> fine, but the form validation fails if the user types in 0.01.
> >
> >
> > Form form = new Form<>(“form”, getModel());
> > add(form);
> >
> > NumberTextField testField = new
> NumberTextField(“testField”, new
> PropertyModel(form.getModel(), “testProp”));
> > form.add(testField);
> >
> >
> > I’ve been digging and I found the oddity:
> >
> > If I set the min value as follows:
> >
> > testField.setMinimum(new BigDecimal(0.00));
> >
> > When the user enters 0.01, the following feedback message is showed:
> >
> > The value of ’testField’ must be between 0.01 and 999,999.99.
> >
> > However, if I set the min value with:
> >
> > testField.setMinimum(BigDecimal.valueOf(0.00));
> >
> > The user can enter 0.01 and NO feedback message is showed.
> >
> >
> >
> > -
> > Eric H.
> >
> >
> >
> >
> >
> >> On Dec 20, 2023, at 8:48 AM, Bas Gooren  wrote:
> >>
> >> Hi Eric,
> >>
> >> First off: according to the source of NumberTextField, it automatically
> adds a RangeValidator (see NumberTextField#onConfigure). So you shouldn’t
> need to add the RangeValidator yourself.
> >>
> >> Regarding your problem: what kind of error messages are you getting?
> >>
> >> The range validator (or more specifically: the AbstractRangeValidator
> class) handles the comparison between min, max and actual values using
> compareTo. So there should not be any issues with rounding.
> >>
> >> Please share the code you use to initialize the relevant field, perhaps
> we can spot a mistake.
> >>
> >> Met vriendelijke groet,
> >> Kind regards,
> >>
> >> Bas Gooren
> >>
> >> Op 20 december 2023 bij 14:38:53, Eric Hamel (eric.ha...@albanyitg.com
> ) schreef:
> >>
> >>> Good morning,
> >>>
> >>> We encountered an issue this morning with our use of
> RangeValidator.
> >>>
> >>> The customer requested a validation for amounts between 0.01 and
> 999,999.00.
> >>>
> >>> We have a NumberTextField to which we added the
> RangeValidator. If the user enters 0.01 the validation fails.
> >>>
> >>> If I set the min value to 0.009 I can get it to work but the error
> messages are off.
> >>>
> >>> I’m wondering if it’s a rounding or scale issue but I cannot figure
> out how to make the RangeValidator work.
> >>>
> >>> Anyone have any insight on this ?
> >>>
> >>> Thank you.
> >>> Eric H.
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org  users-unsubscr...@wicket.apache.org>
> >>> For additional commands, e-mail: users-h...@wicket.apache.org  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: RangeValidator and BigDecimal

[Bas Gooren]

Hi all,

Yeah, that was easy to spot: BigDecimal is only accurate when provided with
a string or fixed input (e.g. integer or long).
Doubles and floats are inherently inaccurate (as they are non-exact values).

So if you change your code to ...

testField.setMinimum(new BigDecimal(“0.01"));

… it will work correctly.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 20 december 2023 bij 15:25:23, Sven Meier (s...@meiers.net) schreef:

Hi Eric,

you can read in the javadoc, why your first solution is 'unpredictable':

https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/math/BigDecimal.html#%3Cinit%3E(double)

Sven

On 20.12.23 15:18, Eric Hamel wrote:
> Hi Bas,
>
> Thanks for the response.
>
> I discovered the NumberTextField had its own RangeValidator 2 seconds
after posting. With that said, I’m getting the same issue when using it.
>
> To be clear, I’m not getting any Exceptions, everything seems to work
fine, but the form validation fails if the user types in 0.01.
>
>
> Form form = new Form<>(“form”, getModel());
> add(form);
>
> NumberTextField testField = new
NumberTextField(“testField”, new
PropertyModel(form.getModel(), “testProp”));
> form.add(testField);
>
>
> I’ve been digging and I found the oddity:
>
> If I set the min value as follows:
>
> testField.setMinimum(new BigDecimal(0.00));
>
> When the user enters 0.01, the following feedback message is showed:
>
> The value of ’testField’ must be between 0.01 and 999,999.99.
>
> However, if I set the min value with:
>
> testField.setMinimum(BigDecimal.valueOf(0.00));
>
> The user can enter 0.01 and NO feedback message is showed.
>
>
>
> -
> Eric H.
>
>
>
>
>
>> On Dec 20, 2023, at 8:48 AM, Bas Gooren  wrote:
>>
>> Hi Eric,
>>
>> First off: according to the source of NumberTextField, it automatically
adds a RangeValidator (see NumberTextField#onConfigure). So you shouldn’t
need to add the RangeValidator yourself.
>>
>> Regarding your problem: what kind of error messages are you getting?
>>
>> The range validator (or more specifically: the AbstractRangeValidator
class) handles the comparison between min, max and actual values using
compareTo. So there should not be any issues with rounding.
>>
>> Please share the code you use to initialize the relevant field, perhaps
we can spot a mistake.
>>
>> Met vriendelijke groet,
>> Kind regards,
>>
>> Bas Gooren
>>
>> Op 20 december 2023 bij 14:38:53, Eric Hamel (eric.ha...@albanyitg.com
) schreef:
>>
>>> Good morning,
>>>
>>> We encountered an issue this morning with our use of
RangeValidator.
>>>
>>> The customer requested a validation for amounts between 0.01 and
999,999.00.
>>>
>>> We have a NumberTextField to which we added the
RangeValidator. If the user enters 0.01 the validation fails.
>>>
>>> If I set the min value to 0.009 I can get it to work but the error
messages are off.
>>>
>>> I’m wondering if it’s a rounding or scale issue but I cannot figure out
how to make the RangeValidator work.
>>>
>>> Anyone have any insight on this ?
>>>
>>> Thank you.
>>> Eric H.
>>>
>>>
>>> -
>>> 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: RangeValidator and BigDecimal

[Sven Meier]

Hi Eric,

you can read in the javadoc, why your first solution is 'unpredictable':

https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/math/BigDecimal.html#%3Cinit%3E(double)

Sven

On 20.12.23 15:18, Eric Hamel wrote:

Hi Bas,

Thanks for the response.

I discovered the NumberTextField had its own RangeValidator 2 seconds after 
posting. With that said, I’m getting the same issue when using it.

To be clear, I’m not getting any Exceptions, everything seems to work fine, but 
the form validation fails if the user types in 0.01.


Form form = new Form<>(“form”, getModel());
add(form);

NumberTextField testField = new NumberTextField(“testField”, 
new PropertyModel(form.getModel(), “testProp”));
form.add(testField);


I’ve been digging and I found the oddity:

If I set the min value as follows:

testField.setMinimum(new BigDecimal(0.00));

When the user enters 0.01, the following feedback message is showed:

The value of ’testField’ must be between 0.01 and 999,999.99.

However, if I set the min value with:

testField.setMinimum(BigDecimal.valueOf(0.00));

The user can enter 0.01 and NO feedback message is showed.



-
Eric H.






On Dec 20, 2023, at 8:48 AM, Bas Gooren  wrote:

Hi Eric,

First off: according to the source of NumberTextField, it automatically adds a 
RangeValidator (see NumberTextField#onConfigure). So you shouldn’t need to add 
the RangeValidator yourself.

Regarding your problem: what kind of error messages are you getting?

The range validator (or more specifically: the AbstractRangeValidator class) 
handles the comparison between min, max and actual values using compareTo. So 
there should not be any issues with rounding.

Please share the code you use to initialize the relevant field, perhaps we can 
spot a mistake.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 20 december 2023 bij 14:38:53, Eric Hamel (eric.ha...@albanyitg.com 
) schreef:


Good morning,

We encountered an issue this morning with our use of RangeValidator.

The customer requested a validation for amounts between 0.01 and 999,999.00.

We have a NumberTextField to which we added the RangeValidator. If 
the user enters 0.01 the validation fails.

If I set the min value to 0.009 I can get it to work but the error messages are 
off.

I’m wondering if it’s a rounding or scale issue but I cannot figure out how to 
make the RangeValidator work.

Anyone have any insight on this ?

Thank you.
Eric H.


-
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: RangeValidator and BigDecimal

[Eric Hamel]

Hi Bas,

Thanks for the response.

I discovered the NumberTextField had its own RangeValidator 2 seconds after 
posting. With that said, I’m getting the same issue when using it.

To be clear, I’m not getting any Exceptions, everything seems to work fine, but 
the form validation fails if the user types in 0.01.


Form form = new Form<>(“form”, getModel());
add(form);

NumberTextField testField = new 
NumberTextField(“testField”, new 
PropertyModel(form.getModel(), “testProp”));
form.add(testField);


I’ve been digging and I found the oddity:

If I set the min value as follows:

testField.setMinimum(new BigDecimal(0.00));

When the user enters 0.01, the following feedback message is showed:

The value of ’testField’ must be between 0.01 and 999,999.99.

However, if I set the min value with:

testField.setMinimum(BigDecimal.valueOf(0.00));

The user can enter 0.01 and NO feedback message is showed.



-
Eric H.





> On Dec 20, 2023, at 8:48 AM, Bas Gooren  wrote:
> 
> Hi Eric,
> 
> First off: according to the source of NumberTextField, it automatically adds 
> a RangeValidator (see NumberTextField#onConfigure). So you shouldn’t need to 
> add the RangeValidator yourself.
> 
> Regarding your problem: what kind of error messages are you getting?
> 
> The range validator (or more specifically: the AbstractRangeValidator class) 
> handles the comparison between min, max and actual values using compareTo. So 
> there should not be any issues with rounding.
> 
> Please share the code you use to initialize the relevant field, perhaps we 
> can spot a mistake.
> 
> Met vriendelijke groet,
> Kind regards,
> 
> Bas Gooren
> 
> Op 20 december 2023 bij 14:38:53, Eric Hamel (eric.ha...@albanyitg.com 
> ) schreef:
> 
>> Good morning,
>> 
>> We encountered an issue this morning with our use of 
>> RangeValidator. 
>> 
>> The customer requested a validation for amounts between 0.01 and 999,999.00. 
>> 
>> We have a NumberTextField to which we added the RangeValidator. 
>> If the user enters 0.01 the validation fails. 
>> 
>> If I set the min value to 0.009 I can get it to work but the error messages 
>> are off. 
>> 
>> I’m wondering if it’s a rounding or scale issue but I cannot figure out how 
>> to make the RangeValidator work. 
>> 
>> Anyone have any insight on this ?
>> 
>> Thank you. 
>> Eric H. 
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org 
>> 
>> For additional commands, e-mail: users-h...@wicket.apache.org 
>> 

Re: RangeValidator and BigDecimal

[Bas Gooren]

Hi Eric,

First off: according to the source of NumberTextField, it automatically
adds a RangeValidator (see NumberTextField#onConfigure). So you shouldn’t
need to add the RangeValidator yourself.

Regarding your problem: what kind of error messages are you getting?

The range validator (or more specifically: the AbstractRangeValidator
class) handles the comparison between min, max and actual values using
compareTo. So there should not be any issues with rounding.

Please share the code you use to initialize the relevant field, perhaps we
can spot a mistake.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 20 december 2023 bij 14:38:53, Eric Hamel (eric.ha...@albanyitg.com)
schreef:

Good morning,

We encountered an issue this morning with our use of
RangeValidator.

The customer requested a validation for amounts between 0.01 and
999,999.00.

We have a NumberTextField to which we added the RangeValidator.
If the user enters 0.01 the validation fails.

If I set the min value to 0.009 I can get it to work but the error messages
are off.

I’m wondering if it’s a rounding or scale issue but I cannot figure out how
to make the RangeValidator work.

Anyone have any insight on this ?

Thank you.
Eric H.


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

Re: wicket 10

[Martin Grigorov]

Please check
https://lists.apache.org/thread/5shcr43foncvt237wmp1fr8lponx4z9h

On Fri, Dec 15, 2023 at 10:53 AM xuwei zhang 
wrote:

> Hello Wicket Team,
>
>
> Do we have any plans for the release date of the Wicket 10 stable version?
>
>
> BR.
>

Re: problem using DropDownChoice

[Bas Gooren]

Hi!

Normally this should work just fine:

otReasonDropDown = new DropDownChoice("otReason", new PropertyModel
(commentAndOtReason, "otReasonText"), ldm2);
otReasonDropDown.setNullValid(false);

So my guess is that either commentAndOtReason is null (unlikely, as that
would throw an NPE in the other code you provided)
or commentAndOtReason.otReasonText is null.

The PropertyModel (and any model for that matter) is a simple container to
pull a value out for display/use and push a value back (e.g. on form
submit).

If you put a breakpoint on the line where you construct the DropDownChoice,
you can inspect the variable commentAndOtReason to see what is inside.

Should that not be the issue, and the
variable commentAndOtReason.otReasonText contains text, then it means that
between construction and render of your page, the commentAndOtReason is
updated and/or its contents are updated.

If you still cannot figure it out, please provide a quickstart that
demonstrates your issue. That will help others (like me) to spot the
underlying issue quickly.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 14 december 2023 bij 19:27:30, Nelligan, Steven M (snell...@illinois.edu)
schreef:


Help, I am new to Wicket...and have taken over a project with wicket
version 1.4.18.

I need to add another DropDownChoice in my application.
I was able to create the add logic, but the change logic is not working as
expected.
I've been working on this for a couple of weeks, and still could not get it
working.
Following is a snip of code causing the problem:
otReasonDropDown = new DropDownChoice("otReason", new PropertyModel
(commentAndOtReason, "otReasonText"), ldm2);
otReasonDropDown.setNullValid(false);
if (commentAndOtReason.getOtReasonText() != null) {
//
otReasonDropDown.setDefaultModelObject(commentAndOtReason.getOtReasonText()
+ "");
otReasonDropDown.setDefaultModelObject(commentAndOtReason.getOtReasonText()
+ "");
}
String s3 = ((String) otReasonDropDown.getModelObject());
String s31 = ((String)otReasonDropDown.getDefaultModelObjectAsString());
int i3 = 1; //debugging
timeCardForm.add(otReasonDropDown);

The variable commentAndOtReason.otReasonText contains the string I want the
dropdown list to show as a default.

But the dropdown list is not showing any default, but rather an empty
value.
If I select the dropdownlist, it shows the select list, including what I
want as a default value.

How do I setup DropDownChoice to have the value in
commentAndOtReason.otReasonText show as the current value(default value).

Thanks,
Steven M Nelligan
SENIOR SOFTWARE DEVELOPER

Re: Aw: Re: Odd behaviour with StatelessForm and onInitialize()

[Bas Gooren]

Hi Daniel,

I did some debugging, and found out why this is not working as expected.

When you add your components to the page in onInitialize(), the following
happens:

Wicket runs a ListenerRequestHandler for the form submit.
That handler tries to find the form component, and does not find it
(PageAndComponentProvider#getComponent) and then initializes the page +
calls beforeRender() on the page.
Through beforeRender, the components in the page are configured
(onConfigure() is called).
This is where your behavior hides the label.
After the form submit is processed, wicket schedules a
RenderPageRequestHandler (in ListenerRequestHandler#internalInvoke).
Normally I’d expect the page to be configured & rendered again at that
point, but because the label was already configured before, it stays hidden.

My first idea was to call Page#configure() in your Form#onSubmit method,
but that didn’t do anything, because configure ensures the logic only runs
once per render (by setting some flags).

My second idea was to detach the page, which did the trick in your example.
Detaching the page forces a re-render after the form submit.

More specifically:

Form form = new StatelessForm<>( "form" )
{
@Override
protected String getMethod()
{
return "GET";
}

@Override
protected void onSubmit()
{
super.onSubmit();

System.out.println( "Form submit" );

getPage().detach();
}
};

Conclusion: try if that works for you in your actual code.
There is differences in how things are handled by wicket depending on where
you add (form) components to your page (in ctor or in onInitialize).

Perhaps one of the core devs can comment on if what I found to happen is
desired behavior (components not configured after form submit in stateless
page, when components are added in onInitialize).

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 30 november 2023 bij 16:45:48, ihmehlm...@gmx.de (ihmehlm...@gmx.de)
schreef:

Hello!

I now uploaded the whole quickstart. It's basicly the same as in my initial
post though just with some added debugging code, so not sure it helps more.
https://drive.google.com/file/d/1UWm3eEf4ddzRy0QeI0DdhsPB7bT2gRcm/view?usp=sharing

The page is the same for both cases and it is indeed supposed to be
stateless.
Simply (un)commenting the initComponents() method in either the page's
constructur or the onInitialize() method changes how the page behaves.
The goal in this quickstart is, that the entered text gets displayed, which
right now doesn't seem to work, if I add my components in the
onInitialize() method.

Adding the components in the constructor prints the following when
submitting the form:

--Constructor--
init components
before super.onInitialize
after super.onInitialize
<< get
>> set <- Setter called before the Behavior
calling get from Behavior
<< get
Setting visibility to true
<< get
<< get

Here you can see, that the setter of the Model is call before the Behavior
is evaluated.
With a value being in the model, the Behavior sets the visibility of the
label to true.


Adding the components in the onInitialize() method prints the following
when submitting the form:

--Constructor--
before super.onInitialize
after super.onInitialize
init components
calling get from Behavior
<< get
Setting visibility to false
<< get
>> set <- Setter called after the Behavior
<< get

Here though you can see, that the setter of the Model is called after the
Behavior is evaluated.
So at the time of evaluation there is no value in the the Model and the
Behavior sets the visibility of the label to false.

If there is anything else I can provide I'll happily do so.

Daniel


Gesendet: Mittwoch, 29. November 2023 um 07:03 Uhr
Von: "Bas Gooren" 
An: users@wicket.apache.org, ihmehlm...@gmx.de
Betreff: Re: Odd behaviour with StatelessForm and onInitialize()
Hi!

Can you share some code? (e.g. a quickstart which reproduces your issue)

It sounds to me like in the one case you are dealing with a stateless page,
and the other a stateful page.

In general, with stateless pages, everything is initialized on every render
/ submit, because there is no page instance (since the page is stateless).
If in some conditions you see that your behavior is run before the submit,
it sounds like you’re dealing with a stateless page. If in other conditions
the behavior is only run on initial page render and after the submit, it
sounds like you’re dealing with a stateful page.

But this is just me guessing without looking at your code.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 23 november 2023 bij 16:09:53, ihmehlm...@gmx.de (ihmehlm...@gmx.de)
schreef:

Hello,
upon working with StatelessForms for the first time I stumbled up an odd
behav

Aw: Re: Odd behaviour with StatelessForm and onInitialize()

[ihmehlmenn]

Hello!

I now uploaded the whole quickstart. It's basicly the same as in my initial 
post though just with some added debugging code, so not sure it helps more.
https://drive.google.com/file/d/1UWm3eEf4ddzRy0QeI0DdhsPB7bT2gRcm/view?usp=sharing

The page is the same for both cases and it is indeed supposed to be stateless.
Simply (un)commenting the initComponents() method in either the page's 
constructur or the onInitialize() method changes how the page behaves.
The goal in this quickstart is, that the entered text gets displayed, which 
right now doesn't seem to work, if I add my components in the onInitialize() 
method.

Adding the components in the constructor prints the following when submitting 
the form:

--Constructor--
init components
before super.onInitialize
after super.onInitialize
<< get
>> set<- Setter called before the Behavior
calling get from Behavior
<< get
Setting visibility to true
<< get
<< get

Here you can see, that the setter of the Model is call before the Behavior is 
evaluated.
With a value being in the model, the Behavior sets the visibility of the label 
to true.


Adding the components in the onInitialize() method prints the following when 
submitting the form:

--Constructor--
before super.onInitialize
after super.onInitialize
init components
calling get from Behavior
<< get
Setting visibility to false
<< get
>> set<- Setter called after the Behavior
<< get

Here though you can see, that the setter of the Model is called after the 
Behavior is evaluated.
So at the time of evaluation there is no value in the the Model and the 
Behavior sets the visibility of the label to false.

If there is anything else I can provide I'll happily do so.

Daniel


Gesendet: Mittwoch, 29. November 2023 um 07:03 Uhr
Von: "Bas Gooren" 
An: users@wicket.apache.org, ihmehlm...@gmx.de
Betreff: Re: Odd behaviour with StatelessForm and onInitialize()
Hi!

Can you share some code? (e.g. a quickstart which reproduces your issue)

It sounds to me like in the one case you are dealing with a stateless page,
and the other a stateful page.

In general, with stateless pages, everything is initialized on every render
/ submit, because there is no page instance (since the page is stateless).
If in some conditions you see that your behavior is run before the submit,
it sounds like you’re dealing with a stateless page. If in other conditions
the behavior is only run on initial page render and after the submit, it
sounds like you’re dealing with a stateful page.

But this is just me guessing without looking at your code.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 23 november 2023 bij 16:09:53, ihmehlm...@gmx.de (ihmehlm...@gmx.de)
schreef:

Hello,
upon working with StatelessForms for the first time I stumbled up an odd
behavior in regards to when the corresponding models are updated.

Following setup:

The base for this is a wicket quickstart 9.15.0. I modified the two
HomePage files, which can be found here:
https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6

In this I have a Page with a StatelessForm with a single TextField and a
Label. The TextField and Label share a single String-Model. The Label has a
Behavior which sets the visibility of the attached component to false in
the configure-phase if the String-Model is empty.
Here this is needed to hide the whole HTML-tag instead of rendering an
empty li-tag. In my actual application this applies to much bigger and more
complex panels and lists which need to be hidden/shown when certain form
values are set/not set.


Now the to me odd behavior:

If I initialise all components in the constructor of the page, everything
works as expected.
The request of the form submit gets processed, the model updated and then
afterwards the page gets rendered among which also the Behaviour is run to
set the visibility of the label.
So the visibility is decided on the just submitted form value.

Now if I initialise all components in the onInitialize() method, which by
my understanding is supposed to work like the constructor, the order of
execution seems wrong.
First, my Behaviour is run to set the visibility. Then the request of the
form submit gets processed, the model updated and the page rendered.
So here now the visibility is suddenly decided on the old value, which in
my case initially is an empty Model, so my Label is always hidden.

It's not a matter of using GET or POST and only seems to happen with
StatelessForm. Using a normal statefull Form is working just fine.

Is this a bug or an expected behaviour? I couldn't find anything about this
in the description of the StatelessForm about this.
I am exclusivly using the onInitialize() method for constructing all my
pages, so before having to change several hundred pages to using the
constructor, I rather ask first if it's maybe something that can be fixed.

Regards
Daniel

---

Re: Odd behaviour with StatelessForm and onInitialize()

[Bas Gooren]

Hi!

Can you share some code? (e.g. a quickstart which reproduces your issue)

It sounds to me like in the one case you are dealing with a stateless page,
and the other a stateful page.

In general, with stateless pages, everything is initialized on every render
/ submit, because there is no page instance (since the page is stateless).
If in some conditions you see that your behavior is run before the submit,
it sounds like you’re dealing with a stateless page. If in other conditions
the behavior is only run on initial page render and after the submit, it
sounds like you’re dealing with a stateful page.

But this is just me guessing without looking at your code.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 23 november 2023 bij 16:09:53, ihmehlm...@gmx.de (ihmehlm...@gmx.de)
schreef:

Hello,
upon working with StatelessForms for the first time I stumbled up an odd
behavior in regards to when the corresponding models are updated.

Following setup:

The base for this is a wicket quickstart 9.15.0. I modified the two
HomePage files, which can be found here:
https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6

In this I have a Page with a StatelessForm with a single TextField and a
Label. The TextField and Label share a single String-Model. The Label has a
Behavior which sets the visibility of the attached component to false in
the configure-phase if the String-Model is empty.
Here this is needed to hide the whole HTML-tag instead of rendering an
empty li-tag. In my actual application this applies to much bigger and more
complex panels and lists which need to be hidden/shown when certain form
values are set/not set.


Now the to me odd behavior:

If I initialise all components in the constructor of the page, everything
works as expected.
The request of the form submit gets processed, the model updated and then
afterwards the page gets rendered among which also the Behaviour is run to
set the visibility of the label.
So the visibility is decided on the just submitted form value.

Now if I initialise all components in the onInitialize() method, which by
my understanding is supposed to work like the constructor, the order of
execution seems wrong.
First, my Behaviour is run to set the visibility. Then the request of the
form submit gets processed, the model updated and the page rendered.
So here now the visibility is suddenly decided on the old value, which in
my case initially is an empty Model, so my Label is always hidden.

It's not a matter of using GET or POST and only seems to happen with
StatelessForm. Using a normal statefull Form is working just fine.

Is this a bug or an expected behaviour? I couldn't find anything about this
in the description of the StatelessForm about this.
I am exclusivly using the onInitialize() method for constructing all my
pages, so before having to change several hundred pages to using the
constructor, I rather ask first if it's maybe something that can be fixed.

Regards
Daniel

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

Aw: Re: Odd behaviour with StatelessForm and onInitialize()

[ihmehlmenn]

Thanks for the idea, but there doesn't seem to be any difference between adding 
the components before or after calling super.onInitialize()
 

Gesendet: Freitag, 24. November 2023 um 13:56 Uhr
Von: "Martin Grigorov" 
An: users@wicket.apache.org
Betreff: Re: Odd behaviour with StatelessForm and onInitialize()
Hi,

I don't have time to debug the problem right now but could you try
something: swap these two lines -
https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6#file-homepage-java-L25-L26
I.e. first add() the components to the page and then call
super.onInitialize()

On Thu, Nov 23, 2023 at 5:09 PM  wrote:

> Hello,
> upon working with StatelessForms for the first time I stumbled up an odd
> behavior in regards to when the corresponding models are updated.
>
> Following setup:
>
> The base for this is a wicket quickstart 9.15.0. I modified the two
> HomePage files, which can be found here:
> https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6[https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6]
>
> In this I have a Page with a StatelessForm with a single TextField and a
> Label. The TextField and Label share a single String-Model. The Label has a
> Behavior which sets the visibility of the attached component to false in
> the configure-phase if the String-Model is empty.
> Here this is needed to hide the whole HTML-tag instead of rendering an
> empty li-tag. In my actual application this applies to much bigger and more
> complex panels and lists which need to be hidden/shown when certain form
> values are set/not set.
>
>
> Now the to me odd behavior:
>
> If I initialise all components in the constructor of the page, everything
> works as expected.
> The request of the form submit gets processed, the model updated and then
> afterwards the page gets rendered among which also the Behaviour is run to
> set the visibility of the label.
> So the visibility is decided on the just submitted form value.
>
> Now if I initialise all components in the onInitialize() method, which by
> my understanding is supposed to work like the constructor, the order of
> execution seems wrong.
> First, my Behaviour is run to set the visibility. Then the request of the
> form submit gets processed, the model updated and the page rendered.
> So here now the visibility is suddenly decided on the old value, which in
> my case initially is an empty Model, so my Label is always hidden.
>
> It's not a matter of using GET or POST and only seems to happen with
> StatelessForm. Using a normal statefull Form is working just fine.
>
> Is this a bug or an expected behaviour? I couldn't find anything about
> this in the description of the StatelessForm about this.
> I am exclusivly using the onInitialize() method for constructing all my
> pages, so before having to change several hundred pages to using the
> constructor, I rather ask first if it's maybe something that can be fixed.
>
> Regards
> Daniel
>
> -
> 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: [ANNOUNCE] WicketStuff 9.16.0 Released

[Andrea Del Bene]

Thank you Maxim!

On Tue, Nov 28, 2023 at 7:55 AM Maxim Solodovnik  wrote:

> WicketStuff core 9.16.0 based on Apache Wicket 9.16.0 is released
> and soon will be available at Maven Central!
>
> Maxim Solodovnik (5):
>   Switching to the next development version
>   BCprov is updated; Tests are fixed
>   Jetty is updated
>   Dependencies are updated
>   wicketstuff-core-9.16.0 release build is successful
>
> The WicketStuff team
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Andrea Del Bene.
Apache Wicket committer.

Re: [ANNOUNCE] Apache Wicket 9.16.0 released

[mail]

I want to join in saying thank you! You did an awesome job with the changes in 
the latest versions. I had the chance to start a new project with strict CSP 
enforced and it has never been easier to write web apps with secure defaults. 
Danke from Germany ;)

> On 27. Nov 2023, at 16:45, Ernesto Reinaldo Barreiro  
> wrote:
> 
> Many thanks!
> 
> On Sun, Nov 26, 2023 at 2:27 PM Andrea Del Bene  wrote:
> 
>> The Apache Wicket PMC is proud to announce Apache Wicket 9.16.0!
>> 
>> Apache Wicket is an open source Java component oriented web application
>> framework that powers thousands of web applications and web sites for
>> governments, stores, universities, cities, banks, email providers, and
>> more. You can find more about Apache Wicket at https://wicket.apache.org
>> 
>> This release marks another minor release of Wicket 9. We
>> use semantic versioning for the development of Wicket, and as such no
>> API breaks are present in this release compared to 9.0.0.
>> 
>> Using this release
>> --
>> 
>> With Apache Maven update your dependency to (and don't forget to
>> update any other dependencies on Wicket projects to the same version):
>> 
>> 
>> org.apache.wicket
>> wicket-core
>> 9.16.0
>> 
>> 
>> Or download and build the distribution yourself, or use our
>> convenience binary package you can find here:
>> 
>>  * Download: http://wicket.apache.org/start/wicket-9.x.html#manually
>> 
>> Upgrading from earlier versions
>> ---
>> 
>> If you upgrade from 9.y.z this release is a drop in replacement. If
>> you come from a version prior to 9.0.0, please read our Wicket 9
>> migration guide found at
>> 
>>  * http://s.apache.org/wicket9migrate
>> 
>> Have fun!
>> 
>> — The Wicket team
>> 
>> 
>> 
>> 
>> CHANGELOG for 9.16.0:
>> 
>> ** Bug
>> 
>> * [WICKET-7056] - HttpSessionStore#getAttribute called on
>> invalidated session
>> * [WICKET-7074] - [AJAX] malformed XML is produced if an error is
>> produced during AJAX rendering and a redirect is issued
>> * [WICKET-7076] - JavaScriptReferenceType newly created is not
>> serializable
>> * [WICKET-7081] - Open packages to expose resources to other modules
>> 
>> ** Improvement
>> 
>> * [WICKET-7078] - CSP: inline JS in Choices and Selection of Palette
>> * [WICKET-7080] - [Events] make default events delivery machinery
>> pluggable and roll usable annotation based one
>> * [WICKET-7082] - Easier to work with polymorphic values inside IModel
>> * [WICKET-7083] - Trigger client side validation when using
>> SubmitLinks
>> 
>> ** Task
>> 
>> * [WICKET-7073] - Update JQuery to 3.7.1
>> 
>> 
> 
> -- 
> Regards - Ernesto Reinaldo Barreiro


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

Re: [ANNOUNCE] Apache Wicket 9.16.0 released

[Ernesto Reinaldo Barreiro]

Many thanks!

On Sun, Nov 26, 2023 at 2:27 PM Andrea Del Bene  wrote:

> The Apache Wicket PMC is proud to announce Apache Wicket 9.16.0!
>
> Apache Wicket is an open source Java component oriented web application
> framework that powers thousands of web applications and web sites for
> governments, stores, universities, cities, banks, email providers, and
> more. You can find more about Apache Wicket at https://wicket.apache.org
>
> This release marks another minor release of Wicket 9. We
> use semantic versioning for the development of Wicket, and as such no
> API breaks are present in this release compared to 9.0.0.
>
> Using this release
> --
>
> With Apache Maven update your dependency to (and don't forget to
> update any other dependencies on Wicket projects to the same version):
>
> 
>  org.apache.wicket
>  wicket-core
>  9.16.0
> 
>
> Or download and build the distribution yourself, or use our
> convenience binary package you can find here:
>
>   * Download: http://wicket.apache.org/start/wicket-9.x.html#manually
>
> Upgrading from earlier versions
> ---
>
> If you upgrade from 9.y.z this release is a drop in replacement. If
> you come from a version prior to 9.0.0, please read our Wicket 9
> migration guide found at
>
>   * http://s.apache.org/wicket9migrate
>
> Have fun!
>
> — The Wicket team
>
>
> 
>
>  CHANGELOG for 9.16.0:
>
> ** Bug
>
>  * [WICKET-7056] - HttpSessionStore#getAttribute called on
> invalidated session
>  * [WICKET-7074] - [AJAX] malformed XML is produced if an error is
> produced during AJAX rendering and a redirect is issued
>  * [WICKET-7076] - JavaScriptReferenceType newly created is not
> serializable
>  * [WICKET-7081] - Open packages to expose resources to other modules
>
> ** Improvement
>
>  * [WICKET-7078] - CSP: inline JS in Choices and Selection of Palette
>  * [WICKET-7080] - [Events] make default events delivery machinery
> pluggable and roll usable annotation based one
>  * [WICKET-7082] - Easier to work with polymorphic values inside IModel
>  * [WICKET-7083] - Trigger client side validation when using
> SubmitLinks
>
> ** Task
>
>  * [WICKET-7073] - Update JQuery to 3.7.1
>
>

-- 
Regards - Ernesto Reinaldo Barreiro

Re: Odd behaviour with StatelessForm and onInitialize()

[Martin Grigorov]

Hi,

I don't have time to debug the problem right now but could you try
something: swap these two lines -
https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6#file-homepage-java-L25-L26
I.e. first add() the components to the page and then call
super.onInitialize()

On Thu, Nov 23, 2023 at 5:09 PM  wrote:

> Hello,
> upon working with StatelessForms for the first time I stumbled up an odd
> behavior in regards to when the corresponding models are updated.
>
> Following setup:
>
> The base for this is a wicket quickstart 9.15.0. I modified the two
> HomePage files, which can be found here:
> https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6
>
> In this I have a Page with a StatelessForm with a single TextField and a
> Label. The TextField and Label share a single String-Model. The Label has a
> Behavior which sets the visibility of the attached component to false in
> the configure-phase if the String-Model is empty.
> Here this is needed to hide the whole HTML-tag instead of rendering an
> empty li-tag. In my actual application this applies to much bigger and more
> complex panels and lists which need to be hidden/shown when certain form
> values are set/not set.
>
>
> Now the to me odd behavior:
>
> If I initialise all components in the constructor of the page, everything
> works as expected.
> The request of the form submit gets processed, the model updated and then
> afterwards the page gets rendered among which also the Behaviour is run to
> set the visibility of the label.
> So the visibility is decided on the just submitted form value.
>
> Now if I initialise all components in the onInitialize() method, which by
> my understanding is supposed to work like the constructor, the order of
> execution seems wrong.
> First, my Behaviour is run to set the visibility. Then the request of the
> form submit gets processed, the model updated and the page rendered.
> So here now the visibility is suddenly decided on the old value, which in
> my case initially is an empty Model, so my Label is always hidden.
>
> It's not a matter of using GET or POST and only seems to happen with
> StatelessForm. Using a normal statefull Form is working just fine.
>
> Is this a bug or an expected behaviour? I couldn't find anything about
> this in the description of the StatelessForm about this.
> I am exclusivly using the onInitialize() method for constructing all my
> pages, so before having to change several hundred pages to using the
> constructor, I rather ask first if it's maybe something that can be fixed.
>
> Regards
> Daniel
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: ModalWindow to ModalDialog // closedCallback

[Johannes Renoth]

Hi Korbinian,

you can overwrite ModalDialog#close and do something like this.

public class MyModalDialog extends ModalDialog {

private SerializableConsumer closeWindowCallback;
...
public void 
setCloseWindowCallback(SerializableConsumer 
closeWindowCallback) { this.closeWindowCallback = closeWindowCallback; }
@Override public ModalDialog close(AjaxRequestTarget target) { 
super.close(target); if (closeWindowCallback != null) { 
closeWindowCallback.accept(target); } return this; }

...
}
I also could not find many of the features the old ModalWindow had in 
ModalDialog. (for example resize, move, header, closebutton).

Hope that helps,
Johannes Renoth

On 20/10/2023 10:31, Korbinian Bachl wrote:

Hi,

when I try to migrate a ModalWindow to ModalDialog i came accross this:

  add(new AjaxLink("edit") {
 @Override
 public void onClick(AjaxRequestTarget target) {
 
getModalWindow().setModel(ReferenceEditorPanel.this.getModel());
 getModalWindow().setWindowClosedCallback(new 
ModalWindow.WindowClosedCallback() {
 public void onClose(AjaxRequestTarget target) {
 target.add(ReferenceEditorPanel.this);
 ReferenceEditorPanel.this.onUpdate(target);
 }
 });
 getModalWindow().show(target);
 }
 });

-> What would a correct way be for the setWindowClosedCallback? Have only see 
some onOk(AjaxRequestTarget) and onCancel(AjaxRequestTarget)?


Best,

KB

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

Re: Wicket 10 Release Plans

[Martin Grigorov]

https://lists.apache.org/thread/p0gjllpk7zh8wwz3jm3r4v495ylp47rz
Now is the moment to test the candidate and vote for it!

On Tue, Sep 19, 2023 at 12:19 PM Martin Grigorov 
wrote:

> You might be interested in
> https://issues.apache.org/jira/browse/WICKET-7072
> This refactoring may require one more milestone/release candidate.
> Your input is very welcome!
>
> On Tue, Sep 12, 2023 at 3:09 PM Martin Grigorov 
> wrote:
>
>>
>>
>> On Tue, Sep 12, 2023 at 2:11 PM Andrea Del Bene 
>> wrote:
>>
>>> That's the right spirit! 👍 I can start working on an official
>>> announcement
>>> right after M2. This time the process should be faster as I learnt
>>> something with the previous release...🤞
>>>
>>
>> That would be great!
>> Thank you, Andrea!
>>
>>
>>
>>>
>>> On Mon, Sep 11, 2023 at 4:36 PM Thomas Heigl 
>>> wrote:
>>>
>>> > +1 for M2 and a final release as soon as possible.
>>> >
>>> > I also have no plans of adding anything to Wicket 10 before the
>>> release.
>>> >
>>> > I would have deployed M1 to production already if my Jakarta migration
>>> > wasn't blocked by performance issues in Hibernate 6 ,)
>>> >
>>> > Best,
>>> >
>>> > Thomas
>>> >
>>> > On Mon, Sep 11, 2023 at 3:30 PM Martin Grigorov 
>>> > wrote:
>>> >
>>> > > On Mon, Sep 11, 2023 at 4:13 PM Korbinian Bachl <
>>> > > korbinian.ba...@whiskyworld.de> wrote:
>>> > >
>>> > > > +1 for M2 or maybe even a RC1 if no big changes are outstanding?
>>> > > >
>>> > > > Usually I dont care for latest wicket versions (we stayed on 6 way
>>> too
>>> > > > long :D),
>>> > > > but since the JavaEE -> JakartaEE this is a showstopper for us as
>>> you
>>> > > even
>>> > > > cant access anything HTTPSession related as you include the
>>> jakarta-api
>>> > > on
>>> > > > jakarta.*
>>> > > > namespace but wicket 9 only delivers javax.* results
>>> > > >
>>> > > > Or if this really takes a year to release maybe a wicket-9-jakarta
>>> > > version?
>>> > > >
>>> > >
>>> > > Anyone can migrate his/her Javax based application to Jakarta now via
>>> > > migration tools like
>>> > https://github.com/apache/tomcat-jakartaee-migration
>>> > > It is a bytecode translator and has been tested with Wicket
>>> application
>>> > > several years ago!
>>> > >
>>> > >
>>> > >
>>> > > >
>>> > > >
>>> > > > - Ursprüngliche Mail -
>>> > > > > Von: "Martin Grigorov" 
>>> > > > > An: "users" 
>>> > > > > Gesendet: Montag, 11. September 2023 13:00:46
>>> > > > > Betreff: Re: Wicket 10 Release Plans
>>> > > >
>>> > > > > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene <
>>> > an.delb...@gmail.com
>>> > > >
>>> > > > > wrote:
>>> > > > >
>>> > > > >> Hi,
>>> > > > >>
>>> > > > >> as usual it's not easy making precise plans for the future since
>>> > many
>>> > > > of us
>>> > > > >> (probably all of us) works on Wicket on a voluntary base.
>>> However,
>>> > for
>>> > > > the
>>> > > > >> imminent future we are about to release Wicket 10 M2 and check
>>> that
>>> > > > >> everything is fine with the new dependency on Commons
>>> FileUpload M1.
>>> > > > After
>>> > > > >>
>>> > > > >
>>> > > > > +1 for M2 to re-test the latest dependencies updates (fileupload
>>> and
>>> > > > > others) !
>>> > > > >
>>> > > > >
>>> > > > >> this step we might be ready for a GA release of Wicket 10, but
>>> there
>>> > > are
>>> > > > >> some necessary steps (make a public announce, update the site,
>>> > etc...)
>>> > &g

Re: Wicket 10 Release Plans

[Martin Grigorov]

You might be interested in https://issues.apache.org/jira/browse/WICKET-7072
This refactoring may require one more milestone/release candidate.
Your input is very welcome!

On Tue, Sep 12, 2023 at 3:09 PM Martin Grigorov 
wrote:

>
>
> On Tue, Sep 12, 2023 at 2:11 PM Andrea Del Bene 
> wrote:
>
>> That's the right spirit! 👍 I can start working on an official
>> announcement
>> right after M2. This time the process should be faster as I learnt
>> something with the previous release...🤞
>>
>
> That would be great!
> Thank you, Andrea!
>
>
>
>>
>> On Mon, Sep 11, 2023 at 4:36 PM Thomas Heigl  wrote:
>>
>> > +1 for M2 and a final release as soon as possible.
>> >
>> > I also have no plans of adding anything to Wicket 10 before the release.
>> >
>> > I would have deployed M1 to production already if my Jakarta migration
>> > wasn't blocked by performance issues in Hibernate 6 ,)
>> >
>> > Best,
>> >
>> > Thomas
>> >
>> > On Mon, Sep 11, 2023 at 3:30 PM Martin Grigorov 
>> > wrote:
>> >
>> > > On Mon, Sep 11, 2023 at 4:13 PM Korbinian Bachl <
>> > > korbinian.ba...@whiskyworld.de> wrote:
>> > >
>> > > > +1 for M2 or maybe even a RC1 if no big changes are outstanding?
>> > > >
>> > > > Usually I dont care for latest wicket versions (we stayed on 6 way
>> too
>> > > > long :D),
>> > > > but since the JavaEE -> JakartaEE this is a showstopper for us as
>> you
>> > > even
>> > > > cant access anything HTTPSession related as you include the
>> jakarta-api
>> > > on
>> > > > jakarta.*
>> > > > namespace but wicket 9 only delivers javax.* results
>> > > >
>> > > > Or if this really takes a year to release maybe a wicket-9-jakarta
>> > > version?
>> > > >
>> > >
>> > > Anyone can migrate his/her Javax based application to Jakarta now via
>> > > migration tools like
>> > https://github.com/apache/tomcat-jakartaee-migration
>> > > It is a bytecode translator and has been tested with Wicket
>> application
>> > > several years ago!
>> > >
>> > >
>> > >
>> > > >
>> > > >
>> > > > - Ursprüngliche Mail -
>> > > > > Von: "Martin Grigorov" 
>> > > > > An: "users" 
>> > > > > Gesendet: Montag, 11. September 2023 13:00:46
>> > > > > Betreff: Re: Wicket 10 Release Plans
>> > > >
>> > > > > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene <
>> > an.delb...@gmail.com
>> > > >
>> > > > > wrote:
>> > > > >
>> > > > >> Hi,
>> > > > >>
>> > > > >> as usual it's not easy making precise plans for the future since
>> > many
>> > > > of us
>> > > > >> (probably all of us) works on Wicket on a voluntary base.
>> However,
>> > for
>> > > > the
>> > > > >> imminent future we are about to release Wicket 10 M2 and check
>> that
>> > > > >> everything is fine with the new dependency on Commons FileUpload
>> M1.
>> > > > After
>> > > > >>
>> > > > >
>> > > > > +1 for M2 to re-test the latest dependencies updates (fileupload
>> and
>> > > > > others) !
>> > > > >
>> > > > >
>> > > > >> this step we might be ready for a GA release of Wicket 10, but
>> there
>> > > are
>> > > > >> some necessary steps (make a public announce, update the site,
>> > etc...)
>> > > > that
>> > > > >> make it quite unlikely to release it before the end of the year.
>> At
>> > > the
>> > > > >>
>> > > > >
>> > > > > Next year ?!
>> > > > > I really do not understand why it has to be delayed so much when
>> > there
>> > > is
>> > > > > almost no active work on Wicket!
>> > > > > Kudos to Maxim for working on the FileUpload issue! But apart from
>> > > that I
>> > > > > don't see any plans for working on anything major that could not
>> be

Re: Wicket 10.x milestone-Release works great - production release would be appreciated

[Andrea Del Bene]

Hi,

you missed a recent discussion about it :
https://lists.apache.org/thread/rkmcf1tk51sw8vkfy7hpm7gmhj3h9c62

We are going to release M2 in the next days and then we will start to work
on the final release. If everything will go smooth we might release a final
version for (early?) November

On Thu, Sep 14, 2023 at 6:07 PM Geiß, Matthias (KVB - München) <
matthias.ge...@kvb.de> wrote:

> Dear Wicket Community,
>
> just wanted to let you all know, that the Wicket 10.0.0-M1 release has
> worked fine for us in an internal application for several month by now.
> (the upgrade from version 9 had worked fine as well - we just hat to
> replace a modal dialoge)
>
> We would highly appreciate it if a regular production-ready version was
> released. We would feel safer regarding the expected time it takes until a
> hypothetical security issue is fixed for version 10.x.
>
> Is the any internal time frame for the expected 10.x releases?
>
> Best regards,
> Matthias
> Disclaimer:
> Bitte beachten Sie: die obige Mitteilung ist ausschließlich für die in den
> Adresszeilen benannten Personen bestimmt und enthält möglicherweise
> vertrauliche Informationen. Sollten Sie diese Nachricht fälschlicherweise
> erhalten haben, informieren Sie bitte den Absender. Bitte löschen Sie
> die Nachricht und sehen Sie davon ab, die Inhalte zu nutzen,
> aufzubewahren, weiterzuleiten oder zu reproduzieren.
>
> Virenschutz:
> Unser Unternehmen verfügt über eine funktionierende Anti-Viren-
> Software und prüft jede abgesendete E-Mail und deren Anhänge auf
> Viren. Trotzdem können wir nicht garantieren, dass die E-Mail virenfrei
> ist und übernehmen keine Haftung für Schäden, die aus Viren entstehen.
>
> Hinweis zum Datenschutz:
> Die Informationen nach Art. 13 und 14 DSGVO finden Sie unter
> "www.kvb.de/datenschutz"
>


-- 
Andrea Del Bene.
Apache Wicket committer.

Re: Wicket 10 Release Plans

[Martin Grigorov]

On Tue, Sep 12, 2023 at 2:11 PM Andrea Del Bene 
wrote:

> That's the right spirit! 👍 I can start working on an official announcement
> right after M2. This time the process should be faster as I learnt
> something with the previous release...🤞
>

That would be great!
Thank you, Andrea!



>
> On Mon, Sep 11, 2023 at 4:36 PM Thomas Heigl  wrote:
>
> > +1 for M2 and a final release as soon as possible.
> >
> > I also have no plans of adding anything to Wicket 10 before the release.
> >
> > I would have deployed M1 to production already if my Jakarta migration
> > wasn't blocked by performance issues in Hibernate 6 ,)
> >
> > Best,
> >
> > Thomas
> >
> > On Mon, Sep 11, 2023 at 3:30 PM Martin Grigorov 
> > wrote:
> >
> > > On Mon, Sep 11, 2023 at 4:13 PM Korbinian Bachl <
> > > korbinian.ba...@whiskyworld.de> wrote:
> > >
> > > > +1 for M2 or maybe even a RC1 if no big changes are outstanding?
> > > >
> > > > Usually I dont care for latest wicket versions (we stayed on 6 way
> too
> > > > long :D),
> > > > but since the JavaEE -> JakartaEE this is a showstopper for us as you
> > > even
> > > > cant access anything HTTPSession related as you include the
> jakarta-api
> > > on
> > > > jakarta.*
> > > > namespace but wicket 9 only delivers javax.* results
> > > >
> > > > Or if this really takes a year to release maybe a wicket-9-jakarta
> > > version?
> > > >
> > >
> > > Anyone can migrate his/her Javax based application to Jakarta now via
> > > migration tools like
> > https://github.com/apache/tomcat-jakartaee-migration
> > > It is a bytecode translator and has been tested with Wicket application
> > > several years ago!
> > >
> > >
> > >
> > > >
> > > >
> > > > - Ursprüngliche Mail -
> > > > > Von: "Martin Grigorov" 
> > > > > An: "users" 
> > > > > Gesendet: Montag, 11. September 2023 13:00:46
> > > > > Betreff: Re: Wicket 10 Release Plans
> > > >
> > > > > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene <
> > an.delb...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> as usual it's not easy making precise plans for the future since
> > many
> > > > of us
> > > > >> (probably all of us) works on Wicket on a voluntary base. However,
> > for
> > > > the
> > > > >> imminent future we are about to release Wicket 10 M2 and check
> that
> > > > >> everything is fine with the new dependency on Commons FileUpload
> M1.
> > > > After
> > > > >>
> > > > >
> > > > > +1 for M2 to re-test the latest dependencies updates (fileupload
> and
> > > > > others) !
> > > > >
> > > > >
> > > > >> this step we might be ready for a GA release of Wicket 10, but
> there
> > > are
> > > > >> some necessary steps (make a public announce, update the site,
> > etc...)
> > > > that
> > > > >> make it quite unlikely to release it before the end of the year.
> At
> > > the
> > > > >>
> > > > >
> > > > > Next year ?!
> > > > > I really do not understand why it has to be delayed so much when
> > there
> > > is
> > > > > almost no active work on Wicket!
> > > > > Kudos to Maxim for working on the FileUpload issue! But apart from
> > > that I
> > > > > don't see any plans for working on anything major that could not be
> > > > > introduced in a minor version!
> > > > > The official announcement (coordinated with press@a.o) has proved
> to
> > > be
> > > > an
> > > > > issue for the last few major releases! I'd rather go without it
> than
> > > > delay
> > > > > the release for half a year.
> > > > >
> > > > >
> > > > >> moment I don't have elements to be more precise, but probably
> after
> > > the
> > > > M2
> > > > >> we will have a clearer view of the next steps toward a final
> > rel

Re: Wicket 10 Release Plans

[Andrea Del Bene]

That's the right spirit! 👍 I can start working on an official announcement
right after M2. This time the process should be faster as I learnt
something with the previous release...🤞

On Mon, Sep 11, 2023 at 4:36 PM Thomas Heigl  wrote:

> +1 for M2 and a final release as soon as possible.
>
> I also have no plans of adding anything to Wicket 10 before the release.
>
> I would have deployed M1 to production already if my Jakarta migration
> wasn't blocked by performance issues in Hibernate 6 ,)
>
> Best,
>
> Thomas
>
> On Mon, Sep 11, 2023 at 3:30 PM Martin Grigorov 
> wrote:
>
> > On Mon, Sep 11, 2023 at 4:13 PM Korbinian Bachl <
> > korbinian.ba...@whiskyworld.de> wrote:
> >
> > > +1 for M2 or maybe even a RC1 if no big changes are outstanding?
> > >
> > > Usually I dont care for latest wicket versions (we stayed on 6 way too
> > > long :D),
> > > but since the JavaEE -> JakartaEE this is a showstopper for us as you
> > even
> > > cant access anything HTTPSession related as you include the jakarta-api
> > on
> > > jakarta.*
> > > namespace but wicket 9 only delivers javax.* results
> > >
> > > Or if this really takes a year to release maybe a wicket-9-jakarta
> > version?
> > >
> >
> > Anyone can migrate his/her Javax based application to Jakarta now via
> > migration tools like
> https://github.com/apache/tomcat-jakartaee-migration
> > It is a bytecode translator and has been tested with Wicket application
> > several years ago!
> >
> >
> >
> > >
> > >
> > > - Ursprüngliche Mail -
> > > > Von: "Martin Grigorov" 
> > > > An: "users" 
> > > > Gesendet: Montag, 11. September 2023 13:00:46
> > > > Betreff: Re: Wicket 10 Release Plans
> > >
> > > > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene <
> an.delb...@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> as usual it's not easy making precise plans for the future since
> many
> > > of us
> > > >> (probably all of us) works on Wicket on a voluntary base. However,
> for
> > > the
> > > >> imminent future we are about to release Wicket 10 M2 and check that
> > > >> everything is fine with the new dependency on Commons FileUpload M1.
> > > After
> > > >>
> > > >
> > > > +1 for M2 to re-test the latest dependencies updates (fileupload and
> > > > others) !
> > > >
> > > >
> > > >> this step we might be ready for a GA release of Wicket 10, but there
> > are
> > > >> some necessary steps (make a public announce, update the site,
> etc...)
> > > that
> > > >> make it quite unlikely to release it before the end of the year. At
> > the
> > > >>
> > > >
> > > > Next year ?!
> > > > I really do not understand why it has to be delayed so much when
> there
> > is
> > > > almost no active work on Wicket!
> > > > Kudos to Maxim for working on the FileUpload issue! But apart from
> > that I
> > > > don't see any plans for working on anything major that could not be
> > > > introduced in a minor version!
> > > > The official announcement (coordinated with press@a.o) has proved to
> > be
> > > an
> > > > issue for the last few major releases! I'd rather go without it than
> > > delay
> > > > the release for half a year.
> > > >
> > > >
> > > >> moment I don't have elements to be more precise, but probably after
> > the
> > > M2
> > > >> we will have a clearer view of the next steps toward a final
> release.
> > > >>
> > > >> Andrea.
> > > >>
> > > >> On Mon, Sep 11, 2023 at 8:18 AM Korbinian Bachl <
> > > >> korbinian.ba...@whiskyworld.de> wrote:
> > > >>
> > > >> > Hi Fellow Wicket-Devs!
> > > >> >
> > > >> > I'd like to also ask this question as wicket is the only part that
> > > holds
> > > >> > us back from jumping up to JakartaEE (currently JavaEE 8).
> > > >> >
> > > >> > Any eta on final release?
> > > >> >
> > > >> > - Ursprüngliche Mail -
> > > >> > > Von: "Tony Tkacik" 
> > > >> > > An: "users" 
> > > >> > > Gesendet: Donnerstag, 7. September 2023 13:54:41
> > > >> > > Betreff: Wicket 10 Release Plans
> > > >> >
> > > >> > > Hi,
> > > >> > > we are using Wicket 10 M1 for few months and we plan to release
> > LTS
> > > of
> > > >> > our open
> > > >> > > source project midPoint 4.8 on 17 October 2023,
> > > >> > > are there any concrete plans about release timeframe of Wicket
> 10?
> > > >> > >
> > > >> > > Thanks
> > > >> > > Anton Tkacik
> > > >> >
> > > >> >
> > -
> > > >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > >> > For additional commands, e-mail: users-h...@wicket.apache.org
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> Andrea Del Bene.
> > > >> Apache Wicket committer.
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> > >
> > >
> >
>


-- 
Andrea Del Bene.
Apache Wicket committer.

Re: Wicket 10 Release Plans

[Thomas Heigl]

+1 for M2 and a final release as soon as possible.

I also have no plans of adding anything to Wicket 10 before the release.

I would have deployed M1 to production already if my Jakarta migration
wasn't blocked by performance issues in Hibernate 6 ,)

Best,

Thomas

On Mon, Sep 11, 2023 at 3:30 PM Martin Grigorov 
wrote:

> On Mon, Sep 11, 2023 at 4:13 PM Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
> > +1 for M2 or maybe even a RC1 if no big changes are outstanding?
> >
> > Usually I dont care for latest wicket versions (we stayed on 6 way too
> > long :D),
> > but since the JavaEE -> JakartaEE this is a showstopper for us as you
> even
> > cant access anything HTTPSession related as you include the jakarta-api
> on
> > jakarta.*
> > namespace but wicket 9 only delivers javax.* results
> >
> > Or if this really takes a year to release maybe a wicket-9-jakarta
> version?
> >
>
> Anyone can migrate his/her Javax based application to Jakarta now via
> migration tools like https://github.com/apache/tomcat-jakartaee-migration
> It is a bytecode translator and has been tested with Wicket application
> several years ago!
>
>
>
> >
> >
> > - Ursprüngliche Mail -
> > > Von: "Martin Grigorov" 
> > > An: "users" 
> > > Gesendet: Montag, 11. September 2023 13:00:46
> > > Betreff: Re: Wicket 10 Release Plans
> >
> > > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene  >
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> as usual it's not easy making precise plans for the future since many
> > of us
> > >> (probably all of us) works on Wicket on a voluntary base. However, for
> > the
> > >> imminent future we are about to release Wicket 10 M2 and check that
> > >> everything is fine with the new dependency on Commons FileUpload M1.
> > After
> > >>
> > >
> > > +1 for M2 to re-test the latest dependencies updates (fileupload and
> > > others) !
> > >
> > >
> > >> this step we might be ready for a GA release of Wicket 10, but there
> are
> > >> some necessary steps (make a public announce, update the site, etc...)
> > that
> > >> make it quite unlikely to release it before the end of the year. At
> the
> > >>
> > >
> > > Next year ?!
> > > I really do not understand why it has to be delayed so much when there
> is
> > > almost no active work on Wicket!
> > > Kudos to Maxim for working on the FileUpload issue! But apart from
> that I
> > > don't see any plans for working on anything major that could not be
> > > introduced in a minor version!
> > > The official announcement (coordinated with press@a.o) has proved to
> be
> > an
> > > issue for the last few major releases! I'd rather go without it than
> > delay
> > > the release for half a year.
> > >
> > >
> > >> moment I don't have elements to be more precise, but probably after
> the
> > M2
> > >> we will have a clearer view of the next steps toward a final release.
> > >>
> > >> Andrea.
> > >>
> > >> On Mon, Sep 11, 2023 at 8:18 AM Korbinian Bachl <
> > >> korbinian.ba...@whiskyworld.de> wrote:
> > >>
> > >> > Hi Fellow Wicket-Devs!
> > >> >
> > >> > I'd like to also ask this question as wicket is the only part that
> > holds
> > >> > us back from jumping up to JakartaEE (currently JavaEE 8).
> > >> >
> > >> > Any eta on final release?
> > >> >
> > >> > - Ursprüngliche Mail -
> > >> > > Von: "Tony Tkacik" 
> > >> > > An: "users" 
> > >> > > Gesendet: Donnerstag, 7. September 2023 13:54:41
> > >> > > Betreff: Wicket 10 Release Plans
> > >> >
> > >> > > Hi,
> > >> > > we are using Wicket 10 M1 for few months and we plan to release
> LTS
> > of
> > >> > our open
> > >> > > source project midPoint 4.8 on 17 October 2023,
> > >> > > are there any concrete plans about release timeframe of Wicket 10?
> > >> > >
> > >> > > Thanks
> > >> > > Anton Tkacik
> > >> >
> > >> >
> -
> > >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > >> > For additional commands, e-mail: users-h...@wicket.apache.org
> > >> >
> > >> >
> > >>
> > >> --
> > >> Andrea Del Bene.
> > >> Apache Wicket committer.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>

Re: Wicket 10 Release Plans

[Martin Grigorov]

On Mon, Sep 11, 2023 at 4:13 PM Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:

> +1 for M2 or maybe even a RC1 if no big changes are outstanding?
>
> Usually I dont care for latest wicket versions (we stayed on 6 way too
> long :D),
> but since the JavaEE -> JakartaEE this is a showstopper for us as you even
> cant access anything HTTPSession related as you include the jakarta-api on
> jakarta.*
> namespace but wicket 9 only delivers javax.* results
>
> Or if this really takes a year to release maybe a wicket-9-jakarta version?
>

Anyone can migrate his/her Javax based application to Jakarta now via
migration tools like https://github.com/apache/tomcat-jakartaee-migration
It is a bytecode translator and has been tested with Wicket application
several years ago!



>
>
> - Ursprüngliche Mail -
> > Von: "Martin Grigorov" 
> > An: "users" 
> > Gesendet: Montag, 11. September 2023 13:00:46
> > Betreff: Re: Wicket 10 Release Plans
>
> > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene 
> > wrote:
> >
> >> Hi,
> >>
> >> as usual it's not easy making precise plans for the future since many
> of us
> >> (probably all of us) works on Wicket on a voluntary base. However, for
> the
> >> imminent future we are about to release Wicket 10 M2 and check that
> >> everything is fine with the new dependency on Commons FileUpload M1.
> After
> >>
> >
> > +1 for M2 to re-test the latest dependencies updates (fileupload and
> > others) !
> >
> >
> >> this step we might be ready for a GA release of Wicket 10, but there are
> >> some necessary steps (make a public announce, update the site, etc...)
> that
> >> make it quite unlikely to release it before the end of the year. At the
> >>
> >
> > Next year ?!
> > I really do not understand why it has to be delayed so much when there is
> > almost no active work on Wicket!
> > Kudos to Maxim for working on the FileUpload issue! But apart from that I
> > don't see any plans for working on anything major that could not be
> > introduced in a minor version!
> > The official announcement (coordinated with press@a.o) has proved to be
> an
> > issue for the last few major releases! I'd rather go without it than
> delay
> > the release for half a year.
> >
> >
> >> moment I don't have elements to be more precise, but probably after the
> M2
> >> we will have a clearer view of the next steps toward a final release.
> >>
> >> Andrea.
> >>
> >> On Mon, Sep 11, 2023 at 8:18 AM Korbinian Bachl <
> >> korbinian.ba...@whiskyworld.de> wrote:
> >>
> >> > Hi Fellow Wicket-Devs!
> >> >
> >> > I'd like to also ask this question as wicket is the only part that
> holds
> >> > us back from jumping up to JakartaEE (currently JavaEE 8).
> >> >
> >> > Any eta on final release?
> >> >
> >> > - Ursprüngliche Mail -
> >> > > Von: "Tony Tkacik" 
> >> > > An: "users" 
> >> > > Gesendet: Donnerstag, 7. September 2023 13:54:41
> >> > > Betreff: Wicket 10 Release Plans
> >> >
> >> > > Hi,
> >> > > we are using Wicket 10 M1 for few months and we plan to release LTS
> of
> >> > our open
> >> > > source project midPoint 4.8 on 17 October 2023,
> >> > > are there any concrete plans about release timeframe of Wicket 10?
> >> > >
> >> > > Thanks
> >> > > Anton Tkacik
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> > For additional commands, e-mail: users-h...@wicket.apache.org
> >> >
> >> >
> >>
> >> --
> >> Andrea Del Bene.
> >> Apache Wicket committer.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Wicket 10 Release Plans

[Ernesto Reinaldo Barreiro]

Hi,

I do agree with Martin Grigorov. There are not many new things added to
Wicket. I have added not long ago some upload to resource functionality but
apart from that I do not know of any planned big features. Thus, why not
simply release ASAP as using jakarta was the main focus of release.

On Mon, Sep 11, 2023 at 8:13 AM Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:

> +1 for M2 or maybe even a RC1 if no big changes are outstanding?
>
> Usually I dont care for latest wicket versions (we stayed on 6 way too
> long :D),
> but since the JavaEE -> JakartaEE this is a showstopper for us as you even
> cant access anything HTTPSession related as you include the jakarta-api on
> jakarta.*
> namespace but wicket 9 only delivers javax.* results
>
> Or if this really takes a year to release maybe a wicket-9-jakarta version?
>
>
> - Ursprüngliche Mail -
> > Von: "Martin Grigorov" 
> > An: "users" 
> > Gesendet: Montag, 11. September 2023 13:00:46
> > Betreff: Re: Wicket 10 Release Plans
>
> > On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene 
> > wrote:
> >
> >> Hi,
> >>
> >> as usual it's not easy making precise plans for the future since many
> of us
> >> (probably all of us) works on Wicket on a voluntary base. However, for
> the
> >> imminent future we are about to release Wicket 10 M2 and check that
> >> everything is fine with the new dependency on Commons FileUpload M1.
> After
> >>
> >
> > +1 for M2 to re-test the latest dependencies updates (fileupload and
> > others) !
> >
> >
> >> this step we might be ready for a GA release of Wicket 10, but there are
> >> some necessary steps (make a public announce, update the site, etc...)
> that
> >> make it quite unlikely to release it before the end of the year. At the
> >>
> >
> > Next year ?!
> > I really do not understand why it has to be delayed so much when there is
> > almost no active work on Wicket!
> > Kudos to Maxim for working on the FileUpload issue! But apart from that I
> > don't see any plans for working on anything major that could not be
> > introduced in a minor version!
> > The official announcement (coordinated with press@a.o) has proved to be
> an
> > issue for the last few major releases! I'd rather go without it than
> delay
> > the release for half a year.
> >
> >
> >> moment I don't have elements to be more precise, but probably after the
> M2
> >> we will have a clearer view of the next steps toward a final release.
> >>
> >> Andrea.
> >>
> >> On Mon, Sep 11, 2023 at 8:18 AM Korbinian Bachl <
> >> korbinian.ba...@whiskyworld.de> wrote:
> >>
> >> > Hi Fellow Wicket-Devs!
> >> >
> >> > I'd like to also ask this question as wicket is the only part that
> holds
> >> > us back from jumping up to JakartaEE (currently JavaEE 8).
> >> >
> >> > Any eta on final release?
> >> >
> >> > - Ursprüngliche Mail -
> >> > > Von: "Tony Tkacik" 
> >> > > An: "users" 
> >> > > Gesendet: Donnerstag, 7. September 2023 13:54:41
> >> > > Betreff: Wicket 10 Release Plans
> >> >
> >> > > Hi,
> >> > > we are using Wicket 10 M1 for few months and we plan to release LTS
> of
> >> > our open
> >> > > source project midPoint 4.8 on 17 October 2023,
> >> > > are there any concrete plans about release timeframe of Wicket 10?
> >> > >
> >> > > Thanks
> >> > > Anton Tkacik
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> > For additional commands, e-mail: users-h...@wicket.apache.org
> >> >
> >> >
> >>
> >> --
> >> Andrea Del Bene.
> >> Apache Wicket committer.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-- 
Regards - Ernesto Reinaldo Barreiro

Re: Wicket 10 Release Plans

[Korbinian Bachl]

+1 for M2 or maybe even a RC1 if no big changes are outstanding?

Usually I dont care for latest wicket versions (we stayed on 6 way too long 
:D), 
but since the JavaEE -> JakartaEE this is a showstopper for us as you even 
cant access anything HTTPSession related as you include the jakarta-api on 
jakarta.* 
namespace but wicket 9 only delivers javax.* results

Or if this really takes a year to release maybe a wicket-9-jakarta version?


- Ursprüngliche Mail -
> Von: "Martin Grigorov" 
> An: "users" 
> Gesendet: Montag, 11. September 2023 13:00:46
> Betreff: Re: Wicket 10 Release Plans

> On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene 
> wrote:
> 
>> Hi,
>>
>> as usual it's not easy making precise plans for the future since many of us
>> (probably all of us) works on Wicket on a voluntary base. However, for the
>> imminent future we are about to release Wicket 10 M2 and check that
>> everything is fine with the new dependency on Commons FileUpload M1. After
>>
> 
> +1 for M2 to re-test the latest dependencies updates (fileupload and
> others) !
> 
> 
>> this step we might be ready for a GA release of Wicket 10, but there are
>> some necessary steps (make a public announce, update the site, etc...) that
>> make it quite unlikely to release it before the end of the year. At the
>>
> 
> Next year ?!
> I really do not understand why it has to be delayed so much when there is
> almost no active work on Wicket!
> Kudos to Maxim for working on the FileUpload issue! But apart from that I
> don't see any plans for working on anything major that could not be
> introduced in a minor version!
> The official announcement (coordinated with press@a.o) has proved to be an
> issue for the last few major releases! I'd rather go without it than delay
> the release for half a year.
> 
> 
>> moment I don't have elements to be more precise, but probably after the M2
>> we will have a clearer view of the next steps toward a final release.
>>
>> Andrea.
>>
>> On Mon, Sep 11, 2023 at 8:18 AM Korbinian Bachl <
>> korbinian.ba...@whiskyworld.de> wrote:
>>
>> > Hi Fellow Wicket-Devs!
>> >
>> > I'd like to also ask this question as wicket is the only part that holds
>> > us back from jumping up to JakartaEE (currently JavaEE 8).
>> >
>> > Any eta on final release?
>> >
>> > - Ursprüngliche Mail -
>> > > Von: "Tony Tkacik" 
>> > > An: "users" 
>> > > Gesendet: Donnerstag, 7. September 2023 13:54:41
>> > > Betreff: Wicket 10 Release Plans
>> >
>> > > Hi,
>> > > we are using Wicket 10 M1 for few months and we plan to release LTS of
>> > our open
>> > > source project midPoint 4.8 on 17 October 2023,
>> > > are there any concrete plans about release timeframe of Wicket 10?
>> > >
>> > > Thanks
>> > > Anton Tkacik
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>> >
>>
>> --
>> Andrea Del Bene.
>> Apache Wicket committer.

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

Re: Wicket 10 Release Plans

[Martin Grigorov]

On Mon, Sep 11, 2023 at 11:06 AM Andrea Del Bene 
wrote:

> Hi,
>
> as usual it's not easy making precise plans for the future since many of us
> (probably all of us) works on Wicket on a voluntary base. However, for the
> imminent future we are about to release Wicket 10 M2 and check that
> everything is fine with the new dependency on Commons FileUpload M1. After
>

+1 for M2 to re-test the latest dependencies updates (fileupload and
others) !


> this step we might be ready for a GA release of Wicket 10, but there are
> some necessary steps (make a public announce, update the site, etc...) that
> make it quite unlikely to release it before the end of the year. At the
>

Next year ?!
I really do not understand why it has to be delayed so much when there is
almost no active work on Wicket!
Kudos to Maxim for working on the FileUpload issue! But apart from that I
don't see any plans for working on anything major that could not be
introduced in a minor version!
The official announcement (coordinated with press@a.o) has proved to be an
issue for the last few major releases! I'd rather go without it than delay
the release for half a year.


> moment I don't have elements to be more precise, but probably after the M2
> we will have a clearer view of the next steps toward a final release.
>
> Andrea.
>
> On Mon, Sep 11, 2023 at 8:18 AM Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
> > Hi Fellow Wicket-Devs!
> >
> > I'd like to also ask this question as wicket is the only part that holds
> > us back from jumping up to JakartaEE (currently JavaEE 8).
> >
> > Any eta on final release?
> >
> > - Ursprüngliche Mail -
> > > Von: "Tony Tkacik" 
> > > An: "users" 
> > > Gesendet: Donnerstag, 7. September 2023 13:54:41
> > > Betreff: Wicket 10 Release Plans
> >
> > > Hi,
> > > we are using Wicket 10 M1 for few months and we plan to release LTS of
> > our open
> > > source project midPoint 4.8 on 17 October 2023,
> > > are there any concrete plans about release timeframe of Wicket 10?
> > >
> > > Thanks
> > > Anton Tkacik
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
> --
> Andrea Del Bene.
> Apache Wicket committer.
>