Re: ApacheCon: Community Over Code Bratislava
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: A simple Wicket component to render a Vue app
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.
> <https://github.com/freemant2000/WicketVueApp#how-to-use>How to use
>
> Suppose that you want a Vue app on an HTML page like below:
>
> https://.../vue.js"</a>;>
>
>
> var app = Vue.createApp({
> data() {
> return {a: 4, b: "Hi"};
> },
> template: `<span @click='m1()'>{{a}} {{b}}<span>`,
> 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: [ANNOUNCE] Apache Wicket 9.16.0 released
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: Wicket 10 Release Plans
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: Question about log warning: "IndicatingAjaxButton should be applied on a 'button' tag"
This is true. Looking at the source code I don't why it needs to be a button :-) On Wed, Jun 28, 2023 at 4:34 PM Martin Grigorov wrote: > For me the real question is why is not supported too > ?! > IMO this is a bug! > > On Wed, Jun 28, 2023 at 4:28 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > By the way... in almost all wicket applications I have worked with we > had a > > blocking div covering the page and activated/deactivated via global AJAX > > listeners. > > > > On Wed, Jun 28, 2023 at 4:24 PM Shawn McKinney > > wrote: > > > > > > > > > On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote: > > > > > > > > Hi Shawn, > > > > > > > > The code basically checks if you apply the behavior to a > > > element. > > > > > > > > In other words: > > > > > > > > is considered an “invalid” element for this > > > behavior. > > > > > > > > is considered “valid”. > > > > > > > > > > Hello, > > > > > > As part of my scientific ‘poke and hope’ methodology;-), I had tried > > that. > > > > > > Now, the warning has disappeared. But, the button renders on the page > as > > a > > > tiny dot, that actually works. I doubt my users would be a big fan of > it > > > (tiny buttons), although their eye doctors might? > > > > > > Anyway, all kidding aside, here’s what the html looks like: > > > > > > ``` > > > > >wicket:id="wspage1.button1" > > > value="wspage1.button1" name="wspage1.button1”/> > > > ``` > > > > > > Best > > > > > > — > > > Shawn > > > > > > > Met vriendelijke groet, > > > > Kind regards, > > > > > > > > Bas Gooren > > > > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Question about log warning: "IndicatingAjaxButton should be applied on a 'button' tag"
I mean something like this:
;Wicket.Event.subscribe('/ajax/call/beforeSend', function(jqEvent,
attributes, jqXHR, errorThrown, textStatus) {
pageLoadingFrame("show");
});
Wicket.Event.subscribe('/ajax/call/failure', function(jqEvent, attributes,
jqXHR, errorThrown, textStatus) {
pageLoadingFrame("hide");
});
This will prevent your users from clicking on components that will no
longer be there when the current AJAX request finishes.
On Wed, Jun 28, 2023 at 4:24 PM Shawn McKinney wrote:
>
> > On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote:
> >
> > Hi Shawn,
> >
> > The code basically checks if you apply the behavior to a
> element.
> >
> > In other words:
> >
> > is considered an “invalid” element for this
> behavior.
> >
> > is considered “valid”.
> >
>
> Hello,
>
> As part of my scientific ‘poke and hope’ methodology;-), I had tried that.
>
> Now, the warning has disappeared. But, the button renders on the page as a
> tiny dot, that actually works. I doubt my users would be a big fan of it
> (tiny buttons), although their eye doctors might?
>
> Anyway, all kidding aside, here’s what the html looks like:
>
> ```
> wicket:id="wspage1.button1"
> value="wspage1.button1" name="wspage1.button1”/>
> ```
>
> Best
>
> —
> Shawn
>
> > Met vriendelijke groet,
> > Kind regards,
> >
> > Bas Gooren
>
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Question about log warning: "IndicatingAjaxButton should be applied on a 'button' tag"
By the way... in almost all wicket applications I have worked with we had a blocking div covering the page and activated/deactivated via global AJAX listeners. On Wed, Jun 28, 2023 at 4:24 PM Shawn McKinney wrote: > > > On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote: > > > > Hi Shawn, > > > > The code basically checks if you apply the behavior to a > element. > > > > In other words: > > > > is considered an “invalid” element for this > behavior. > > > > is considered “valid”. > > > > Hello, > > As part of my scientific ‘poke and hope’ methodology;-), I had tried that. > > Now, the warning has disappeared. But, the button renders on the page as a > tiny dot, that actually works. I doubt my users would be a big fan of it > (tiny buttons), although their eye doctors might? > > Anyway, all kidding aside, here’s what the html looks like: > > ``` > wicket:id="wspage1.button1" > value="wspage1.button1" name="wspage1.button1”/> > ``` > > Best > > — > Shawn > > > Met vriendelijke groet, > > Kind regards, > > > > Bas Gooren > > > --------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Question about log warning: "IndicatingAjaxButton should be applied on a 'button' tag"
You need to put something inside the button for it not to be tiny On Wed, Jun 28, 2023 at 4:24 PM Shawn McKinney wrote: > > > On Jun 28, 2023, at 8:11 AM, Bas Gooren wrote: > > > > Hi Shawn, > > > > The code basically checks if you apply the behavior to a > element. > > > > In other words: > > > > is considered an “invalid” element for this > behavior. > > > > is considered “valid”. > > > > Hello, > > As part of my scientific ‘poke and hope’ methodology;-), I had tried that. > > Now, the warning has disappeared. But, the button renders on the page as a > tiny dot, that actually works. I doubt my users would be a big fan of it > (tiny buttons), although their eye doctors might? > > Anyway, all kidding aside, here’s what the html looks like: > > ``` > wicket:id="wspage1.button1" > value="wspage1.button1" name="wspage1.button1”/> > ``` > > Best > > — > Shawn > > > Met vriendelijke groet, > > Kind regards, > > > > Bas Gooren > > > --------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Question about log warning: "IndicatingAjaxButton should be applied on a 'button' tag"
I think your question has been correctly answered already. But, anyways, it
is pleasant to have questions in wicket's users list :-)
On Wed, Jun 28, 2023 at 4:08 PM Shawn McKinney wrote:
> Howdy,
>
> I’m a little embarrassed to be asking. It seems so basic, should know it
> already.
>
> But, I’ve already spent a fair amount of time digging with no answers.
>
> My usage of Ajax buttons generates this warning in the logs:
>
> ```
> WARN - 28 Jun 2023 07:35:56,704 - IndicatingAjaxButton -
> IndicatingAjaxButton should be applied on a 'button’ tag
> ```
>
> Looking at the wicket source, I see:
>
>
> ```
> public abstract class IndicatingAjaxButton extends AjaxButton
> ...
> @Override
> protected void onComponentTag(ComponentTag tag)
> {
> super.onComponentTag(tag);
> if (!"button".equalsIgnoreCase(tag.getName()))
> {
> LOG.warn("IndicatingAjaxButton should be applied on a 'button' tag”);
> }
> }
> ```
>
> A head scratcher to me why that warning is in place.
>
> Obviously, there’s something I’m missing.
>
> Here’s my code. It all “seems" to work just fine (other than the warning).
> What am I doing wrong?
>
> ```java
> public Page1Form( String id )
> {
> …
>
> add( new IndicatingAjaxButton( "wspage1.button1" )
> {
> @Override protected void onSubmit( AjaxRequestTarget target )
> {
> logIt( target, “..." );
> }
> }
> ...
> ```
>
> ```html
>
> class="ui-button ui-widget ui-state-default ui-corner-all
> ui-button-text-only”
> wicket:id="wspage1.button1” value="wspage1.button1"
> name="wspage1.button1"/>
>
> ```
>
> I’m using the latest Wicket (v10). This behavior (log warnings) was
> present on earlier versions as well.
>
> Thanks
>
> —
> Shawn
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Plans for Wicket 10 Release
Maybe we can move the CDI module to wicket-stuff or somewhere else till there is an implementation for those? On Thu, May 25, 2023 at 11:08 AM Martin Grigorov wrote: > Since we use a local copy of commons-fileupload2 I see no stopper for a > release! A milestone one or a release candidate. > > The last problem is in the CDI module - several dependencies still miss > jakarta impls (e.g. cdi-unit). I cannot say how big of an issue this is for > a Wicket itself. > > On Thu, May 25, 2023 at 11:01 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > As far as I know release of wicket 10 is blocked by commons upload > project. > > That project has been cloned as part of wicket 10.x branch and we have > > fixed at least one bug in it (and in parallel in the original project). > > Maybe other more experienced committers can comment? > > > > On Thu, May 25, 2023 at 10:52 AM János Cserép > > wrote: > > > > > Just a thought... > > > > > > I've been using Wicket 10 snapshot builds in production for over a year > > now > > > with latest Spring and Jakarta libs without any major issues, so if > that > > is > > > an option for you, go ahead. You can mitigate risks by creating release > > > from a known git rev yourself if your release process does not like > > > SNAPSHOT dependencies. > > > > > > j > > > > > > > > > On Thu, 25 May 2023 at 09:15, Tony Tkacik > > .invalid> > > > wrote: > > > > > > > Hi, > > > > I would like to ask about your timeline / plans regarding release of > > > > Wicket 10? > > > > > > > > We are in process of upgrading our open-source project midPoint to > > latest > > > > Spring releases and that requires Wicket to be updated to version 10 > > > > in order to support Spring 6. > > > > > > > > Thanks, > > > > Anton Tkacik > > > > > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Plans for Wicket 10 Release
Hi, As far as I know release of wicket 10 is blocked by commons upload project. That project has been cloned as part of wicket 10.x branch and we have fixed at least one bug in it (and in parallel in the original project). Maybe other more experienced committers can comment? On Thu, May 25, 2023 at 10:52 AM János Cserép wrote: > Just a thought... > > I've been using Wicket 10 snapshot builds in production for over a year now > with latest Spring and Jakarta libs without any major issues, so if that is > an option for you, go ahead. You can mitigate risks by creating release > from a known git rev yourself if your release process does not like > SNAPSHOT dependencies. > > j > > > On Thu, 25 May 2023 at 09:15, Tony Tkacik .invalid> > wrote: > > > Hi, > > I would like to ask about your timeline / plans regarding release of > > Wicket 10? > > > > We are in process of upgrading our open-source project midPoint to latest > > Spring releases and that requires Wicket to be updated to version 10 > > in order to support Spring 6. > > > > Thanks, > > Anton Tkacik > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Is Wicket In Action still relevant?
Hi, On Fri, May 12, 2023 at 9:14 PM Kyrindorx wrote: > Hey all > > It is compact, has many functions and does its job well. If you compare > it with JSF, Vaadin it compares well. > > Advantages: > - flexible > - Java + HTML > is ok > Huge advantages, only my opinion, you forgot to mention 1. You can do very complex applications with backend developers (Java developers) who know little about JavaScript. You have a team member that knows JavaScript and low level things well and the rest just use components and Java. Many times those backend developers can fix and implement complex issues without waiting for the javaScript guy coming back from holidays. The slogan on NodeJS was JavaScript at all levels. Wicket is Java at all levels (if you have a guru on board hiding JavaScript for the rest of the team). 2. You can maintain huge applications with very few developers. 3. Many applications do not need to scale. Just provide as much functionality as possible with as less maintenance cost as possible. Wicket excels on that. 4. Secure. > Disadvantages: > - modern plugins for Wicket: outdated and quite little. > True. Sadly many companies just want to leach open source and not pay developers to contribute. And developers just want to do trendy things that help you land good jobs. - CSS Libs like Bootstrap: outdated and strong coupling (plugin) > Who forces you to use those libraries? I have used wicket and bootstrap together with minimal use of those libraries. > - use of modern JS techniques + Wicket: difficult > Stated like this, this is just an opinion. One big disadvantage of wicket (IMHO) is it is difficult to grasp and understand for developers. Concepts like detaching and the request cycle are difficult to explain and more difficult to keep pages small after detach. > Conclusion: > > For medium sized sites working with Apache Wicket basic components and > using Java, HTML and Wicket JQuery > ok. > Again this is just your opinion. I have built/worked on many wicket applications with very strong use of JavaScript and very dynamic client side behavior. > > The development of modern JS applications Apache Wicket is (my opinion) > outdated. It very good flexible JS frameworks, more plugins, lots of > docs and examples. And the number of developers for modern JS frameworks > is huge! > True. > > In the end, I think Apache Wicket is past its prime and we are talking > about product maintenance here. I wouldn't develop new big projects with > Apache Wicket anymore. Here it is not the evaluation of the framework, > but the number of projects and the amount of developers that matters. > This depends on your goals and the needs these applications have. > Greets > Kyrindor > -- > > Am 11.05.2023 um 14:23 schrieb Andrea Del Bene: > > If you are new to Apache Wicket it might be better starting with the user > > guide which is meant for a full introduction from scratch and is updated. > > > > On Thu, 11 May 2023, 10:29 James Selvakumar, > wrote: > > > >> Hi all, > >> > >> Just wondering whether Wicket in Action is still relevant with all the > >> recent changes to Wicket? Can it be used to help a new developer > understand > >> Wicket? > >> > >> -- > >> Thanks & regards > >> James > >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 9.13.0 released
Thanks for the release! On Tue, Apr 18, 2023 at 4:03 PM Andrea Del Bene wrote: > The Apache Wicket PMC is proud to announce Apache Wicket 9.13.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.13.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.13.0: > > ** Bug > > * [WICKET-7005] - ByteBuddy IllegalStateException: Cannot inject > already loaded type > * [WICKET-7022] - JavaScriptStripper fails to detect regular expression > correctly > * [WICKET-7028] - CSP header not rendered when using > RedirectPolicy.NEVER_REDIRECT > * [WICKET-7034] - WebSocket.Closed event not fired when error occurred > * [WICKET-7037] - [Ajax Download] cookie used to track download > complete misses the SameSite attribute > * [WICKET-7044] - Images in the Wicket 9.x reference guide are not > displayed. > > ** Improvement > > * [WICKET-7011] - Improve usage of JUnit 5.x APIs > * [WICKET-7014] - Use new API for forward compatibility with CDI 4 > * [WICKET-7016] - Support GCM-SIV for page store encryption > * [WICKET-7017] - ListenerRequestHandler should not hide > IndexOutOfBoundsException > * [WICKET-7021] - Additional OSGi import fixes > * [WICKET-7025] - Package private methods should be proxied by > ByteBuddy > * [WICKET-7031] - Update to JQuery 3.6.4 > * [WICKET-7032] - Update the JS tests to use latest version of QUnit > (2.x) > * [WICKET-7035] - fileCountMax should be added to control the amount of > files being uploaded > * [WICKET-7041] - Reduce allocations when rendering component headers > * [WICKET-7042] - Improve sizing of StringResponse when writing scripts > in PartialPageResponse > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.13.0 Released
Many thanks for the release! On Tue, Apr 18, 2023 at 6:31 PM Maxim Solodovnik wrote: > WicketStuff core 9.13.0 based on Apache Wicket 9.13.0 is released > and soon will be available at Maven Central! > > Maxim Solodovnik (16): > Switching to the next development version > Dependencies are updated > Dependencies are updated, vulnerable testng is removed > Dependencies are updated > Fixes Issue #743: JSON.stringify is used instead of $.toJson > Attempt to fix CI build > Another attempt to fix CI build > Deprecated code is removed > Dependencies are updated > Fixing CI build > Dependencies are updated, tests are fixed > More dependencies are updated; Attempt to fix CI build > maven-deploy-plugin is updated > Tests are fixed > Dependencies are updated > wicketstuff-core-9.13.0 is released > > Martin Tzvetanov Grigorov (1): > Build only when wicket-9.x branch is modified > > muecke87 (1): > fixes issue #737 (#738) > > The WicketStuff team > -- Regards - Ernesto Reinaldo Barreiro
Re: addying support for upload to resource
https://github.com/apache/wicket/pull/571 On Wed, Mar 22, 2023 at 9:26 PM Matt Pavlovich wrote: > +1 that’d be great! Especially w/ ability to have visibility to progress. > > > On Mar 15, 2023, at 5:25 AM, Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > > Hi, > > > > In our application we are heavily using web socket push (repainting web > > wicket components via web-socket push). One problem we found is that in > > some pages we have some uploads and those uploads can be very large, and > > while they are happening the page is "frozen" and no new web socket > > messages are received. Because of that, I have implemented a custom > upload > > to a wicket resource. In essence some adaptation of > > > > > https://github.com/martin-g/blogs/blob/master/file-upload/src/main/java/com/mycompany/fileupload/AbstractFileUploadResource.java > > > > > > But I also had to adapt the upload progress bar in order to be able to > > report progress upload. Would this be something interesting to have in > > a "generic" way in Wicket itself? > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > -- Regards - Ernesto Reinaldo Barreiro
Re: addying support for upload to resource
FYI: https://issues.apache.org/jira/browse/WICKET-7033 On Wed, Mar 15, 2023 at 3:22 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > On Wed, Mar 15, 2023 at 2:24 PM Martin Grigorov > wrote: > >> On Wed, Mar 15, 2023 at 2:16 PM Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >> > Ok. Then I will create an issue... Things I will try to achieve: >> > >> > >> >- Upload to a resource in an asynchronous non page blocking request >> >- Add an optional way to block the user from leaving the page while >> the >> >upload is happening >> >- Ways to cancel the upload >> >- Adapt the upload progress bar to work with this new "component" and >> >improve its code as in some corner cases it is producing client side >> > errors >> >(I created an issue for that some time ago). >> >- Maybe useful too: create a web socket based progress bar, as the >> >upload progress bar now works pulling the server every second. >> > >> > Shall this work be done for 10.x only or two for 9.x? I think both >> would be >> > good. >> > >> >> Both is fine! >> >> I think it would be good also to add an example to wicket-examples that >> uses a smart JS uploader, llike in the blog. >> This way you will verify that the new APIs are easily extendable. >> > > Very good idea! > > >> >> >> > >> > On Wed, Mar 15, 2023 at 1:59 PM Martin Grigorov >> > wrote: >> > >> > > On Wed, Mar 15, 2023 at 12:25 PM Ernesto Reinaldo Barreiro < >> > > reier...@gmail.com> wrote: >> > > >> > > > Hi, >> > > > >> > > > In our application we are heavily using web socket push (repainting >> web >> > > > wicket components via web-socket push). One problem we found is >> that in >> > > > some pages we have some uploads and those uploads can be very large, >> > and >> > > > while they are happening the page is "frozen" and no new web socket >> > > > messages are received. Because of that, I have implemented a custom >> > > upload >> > > > to a wicket resource. In essence some adaptation of >> > > > >> > > > >> > > > >> > > >> > >> https://github.com/martin-g/blogs/blob/master/file-upload/src/main/java/com/mycompany/fileupload/AbstractFileUploadResource.java >> > > > >> > > > >> > > > But I also had to adapt the upload progress bar in order to be able >> to >> > > > report progress upload. Would this be something interesting to have >> in >> > > > a "generic" way in Wicket itself? >> > > > >> > > >> > > +1 >> > > I think it would be a good addition! >> > > >> > > >> > > >> > > > >> > > > >> > > > -- >> > > > Regards - Ernesto Reinaldo Barreiro >> > > > >> > > >> > >> > >> > -- >> > Regards - Ernesto Reinaldo Barreiro >> > >> > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: addying support for upload to resource
Hi, On Wed, Mar 15, 2023 at 2:24 PM Martin Grigorov wrote: > On Wed, Mar 15, 2023 at 2:16 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Ok. Then I will create an issue... Things I will try to achieve: > > > > > >- Upload to a resource in an asynchronous non page blocking request > >- Add an optional way to block the user from leaving the page while > the > >upload is happening > >- Ways to cancel the upload > >- Adapt the upload progress bar to work with this new "component" and > >improve its code as in some corner cases it is producing client side > > errors > >(I created an issue for that some time ago). > >- Maybe useful too: create a web socket based progress bar, as the > >upload progress bar now works pulling the server every second. > > > > Shall this work be done for 10.x only or two for 9.x? I think both would > be > > good. > > > > Both is fine! > > I think it would be good also to add an example to wicket-examples that > uses a smart JS uploader, llike in the blog. > This way you will verify that the new APIs are easily extendable. > Very good idea! > > > > > > On Wed, Mar 15, 2023 at 1:59 PM Martin Grigorov > > wrote: > > > > > On Wed, Mar 15, 2023 at 12:25 PM Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > Hi, > > > > > > > > In our application we are heavily using web socket push (repainting > web > > > > wicket components via web-socket push). One problem we found is that > in > > > > some pages we have some uploads and those uploads can be very large, > > and > > > > while they are happening the page is "frozen" and no new web socket > > > > messages are received. Because of that, I have implemented a custom > > > upload > > > > to a wicket resource. In essence some adaptation of > > > > > > > > > > > > > > > > > > https://github.com/martin-g/blogs/blob/master/file-upload/src/main/java/com/mycompany/fileupload/AbstractFileUploadResource.java > > > > > > > > > > > > But I also had to adapt the upload progress bar in order to be able > to > > > > report progress upload. Would this be something interesting to have > in > > > > a "generic" way in Wicket itself? > > > > > > > > > > +1 > > > I think it would be a good addition! > > > > > > > > > > > > > > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: addying support for upload to resource
Ok. Then I will create an issue... Things I will try to achieve: - Upload to a resource in an asynchronous non page blocking request - Add an optional way to block the user from leaving the page while the upload is happening - Ways to cancel the upload - Adapt the upload progress bar to work with this new "component" and improve its code as in some corner cases it is producing client side errors (I created an issue for that some time ago). - Maybe useful too: create a web socket based progress bar, as the upload progress bar now works pulling the server every second. Shall this work be done for 10.x only or two for 9.x? I think both would be good. On Wed, Mar 15, 2023 at 1:59 PM Martin Grigorov wrote: > On Wed, Mar 15, 2023 at 12:25 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > In our application we are heavily using web socket push (repainting web > > wicket components via web-socket push). One problem we found is that in > > some pages we have some uploads and those uploads can be very large, and > > while they are happening the page is "frozen" and no new web socket > > messages are received. Because of that, I have implemented a custom > upload > > to a wicket resource. In essence some adaptation of > > > > > > > https://github.com/martin-g/blogs/blob/master/file-upload/src/main/java/com/mycompany/fileupload/AbstractFileUploadResource.java > > > > > > But I also had to adapt the upload progress bar in order to be able to > > report progress upload. Would this be something interesting to have in > > a "generic" way in Wicket itself? > > > > +1 > I think it would be a good addition! > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
addying support for upload to resource
Hi, In our application we are heavily using web socket push (repainting web wicket components via web-socket push). One problem we found is that in some pages we have some uploads and those uploads can be very large, and while they are happening the page is "frozen" and no new web socket messages are received. Because of that, I have implemented a custom upload to a wicket resource. In essence some adaptation of https://github.com/martin-g/blogs/blob/master/file-upload/src/main/java/com/mycompany/fileupload/AbstractFileUploadResource.java But I also had to adapt the upload progress bar in order to be able to report progress upload. Would this be something interesting to have in a "generic" way in Wicket itself? -- Regards - Ernesto Reinaldo Barreiro
Re: data persistence using hibernate
Hi James, On Thu, Dec 22, 2022 at 2:24 PM James wrote: > Thanks for the guidance so far, that pointed me to find additional > resources on JPA > I believe I have this configured correctly, but I'm confused about how > to integrate JPA/Hibernate into a > pure wicket authenticated web application project since the resource you > directed me to previously > seems to be more heavily on the spring side of things. > This is true. I have used Hibernate/JPA without the SpringBoot parts... But those projects are private: some owned by me, others no. > Thank you for accommodating all my questions and misunderstandings so > far, I tend to use a reverse > engineer learning style so it's helped me immensely. > > Glad to be of some help. This is why this place is for. > I've included screenshots of the project file list and the application > class in the hopes that it makes > They didn't > understanding what I'm trying to convey easier > > Best Regards > James Pollard > james.poll...@iinet.net.au > > On 20/12/22 12:58 pm, Ernesto Reinaldo Barreiro wrote: > > > https://github.com/MarcGiffing/wicket-spring-boot/blob/master/wicket-spring-boot-starter-example/src/main/java/com/giffing/wicket/spring/boot/example/model/Customer.java > > > > This defines a JPA entity and this JPA/Hibernate > > > > > https://github.com/MarcGiffing/wicket-spring-boot/blob/master/wicket-spring-boot-starter-example/src/main/resources/application.yml > > > > Project uses Spring magic I guess and will start a Hibernate with H2. > > Wicket is also started via SpringBoot. > > > > > > On Tue, Dec 20, 2022 at 7:44 AM James > wrote: > > > >> I've had a look through it but couldn't find any reference to hibernate > >> so far, its entirely > >> possible that I managed to miss it while I was searching though > >> > >> Best Regards > >> James Pollard > >> james.poll...@iinet.net.au > >> > >> On 19/12/22 5:06 pm, Ernesto Reinaldo Barreiro wrote: > >>> Hi, > >>> > >>> This project > >>> > >>> https://github.com/MarcGiffing/wicket-spring-boot > >>> > >>> contains a sample project that integrates with JPA/hibernate. > >>> > >>> > >>> On Mon, Dec 19, 2022 at 9:12 AM James > >> wrote: > >>>> Hi, > >>>> can anyone direct me to any resources on how to integrate hibernate > for > >>>> data persistence? > >>>> > >>>> the closest I've managed to find is > >>>> > >>>> > >> > https://www.infoworld.com/article/2077901/web-development-with-wicket--part-3--many-ways-to-persist.html?page=7 > >>>> but there's still things that are confusing me on how to ingrate an > >>>> authenticated application with hibernate > >>>> > >>>> -- > >>>> Best Regards > >>>> James Pollard > >>>> james.poll...@iinet.net.au > >>>> > >>>> > >>>> --------- > >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>>> For additional commands, e-mail: users-h...@wicket.apache.org > >>>> > >>>> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org -- Regards - Ernesto Reinaldo Barreiro
Re: data persistence using hibernate
https://github.com/MarcGiffing/wicket-spring-boot/blob/master/wicket-spring-boot-starter-example/src/main/java/com/giffing/wicket/spring/boot/example/model/Customer.java This defines a JPA entity and this JPA/Hibernate https://github.com/MarcGiffing/wicket-spring-boot/blob/master/wicket-spring-boot-starter-example/src/main/resources/application.yml Project uses Spring magic I guess and will start a Hibernate with H2. Wicket is also started via SpringBoot. On Tue, Dec 20, 2022 at 7:44 AM James wrote: > I've had a look through it but couldn't find any reference to hibernate > so far, its entirely > possible that I managed to miss it while I was searching though > > Best Regards > James Pollard > james.poll...@iinet.net.au > > On 19/12/22 5:06 pm, Ernesto Reinaldo Barreiro wrote: > > Hi, > > > > This project > > > > https://github.com/MarcGiffing/wicket-spring-boot > > > > contains a sample project that integrates with JPA/hibernate. > > > > > > On Mon, Dec 19, 2022 at 9:12 AM James > wrote: > > > >> Hi, > >> can anyone direct me to any resources on how to integrate hibernate for > >> data persistence? > >> > >> the closest I've managed to find is > >> > >> > https://www.infoworld.com/article/2077901/web-development-with-wicket--part-3--many-ways-to-persist.html?page=7 > >> but there's still things that are confusing me on how to ingrate an > >> authenticated application with hibernate > >> > >> -- > >> Best Regards > >> James Pollard > >> james.poll...@iinet.net.au > >> > >> > >> - > >> 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: data persistence using hibernate
Hi, This project https://github.com/MarcGiffing/wicket-spring-boot contains a sample project that integrates with JPA/hibernate. On Mon, Dec 19, 2022 at 9:12 AM James wrote: > Hi, > can anyone direct me to any resources on how to integrate hibernate for > data persistence? > > the closest I've managed to find is > > https://www.infoworld.com/article/2077901/web-development-with-wicket--part-3--many-ways-to-persist.html?page=7 > but there's still things that are confusing me on how to ingrate an > authenticated application with hibernate > > -- > Best Regards > James Pollard > james.poll...@iinet.net.au > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Ajax - component not rendered.
Hi,
is devicesGroup initially visible? if not you need to
setOutputMarkupplaceHolder(true) in it. Because otherwise wicket will not
output anything for it and AJAX replacement will fail at client side.
On Fri, Oct 28, 2022 at 4:27 PM Martin Grigorov
wrote:
> Hi Laurent,
>
> Few questions:
> 1) is the Ajax call actually executed ?
> Set a breakpoint inside #onClick() and see whether it breaks
> 2) Is there any error (Java or JavaScript) ?
> Check both the server logs and the browser console
>
>
> On Fri, Oct 28, 2022 at 10:45 AM Laurent Duparchy
> wrote:
>
> > Hi,
> >
> > Sorry for the basic question If this is the wrong place to ask,
> please
> > tell me.
> > If there is a relevant documentation to read, tell me as well.
> >
> > I'm upgrading a very old & small app from Wicket 1.4 to Wicket 9.
> >
> > Following an Ajax call, one component is not refreshed as it was before.
> >
> > This is the "userDevicesListView" which is inside the "devicesGroup"
> > component. See below.
> >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> >
> > Upon the Ajax call the userDevicesListView is changed and devicesGroup is
> > added to the target and should be rendered / repainted but it is not.
> >
> > > public void onClick(Optional target) {
> > > Device deviceToRemove = (Device) getModelObject();
> > > try {
> > > removeDevice(deviceToRemove, user);
> > > info(deviceToRemove.getHostName() + " " +
> > getString("device.removed"));
> > > } catch (Exception e) {
> > >
> > > LOG.error("error while deleting" +
> > deviceToRemove.getHostName(), e);
> > > error(e);
> > >
> > > }
> > >
> > > target.get().add(devicesGroup);
> > > target.get().add(feedbackPanel);
> > > }
> >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
--
Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 9.12.0 released
Thanks!
On Sat, Oct 15, 2022 at 8:52 PM Andrea Del Bene wrote:
> The Apache Wicket PMC is proud to announce Apache Wicket 9.12.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.12.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.12.0:
>
> ** Bug
>
> * [WICKET-6955] - Wicket uses unstable slf4j version
> * [WICKET-6996] - NotSerializableException near
> KeyInSessionSunJceCryptFactory
> * [WICKET-6999] - Missing Export-Package of packages with
> "internal" in name
> * [WICKET-7007] - Code snippets for CSRF documentation fixing
>
> ** Improvement
>
> * [WICKET-6958] - Allow to use Slf4j 1.7.x in OSGi runtime
> * [WICKET-6982] - Unnecessary initialization of stateful pages in
> ListenerRequestHandler
> * [WICKET-6998] - Bump slf4j-api to 2.0.0
> * [WICKET-7000] - ParseException ("Malformed tag") if
Re: Is there any way to get an error message when uploading a file that exceeds the size limit?
Thanks for the info On Sat, Jun 11, 2022 at 2:20 AM Ryo Tsunoda wrote: > > https://github.com/try0/wicket-fileupload-example/blob/main/wicket-fileupload-example-app/src/main/java/jp/try0/wicket/example/fileupload/HomePage.java#L52 > > if this line uncomment, FilesSelectedBehavior#onSelected is not fired. > > 2022年6月10日(金) 23:18 Ryo Tsunoda : > > > >Hum... if you can explain more I would appreciate it... because maybe > > this can be improved in Wicket itself. > > > > If use FileUploadField#setRequired(true), FormComponent #validateRequired > > -> #checkRequired will be executed. > > But FileUploadField#getInput() returns null, so validation result in an > > error. > > Therefore, It seems that the Behavior's(FilesSelectedBehavior) event that > > FileUploadField has is not fired. > > > > 2022年6月10日(金) 21:19 Ernesto Reinaldo Barreiro : > > > >> Hi, > >> > >> On Fri, Jun 10, 2022 at 2:31 PM Ryo Tsunoda > > >> wrote: > >> > >> > Thanks for the reply. > >> > > >> > I have tried it and I can display the error without changing the > request > >> > limit. > >> > Thank you. > >> > > >> > >> Yes. This is just a kind of preprocessing. When the file (files) is > (are) > >> selected the info is collected via JavaScript and is sent to the server. > >> Thus you can decide what to do before uploading: e.g an upload button > >> might > >> only be enabled if file (files) match your expectations regarding type, > >> syze and so on. > >> > >> > >> > It does not seem to work well when used with > >> FileUploadField#setRequired. > >> > I will change the implementation of the required validation and then > use > >> > that. > >> > > >> Hum... if you can explain more I would appreciate it... because maybe > this > >> can be improved in Wicket itself. > >> > >> > >> > >> > > >> > 2022年6月10日(金) 16:21 Ernesto Reinaldo Barreiro : > >> > > >> > > See > >> > > > >> > > > >> > > > >> > > >> > https://javadoc.io/doc/org.apache.wicket/wicket-core/9.4.0/org/apache/wicket/markup/html/form/upload/FilesSelectedBehavior.html > >> > > > >> > > This behavior can be used to get an AJAX round trip to the server > when > >> > the > >> > > user selects a file (or files). Then you can use that information to > >> let > >> > > the user know the selected file is bigger than it should (and > possibly > >> > > disable the upload "button"). > >> > > > >> > > > >> > > On Thu, Jun 9, 2022 at 2:57 PM Ryo Tsunoda < > >> try0.developm...@gmail.com> > >> > > wrote: > >> > > > >> > > > Hi. > >> > > > > >> > > > Looking at Form#onFileUploadException, I see that it sets an error > >> > > message > >> > > > (resource key: uploadTooLarge), is there any way to display this > >> error > >> > in > >> > > > the browser? > >> > > > > >> > > > I use Form#setMaxSize and > >> > ApplicationSettings#setDefaultMaximumUploadSize > >> > > > methods. > >> > > > When I upload a file that exceeds these settings, I would like to > >> > return > >> > > a > >> > > > response with an error message and display it on browser. However, > >> the > >> > > > browser displays [ERR_CONNECTION_RESET] now. > >> > > > > >> > > > > >> > > > Regards, > >> > > > Ryo Tsunoda. > >> > > > > >> > > > >> > > > >> > > -- > >> > > Regards - Ernesto Reinaldo Barreiro > >> > > > >> > > >> > >> > >> -- > >> Regards - Ernesto Reinaldo Barreiro > >> > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Is there any way to get an error message when uploading a file that exceeds the size limit?
Hi, On Fri, Jun 10, 2022 at 2:31 PM Ryo Tsunoda wrote: > Thanks for the reply. > > I have tried it and I can display the error without changing the request > limit. > Thank you. > Yes. This is just a kind of preprocessing. When the file (files) is (are) selected the info is collected via JavaScript and is sent to the server. Thus you can decide what to do before uploading: e.g an upload button might only be enabled if file (files) match your expectations regarding type, syze and so on. > It does not seem to work well when used with FileUploadField#setRequired. > I will change the implementation of the required validation and then use > that. > Hum... if you can explain more I would appreciate it... because maybe this can be improved in Wicket itself. > > 2022年6月10日(金) 16:21 Ernesto Reinaldo Barreiro : > > > See > > > > > > > https://javadoc.io/doc/org.apache.wicket/wicket-core/9.4.0/org/apache/wicket/markup/html/form/upload/FilesSelectedBehavior.html > > > > This behavior can be used to get an AJAX round trip to the server when > the > > user selects a file (or files). Then you can use that information to let > > the user know the selected file is bigger than it should (and possibly > > disable the upload "button"). > > > > > > On Thu, Jun 9, 2022 at 2:57 PM Ryo Tsunoda > > wrote: > > > > > Hi. > > > > > > Looking at Form#onFileUploadException, I see that it sets an error > > message > > > (resource key: uploadTooLarge), is there any way to display this error > in > > > the browser? > > > > > > I use Form#setMaxSize and > ApplicationSettings#setDefaultMaximumUploadSize > > > methods. > > > When I upload a file that exceeds these settings, I would like to > return > > a > > > response with an error message and display it on browser. However, the > > > browser displays [ERR_CONNECTION_RESET] now. > > > > > > > > > Regards, > > > Ryo Tsunoda. > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Is there any way to get an error message when uploading a file that exceeds the size limit?
See https://javadoc.io/doc/org.apache.wicket/wicket-core/9.4.0/org/apache/wicket/markup/html/form/upload/FilesSelectedBehavior.html This behavior can be used to get an AJAX round trip to the server when the user selects a file (or files). Then you can use that information to let the user know the selected file is bigger than it should (and possibly disable the upload "button"). On Thu, Jun 9, 2022 at 2:57 PM Ryo Tsunoda wrote: > Hi. > > Looking at Form#onFileUploadException, I see that it sets an error message > (resource key: uploadTooLarge), is there any way to display this error in > the browser? > > I use Form#setMaxSize and ApplicationSettings#setDefaultMaximumUploadSize > methods. > When I upload a file that exceeds these settings, I would like to return a > response with an error message and display it on browser. However, the > browser displays [ERR_CONNECTION_RESET] now. > > > Regards, > Ryo Tsunoda. > -- Regards - Ernesto Reinaldo Barreiro
Re: Written in Wicket, OneDev UI is 10x~30x faster than GitLab
Thanks for sharing and for using Wicket! On Tue, May 31, 2022 at 10:04 AM OneDev wrote: > Dear wicket users, > > Just want to share my recent performance comparison of OneDev, which is > written in Wicket, with GitLab: > > > https://robinshen.medium.com/performance-compasion-of-onedev-and-gitlab-c11fc27b25be > > Robin > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 9.10.0 released
Many thanks for taking care of releases! On Thu, May 5, 2022 at 3:46 PM Andrea Del Bene wrote: > The Apache Wicket PMC is proud to announce Apache Wicket 9.10.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.10.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.10.0: > > ** Bug > > * [WICKET-6970] - Unnecessary string building in > AssociatedMarkupSourcingStrategy > * [WICKET-6971] - NullPointerException in ModificationWatcher > * [WICKET-6974] - JavaxUpgradeHttpRequest returns an empty contextPath > * [WICKET-6975] - Behavior.renderHead may be called multiple times > > ** Improvement > > * [WICKET-6963] - Use singletons for PanelMarkupSourcingStrategy > * [WICKET-6967] - allow to send non-blocking web socket messages > * [WICKET-6969] - allow to process web socket push messages in an > asynchronous way. > * [WICKET-6972] - Add Resource key to be logged on Warning in > Localizer.java > * [WICKET-6976] - Reduce allocations when writing synthetic closing > tags > * [WICKET-6977] - hashCode computations generate excessive garbage > objects > > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.10.0 Released
Thanks! On Fri, May 6, 2022 at 6:23 AM Maxim Solodovnik wrote: > WicketStuff core 9.10.0 based on Apache Wicket 9.10.0 is released > and soon will be available at Maven Central! > > Maxim Solodovnik (3): > Switching to the next development version > Dependencies are updated > wicketstuff-core-9.10.0 is released > > The WicketStuff team > -- Regards - Ernesto Reinaldo Barreiro
Re: module error
This is then the problem :-) Thanks to you for Wicket :-) On Sun, Feb 20, 2022 at 1:00 AM Locke, Jonathan (Luo Shibo) < jonath...@telenav.com> wrote: > Yes, I checked. I don't. > > From: Maxim Solodovnik > Sent: Saturday, February 19, 2022 8:11 PM > To: users@wicket.apache.org > Subject: Re: module error > > from mobile (sorry for typos ;) > > > On Sun, Feb 20, 2022, 02:41 Locke, Jonathan (Luo Shibo) < > jonath...@telenav.com> wrote: > > > I don't think I'm a committer anymore. It's been at least a decade since > > my last commit. > > > > Commitership shouldn't be dropped due to inactivity > > Can you check if you have your github login at id.apache.org ? > > > I'm amazed that wicket is still going strong. In two years it will be 20 > > years of Wicket. > > > >Jon > > > > > > From: Maxim Solodovnik > > Sent: Saturday, February 19, 2022 5:57 AM > > To: users@wicket.apache.org > > Subject: Re: module error > > > > from mobile (sorry for typos ;) > > > > > > On Sat, Feb 19, 2022, 19:20 Ernesto Reinaldo Barreiro < > reier...@gmail.com> > > wrote: > > > > > No if you are a committer :-) > > > > > > > Commiter will never see 403 :) > > > > > > > > On Fri, Feb 18, 2022 at 11:44 PM Maxim Solodovnik < > solomax...@gmail.com> > > > wrote: > > > > > > > On Sat, 19 Feb 2022 at 03:04, Locke, Jonathan (Luo Shibo) < > > > > jonath...@telenav.com> wrote: > > > > > > > > > Hi Martin, > > > > > > > > > > I was able to fix the problem as you suggested by adding: > > > > > > > > > > uses org.apache.wicket.IInitializer; > > > > > > > > > > to > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fmodule-info.java=E,1,WO4T_dAL8ww57jzExgL1QE2YUg9PSzf2JkCUtz233hgGolAnoaigRG7sFCy0R4-qUwC5-Hx7dj3RPzsVYEU2af8Pfa75fVWyNkUJcZk3X0YerNK-FcxQ=1 > > in wicket-core. I created a pull request, but got > > > an > > > > > error trying to push it in IntelliJ: > > > > > > > > > > Can't create a new pull request: Push failed: remote: Permission to > > > > > apache/wicket.git denied to jonathanlocke. unable to access ' > > > > > https://github.com/apache/wicket.git/': The requested URL returned > > > > error: > > > > > 403 > > > > > > > > > > > > > You need to fork the repo first :) > > > > > > > > > > > > > > > > > > Could we add this as a patch release to wicket 9.8.x? > > > > > > > > > > Thanks, > > > > > > > > > > Jon > > > > > > > > > > From: Martin Grigorov > > > > > Sent: Friday, February 18, 2022 2:55 AM > > > > > To: users@wicket.apache.org > > > > > Subject: Re: module error > > > > > > > > > > Hm. > > > > > Looking at https://github.com/qos-ch/logback/commit/5186d2604b460f > I > > > > think > > > > > we need the 'uses' only in the module where we call > > > ServiceLoader.load(), > > > > > i.e. in wicket-core. > > > > > > > > > > On Fri, Feb 18, 2022 at 11:53 AM Martin Grigorov < > > mgrigo...@apache.org > > > > > > > > > wrote: > > > > > > > > > > > Hi Jon, > > > > > > > > > > > > According to > > > > > > > > > > > > > > > > > > > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.oracle.com%2fcorporate%2ffeatures%2funderstanding-java-9-modules.html=E,1,AlcuJddqQ1zhtdsihzDbje23huNpDs6zcgn19JZMXP_Y1UGGpZLts-DudDYPcu75JyHkjFHLNGJw3KmnkhBiyTndIjuRNCIVCuhKfLjxxCsCSVE,=1 > > > > > > > > > > > > *provides…with.* A provides…with module directive specifies that > a > > > > module > > > > > > provides a service implementation—making the module a *service > > > > provider*. > > > > > > The provides part of the directive specifies an interface or > > abstract > > > > > > class listed in a module’s uses directive and the with part of > the > > > > > > directive specifies the name of the service provider class t
Re: module error
vc.com/url?a=https%3a%2f%2fApplication.java%3a765=E,1,53VvaIOZTG7mETf35tkUcXDXfgaVHqiw29gxxq_4y_ZXHn8AGzbIbtFXR4tf6Oh_rbl7mOLXjgPBeEW3-pd7jBqEp-30i2WA26_CdN5uIVJtHsjBDJuep4DVDA,,=1 > > ) > > >> at org.apache.wicket.core@9.6.0 > > >> /org.apache.wicket.protocol.http.WicketFilter.init( > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fWicketFilter.java%3a441=E,1,He0Z2RxpNcC-ziRHqyjYFORYOn-LK_eNOZGT9zHWjBKPv3GAhtI8TUG2W-9YOiYdW6_ArVy_6GMjKIt_0nLh3u0FHuh0H-pscUXDZj11B8s,=1 > > ) > > >> at org.apache.wicket.core@9.6.0 > > >> /org.apache.wicket.protocol.http.WicketFilter.init( > > > https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fWicketFilter.java%3a365=E,1,yo_2tJnAV4qbr-cq49OMx3sq4HWonvaqycQkJ_db-wYcUtt-8EyuDB-_tz0hjwH9lQgYN9mHJniiRilRX9pL2VXbKQEd6QnNcrLzbwVOzRzTSmM,=1 > > ) > > >> > > >> > > [EXTERNAL EMAIL] CAUTION: This email originated from outside of Telenav. > > DO NOT CLICK links or attachments unless you recognize the sender and > know > > the content is safe. > > > > > -- > Best regards, > Maxim > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 8.14.0 released
Many thanks for the release! On Wed, Feb 2, 2022 at 3:45 PM Andrea Del Bene wrote: > The Apache Wicket PMC is proud to announce Apache Wicket 8.14.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 8. We > use semantic versioning for the development of Wicket, and as such no > API breaks are present in this release compared to 8.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 > 8.14.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-8.x.html#manually > > Upgrading from earlier versions > --- > > If you upgrade from 8.y.z this release is a drop in replacement. If > you come from a version prior to 8.0.0, please read our Wicket 8 > migration guide found at > > * http://s.apache.org/wicket8migrate > > Have fun! > > — The Wicket team > > > > > CHANGELOG for 8.14.0: > > ** Bug > > * [WICKET-6908] - Possible bug / edge case where page is not detached > * [WICKET-6910] - StalePageException not thrown > * [WICKET-6914] - Visibility change of "File Upload" via ajax > causes "missing" form-data > * [WICKET-6931] - User guide: 'determinate' is not a verb; should > be changed into 'to determine' > * [WICKET-6944] - Memory leak in WicketEndpoint > * [WICKET-6945] - MultipartFormComponentListener modifies enctype > on invisible forms, leading to javascript errors > > ** Task > > * [WICKET-6919] - Improve EnclosureContainer's javadoc to explain > that it should not be used with > * [WICKET-6937] - Update the keystore used by the quickstart > application > * [WICKET-6942] - Replace usage of log4j 1.x in tests and > wicket-examples with slf4j-simple > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Selenium testing
Hi,
Our app contains about 600 selenium tests... They are a pain to maintain
even when we are trying to do things "the smart way". By this we mean:
- We have some reusable wicket components. E.g. some AJAX table with
lateral filtering facets. We roll in component marker CSS classes (e.g.
.facets, .facet, .date-time-facet) + "use custom key attributes" (e.g
facet-category="").
- We mirror this component structure at client side selenium tests. i.e.
we have a FacetsDriver that hides low level complexity (e.g. FacetDriver
xxx = tableWithFacets.getFacteDriverFof("xxx") and xxx.select("aaa")).
The above works fine (mostly). Except people sometimes forget to use proper
ways and reinvent the wheel. Sometimes tests do not pass or are shaky for
no clear reason and a lot of time goes into stabilizing those. We are using
global AJAX blocker div for pages, to prevent component not found issues,
this makes very easy to have a global waitForAjaxFinished().
In summary. We run our tests on a server running in production mode. Thus
we do not use any wicket path or anything similar, we use custom CSS
classes + custom element attributes to give a more precise context.
Hope this helps?
On Mon, Jan 31, 2022 at 8:38 AM Wayne W wrote:
> Hello all,
>
> Is anyone out there successfully using Selenium to do regression testing?
> It seems with the latest version of Selenium you cannot add custom
> selectors anymore (the idea turning on
> getDebugSettings().setComponentPathAttributeName("wicketpath") ). So it
> just uses css selectors and xpath now.
>
> Whilst I can had craft css selectors to use the wicketpath attribute I
> cannot get the IDE to use this by default. The problem is I want to hand
> this over to our QA person but she is not technical nature and would
> struggle to understand the correct selector when looking at the code and
> also it would really slow down the whole process of setting up tests.
>
> Anyone got Selenium working well, or can recommend another tool for web
> regressing testing that works well with Wicket?
>
> thanks
>
--
Regards - Ernesto Reinaldo Barreiro
Re: initialializers documentation
Thanks for your super fast reply. On Wed, Jan 19, 2022 at 4:16 PM Sven Meier wrote: > Hi Ernesto, > > yes, that is outdated, see > > https://issues.apache.org/jira/browse/WICKET-5997 > > Sven > > > On 19.01.22 16:10, Ernesto Reinaldo Barreiro wrote: > > Hi, > > > > A colleague pointed me to > > > > https://nightlies.apache.org/wicket/guide/9.x/single.html#_initializers > > > > and remarked that we are using them differently. I digged the source code > > and it seems this is now working by means of > > > > https://docs.oracle.com/javase/9/docs/api/java/util/ServiceLoader.html > > > > Is the documentation outdated? > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
initialializers documentation
Hi, A colleague pointed me to https://nightlies.apache.org/wicket/guide/9.x/single.html#_initializers and remarked that we are using them differently. I digged the source code and it seems this is now working by means of https://docs.oracle.com/javase/9/docs/api/java/util/ServiceLoader.html Is the documentation outdated? -- Regards - Ernesto Reinaldo Barreiro
Re: wicket:child
Hi, You can do what you want using DIVs and protected factory methods. Thus you have extension points where you can plug custom "panels". On Sun, Jan 9, 2022 at 1:56 PM vahid ghasemi wrote: > Hello, > How can I use 2 wicket:child for 1 inherited class? > Like this: > > Hello > > Hello > > > > > Hello again > > Hello again > -- Regards - Ernesto Reinaldo Barreiro
stress/load testing wicket application
Hi smart guys in the list, What would you use if you need to test how a wicket application behaves under stress? Taking into account we have a heavily AJAXified application and many heavy operations are just triggered AJAX-navigating pages. We have some fair amount of selenium tests covering our application (most of them very consistent). How would you go about this task? Many thanks in advance! -- Regards - Ernesto Reinaldo Barreiro
Re: exception in windows while using FilePageStore
https://issues.apache.org/jira/browse/WICKET-6936 On Thu, Nov 18, 2021 at 1:10 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi Sven, > > Many thanks for your answer. > > On Thu, Nov 18, 2021 at 12:36 PM Sven Meier wrote: > >> Hi Ernesto, >> >> I've tested FilePageStore without TRUNCATE_EXISTING - in that case the >> file will not shrink, when the page has reduced its size. >> > Ok. > >> >> Luckily this doesn't disturb Java's default deserialization, the excess >> is just ignored. >> But what if a project uses another serializer? >> >> Good point. For us something like this will be enough: > > https://github.com/apache/wicket/pull/484 > > > >> Regards >> >> Sven >> >> >> On 17.11.21 10:57, Ernesto Reinaldo Barreiro wrote: >> > Hi Sven, >> > >> > Getting rid of the StandardOpenOption.TRUNCATE_EXISTING here >> > >> > >> https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/pageStore/FilePageStore.java#L189 >> > >> > seems to "fix" the problem in windows and I also do not see problems in >> > linux. To be honest I have no idea of the full implications of this >> change. >> > >> > >> > >> > On Tue, Nov 16, 2021 at 11:40 PM Sven Meier wrote: >> > >> >> Hi Ernesto, >> >> >> >> I'm no expert in this, but as I understood it FileChannel should be >> save >> >> to be written to in parallel: >> >> >> >> >> >> >> https://docs.oracle.com/javase/1.5.0/docs/api/java/nio/channels/FileChannel.html >> >> >> >> "File channels are safe for use by multiple concurrent threads. ... >> >> Only one operation that involves the channel's position or can change >> >> its file's size may be in progress at any given time; attempts to >> >> initiate a second such operation while the first is still in progress >> >> will block until the first operation completes. ... The view of a file >> >> provided by an instance of this class is guaranteed to be consistent >> >> with other views of the same file provided by other instances in the >> >> same program." >> >> >> >> This sounds related though: >> >> >> >> >> >> >> https://stackoverflow.com/questions/45441249/why-does-java-filechannel-truncate-fail-predictably-on-windows-only >> >> >> >> Regards >> >> Sven >> >> >> >> >> >> On 16.11.21 19:56, Ernesto Reinaldo Barreiro wrote: >> >>> Hi Sven, >> >>> >> >>> Many thanks for your answer. Main problem is I do not have Windows >> >>> around... this happens only in our Jenkins (which needs to be a >> windows >> >>> machine). I did some googling around and it seems it can be the >> operating >> >>> system itself if you access the same file in a very fast sequence: >> this >> >>> might be our case, as we are generating many web sockets messages >> >> (pushing >> >>> components) and this seems to trigger page serialization. >> >>> >> >>> On Linux and Mac we have no problems at all. >> >>> >> >>> >> >>> On Tue, Nov 16, 2021 at 7:28 PM Sven Meier wrote: >> >>> >> >>>> Hi Ernesto, >> >>>> >> >>>> maybe an issue with concurrent file writes? >> >>>> >> >>>> I've tested the new FilePageStore on Linux only, and as it seems I >> >>>> didn't add any synchronization to it. >> >>>> >> >>>> Could you try out FilePageStoreTest? >> >>>> >> >>>> Regards >> >>>> Sven >> >>>> >> >>>> >> >>>> On 16.11.21 16:18, Ernesto Reinaldo Barreiro wrote: >> >>>>> Hi, >> >>>>> >> >>>>> We are trying to use FilePageStore and we are getting following >> >>>>> exception (a lot of them actually) >> >>>>> >> >>>>> he requested operation cannot be performed on a file with a >> user-mapped >> >>>>> section open >> >>>>> [2021-11-16T07:34:00.699Z] at >> >>>>> >> >> >> sun.nio.fs.Windo
Re: exception in windows while using FilePageStore
Hi Sven, Many thanks for your answer. On Thu, Nov 18, 2021 at 12:36 PM Sven Meier wrote: > Hi Ernesto, > > I've tested FilePageStore without TRUNCATE_EXISTING - in that case the > file will not shrink, when the page has reduced its size. > Ok. > > Luckily this doesn't disturb Java's default deserialization, the excess > is just ignored. > But what if a project uses another serializer? > > Good point. For us something like this will be enough: https://github.com/apache/wicket/pull/484 > Regards > > Sven > > > On 17.11.21 10:57, Ernesto Reinaldo Barreiro wrote: > > Hi Sven, > > > > Getting rid of the StandardOpenOption.TRUNCATE_EXISTING here > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/pageStore/FilePageStore.java#L189 > > > > seems to "fix" the problem in windows and I also do not see problems in > > linux. To be honest I have no idea of the full implications of this > change. > > > > > > > > On Tue, Nov 16, 2021 at 11:40 PM Sven Meier wrote: > > > >> Hi Ernesto, > >> > >> I'm no expert in this, but as I understood it FileChannel should be save > >> to be written to in parallel: > >> > >> > >> > https://docs.oracle.com/javase/1.5.0/docs/api/java/nio/channels/FileChannel.html > >> > >> "File channels are safe for use by multiple concurrent threads. ... > >> Only one operation that involves the channel's position or can change > >> its file's size may be in progress at any given time; attempts to > >> initiate a second such operation while the first is still in progress > >> will block until the first operation completes. ... The view of a file > >> provided by an instance of this class is guaranteed to be consistent > >> with other views of the same file provided by other instances in the > >> same program." > >> > >> This sounds related though: > >> > >> > >> > https://stackoverflow.com/questions/45441249/why-does-java-filechannel-truncate-fail-predictably-on-windows-only > >> > >> Regards > >> Sven > >> > >> > >> On 16.11.21 19:56, Ernesto Reinaldo Barreiro wrote: > >>> Hi Sven, > >>> > >>> Many thanks for your answer. Main problem is I do not have Windows > >>> around... this happens only in our Jenkins (which needs to be a windows > >>> machine). I did some googling around and it seems it can be the > operating > >>> system itself if you access the same file in a very fast sequence: this > >>> might be our case, as we are generating many web sockets messages > >> (pushing > >>> components) and this seems to trigger page serialization. > >>> > >>> On Linux and Mac we have no problems at all. > >>> > >>> > >>> On Tue, Nov 16, 2021 at 7:28 PM Sven Meier wrote: > >>> > >>>> Hi Ernesto, > >>>> > >>>> maybe an issue with concurrent file writes? > >>>> > >>>> I've tested the new FilePageStore on Linux only, and as it seems I > >>>> didn't add any synchronization to it. > >>>> > >>>> Could you try out FilePageStoreTest? > >>>> > >>>> Regards > >>>> Sven > >>>> > >>>> > >>>> On 16.11.21 16:18, Ernesto Reinaldo Barreiro wrote: > >>>>> Hi, > >>>>> > >>>>> We are trying to use FilePageStore and we are getting following > >>>>> exception (a lot of them actually) > >>>>> > >>>>> he requested operation cannot be performed on a file with a > user-mapped > >>>>> section open > >>>>> [2021-11-16T07:34:00.699Z] at > >>>>> > >> > sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92) > >>>>> ~[?:?] > >>>>> [2021-11-16T07:34:00.699Z] at > >>>>> > >> > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) > >>>>> ~[?:?] > >>>>> [2021-11-16T07:34:00.699Z] at > >>>>> > >> > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) > >>>>> ~[?:?] > >>>>> [2021-11-16T07:34:00.699Z] at > >>>>> > >> > sun.nio.fs.WindowsFileSystemProvider.newFile
Re: exception in windows while using FilePageStore
Hi Sven, Getting rid of the StandardOpenOption.TRUNCATE_EXISTING here https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/pageStore/FilePageStore.java#L189 seems to "fix" the problem in windows and I also do not see problems in linux. To be honest I have no idea of the full implications of this change. On Tue, Nov 16, 2021 at 11:40 PM Sven Meier wrote: > Hi Ernesto, > > I'm no expert in this, but as I understood it FileChannel should be save > to be written to in parallel: > > > https://docs.oracle.com/javase/1.5.0/docs/api/java/nio/channels/FileChannel.html > > "File channels are safe for use by multiple concurrent threads. ... > Only one operation that involves the channel's position or can change > its file's size may be in progress at any given time; attempts to > initiate a second such operation while the first is still in progress > will block until the first operation completes. ... The view of a file > provided by an instance of this class is guaranteed to be consistent > with other views of the same file provided by other instances in the > same program." > > This sounds related though: > > > https://stackoverflow.com/questions/45441249/why-does-java-filechannel-truncate-fail-predictably-on-windows-only > > Regards > Sven > > > On 16.11.21 19:56, Ernesto Reinaldo Barreiro wrote: > > Hi Sven, > > > > Many thanks for your answer. Main problem is I do not have Windows > > around... this happens only in our Jenkins (which needs to be a windows > > machine). I did some googling around and it seems it can be the operating > > system itself if you access the same file in a very fast sequence: this > > might be our case, as we are generating many web sockets messages > (pushing > > components) and this seems to trigger page serialization. > > > > On Linux and Mac we have no problems at all. > > > > > > On Tue, Nov 16, 2021 at 7:28 PM Sven Meier wrote: > > > >> Hi Ernesto, > >> > >> maybe an issue with concurrent file writes? > >> > >> I've tested the new FilePageStore on Linux only, and as it seems I > >> didn't add any synchronization to it. > >> > >> Could you try out FilePageStoreTest? > >> > >> Regards > >> Sven > >> > >> > >> On 16.11.21 16:18, Ernesto Reinaldo Barreiro wrote: > >>> Hi, > >>> > >>> We are trying to use FilePageStore and we are getting following > >>> exception (a lot of them actually) > >>> > >>> he requested operation cannot be performed on a file with a user-mapped > >>> section open > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsFileSystemProvider.newFileChannel(WindowsFileSystemProvider.java:121) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> java.nio.channels.FileChannel.open(FileChannel.java:298) ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> java.nio.channels.FileChannel.open(FileChannel.java:357) ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.FilePageStore.writeFile(FilePageStore.java:188) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.FilePageStore.addPersistedPage(FilePageStore.java:178) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.AbstractPersistentPageStore.addPage(AbstractPersistentPageStore.java:128) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.AsynchronousPageStore$PageAddingRunnable.run(AsynchronousPageStore.java:292) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at java.lang.Thread.run(Thread.java:833) > [?:?] > >>> > >>> This does not happen for other operating systems. Is this a known > >>> limitation? Is there anything else that needs to be configured at > >> operating > >>> system level? > >>> > >>> Thanks in advance. > >>> > >> - > >> 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: exception in windows while using FilePageStore
Hi Sven, Many thanks for your answer and ultra fast response! On Tue, Nov 16, 2021 at 11:40 PM Sven Meier wrote: > Hi Ernesto, > > I'm no expert in this, but as I understood it FileChannel should be save > to be written to in parallel: > > > https://docs.oracle.com/javase/1.5.0/docs/api/java/nio/channels/FileChannel.html > > "File channels are safe for use by multiple concurrent threads. ... > Only one operation that involves the channel's position or can change > its file's size may be in progress at any given time; attempts to > initiate a second such operation while the first is still in progress > will block until the first operation completes. ... The view of a file > provided by an instance of this class is guaranteed to be consistent > with other views of the same file provided by other instances in the > same program." > > This sounds related though: > > > https://stackoverflow.com/questions/45441249/why-does-java-filechannel-truncate-fail-predictably-on-windows-only Yes I hit some other posts similar to this one. We have other team members looking at this too and any answer they found we will come back to you. If there is anything that can be improved at wicket level (e.g. documentation on how to use this in windows) we will share what we found. Many thanks again! > > > Regards > Sven > > > On 16.11.21 19:56, Ernesto Reinaldo Barreiro wrote: > > Hi Sven, > > > > Many thanks for your answer. Main problem is I do not have Windows > > around... this happens only in our Jenkins (which needs to be a windows > > machine). I did some googling around and it seems it can be the operating > > system itself if you access the same file in a very fast sequence: this > > might be our case, as we are generating many web sockets messages > (pushing > > components) and this seems to trigger page serialization. > > > > On Linux and Mac we have no problems at all. > > > > > > On Tue, Nov 16, 2021 at 7:28 PM Sven Meier wrote: > > > >> Hi Ernesto, > >> > >> maybe an issue with concurrent file writes? > >> > >> I've tested the new FilePageStore on Linux only, and as it seems I > >> didn't add any synchronization to it. > >> > >> Could you try out FilePageStoreTest? > >> > >> Regards > >> Sven > >> > >> > >> On 16.11.21 16:18, Ernesto Reinaldo Barreiro wrote: > >>> Hi, > >>> > >>> We are trying to use FilePageStore and we are getting following > >>> exception (a lot of them actually) > >>> > >>> he requested operation cannot be performed on a file with a user-mapped > >>> section open > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > sun.nio.fs.WindowsFileSystemProvider.newFileChannel(WindowsFileSystemProvider.java:121) > >>> ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> java.nio.channels.FileChannel.open(FileChannel.java:298) ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> java.nio.channels.FileChannel.open(FileChannel.java:357) ~[?:?] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.FilePageStore.writeFile(FilePageStore.java:188) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.FilePageStore.addPersistedPage(FilePageStore.java:178) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.AbstractPersistentPageStore.addPage(AbstractPersistentPageStore.java:128) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at > >>> > >> > org.apache.wicket.pageStore.AsynchronousPageStore$PageAddingRunnable.run(AsynchronousPageStore.java:292) > >>> [wicket-core-9.6.0.jar:9.6.0] > >>> [2021-11-16T07:34:00.699Z] at java.lang.Thread.run(Thread.java:833) > [?:?] > >>> > >>> This does not happen for other operating systems. Is this a known > >>> limitation? Is there anything else that needs to be configured at > >> operating > >>> system level? > >>> > >>> Thanks in advance. > >>> > >> - > >> 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: exception in windows while using FilePageStore
Hi Sven, Many thanks for your answer. Main problem is I do not have Windows around... this happens only in our Jenkins (which needs to be a windows machine). I did some googling around and it seems it can be the operating system itself if you access the same file in a very fast sequence: this might be our case, as we are generating many web sockets messages (pushing components) and this seems to trigger page serialization. On Linux and Mac we have no problems at all. On Tue, Nov 16, 2021 at 7:28 PM Sven Meier wrote: > Hi Ernesto, > > maybe an issue with concurrent file writes? > > I've tested the new FilePageStore on Linux only, and as it seems I > didn't add any synchronization to it. > > Could you try out FilePageStoreTest? > > Regards > Sven > > > On 16.11.21 16:18, Ernesto Reinaldo Barreiro wrote: > > Hi, > > > > We are trying to use FilePageStore and we are getting following > > exception (a lot of them actually) > > > > he requested operation cannot be performed on a file with a user-mapped > > section open > > [2021-11-16T07:34:00.699Z] at > > > sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92) > > ~[?:?] > > [2021-11-16T07:34:00.699Z] at > > > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) > > ~[?:?] > > [2021-11-16T07:34:00.699Z] at > > > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) > > ~[?:?] > > [2021-11-16T07:34:00.699Z] at > > > sun.nio.fs.WindowsFileSystemProvider.newFileChannel(WindowsFileSystemProvider.java:121) > > ~[?:?] > > [2021-11-16T07:34:00.699Z] at > > java.nio.channels.FileChannel.open(FileChannel.java:298) ~[?:?] > > [2021-11-16T07:34:00.699Z] at > > java.nio.channels.FileChannel.open(FileChannel.java:357) ~[?:?] > > [2021-11-16T07:34:00.699Z] at > > > org.apache.wicket.pageStore.FilePageStore.writeFile(FilePageStore.java:188) > > [wicket-core-9.6.0.jar:9.6.0] > > [2021-11-16T07:34:00.699Z] at > > > org.apache.wicket.pageStore.FilePageStore.addPersistedPage(FilePageStore.java:178) > > [wicket-core-9.6.0.jar:9.6.0] > > [2021-11-16T07:34:00.699Z] at > > > org.apache.wicket.pageStore.AbstractPersistentPageStore.addPage(AbstractPersistentPageStore.java:128) > > [wicket-core-9.6.0.jar:9.6.0] > > [2021-11-16T07:34:00.699Z] at > > > org.apache.wicket.pageStore.AsynchronousPageStore$PageAddingRunnable.run(AsynchronousPageStore.java:292) > > [wicket-core-9.6.0.jar:9.6.0] > > [2021-11-16T07:34:00.699Z] at java.lang.Thread.run(Thread.java:833) [?:?] > > > > This does not happen for other operating systems. Is this a known > > limitation? Is there anything else that needs to be configured at > operating > > system level? > > > > Thanks in advance. > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
exception in windows while using FilePageStore
Hi, We are trying to use FilePageStore and we are getting following exception (a lot of them actually) he requested operation cannot be performed on a file with a user-mapped section open [2021-11-16T07:34:00.699Z] at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92) ~[?:?] [2021-11-16T07:34:00.699Z] at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) ~[?:?] [2021-11-16T07:34:00.699Z] at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) ~[?:?] [2021-11-16T07:34:00.699Z] at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(WindowsFileSystemProvider.java:121) ~[?:?] [2021-11-16T07:34:00.699Z] at java.nio.channels.FileChannel.open(FileChannel.java:298) ~[?:?] [2021-11-16T07:34:00.699Z] at java.nio.channels.FileChannel.open(FileChannel.java:357) ~[?:?] [2021-11-16T07:34:00.699Z] at org.apache.wicket.pageStore.FilePageStore.writeFile(FilePageStore.java:188) [wicket-core-9.6.0.jar:9.6.0] [2021-11-16T07:34:00.699Z] at org.apache.wicket.pageStore.FilePageStore.addPersistedPage(FilePageStore.java:178) [wicket-core-9.6.0.jar:9.6.0] [2021-11-16T07:34:00.699Z] at org.apache.wicket.pageStore.AbstractPersistentPageStore.addPage(AbstractPersistentPageStore.java:128) [wicket-core-9.6.0.jar:9.6.0] [2021-11-16T07:34:00.699Z] at org.apache.wicket.pageStore.AsynchronousPageStore$PageAddingRunnable.run(AsynchronousPageStore.java:292) [wicket-core-9.6.0.jar:9.6.0] [2021-11-16T07:34:00.699Z] at java.lang.Thread.run(Thread.java:833) [?:?] This does not happen for other operating systems. Is this a known limitation? Is there anything else that needs to be configured at operating system level? Thanks in advance. -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.6.0 Released
Thanks! On Fri, Nov 12, 2021 at 7:02 AM Maxim Solodovnik wrote: > WicketStuff core 9.6.0 based on Apache Wicket 9.6.0 is released > and soon will be available at Maven Central! > > The changelog is: > > Maxim Solodovnik (7): > Switching to the next development version > Cometd version is increased > javadocs are partially fixed > Wicket is updated, link to broken javadoc is commented out > Javadocs seems to be fixed > Dependencies are updated > wicketstuff-core-9.6.0 released > > > The WicketStuff team > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 9.6.0 released
Many thanks! Would we have a new release of the wicket-stuff project or that is not needed? On Wed, Nov 3, 2021 at 12:25 AM Andrea Del Bene wrote: > The Apache Wicket PMC is proud to announce Apache Wicket 9.6.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.6.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.6.0: > > > ** Bug > > * [WICKET-6921] - MultipartFormComponentListener breaks on hidden > components > > ** Improvement > > * [WICKET-6920] - Improve the examples to use the browser's > light/dark mode > * [WICKET-6924] - Allow image/avif in SecurePackageResourceGuard > * [WICKET-6927] - Get rid of java.security.AccessController > > ** Task > > * [WICKET-6918] - Add links to latest wicket.xsd to the web site > * [WICKET-6919] - Improve EnclosureContainer's javadoc to explain > that it should not be used with > * [WICKET-6925] - Deprecate AbstractWrapModel > > -- Regards - Ernesto Reinaldo Barreiro
Re: Wicket 8 + 9 on jdk17?
Hi, On Thu, Oct 7, 2021 at 10:09 AM Martin Grigorov wrote: > On Thu, Oct 7, 2021 at 9:57 AM Jeroen Steenbeeke < > j.steenbeeke...@gmail.com> > wrote: > > > My personal Wicket apps (Wicket 9) are all running on JDK17 now. No > > problems so far, other than certain libraries not being able to handle > code > > compiled with JDK17, but this was easily fixed by upgrading those > > libraries. > > > > What helps is that the Wicket team periodically runs the entire test > suite > > against JDK release candidates and communicates their findings with the > JDK > > team. > > > > I even use JDK 18 EA for some of my projects. > But my apps are not so important. It is not like I'd lose few billions $$$ > if something breaks for few hours :-) > > > > > In a fair world maybe you, Sven and some other folks deserve some part of those billions of $$$. But that's another story :-( -- Regards - Ernesto Reinaldo Barreiro
Re: using web sockets push to repaint parts of UI (wicket 9.3.0)
Hi Sven, Many thanks for your answer. My answers inlined On Thu, May 20, 2021 at 12:24 AM Sven Meier wrote: > Hi Ernesto, > > have you compared with Wicket's websocket example? > Yes... I see no differences :-( Except we are using push components. I tried to simulate our use case with a new example https://github.com/apache/wicket/pull/469 but I can't reproduce the error in the example. Thus I still need to find out what is different in our application or what the example is missing in order to produce error. Check what thread is locking your page - do you have > ExceptionSettings#ThreadDumpStrategy set to THREAD_HOLDING_LOCK or > ALL_THREADS? > The default. No changes here. > > Regards > Sven > > > On 19.05.21 19:14, Ernesto Reinaldo Barreiro wrote: > > Hi, > > > > Context: we are trying to replace in our wicket application the use of > AJAX > > timers with Web sockets push. We are getting "strange" exceptions like > the > > ones below. > > > > -- > > java.lang.InterruptedException > > at > > > java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1261) > > at > > > java.base/java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:317) > > at > > > java.base/java.util.concurrent.LinkedBlockingQueue.offer(LinkedBlockingQueue.java:371) > > at > > > org.apache.wicket.pageStore.AsynchronousPageStore.addPage(AsynchronousPageStore.java:375) > > at > > > org.apache.wicket.pageStore.SerializingPageStore.addPage(SerializingPageStore.java:82) > > 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) > > at > > org.apache.wicket.page > .PageAccessSynchronizer$1.detach(PageAccessSynchronizer.java:170) > > at > > org.apache.wicket.protocol.ws > .api.AbstractWebSocketProcessor$1.onDetach(AbstractWebSocketProcessor.java:322) > > at > > > org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:105) > > at > > > org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:101) > > at > > > org.apache.wicket.util.listener.ListenerCollection$1.notify(ListenerCollection.java:120) > > at > > > org.apache.wicket.util.listener.ListenerCollection.reversedNotify(ListenerCollection.java:144) > > at > > > org.apache.wicket.util.listener.ListenerCollection.reversedNotifyIgnoringExceptions(ListenerCollection.java:113) > > at > > > org.apache.wicket.request.cycle.RequestCycleListenerCollection.onDetach(RequestCycleListenerCollection.java:100) > > at > > > org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:670) > > at > > > org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:625) > > at > > > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:227) > > at > > org.apache.wicket.protocol.ws > .api.AbstractWebSocketProcessor.broadcastMessage(AbstractWebSocketProcessor.java:272) > > at > > org.apache.wicket.protocol.ws > .api.AbstractWebSocketConnection.sendMessage(AbstractWebSocketConnection.java:53) > > at > > org.apache.wicket.protocol.ws > .api.WebSocketPushBroadcaster$1.run(WebSocketPushBroadcaster.java:124) > > at > > org.apache.wicket.protocol.ws > .WebSocketSettings$WebSocketPushMessageExecutor.run(WebSocketSettings.java:456) > > at > > org.apache.wicket.protocol.ws > .api.WebSocketPushBroadcaster.process(WebSocketPushBroadcaster.java:119) > > at > > org.apache.wicket.protocol.ws > .api.WebSocketPushBroadcaster.broadcast(WebSocketPushBroadcaster.java:79) > > > > > > > > org.apache.wicket.page.CouldNotLockPageException: Could not lock page 5. > > Attempt lasted PT1M > > at > > org.apache.wicket.page > .DefaultPageLockManager.lockPage(DefaultPageLockManager.java:170) > > at > > org.apache.wicket.page > .PageAccessSynchronizer.lockPage(PageAccessSynchronizer.java:72) > > at > > org.apache.wicket.page > .PageAccessSynchronizer$1.getPage(PageAccessSynchronizer.java:116) > > at > > org.apache.wicket.protocol.ws > .api.AbstractWebSocketProcessor.getPage(AbstractWebSocketProcessor.java:340) > > at > > org.apache.wicket.protocol.ws > .api.AbstractWebSocketProcessor.broadcastMessage(
using web sockets push to repaint parts of UI (wicket 9.3.0)
Hi, Context: we are trying to replace in our wicket application the use of AJAX timers with Web sockets push. We are getting "strange" exceptions like the ones below. -- java.lang.InterruptedException at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1261) at java.base/java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:317) at java.base/java.util.concurrent.LinkedBlockingQueue.offer(LinkedBlockingQueue.java:371) at org.apache.wicket.pageStore.AsynchronousPageStore.addPage(AsynchronousPageStore.java:375) at org.apache.wicket.pageStore.SerializingPageStore.addPage(SerializingPageStore.java:82) 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) at org.apache.wicket.page.PageAccessSynchronizer$1.detach(PageAccessSynchronizer.java:170) at org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor$1.onDetach(AbstractWebSocketProcessor.java:322) at org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:105) at org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:101) at org.apache.wicket.util.listener.ListenerCollection$1.notify(ListenerCollection.java:120) at org.apache.wicket.util.listener.ListenerCollection.reversedNotify(ListenerCollection.java:144) at org.apache.wicket.util.listener.ListenerCollection.reversedNotifyIgnoringExceptions(ListenerCollection.java:113) at org.apache.wicket.request.cycle.RequestCycleListenerCollection.onDetach(RequestCycleListenerCollection.java:100) at org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:670) at org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:625) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:227) at org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor.broadcastMessage(AbstractWebSocketProcessor.java:272) at org.apache.wicket.protocol.ws.api.AbstractWebSocketConnection.sendMessage(AbstractWebSocketConnection.java:53) at org.apache.wicket.protocol.ws.api.WebSocketPushBroadcaster$1.run(WebSocketPushBroadcaster.java:124) at org.apache.wicket.protocol.ws.WebSocketSettings$WebSocketPushMessageExecutor.run(WebSocketSettings.java:456) at org.apache.wicket.protocol.ws.api.WebSocketPushBroadcaster.process(WebSocketPushBroadcaster.java:119) at org.apache.wicket.protocol.ws.api.WebSocketPushBroadcaster.broadcast(WebSocketPushBroadcaster.java:79) org.apache.wicket.page.CouldNotLockPageException: Could not lock page 5. Attempt lasted PT1M at org.apache.wicket.page.DefaultPageLockManager.lockPage(DefaultPageLockManager.java:170) at org.apache.wicket.page.PageAccessSynchronizer.lockPage(PageAccessSynchronizer.java:72) at org.apache.wicket.page.PageAccessSynchronizer$1.getPage(PageAccessSynchronizer.java:116) at org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor.getPage(AbstractWebSocketProcessor.java:340) at org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor.broadcastMessage(AbstractWebSocketProcessor.java:258) at org.apache.wicket.protocol.ws.api.AbstractWebSocketConnection.sendMessage(AbstractWebSocketConnection.java:53) at org.apache.wicket.protocol.ws.api.WebSocketPushBroadcaster$1.run(WebSocketPushBroadcaster.java:124) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Are there any recommendations or requirements needed to get server side push working properly? -- Regards - Ernesto Reinaldo Barreiro
Re: Ajax debug window missing in Wicket 9
It is gone there AFAIK. On Wed, Apr 7, 2021 at 5:11 PM Bergmann Manfred wrote: > Hi. > > Even when setting explicitly: > > getDebugSettings().setAjaxDebugModeEnabled(true) > > I don’t see the Ajax debug window. > Was this a change in Wicket 9? > > > 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: Prevent script-injection attacks from user's input
Hi,
If you want to make sure none of your developers use his/her fat fingers
you might register at application level a IComponentOnBeforeRenderListener that
checks/sets this to true. If you want to exclude some components you can
create some annotation to mark components that are allowed to have this set
to false.
On Wed, Oct 28, 2020 at 8:57 AM Arunachalam Sibisakkaravarthi <
arunacha...@mcruncher.com> wrote:
> Thanks Maxim Solodovnik.
> It took me a while to identify the problem.
> Your reply helped me, in my case 'setEscapeModelStrings(false)' was set on
> the feedback panel.
> The problem is solved after removing it.
>
>
>
>
> *Thanks And RegardsSibi.ArunachalammCruncher*
>
>
> On Tue, Oct 27, 2020 at 9:01 AM Maxim Solodovnik
> wrote:
>
> > You can completely disable inline scripts using strict CSP
> > And of cause this is you who output the script entered to the page :)
> > If it is done via Label just remove 'setEscapeModelStrings(false)'
> >
> > If you need to accept and display HTML input, you can 'sanitize' form
> value
> >
> > from mobile (sorry for typos ;)
> >
> >
> > On Tue, Oct 27, 2020, 07:34 Arunachalam Sibisakkaravarthi <
> > arunacha...@mcruncher.com> wrote:
> >
> > > Hi guys,
> > > JS script alert is displayed when user input alert('xss
> > > attacks') and submit the form. How to handle this? Basically I
> > > want to prevent Cross-Site-Scripting from user inputs.
> > > Is it possible to do this globally since our Wicket Webapp is big?
> > > I found the below post which is discussed in 2010.
> > > Preventing-user-input-script-injection-attacks
> > > <
> > >
> >
> http://apache-wicket.1842946.n4.nabble.com/Preventing-user-input-script-injection-attacks-td3059119.html
> > > >
> > >
> > >
> > >
> > > *Thanks And RegardsSibi.ArunachalammCruncher*
> > >
> >
>
--
Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
Apologies. On Mon, Oct 12, 2020 at 1:53 PM Martin Grigorov wrote: > Ernesto, Maxim, > > Please do not use announce@ for such discussions! > You can just create an issue at > https://github.com/sebfz1/wicket-jquery-ui/issues/new > > On Mon, Oct 12, 2020 at 1:47 PM Maxim Solodovnik > wrote: > > > Are you using `9.x` branch? > > > > On Mon, 12 Oct 2020 at 17:26, Ernesto Reinaldo Barreiro > > wrote: > > > > > > Or has source code moved to somewhere else? > > > > > > On Mon, Oct 12, 2020 at 1:20 PM Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > I see > > > > > > > > https://github.com/sebfz1/wicket-jquery-ui > > > > > > > > Doesn't compile against wicket 9.1.0. I will fix and create PR > > > > > > > > > > > > On Mon, Oct 12, 2020 at 12:20 PM Ernesto Reinaldo Barreiro < > > > > reier...@gmail.com> wrote: > > > > > > > >> Many thanks. Can > > > >> > > > >> https://github.com/sebfz1/wicket-jquery-ui > > > >> > > > >> Be released too? > > > >> > > > >> > > > >> On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik < > solo...@apache.org> > > > >> wrote: > > > >> > > > >>> WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released > > > >>> and soon will be available at Maven Central! > > > >>> > > > >>> The changelog is: > > > >>> > > > >>> Maxim Solodovnik (7): > > > >>> Switching to the next development version > > > >>> Fixes issue #699: firstDayOfWeek should be displayed as > > expected > > > >>> wicketstuff-datetime-yui: tests are fixed > > > >>> Typos and formatting are fixed, some dependencies are updated > > > >>> Wicket is switched back to SNAPSHOT > > > >>> Release preparation: dependencies are updated > > > >>> wicketstuff-core-9.1.0 release > > > >>> > > > >>> Andrea Del Bene (2): > > > >>> Applied scope test to xml dependencies > > > >>> Try new mvn parameters to avoid "peer not authenticated" > error > > > >>> > > > >>> Erik Geletti (1): > > > >>> Bootstrap version 3 (#698) > > > >>> > > > >>> The WicketStuff team > > > >>> > > > >>> > - > > > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > >>> For additional commands, e-mail: users-h...@wicket.apache.org > > > >>> > > > >>> > > > >> > > > >> -- > > > >> Regards - Ernesto Reinaldo Barreiro > > > >> > > > > > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > -- > > Best regards, > > Maxim > > > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
Yes. It seems my fork was not synchronized with original project On Mon, Oct 12, 2020 at 1:47 PM Maxim Solodovnik wrote: > Are you using `9.x` branch? > > On Mon, 12 Oct 2020 at 17:26, Ernesto Reinaldo Barreiro > wrote: > > > > Or has source code moved to somewhere else? > > > > On Mon, Oct 12, 2020 at 1:20 PM Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > > > I see > > > > > > https://github.com/sebfz1/wicket-jquery-ui > > > > > > Doesn't compile against wicket 9.1.0. I will fix and create PR > > > > > > > > > On Mon, Oct 12, 2020 at 12:20 PM Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > >> Many thanks. Can > > >> > > >> https://github.com/sebfz1/wicket-jquery-ui > > >> > > >> Be released too? > > >> > > >> > > >> On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik > > >> wrote: > > >> > > >>> WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released > > >>> and soon will be available at Maven Central! > > >>> > > >>> The changelog is: > > >>> > > >>> Maxim Solodovnik (7): > > >>> Switching to the next development version > > >>> Fixes issue #699: firstDayOfWeek should be displayed as > expected > > >>> wicketstuff-datetime-yui: tests are fixed > > >>> Typos and formatting are fixed, some dependencies are updated > > >>> Wicket is switched back to SNAPSHOT > > >>> Release preparation: dependencies are updated > > >>> wicketstuff-core-9.1.0 release > > >>> > > >>> Andrea Del Bene (2): > > >>> Applied scope test to xml dependencies > > >>> Try new mvn parameters to avoid "peer not authenticated" error > > >>> > > >>> Erik Geletti (1): > > >>> Bootstrap version 3 (#698) > > >>> > > >>> The WicketStuff team > > >>> > > >>> - > > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >>> For additional commands, e-mail: users-h...@wicket.apache.org > > >>> > > >>> > > >> > > >> -- > > >> Regards - Ernesto Reinaldo Barreiro > > >> > > > > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > -- > Best regards, > Maxim > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
Or has source code moved to somewhere else? On Mon, Oct 12, 2020 at 1:20 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > I see > > https://github.com/sebfz1/wicket-jquery-ui > > Doesn't compile against wicket 9.1.0. I will fix and create PR > > > On Mon, Oct 12, 2020 at 12:20 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > >> Many thanks. Can >> >> https://github.com/sebfz1/wicket-jquery-ui >> >> Be released too? >> >> >> On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik >> wrote: >> >>> WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released >>> and soon will be available at Maven Central! >>> >>> The changelog is: >>> >>> Maxim Solodovnik (7): >>> Switching to the next development version >>> Fixes issue #699: firstDayOfWeek should be displayed as expected >>> wicketstuff-datetime-yui: tests are fixed >>> Typos and formatting are fixed, some dependencies are updated >>> Wicket is switched back to SNAPSHOT >>> Release preparation: dependencies are updated >>> wicketstuff-core-9.1.0 release >>> >>> Andrea Del Bene (2): >>> Applied scope test to xml dependencies >>> Try new mvn parameters to avoid "peer not authenticated" error >>> >>> Erik Geletti (1): >>> Bootstrap version 3 (#698) >>> >>> The WicketStuff team >>> >>> ----- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> -- >> Regards - Ernesto Reinaldo Barreiro >> > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
I see https://github.com/sebfz1/wicket-jquery-ui Doesn't compile against wicket 9.1.0. I will fix and create PR On Mon, Oct 12, 2020 at 12:20 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Many thanks. Can > > https://github.com/sebfz1/wicket-jquery-ui > > Be released too? > > > On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik > wrote: > >> WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released >> and soon will be available at Maven Central! >> >> The changelog is: >> >> Maxim Solodovnik (7): >> Switching to the next development version >> Fixes issue #699: firstDayOfWeek should be displayed as expected >> wicketstuff-datetime-yui: tests are fixed >> Typos and formatting are fixed, some dependencies are updated >> Wicket is switched back to SNAPSHOT >> Release preparation: dependencies are updated >> wicketstuff-core-9.1.0 release >> >> Andrea Del Bene (2): >> Applied scope test to xml dependencies >> Try new mvn parameters to avoid "peer not authenticated" error >> >> Erik Geletti (1): >> Bootstrap version 3 (#698) >> >> The WicketStuff team >> >> --------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] WicketStuff 9.1.0 Released
Many thanks. Can https://github.com/sebfz1/wicket-jquery-ui Be released too? On Mon, Oct 12, 2020 at 8:56 AM Maxim Solodovnik wrote: > WicketStuff core 9.1.0 based on Apache Wicket 9.1.0 is released > and soon will be available at Maven Central! > > The changelog is: > > Maxim Solodovnik (7): > Switching to the next development version > Fixes issue #699: firstDayOfWeek should be displayed as expected > wicketstuff-datetime-yui: tests are fixed > Typos and formatting are fixed, some dependencies are updated > Wicket is switched back to SNAPSHOT > Release preparation: dependencies are updated > wicketstuff-core-9.1.0 release > > Andrea Del Bene (2): > Applied scope test to xml dependencies > Try new mvn parameters to avoid "peer not authenticated" error > > Erik Geletti (1): > Bootstrap version 3 (#698) > > The WicketStuff team > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Display custom page automatically on session expiry without any action
Good to know. Can you share a bit more info regarding what you finally did? This might help other wicket users ;-) On Tue, Sep 29, 2020 at 4:11 AM Arunachalam Sibisakkaravarthi < arunacha...@mcruncher.com> wrote: > Thanks guys, your suggestions helped us. > > > > *Thanks And RegardsSibi.ArunachalammCruncher* > > > On Thu, Sep 24, 2020 at 3:57 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > Glad it helped. After I sent my last message, I was thinking again about > > this problem and I believe another possibility is to use web-sockets and > > some server side logic that just notifies the browser sending a redirect > to > > a "session expired page". This might be more reliable than some client > side > > logic (as far as I remember there was some trickery to account for the > fact > > that inactive tabs on browsers are put on "the background"). > > > > On Thu, Sep 24, 2020 at 7:16 AM Vignesh Palanisamy < > vign...@mcruncher.com> > > wrote: > > > > > Hi Ernesto, > > > > > > Thanks, It helps a lot. it would be good if we had it with wicketstuff. > > > > > > Thanks & Regards > > > Vignesh Palanisamy > > > > > > > > > On Sat, Sep 12, 2020 at 8:42 PM Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> wrote: > > > > > > > Hi, > > > > > > > > > > > > > > https://github.com/reiern70/antilia-bits/tree/master/client-sign-out-parent > > > > > > > > Not sure what is the status of this project but I think use case was > > > > similar tro what you mention > > > > > > > > > > > > On Fri, Sep 11, 2020 at 4:55 AM Arunachalam Sibisakkaravarthi < > > > > arunacha...@mcruncher.com> wrote: > > > > > > > > > Hi guys, > > > > > When session expires, user is redirected to a page set by > > > > > getApplicationSettings().setPageExpiredErrorPage(SomePage.class) on > > his > > > > > next action. > > > > > But I want to display a page automatically without his next action. > > > > > So that last rendered page will not be displayed after session > expiry > > > > like > > > > > banking sites. > > > > > How do I achieve this? > > > > > > > > > > > > > > > > > > > > > > > > > *Thanks And RegardsSibi.ArunachalammCruncher* > > > > > > > > > > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Display custom page automatically on session expiry without any action
Hi, Glad it helped. After I sent my last message, I was thinking again about this problem and I believe another possibility is to use web-sockets and some server side logic that just notifies the browser sending a redirect to a "session expired page". This might be more reliable than some client side logic (as far as I remember there was some trickery to account for the fact that inactive tabs on browsers are put on "the background"). On Thu, Sep 24, 2020 at 7:16 AM Vignesh Palanisamy wrote: > Hi Ernesto, > > Thanks, It helps a lot. it would be good if we had it with wicketstuff. > > Thanks & Regards > Vignesh Palanisamy > > > On Sat, Sep 12, 2020 at 8:42 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > > https://github.com/reiern70/antilia-bits/tree/master/client-sign-out-parent > > > > Not sure what is the status of this project but I think use case was > > similar tro what you mention > > > > > > On Fri, Sep 11, 2020 at 4:55 AM Arunachalam Sibisakkaravarthi < > > arunacha...@mcruncher.com> wrote: > > > > > Hi guys, > > > When session expires, user is redirected to a page set by > > > getApplicationSettings().setPageExpiredErrorPage(SomePage.class) on his > > > next action. > > > But I want to display a page automatically without his next action. > > > So that last rendered page will not be displayed after session expiry > > like > > > banking sites. > > > How do I achieve this? > > > > > > > > > > > > > > > *Thanks And RegardsSibi.ArunachalammCruncher* > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: Display custom page automatically on session expiry without any action
Hi, https://github.com/reiern70/antilia-bits/tree/master/client-sign-out-parent Not sure what is the status of this project but I think use case was similar tro what you mention On Fri, Sep 11, 2020 at 4:55 AM Arunachalam Sibisakkaravarthi < arunacha...@mcruncher.com> wrote: > Hi guys, > When session expires, user is redirected to a page set by > getApplicationSettings().setPageExpiredErrorPage(SomePage.class) on his > next action. > But I want to display a page automatically without his next action. > So that last rendered page will not be displayed after session expiry like > banking sites. > How do I achieve this? > > > > > *Thanks And RegardsSibi.ArunachalammCruncher* > -- Regards - Ernesto Reinaldo Barreiro
Re: generating a quick-start project bocken?
Disregard my previous e-mail. More information. This happens with 8.8.0 and 9.0.0 and works with 8.7.0 mvn archetype:generate -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 -DgroupId=com.mycompany -DartifactId=myproject -DarchetypeRepository= https://repository.apache.org/ -DinteractiveMode=false -X error was * Found archetype org.apache.wicket:wicket-archetype-quickstart:9.0.0 in cache: /home/reiern70/.m2/repository/org/apache/wicket/wicket-archetype-quickstart/9.0.0/wicket-archetype-quickstart-9.0.0.jar[DEBUG] checking fileset archetype status on /home/reiern70/.m2/repository/org/apache/wicket/wicket-archetype-quickstart/9.0.0/wicket-archetype-quickstart-9.0.0.jar[DEBUG] org.apache.maven.archetype.exception.UnknownArchetype: java.util.zip.ZipException: zip END header not found* *I*t seem wicket-archetype-quickstart-9.0.0.jar download was broken on my end. Removing it from my local it made everything work as expected. On Fri, Sep 11, 2020 at 10:05 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > I'm trying > > > *mvn archetype:generate -DarchetypeGroupId=org.apache.wicket > -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=9.0.0 > -DgroupId=com.mycompany -DartifactId=myproject > -DarchetypeRepository=https://repository.apache.org/ > <https://repository.apache.org/> -DinteractiveMode=false* > > and this fails with > > I > > > > > > > > > > > > *NFO] BUILD FAILURE[INFO] > [INFO] > Total time: 0.824 s[INFO] Finished at: 2020-09-11T12:00:24-07:00[INFO] > [ERROR] > Failed to execute goal > org.apache.maven.plugins:maven-archetype-plugin:2.3:generate (default-cli) > on project standalone-pom: null: MojoFailureException: NullPointerException > -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, > re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to > enable full debug logging.[ERROR] [ERROR] For more information about the > errors and possible solutions, please read the following articles:[ERROR] > [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > <http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException>* > > it seems I have latest maven version (http://maven.apache.org/download.cgi > ) > > > > > > > *Apache Maven 3.6.3Maven home: /usr/share/mavenJava version: 11.0.8, > vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64Default locale: > en_US, platform encoding: UTF-8OS name: "linux", version: > "5.4.0-47-generic", arch: "amd64", family: "unix"* > > Does anyone else experience this? > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
generating a quick-start project bocken?
Hi, I'm trying *mvn archetype:generate -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=9.0.0 -DgroupId=com.mycompany -DartifactId=myproject -DarchetypeRepository=https://repository.apache.org/ <https://repository.apache.org/> -DinteractiveMode=false* and this fails with I *NFO] BUILD FAILURE[INFO] [INFO] Total time: 0.824 s[INFO] Finished at: 2020-09-11T12:00:24-07:00[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.3:generate (default-cli) on project standalone-pom: null: MojoFailureException: NullPointerException -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException <http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException>* it seems I have latest maven version (http://maven.apache.org/download.cgi) *Apache Maven 3.6.3Maven home: /usr/share/mavenJava version: 11.0.8, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64Default locale: en_US, platform encoding: UTF-8OS name: "linux", version: "5.4.0-47-generic", arch: "amd64", family: "unix"* Does anyone else experience this? -- Regards - Ernesto Reinaldo Barreiro
Re: JavaScript/CSS/etc resources from NPM
Many thanks for sharing On Thu, Jul 9, 2020 at 2:08 AM Илья Нарыжный wrote: > Hello, Wicket Users, > > I will really appreciate your feedback on a new library which is > almost ready and about to be released. > https://github.com/OrienteerBAP/JNPM > It provides java native API to work with Node Package Manager. > Use Cases: > 1) Explore NPM registry from Java native application > 2) Pack NPM packages inside JAR. Yes - it's alternative for WebJars > and frontend-maven-plugin. Big advantage in respect to WebJars: you > can filter what exact resources you want to pick (for example only > content for dist/ folder from a package) and after packing you can > still use such things like > https://github.com/l0rdn1kk0n/wicket-webjars > 3) Implementation of your own embedded CDN which can transparently > download NPM resources per request and serve the required file to a > client. There are 2 implementations: Wicket and Servlet based. > > Let me also mention that this library was built keeping performance in > mind. It uses RxJava for packages traversal and retrieval. > If you are interested - please read README. > > I will really appreciate for any thought: about functional part or > about library application somewhere or even promotion. > > P.S. There are few things to do as technical debt... So code might be > not so nice and clean as it would be for first public version. > > Thanks, > > Ilia > - > Orienteer(http://orienteer.org) - open source Business Application > Platform > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: How to parse URL-strings based on some template for contained parameters?
Hi,
\
> I'm using Wicket as some template engine to generate reports about
> tabular data as HTML-documents in a backend published using SOAP. The
> called SOAP-interfaces expect what to generate pretty much as some
> path/URL-like resource description:
>
> > alert/topic1/foo/bar
> > report/topic1/foo/bar
> > report/topic2/bar/foo
>
> I would like to have some parser for those kinds of paths/URLs, so
> that I'm able to provide some template-paths and get some results by
> name.
>
> > ${type}/${topic}/foo/${fooVal}
>
>
You can count a resource using exactly like that
https://ci.apache.org/projects/wicket/guide/6.x/guide/resources.html#resources_11
https://wicketinaction.com/2011/07/wicket-1-5-mounting-resources/
> Is something like that available in Wicket already?
>
> Looking at "PageParameters", Wicket does only support query strings
> and indexed parameters, so no support for templates like the above.
> Indexed parameters don't seem too different, though. Additionally,
> "PagerParameters" doesn't seem to support parsing itself.
>
> So how can I parse a string only and get "PageParameters"?
>
> I've found "UrlRequestParametersAdapter" and
> "UrlPathPageParametersEncoder", the latter supports decoding paths
> like "/key1/value/key2/value" etc. And both don't seem to be bound to
> an application or HTTP, which would exactly be what I need.
>
> Anything else to look at? Thanks!
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...05151- 9468- 55
> Fax...05151- 9468- 88
> Mobil..0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Need an event later than 'done'
Hi, I know this is not bulletproof but I always add a timeOut to hiding the veil, usually 300, 400 milliseconds, so that there is some margin for AJAX request to finish. Also some AJAX requests are so fast that veil + almost not visible. spinner is On Tue, Jan 21, 2020 at 11:59 PM Entropy wrote: > That seems promising. If you could look how you did it in your other > project > that would be great. I suppose if I could get access to the response XML I > could look for the redirect in that. I'm not sure where it is though or > even if it's provided to this event. > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: StringResourceModel parameter and AJAX update
Hi,
Instead of passing as parameter selectedUser try passing
new IModel {
getObject() {
return selectedUser;
}
}
as parameter. If you are using wicket 7.x then instead of IModel you could
use an AbstractReadonlyModel
On Tue, Jan 21, 2020 at 11:31 PM Zbynek Vavros
wrote:
> Hi,
>
> just simple use-case but I can't figure it out.
>
> I have DropDownChoice that selects User and Label having
> StringResourceModel where the parameter (new
> StringResourceModel(...).setParameter(selectedUser)) is the selected user.
> How do I update the Label's model so that it reflects User selected via
> AJAX?
>
> Thanks,
> Zbynek
>
--
Regards - Ernesto Reinaldo Barreiro
Re: AjaxEventBehavior/AjaxFormComponentUpdatingBehavior & visibility
Hi,
I don't know if it is related or not but I have experienced a similar
problem while using borders. I don't remember the exact situation but I can
try to dig our code base and find out what was it.
On Tue, Jan 21, 2020 at 10:14 AM Rob Audenaerde
wrote:
> Hi Sven,
>
> Thanks for double-checking!
>
> The weird thing is that I thought this solved my problem, but when I tried
> to create the quickstart; I couldn't reproduce it either :o. I seem to have
> been mistakenly assuming it was this piece of code that fixed the problem.
>
> So I tried to build it more towards our application and I saw a
> that causes this behavior (the isVisibleInHierarchy() is
> not working there).
>
> I attached the quickstart for those who want to experiment with it.
>
> -Rob
>
> On Mon, Jan 20, 2020 at 7:17 PM Sven Meier wrote:
>
>> Hi Rob,
>>
>> actually I wasn't able to reproduce the problem on a second try (not
>> sure what I tested before).
>>
>> Can you create a a quickstart showing the problem?
>>
>> Sven
>>
>> On 20.01.20 13:18, Sven Meier wrote:
>> > Hi Rob,
>> >
>> >> the 'correct' way to solve this?
>> >
>> > the component is explicitly added to the Ajax request for an update,
>> > but decides to hide itself in onConfigure().
>> > Perfectly valid usecase IMHO, but the head will be rendered
>> > nevertheless :/
>> >
>> > Just tested with 7.x, 8.x and master, this seems to have been that way
>> > forever.
>> > But maybe we can improve that in Wicket core?
>> >
>> > Sven
>> >
>> >
>> > On 20.01.20 10:36, Rob Audenaerde wrote:
>> >> Hi all,
>> >>
>> >> I recently got some javascript errors that came from behaviors of
>> >> components that where triggered to be visible or invisible in the dom
>> >> (using onConfigure()) in an ajax request.
>> >>
>> >> Typically something like:
>> >>
>> >> Wicket.Ajax: Cannot bind a listener for event "change" on element
>> >> "format1dd" because the element is not in the DOM
>> >>
>> >> I solve this by adding an isVisibleInHierarchy() check in the
>> >> renderHead()
>> >> like this:
>> >>
>> >> @Override
>> >>
>> >> public void renderHead(final Component component, final IHeaderResponse
>> >> response) {
>> >> if (component.isVisibleInHierarchy()) {
>> >> super.renderHead(component, response);
>> >> }
>> >> }
>> >>
>> >> I was wondering if this is the 'correct' way to solve this? Or am I
>> >> doing
>> >> something wrong?
>> >>
>> >> Please advise :)
>> >>
>> >> -Rob
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
--
Regards - Ernesto Reinaldo Barreiro
Re: Retrieve user's page on the site
Do you mean for the blocker thing? Or for login errors? Or both? Happy new year to all. On Tue, Dec 31, 2019 at 4:07 PM Johannes Renoth wrote: > Hi Ernesto Reinaldo Barreiro , > > Can you provide example code for a solution? Since this is a general > Problem, maybe it would be helpful to add it to the wicket core libaries. > > Have a happy new year, > > Johannes Renoth > > On 2019-12-30 16:52, Ernesto Reinaldo Barreiro wrote: > > Hi, > > > > One thing I immediately do for any wicket application is rolling a > blocker > > DIV preventing users to double click on AJAX links: Situation? User > clicks > > in some AJAX link and meanwhile request is being processed the user > clicks > > on something "that will not be there" when AJAX request finishes. This > > blocking logic can be added globally and it is also easy to mark "request > > and don't show blocker". In my current customer's main application > rolling > > out such a solution drastically reduced the number of such errors. > > > > For other application, a side project, I remember rolling out a > > IRequestCycleListener > > that logged details from errors into some external storage so I had not > > fight with logs (and there you can store the precise info you need to > track > > user's actions). > > > > > > > > On Mon, Dec 30, 2019 at 5:03 PM Bas Gooren wrote: > > > >> Hi! > >> > >> We see these typos of errors every now and then too. It’s usually people > >> navigating to old pages, double clicking on links etc. > >> > >> Nevertheless, in our logs these are relatively easy to find: we send out > >> e-mail notifications when such errors occur, and the e-mail includes > quite > >> some details (page, component, session id, logged in user etc, user ip); > >> So far, I have always been able to trace the user’s steps by simply > >> grepping the access logs for their IP around the time of the exception. > >> > >> Should you not be able to do that, I guess it would be relatively > simple to > >> track user actions (e.g. the last 10 actions) yourself in the user > session. > >> Simply write a request cycle listener, and get some meaningful > information > >> from the next handler to be executed. > >> > >> E.g. override onRequestHandlerScheduled() and deduct the action from the > >> request handler; > >> > >> ListenerRequestHandler: component or behavior invoked > >> etc. > >> > >> Store the actions as strings (e.g. “render pageX(pageParams=XYZ)”, > “Click > >> on link a.b.c in PageX”, “Submit form path.to.component in PageX”). > >> > >> If you have an app where users are logged in, you can track the last X > >> actions in the user’s session; Otherwise you could externalize this > (either > >> in-memory by IP, or some other backing store). > >> When an exception occurs, you can catch it in your request cycle > listener > >> and fetch the last user actions. Together, these should provide a better > >> trail of actions leading up to the exceptions. > >> > >> Met vriendelijke groet, > >> Kind regards, > >> > >> Bas Gooren > >> > >> Op 30 december 2019 bij 05:24:19, Илья Нарыжный (phan...@ydn.ru) > schreef: > >> > >> Hello, > >> > >> We have pretty widely used software with thousands of visits per day. > >> And from time to time we observe pretty weird Wicket related errors > >> in logs. Commonly it's something about components structure: no such > >> child, there is already such element and etc. But the problem is that > >> commonly we can't reproduce the problem right away: page is working as > >> expected. So such mysterious problems just lie in logs and not being > >> fixed. > >> And here is the question: is there some good way to retrieve and log > >> previous user actions and etc.? Theoretically everything should be in > >> PageStore. What can you recommend to handle such problems properly? > >> > >> P.S. To be able to catch such problems we even build a system for > >> gathering all logs on a central server and correlate them with each > >> other according to some correlation logic. But still - no big luck - > >> so we really believe that problem is in fact that we know only current > >> user page/location and do not know historical aspect. > >> > >> Thanks, > >> Ilia > >> > >> - > >> Orienteer(http://orienteer.org) - open source Business Application > >> Platform > >> > >> - > >> 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: Retrieve user's page on the site
Hi, One thing I immediately do for any wicket application is rolling a blocker DIV preventing users to double click on AJAX links: Situation? User clicks in some AJAX link and meanwhile request is being processed the user clicks on something "that will not be there" when AJAX request finishes. This blocking logic can be added globally and it is also easy to mark "request and don't show blocker". In my current customer's main application rolling out such a solution drastically reduced the number of such errors. For other application, a side project, I remember rolling out a IRequestCycleListener that logged details from errors into some external storage so I had not fight with logs (and there you can store the precise info you need to track user's actions). On Mon, Dec 30, 2019 at 5:03 PM Bas Gooren wrote: > Hi! > > We see these typos of errors every now and then too. It’s usually people > navigating to old pages, double clicking on links etc. > > Nevertheless, in our logs these are relatively easy to find: we send out > e-mail notifications when such errors occur, and the e-mail includes quite > some details (page, component, session id, logged in user etc, user ip); > So far, I have always been able to trace the user’s steps by simply > grepping the access logs for their IP around the time of the exception. > > Should you not be able to do that, I guess it would be relatively simple to > track user actions (e.g. the last 10 actions) yourself in the user session. > Simply write a request cycle listener, and get some meaningful information > from the next handler to be executed. > > E.g. override onRequestHandlerScheduled() and deduct the action from the > request handler; > > ListenerRequestHandler: component or behavior invoked > etc. > > Store the actions as strings (e.g. “render pageX(pageParams=XYZ)”, “Click > on link a.b.c in PageX”, “Submit form path.to.component in PageX”). > > If you have an app where users are logged in, you can track the last X > actions in the user’s session; Otherwise you could externalize this (either > in-memory by IP, or some other backing store). > When an exception occurs, you can catch it in your request cycle listener > and fetch the last user actions. Together, these should provide a better > trail of actions leading up to the exceptions. > > Met vriendelijke groet, > Kind regards, > > Bas Gooren > > Op 30 december 2019 bij 05:24:19, Илья Нарыжный (phan...@ydn.ru) schreef: > > Hello, > > We have pretty widely used software with thousands of visits per day. > And from time to time we observe pretty weird Wicket related errors > in logs. Commonly it's something about components structure: no such > child, there is already such element and etc. But the problem is that > commonly we can't reproduce the problem right away: page is working as > expected. So such mysterious problems just lie in logs and not being > fixed. > And here is the question: is there some good way to retrieve and log > previous user actions and etc.? Theoretically everything should be in > PageStore. What can you recommend to handle such problems properly? > > P.S. To be able to catch such problems we even build a system for > gathering all logs on a central server and correlate them with each > other according to some correlation logic. But still - no big luck - > so we really believe that problem is in fact that we know only current > user page/location and do not know historical aspect. > > Thanks, > Ilia > > - > Orienteer(http://orienteer.org) - open source Business Application > Platform > > ----- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Regards - Ernesto Reinaldo Barreiro
Re: Application not seri
By the way: your avatar made me remember good times sitting together with my boy watching adventure times :-) On Sat, Dec 21, 2019 at 9:03 AM ShengChe Hsiao wrote: > Dear all > I faced a strange exception, the error message: > > A problem occurred while checking object with type: > info.sls.WicketApplication > > Field hierarchy is: > > 1 [class=info.sls.MapPage, path=1] > > private java.lang.Object org.apache.wicket.MarkupContainer.children > [class=java.util.ArrayList] > > private java.lang.Object > org.apache.wicket.MarkupContainer.children[write:27][write:28] > [class=org.apache.wicket.markup.html.form.StatelessForm, > path=1:formGMapSelect] > > private java.lang.Object org.apache.wicket.MarkupContainer.children > [class=java.util.ArrayList] > > private final java.lang.String > > org.apache.wicket.markup.html.form.ChoiceRenderer.idExpression[write:8][write:11] > [class=org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink, > path=1:formGMapSelect:btnSelect] > > final info.sls.GMapPanel info.sls.MapPage$1.val$gMapPanel > [class=info.sls.GMapPanel, path=1:gmaps] > > java.lang.Object org.apache.wicket.Component.data > [class=[Ljava.lang.Object;] > > java.lang.Object org.apache.wicket.Component.data[0] > [class=org.apache.wicket.model.LoadableDetachableModel] > > final info.sls.WicketApplication > info.sls.WicketApplication$3.this$0 [class=info.sls.WicketApplication] > <- field that is causing the problem > > > I use transient with WicketApplication in my BasePage, but the issue > continued. > > > private transient WicketApplication wicketApplication; > > > > Any suggestions? > > ---> > To boldly go where no man has gone before. > > ---> > We do this not because it is easy. We do this because it is hard. > - > --> > If I have seen further it is by standing on the shoulders of giants. > -- > -----> > front...@gmail.com > > -> > -- Regards - Ernesto Reinaldo Barreiro
Re: Application not seri
Hi,
Instead of keeping a reference to WebApplication just use
Application.get();: it is bound to thread as a threadlocal. If you need
your specific instance you can always add
public static MyWebApplication getInstance() {
return (MyWebApplication) Application.get();
}
to class MyWebApplication, This way you can always
call MyWebApplication.getInstance() and you don't need to keep a
reference to it as a field on base page.
On Sat, Dec 21, 2019 at 9:03 AM ShengChe Hsiao wrote:
> Dear all
> I faced a strange exception, the error message:
>
> A problem occurred while checking object with type:
> info.sls.WicketApplication
>
> Field hierarchy is:
>
> 1 [class=info.sls.MapPage, path=1]
>
> private java.lang.Object org.apache.wicket.MarkupContainer.children
> [class=java.util.ArrayList]
>
> private java.lang.Object
> org.apache.wicket.MarkupContainer.children[write:27][write:28]
> [class=org.apache.wicket.markup.html.form.StatelessForm,
> path=1:formGMapSelect]
>
> private java.lang.Object org.apache.wicket.MarkupContainer.children
> [class=java.util.ArrayList]
>
> private final java.lang.String
>
> org.apache.wicket.markup.html.form.ChoiceRenderer.idExpression[write:8][write:11]
> [class=org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink,
> path=1:formGMapSelect:btnSelect]
>
> final info.sls.GMapPanel info.sls.MapPage$1.val$gMapPanel
> [class=info.sls.GMapPanel, path=1:gmaps]
>
> java.lang.Object org.apache.wicket.Component.data
> [class=[Ljava.lang.Object;]
>
> java.lang.Object org.apache.wicket.Component.data[0]
> [class=org.apache.wicket.model.LoadableDetachableModel]
>
> final info.sls.WicketApplication
> info.sls.WicketApplication$3.this$0 [class=info.sls.WicketApplication]
> <- field that is causing the problem
>
>
> I use transient with WicketApplication in my BasePage, but the issue
> continued.
>
>
> private transient WicketApplication wicketApplication;
>
>
>
> Any suggestions?
>
> --->
> To boldly go where no man has gone before.
>
> --->
> We do this not because it is easy. We do this because it is hard.
> -
> -->
> If I have seen further it is by standing on the shoulders of giants.
> --
> ----->
> front...@gmail.com
>
> ->
>
--
Regards - Ernesto Reinaldo Barreiro
Re: FileUpload class still implements IClusterable
Done On Tue, Dec 3, 2019 at 6:19 PM Martin Grigorov wrote: > On Tue, Dec 3, 2019 at 3:42 PM Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi Martin, > > > > > > On Tue, Dec 3, 2019 at 3:09 PM Martin Grigorov > > wrote: > > > > > Hi Ernesto, > > > > > > Yes, I think FileUpload should not be Serializable. > > > FileUploadField uses transient reference to the list of file uploads > for > > > this reason: > > > > > > > > > https://github.com/apache/wicket/blob/ad6ecac7fdebefc25d310361f3a92aa481c36b1f/wicket-core/src/main/java/org/apache/wicket/markup/html/form/upload/FileUploadField.java#L50 > > > > > > Yes I'm aware of this behaviour: I just fixed some related issue in our > > project and while doing that I noticed mentioned problem? Shall I create > an > > issue for this or just a PR? > > > > Issue + commit (you have the permissions). > But maybe only in Wicket 9.x because otherwise Clirr plugin will complain > that it is an API break. > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: FileUpload class still implements IClusterable
Hi Martin, On Tue, Dec 3, 2019 at 3:09 PM Martin Grigorov wrote: > Hi Ernesto, > > Yes, I think FileUpload should not be Serializable. > FileUploadField uses transient reference to the list of file uploads for > this reason: > > https://github.com/apache/wicket/blob/ad6ecac7fdebefc25d310361f3a92aa481c36b1f/wicket-core/src/main/java/org/apache/wicket/markup/html/form/upload/FileUploadField.java#L50 Yes I'm aware of this behaviour: I just fixed some related issue in our project and while doing that I noticed mentioned problem? Shall I create an issue for this or just a PR? -- Regards - Ernesto Reinaldo Barreiro
FileUpload class still implements IClusterable
Hi, FileUpload still implements IClusterable but it contains a field of type FileItem: which is no longer Serializable. Should IClusterable be dropped? -- Regards - Ernesto Reinaldo Barreiro
Re: DynamicModel within ListView That Refreshes on ModalWindow Close
Hi, It is difficult to understand what you are describing. What I guess is you have a panel containing a listview and a label and open some modal to do some operation on listview and after that operation you want the label to show correct number of elements? If so, make the label receive a dynamic model not caching the number of elements (e.g. AbstractReadOnlyModel or LDM). Then I would update the whole panel via AJAX. Side note: no one in this list is getting paid for answering and helping people. Maybe starting you messages with "Thanks for your answer... But unfortunately what you have answered does not help me because ..." might increase the chances you get answered in the future. On Wed, Sep 25, 2019 at 9:00 PM dylanbozeman wrote: > I have a Label within a ListView that is refreshed using Ajax upon the > closing of a ModalWindow that is also part of that ListView. > > Th problem is, the Label isn't refreshing. > > I don't believe I can use a PropertyModel within a ListView and I believe I > need that for the Label to by dynamic. (if I can use a PropertyModel, how > so? because I can't specify - new PropertyModel(this, > "localVariableInsideListView") - because it looks at the class level for > that variable) > > Is there a way around this or something I am not seeing? > > When I do this with a regular Model I am getting: > > [qtp976782276-127] WARN org.apache.wicket.page.PartialPageUpdate - > Component > '[Component id = numberLabel]' not rendered because it was already removed > from page > > > > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 8.6.0 released
t; > * [WICKET-6675] - log4j-slf4j-impl requires version 1.7.25 of > slf4j-api while Wicket 8.5 requires version 1.7.26 > * [WICKET-6684] - Make autolabel functionality more flexible by > introducing a locator interface that allows to specify the component the > wicket:for refers to > * [WICKET-6695] - Add AjaxEditable*Label#shouldTrimInput() > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: [ANNOUNCE] Apache Wicket 8.6.0 released
Thanks Andrea On Sat, Sep 7, 2019 at 8:22 PM Andrea Del Bene wrote: > The Apache Wicket PMC is proud to announce Apache Wicket 8.6.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 8. We > use semantic versioning for the development of Wicket, and as such no > API breaks are present breaks are present in this release compared to > 8.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 > 8.6.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-8.x.html#manually > > Upgrading from earlier versions > --- > > If you upgrade from 8.y.z this release is a drop in replacement. If > you come from a version prior to 8.0.0, please read our Wicket 8 > migration guide found at > > * http://s.apache.org/wicket8migrate > > Have fun! > > — The Wicket team > > > > > The signatures for the source release artefacts: > > > Signature for apache-wicket-8.6.0.zip: > > -BEGIN PGP SIGNATURE- > > iQIzBAABCgAdFiEE0a6YZHC1pJw+aieyh48B+qjTVuEFAl1u0ggACgkQh48B+qjT > VuHBVRAAgX8nPfftIKv6z0Rimyg4M9hefpkwcVCkj8mQ2q9cnRQCNN8lWPrVsqOz > jfkWOM1I3rmjR60o5eREFuNK+t7RNxdwfdZqlB+zsgu2BCNscpQMaTruf2uI14ip > B83PYCMkTSDA+BCJD1MTwRf3Ih3M+0rq4l3vedzStfC4GvmmwHRvMWTOml5i9Whg > pSStZvX9h61n6ofRNq/feLQi7342GOgv+/r0cvTVDRdIsEeYGalu1b+ZJKsjfTX3 > l0oMiRILzFltg+CQP0fhWibfLkvyRLM+R4598rgvwM+QcKo7aCn0LcIEIhp0dYDS > KI6IhsPd/NS0qKoKgIPmQ6tMsvMWGOxTOpQMxnAj97wVzYVf1QoXArPuc+JaSrFE > D/a78zUMc78UFjdt38NBA22jf7HbcjVkAUUjD9fPtNStFnnrisniyw16dL0Wa6MA > kuiPuyl7gsPAkmOXH68KtVaR7ncTORPCt4ZC/6GxoRbhDc71+dLPz5XKpeDdqy8O > /pBGtsucjI9xIGZqGHWFvfAaBqqv2t4QARxOdkDA9d09PL4o/N+gljho+a30GrDv > A35wG2y2Idkoe1t4EJeHpMHGPmqMAj/m1wYagJjMeiXRDgtfFoJIlRfAboxq8Dwd > uT+mRsdS0hq8q78yPZPW3N24cC3gwohFJMWfb4IukQbFGI2gznE= > =mzMF > -END PGP SIGNATURE- > > Signature for apache-wicket-8.6.0.tar.gz: > > -BEGIN PGP SIGNATURE- > > iQIzBAABCgAdFiEE0a6YZHC1pJw+aieyh48B+qjTVuEFAl1u0ggACgkQh48B+qjT > VuHSZw//WF61doVJ8fDK8hPvk8Td6Yf4hMzP7kff7tAkm+w72LqnXlUM7IDci5nz > Dcx627fBAYIXdRtfOkq53vRrFV+1e87x8iM/bnp7Tzj5lwF6BOvRkQ+gr6U6+6An > 5CblTMT5kSq9xKGm8/Gj6I1OrQiVdSqFPWt7N/4D7FG9uekRVJoc+0ubekqdGR1M > lkoT8Wfteo7sstoD8qvQEgyKKZLqbxTKDGiVBywmSKVuxkv+4JnETI2k1R1TsCr0 > /JdGx6fNxd/sBUKLoAUo8cxBpv9weuzvPCMw89eVGsKacBDedZMK7iMfR3M43Iz/ > HuEN26JnHM3kqSBCMMYE197djXOroUhXmhr9WfNRxiaTqJsKbS1oG3jO9EkHQt8Y > ldhwiTaH8PmGE72xhn+w+FElZvazwlFXSECHZK92wGFEzq5VO7atv88AOmtQHM1o > LbgHOjhUYLQHj15JXn4g4XYFJ5WnZR3gbldAV9JEhXqnx30M6wMDrWCCw6K0+uh2 > k8Il3y6TMY7KSrnUYwTeljyrLYReoAtYfQxi6EdGBlKamuyKXtSBqO0a2J5wsxnv > Z2fk3efWKDzdxbc9GmYbXMlTKtjYx5UYZ+PcgAuGvS81ejwzmiy5dH8rJYedx235 > j3D8JG/YyG2Ja0r6nmwX7BDm8QS4W5eU+UQIyIq0KLCFND/qzSU= > =VBOu > -END PGP SIGNATURE- > > > > CHANGELOG for 8.6.0: > > ** Bug > > * [WICKET-6613] - Wicket 8.1 ModalWindow autosizing problem > * [WICKET-6671] - IAjaxLink should be serializable > * [WICKET-6676] - Quickstart application won't deploy to GlassFish > * [WICKET-6680] - JavaScriptStripper chokes on template literals > that contain two forward slashes > * [WICKET-6689] - ClientProperties.getTimeZone() has some issue > when DST and UTC offsets are different > * [WICKET-6690] - NullPointerException in > KeyInSessionSunJceCryptFactory. > * [WICKET-6692] - Page deserialization on websocket close - > possible performance issue > > ** Improvement > > * [WICKET-6675] - log4j-slf4j-impl requires version 1.7.25 of > slf4j-api while Wicket 8.5 requires version 1.7.26 > * [WICKET-6684] - Make autolabel functionality more flexible by > introducing a locator interface that allows to specify the component the > wicket:for refers to > * [WICKET-6695] - Add AjaxEditable*Label#shouldTrimInput() > > -- Regards - Ernesto Reinaldo Barreiro
Re: Re: Wrapping a FormComponent with a Border
Hi Tom, Maybe you can roll your own namespace implementing ComponentTag and have something like and this gets replaced by and the corresponding components. On Tue, Sep 3, 2019 at 10:09 AM "Tom Götz" wrote: > Martin, > > maybe you could point me into the right direction concerning the markup > manipulation part? > > This is what I got in my HTML: > > > > > > I guess this is what I need for effectively replacing the input with a > FormGroup border: > > > > > > > > Where would be the best place in the code to start looking? > > Thanks in advance > Tom > > > > > > Gesendet: Montag, 02. September 2019 um 13:57 Uhr > > Von: "Tom Götz" > > An: users@wicket.apache.org > > Betreff: Re: Wrapping a FormComponent with a Border > > > > Thanks Martin, this is exactly what I had in mind. I already implemented > 1), replacing the TextField with said Border but now am stuck with the > "HTML manipulation" part ... > > > > Tom > > > > > > > Gesendet: Montag, 02. September 2019 um 13:47 Uhr > > > Von: "Martin Grigorov" > > > An: "users@wicket.apache.org" > > > Betreff: Re: Wrapping a FormComponent with a Border > > > > > > Hi Tom, > > > > > > I imagine two ways: > > > 1) use org.apache.wicket.application.IComponentInitializationListener > that > > > manipulates the component tree whenever the passed component is an > instance > > > of TextField and has no (direct?!) parent of type FormGroup > > > 2) use AOP > > > > > > In both cases you will need to also the markup because FormGroup > expects to > > > be attached on a , while you will have an . For this you > will > > > probably need to extend Wicket Bootstrap's FormGroup and in your > custom one > > > override onComponentTag() (and onComponentTagBody() - most probably > not). > > > > > > On Mon, Sep 2, 2019 at 2:05 PM "Tom Götz" wrote: > > > > > > > Let me try to explain what I want to achieve more precisely: > > > > > > > > - user adds a TextField to a page > > > > - I want to replace that TextField with a Border (Wicket Border > component, > > > > e.g. FormGroup from wicket-bootstrap) and put the TextField inside > that > > > > border > > > > > > > > The problem ist not: "how do I wrap a component with some HTML > markup?" > > > > (either generated by Java code or clientside), but: how can I > manipulate > > > > the component tree (server side) in such a way, that I can remove the > > > > TextField from it's parent and replace it with a Border that > contains that > > > > TextField!? > > > > > > > > Tom > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Gesendet: Montag, 02. September 2019 um 12:49 Uhr > > > > > Von: "Tobias Soloschenko" > > > > > > An: users@wicket.apache.org > > > > > Betreff: Re: Wrapping a FormComponent with a Border > > > > > > > > > > Hi, > > > > > > > > > > why not add a css class and style it? > > > > > > > > > > kind regards > > > > > > > > > > Tobias > > > > > > > > > > > Am 02.09.2019 um 12:20 schrieb Ernesto Reinaldo Barreiro < > > > > reier...@gmail.com>: > > > > > > > > > > > > Another possibility is to do this client side... > > > > > > > > > > > >> On Mon, Sep 2, 2019, 11:43 AM "Tom Götz" > wrote: > > > > > >> > > > > > >> That would be great, thanks in advance! > > > > > >> > > > > > >> Tom > > > > > >> > > > > > >> > > > > > >>> Gesendet: Montag, 02. September 2019 um 10:39 Uhr > > > > > >>> Von: "Ernesto Reinaldo Barreiro" > > > > > >>> An: users@wicket.apache.org > > > > > >>> Betreff: Re: Wrapping a FormComponent with a Border > > > > > >>> > > > > > >>> Hi, > > > > > >>> > > > > > >>>> On Mon, Sep 2, 2019 at 11:13 AM Tom Götz > > > > > wrote: > > > > > >>>> > > > > > >>>> Thanks Ernesto! This example is from 2007 though and uses > > > > > >>>> compent.setComponentBorder > > > > > >>>> Is there something more close to current Wicket versions > available > > > > > >> maybe? > > > > > >>>> :) > > > > > >>>> > > > > > >>> > > > > > >>> I think I have somewhere on a private project something similar > > > > > >> implemented > > > > > >>> for Wicket 7.x... I can try to dig it up and send classes to > you. > > > > > >>> > > > > > >>> -- > > > > > >>> Regards - Ernesto Reinaldo Barreiro > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Wrapping a FormComponent with a Border
Another possibility is to do this client side... On Mon, Sep 2, 2019, 11:43 AM "Tom Götz" wrote: > That would be great, thanks in advance! > > Tom > > > > Gesendet: Montag, 02. September 2019 um 10:39 Uhr > > Von: "Ernesto Reinaldo Barreiro" > > An: users@wicket.apache.org > > Betreff: Re: Wrapping a FormComponent with a Border > > > > Hi, > > > > On Mon, Sep 2, 2019 at 11:13 AM Tom Götz wrote: > > > > > Thanks Ernesto! This example is from 2007 though and uses > > > compent.setComponentBorder > > > Is there something more close to current Wicket versions available > maybe? > > > :) > > > > > > > I think I have somewhere on a private project something similar > implemented > > for Wicket 7.x... I can try to dig it up and send classes to you. > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Wrapping a FormComponent with a Border
Hi, On Mon, Sep 2, 2019 at 11:13 AM Tom Götz wrote: > Thanks Ernesto! This example is from 2007 though and uses > compent.setComponentBorder > Is there something more close to current Wicket versions available maybe? > :) > I think I have somewhere on a private project something similar implemented for Wicket 7.x... I can try to dig it up and send classes to you. -- Regards - Ernesto Reinaldo Barreiro
Re: Wrapping a FormComponent with a Border
Hi, Would approach described in [1] match your use case? References 1- https://www.scribd.com/document/43719247/LondonWicket-FormsWithFlair On Mon, Sep 2, 2019 at 10:22 AM Tom Götz wrote: > Hi there, > > I would like to automatically wrap a FormComponent with a Border whenever > it is added on a certain page. Let's say, a TextField is added, then I'd > like to replace it with Border and add that TextField to the Border. The > Border itself contains other Wicket Components such as a Label and a > FeedbackPanel. I am aware of BorderBehavior, but it seems that this can > only be used to wrap raw HTML around a Component. > Is this possible somehow? > > Cheers > Tom > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: Streaming a PDF into an iFrame
335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:335) > at > > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:259) > at > > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) > at > > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:275) > at > > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206) > at > > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:299) > at > > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) > at > > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) > at > > org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:740) > at > > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) > at > > org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) > at > > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) > at > > org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at > > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340) > at > > org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) > at > > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) > at > > org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) > at > > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242) > at > > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) > at > > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) > at org.eclipse.jetty.server.Server.handle(Server.java:503) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) > at > org.eclipse.jetty.io > .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) > at > > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) > at > > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) > at > > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) > at > > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) > at > > org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) > at > > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) > at > > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) > at java.lang.Thread.run(Thread.java:745) > /*** END STACK TRACE ***/ > -- Regards - Ernesto Reinaldo Barreiro
Re: release of new milestone of wicket 9..x?
Hi Andrea, Thanks for your answer. Main features I need are some deletion of duration that was rolled back to deprecation (as our main development branch is on wicket 8.x) and I'm keeping a parallel branch for 9.x and I want to minimize conflicts (even if it is with deprecated code). Also some recently added improvements to auto labels (and as far as I can see this could be also ported to 8.x). On Thu, Jul 11, 2019 at 5:37 PM Andrea Del Bene wrote: > Not yet. We are trying to prepare everything we need to roll out Wicket 9, > but it will take some times. What fix/feature do you need most from 9.x > branch? I see some of us still work on a new modal dialog, which is > something that would be "nice to have" in Wicket 9. > > On Thu, Jul 11, 2019 at 7:41 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > Hi, > > > > Any plans to release a new milestone of 9.x? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > Andrea Del Bene. > Apache Wicket committer. > -- Regards - Ernesto Reinaldo Barreiro
release of new milestone of wicket 9..x?
Hi, Any plans to release a new milestone of 9.x? -- Regards - Ernesto Reinaldo Barreiro
Re: improvement for wicket:for
Voila https://github.com/apache/wicket/pull/373 On Wed, Jun 26, 2019 at 9:46 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > ok. > > On Wed, Jun 26, 2019 at 9:43 AM Martin Grigorov > wrote: > >> Hi Ernesto, >> >> Please create a Pull Request and we will discuss it! Thanks! >> >> On Wed, Jun 26, 2019 at 9:34 AM Ernesto Reinaldo Barreiro < >> reier...@gmail.com> wrote: >> >> > I could try to provide a PR implementing this. >> > >> > On Wed, Jun 26, 2019 at 9:30 AM Ernesto Reinaldo Barreiro < >> > reier...@gmail.com> wrote: >> > >> > > Hi, >> > > >> > > In application I'm developing right now we have following situation. >> > > >> > > >> > >1. A repeater consisting of a label with wicket:id "label" + some >> > >complex panel with wicket:id="value" >> > >2. I still would like to use wicket:for but panel value structure >> may >> > >change a lot depending on "type" of current repeater "row". Thus, I >> > can't >> > >alway write wicket:for="value/xxx". >> > > >> > > Thus, I would like to introduce some interface to be implemented by >> > > "ValuePanel" which returns a reference to that for component to which >> > label >> > > should point, so that I could write wicket:for="value" >> > > >> > > WDYT? >> > > >> > > -- >> > > Regards - Ernesto Reinaldo Barreiro >> > > >> > >> > >> > -- >> > Regards - Ernesto Reinaldo Barreiro >> > >> > > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: improvement for wicket:for
ok. On Wed, Jun 26, 2019 at 9:43 AM Martin Grigorov wrote: > Hi Ernesto, > > Please create a Pull Request and we will discuss it! Thanks! > > On Wed, Jun 26, 2019 at 9:34 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> wrote: > > > I could try to provide a PR implementing this. > > > > On Wed, Jun 26, 2019 at 9:30 AM Ernesto Reinaldo Barreiro < > > reier...@gmail.com> wrote: > > > > > Hi, > > > > > > In application I'm developing right now we have following situation. > > > > > > > > >1. A repeater consisting of a label with wicket:id "label" + some > > >complex panel with wicket:id="value" > > >2. I still would like to use wicket:for but panel value structure > may > > >change a lot depending on "type" of current repeater "row". Thus, I > > can't > > >alway write wicket:for="value/xxx". > > > > > > Thus, I would like to introduce some interface to be implemented by > > > "ValuePanel" which returns a reference to that for component to which > > label > > > should point, so that I could write wicket:for="value" > > > > > > WDYT? > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > -- Regards - Ernesto Reinaldo Barreiro
Re: improvement for wicket:for
I could try to provide a PR implementing this. On Wed, Jun 26, 2019 at 9:30 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > In application I'm developing right now we have following situation. > > >1. A repeater consisting of a label with wicket:id "label" + some >complex panel with wicket:id="value" >2. I still would like to use wicket:for but panel value structure may >change a lot depending on "type" of current repeater "row". Thus, I can't >alway write wicket:for="value/xxx". > > Thus, I would like to introduce some interface to be implemented by > "ValuePanel" which returns a reference to that for component to which label > should point, so that I could write wicket:for="value" > > WDYT? > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
improvement for wicket:for
Hi, In application I'm developing right now we have following situation. 1. A repeater consisting of a label with wicket:id "label" + some complex panel with wicket:id="value" 2. I still would like to use wicket:for but panel value structure may change a lot depending on "type" of current repeater "row". Thus, I can't alway write wicket:for="value/xxx". Thus, I would like to introduce some interface to be implemented by "ValuePanel" which returns a reference to that for component to which label should point, so that I could write wicket:for="value" WDYT? -- Regards - Ernesto Reinaldo Barreiro
Re: estimate time for 9.x release?
+1 non binding. I was going to write asking for a M3 release right now :-) On Wed, Jun 26, 2019 at 12:02 AM Martin Grigorov wrote: > In that case I vote to release 9.0.0 with the next releases of 7.x and 8.x, > no need to wait until Q3. > > On Sun, Jun 23, 2019 at 11:43 AM Sven Meier wrote: > > > Hi all, > > > > I haven't had time to work an wicket-ajax-no-jquery.js, and I agree that > > we as well might try that in Wicket 10. > > > > Meanwhile I'm preparing a pull request for another modal-dialog > > proposal, but this doesn't have to delay a Wicket 9 release either. > > > > Have fun > > Sven > > > > > > On 20.06.19 11:50, Martin Grigorov wrote: > > > Hi, > > > > > > The only bigger task I am aware of is the vanilla wicket-ajax.js > rewrite > > > that has been suggested by Korbinian Bachl (some time ago) and Andrew > > > Kondratev (more recently). Sven said that he wants to work on it. > > > But in my opinion this task should not stop us to release 9.0.0. The > > > vanilla impl can be introduced in a minor release too, even in 8.x, if > > the > > > APIs are preserved. > > > > > > On Thu, Jun 20, 2019 at 12:03 AM Andrea Del Bene > > > > wrote: > > > > > >> Hi, > > >> > > >> I'm happy you started to appreciate Wicket 9.x in its earliest > versions! > > >> The short answer is no, there is no estimated time for 9.x to become > EA. > > >> But at the moment I'm not aware of any huge feature or refactoring > being > > >> in progress or even proposed. Let's hear what other developers have to > > >> say about this. > > >> Personally speaking I'm also willing to release Wicket 9.x in a short > > >> time, let's say in the Q4 of this year, after one or two more > milestone > > >> releases. I also believe that the time is now ripe to provide a > version > > >> of Wicket for the "post Java 8 era", which fully supports the last LTS > > JDK. > > >> > > >> Andrea. > > >> > > >> On 6/19/19 12:29 PM, rstolle wrote: > > >>> Same here! I would love to go with wicket 9 ASAP. I'm using 9.0.0-M2 > > >>> on a new > > >>> project and very much appreciate the switch to java.time.Duration, > > >>> which saves > > >>> me a lot of conversions. Junit5 is also a huge plus in my opinion. So > > >>> far I did not > > >>> encounter any problems. > > >>> > > >>> Good moment to THANK THE WICKET TEAM (again) - you doing a wicked > job! > > >>> > > >>> René > > >>> > > >>> Am 2019-06-19 11:30 schrieb Ernesto Reinaldo Barreiro: > > >>>> Hi, > > >>>> > > >>>> Is there an estimated time for 9.x official release? My question is > > not > > >>>> just moot: I'm keeping a parallel version of our project based on > > wicket > > >>>> 9.x. branch, and some problems I encountered on wicket 8.x. are > > >>>> easier to > > >>>> solve on 9.x. So, if release is not too far in the future I might > try > > to > > >>>> convince other team members to go 9.x. for development. > > >>> - > > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >>> For additional commands, e-mail: users-h...@wicket.apache.org > > >>> > > >> - > > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >> For additional commands, e-mail: users-h...@wicket.apache.org > > >> > > >> > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > -- Regards - Ernesto Reinaldo Barreiro
Re: estimate time for 9.x release?
Hi Martin and Andrea, Many thanks for answers. So, I will try to convince my teammates to switch development to 9.x branch and that way provide "life feedback" on new developments. The only bigger task I am aware of is the vanilla wicket-ajax.js rewrite > that has been suggested by Korbinian Bachl (some time ago) and Andrew > Kondratev (more recently). Sven said that he wants to work on it. > But in my opinion this task should not stop us to release 9.0.0. The > vanilla impl can be introduced in a minor release too, even in 8.x, if the > APIs are preserved. > I also remember to have seeing some commits to get rid of wicket AJAX console. Would this also be part of 9.x? Also some proposal of new implementation of modal window? For us this is not relevant as we use bootstrap modal. -- Regards - Ernesto Reinaldo Barreiro
estimate time for 9.x release?
Hi, Is there an estimated time for 9.x official release? My question is not just moot: I'm keeping a parallel version of our project based on wicket 9.x. branch, and some problems I encountered on wicket 8.x. are easier to solve on 9.x. So, if release is not too far in the future I might try to convince other team members to go 9.x. for development. -- Regards - Ernesto Reinaldo Barreiro
Re: thanks for wonderful work with Wicket 8.
Hi, I just created a branch of or application based on 9.X-SNAPSHOT and bootstrap 4.x-SNAPSHOT and I plan to keep it synchronized, at least once per week, with our development branch (wicket 8.X based). So, before any new milestone releases of 9.x I can use it to test if everything still works and hopefully provide some feedback to Wicket developers. Thanks again to Wicket team! On Fri, May 3, 2019 at 9:34 AM nino martinez wael < nino.martinez.w...@gmail.com> wrote: > Sounds great.. For minimal effort, I think the notify plugin would fit very > well here: > > https://github.com/l0rdn1kk0n/wicket-bootstrap > > Under extensions, but it's not my repo.. > > And yes wicket are wonderful, even after all these years :) And I've been > using it on, Guice, OSGI and now with spring boot :) > > > > On Fri, May 3, 2019 at 8:45 AM Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Fri, May 3, 2019 at 8:39 AM nino martinez wael < > > nino.martinez.w...@gmail.com> wrote: > > > > > I could use the > > > > > > Or a wicket wrapper for > > > > http://bootstrap-notify.remabledesigns.com/. > > > > > > I can try to convince my manager to open-source it. We are using it all > > over in our application in combination with wicket AJAX/Web sockets. Also > > > > > >- some home grown bootstrap modal wizard > >- wicket wrapper fro *https://github.com/fronteed/iCheck > ><https://github.com/fronteed/iCheck>* > > > > *And maybe some other home ground components. But this doesn't depend on > > me.* > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > Best regards / Med venlig hilsen > Nino Martinez > -- Regards - Ernesto Reinaldo Barreiro
Re: Wicket DropDown Change event
Look at OnChangeAjaxBehavior
On Mon, May 20, 2019 at 4:13 PM Sibgha Nazir wrote:
> Hi,
>
> I am not able to trigger the on change event of the drop down in the
> wicket.
>
> In the class DPanel,java, I am simply trying to print on the console when
> the change event has occured.
>
> dropdown.add(*new* AjaxFormComponentUpdatingBehavior("onchange") {
>
> /**
>
> *
>
> */
>
> *private* *static* *final* *long* *serialVersionUID* =
> -6744838136235652577L;
>
>
> *protected* *void* onUpdate(AjaxRequestTarget target) {
>
> System.*out*.println("Changed");
>
>
> }
>
> });
>
> Need Help. Following is my quick start application.
> https://github.com/Sibgha360/dropdownexample.git
>
> Thanks
>
--
Regards - Ernesto Reinaldo Barreiro
Re: thanks for wonderful work with Wicket 8.
Hi, On Fri, May 3, 2019 at 8:39 AM nino martinez wael < nino.martinez.w...@gmail.com> wrote: > I could use the > > Or a wicket wrapper for > > http://bootstrap-notify.remabledesigns.com/. > > I can try to convince my manager to open-source it. We are using it all over in our application in combination with wicket AJAX/Web sockets. Also - some home grown bootstrap modal wizard - wicket wrapper fro *https://github.com/fronteed/iCheck <https://github.com/fronteed/iCheck>* *And maybe some other home ground components. But this doesn't depend on me.* -- Regards - Ernesto Reinaldo Barreiro
part time remote wicket developer
Hi, Apologies for noise. Does anyone needs a part-time remote experienced wicket developer? Say for 10/15 hours (maybe more) per week? -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hi, Just to follow up. This was neither a wicket error nor a chrome problem but some weird combination of non rolled back transaction + some transaction controlling filter on top of of wicket filter (that was somehow truncating response). On Tue, Apr 16, 2019 at 6:36 PM Maxim Solodovnik wrote: > Maybe non-minimized stacktrace can gave some more info? > > On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro > wrote: > > > > Hi, > > > > Bumping jQuery version to 3.4.0 provides same results (no minimized). > > > > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik > > wrote: > > > > > non minified jquery and/or wicket.mode=DEVELOPMENT > > > May be it will shed some light on this issue ... > > > > > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik < > solomax...@gmail.com> > > > > wrote: > > > > > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > > > > > > > Do you mean jquery non minified jQuery? > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > -- > WBR > Maxim aka solomax > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
And thanks again for feedback and comments! On Thu, Apr 18, 2019 at 10:24 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > Just to follow up. This was neither a wicket error nor a chrome problem > but some weird combination of non rolled back transaction + some > transaction controlling filter on top of of wicket filter (that was somehow > truncating response). > > On Tue, Apr 16, 2019 at 6:36 PM Maxim Solodovnik > wrote: > >> Maybe non-minimized stacktrace can gave some more info? >> >> On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro >> wrote: >> > >> > Hi, >> > >> > Bumping jQuery version to 3.4.0 provides same results (no minimized). >> > >> > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik >> > wrote: >> > >> > > non minified jquery and/or wicket.mode=DEVELOPMENT >> > > May be it will shed some light on this issue ... >> > > >> > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < >> > > reier...@gmail.com> >> > > wrote: >> > > >> > > > Hi, >> > > > >> > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik < >> solomax...@gmail.com> >> > > > wrote: >> > > > >> > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? >> > > > > >> > > > >> > > > Do you mean jquery non minified jQuery? >> > > > >> > > > -- >> > > > Regards - Ernesto Reinaldo Barreiro >> > > > >> > > >> > > >> > > -- >> > > WBR >> > > Maxim aka solomax >> > > >> > >> > >> > -- >> > Regards - Ernesto Reinaldo Barreiro >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hi, Bumping jQuery version to 3.4.0 provides same results (no minimized). On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik wrote: > non minified jquery and/or wicket.mode=DEVELOPMENT > May be it will shed some light on this issue ... > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > wrote: > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > Do you mean jquery non minified jQuery? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Wicket is on development mode already. I'm serving "my own" minified version of jquery. I will play with that next and try to "reorder my code" to see if I can spot what is different. On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik wrote: > non minified jquery and/or wicket.mode=DEVELOPMENT > May be it will shed some light on this issue ... > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > wrote: > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > Do you mean jquery non minified jQuery? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hi, On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik wrote: > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > Do you mean jquery non minified jQuery? -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hi Maxim, Thanks for feedback. wicket-jquery-ui based Wizard works for me as expected (just have tested > Chrome latest at Ubuntu 18.10) > We are using or own home grown implementation of a wizard on top of a custom wrapper around bootstrap modal (I was the person creating those components, so I know them well). We have many similar wizards in application. I was expecting this wizard to be the same :-( I have already tested some of the other wizards and they still work. Funny thing is we are not doing anything particularly different here.. Or so I believe :-) > > On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > I'm experiencing following error > > > > POST > > > > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > > On latest Chrome on Mac. This does not happens with latest FF (So, I > assume > > this is a wicket bug). Is this a known issue? Our application is very > > complicated and I'm not sure I will be able to create a quickstart. > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
