Re: ModalWindow and wicket 10

cket 10 > Hi, > > I thought we already moved the old implementation to wicket-stuff, but > apparently I forgot to do it actually. > > For explanation: the old ModalWindow is riddled with JS and dynamically > generated HTML markup which we didn't want to maintain any more. >

Re: ModalWindow and wicket 10

o wicket-stuff, but > apparently I forgot to do it actually. > > For explanation: the old ModalWindow is riddled with JS and dynamically > generated HTML markup which we didn't want to maintain any more. > > Sven > > > On 20.10.23 11:22, Korbinian Bachl wrote: >

ModalWindow and wicket 10

Hi, just a short question. Since wicket 10 removed ModalWindow and insists now on using ModalDialog even so many features of ModalWindow aren't in ModalDialog existing (for example closeCallback, resize, move, header, closebutton, init of width, height etc.etc). Would it maybe possible if the

Re: Time for Wicket M1?

When looking at https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+10.0 I wondered what Jakarta version is required? Is Jakarta 9.0 enough? Because, it says Java 17 needed - this is even above Jakarta 9.1 abd 10 that both have a JDK 11 baseline? Oh and also what does

Re: an idea: wicket-resilient mode?

- Ursprüngliche Mail - > > If you are ok with a 80% failing page, I cannot help you, because in that > case you can simply come up with another fallback which works 80%. You know > this leads/creeps to exponential growth of failures and work, yes? > > The right way to handle it is to

Re: an idea: wicket-resilient mode?

> ti 11. lokak. 2022 klo 11.12 Korbinian Bachl (korbinian.ba...@whiskyworld.de) > kirjoitti: > >> >> > >> > It is your application so you must know/design how to recover from the >> > error. You either re-render the same page or redir

Re: an idea: wicket-resilient mode?

> > It is your application so you must know/design how to recover from the > error. You either re-render the same page or redirect the user to a > suitable error page. > > ** > Martin > Thats exactly the misunderstanding. If one of 100s of components fails - not even necessarily "made" by

Re: an idea: wicket-resilient mode?

t.com) > kirjoitti: > >> Yes. You can override runtime handling yourself @ >> RequestCycle.onRuntimeException (at least used to be with such name) >> >> In production it is recommended to do so as you best see fit. >> >> ** >> Martin >> >> ma 10. lokak. 2022 kl

an idea: wicket-resilient mode?

Hi, we use wicket for many years now and so far it is a great framework to use. One thing that however seems still a bit of a problem is the way wicket handles (runtime) errors. If you look at a page then the content is often composed of 100's of panels and components. As long as every

Re: [DISCUSSION] Shall we clean-up git branches?

I wouldn't drop any of the wicket-x.x branches as these were the releases and imagine you had to use wicket 1.4 in an old app and need a fix asap? - Ursprüngliche Mail - > Von: "Maxim Solodovnik" > An: "dev" > Gesendet: Donnerstag, 28. April 2022 09:01:09 > Betreff: Re: [DISCUSSION]

Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

PS: with "rendering" I mean the kind of page composition from changed HTML source, not the rerendering in terms of changed on page content due to Java code... I think I have expressed myself not clear and good here. Sorry :( - Ursprüngliche Mail - > Von: "Korbinian

Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

>> > >>> This is probably caused by my change in >> > >>> https://issues.apache.org/jira/browse/WICKET-6963 >> > >>> >> > >>> I have been using this code in production for a couple of weeks now >> > >>> without issue

Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

leton strategy >>> doesn't work. >>> >>> Can you reproduce this issue in a test-case? >>> >>> Thomas >>> >>> On Thu, Mar 31, 2022 at 10:06 AM Maxim Solodovnik >>> wrote: >>> >>>> " tags are only allowed b

Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

lodovnik" > An: "dev" > Gesendet: Donnerstag, 31. März 2022 10:06:34 > Betreff: Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I > get this? > " tags are only allowed before , , > etc. tag" > sounds reasonable :) > > On

wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I get this?

Hi, I deployed our app on 9.9.0 this morning and after initializing a crawl of the page I ended up getting a low quote of 503s. The 503s are always the same: 2022-03-31 09:35:05,031 ERROR [org.apache.wicket.DefaultExceptionMapper] Unexpected error occurred

Re: Rails 7 features

>> >> I'm a bit short on time currently but what I meant with the fewer >> redeploys is not anywhere near this livereload jvm. Why? well, I dont think >> wicket is used that much in "small" projects but in rather larger ones. >> (I know DHL uses it for the GK-Portal - the solution any smaller

Re: Rails 7 features

- Ursprüngliche Mail - >> > >> Could you make a quickstart example use case and we could maybe brainstorm >> about it together, what would actually be the leanest solution? >> > > http://wicketinaction.com/2014/07/build-resources-with-node.js/ > https://github.com/davidB/livereload-jvm

Re: Rails 7 features

Hi Martin, thanks for the details, please see below. - Ursprüngliche Mail - > > From what I've understood you know just some parts of Wicket and this makes > you think some things are hard or even imposible. > Have you considered using Wicket's mounted resource ? it is something >

Re: Rails 7 features

Hi, I've read the article about rails 7 and the way of its javascript multiple times - yet I'm not 100% sure I understood everything - but for me it sounds somehow awesome. You'll seem to end up getting a choice: 3 choices to be exact. A, use rails as an api backend, meaning you can have your

Re: Wicket 10 based on jakarta.** APIs ?

itag, 3. September 2021 14:12:15 > Betreff: Re: Wicket 10 based on jakarta.** APIs ? > On Fri, Sep 3, 2021 at 3:08 PM Korbinian Bachl < > korbinian.ba...@whiskyworld.de> wrote: > >> Oh, ok. >> Why hold on it? >> IE is dead and ECMAScript 2015 (ES6) is here in a

Re: Wicket 10 based on jakarta.** APIs ?

cket 10 based on jakarta.** APIs ? > On Fri, Sep 3, 2021, 12:08 Korbinian Bachl > wrote: > >> Apologies for hijacking this, but can we assume now the following? >> >> wicket 8: java 8 + java apis + servlet 3.1 + jQuery >> wicket 9: java 11 + java apis + servl

Re: Wicket 10 based on jakarta.** APIs ?

Apologies for hijacking this, but can we assume now the following? wicket 8: java 8 + java apis + servlet 3.1 + jQuery wicket 9: java 11 + java apis + servlet 3.1 + JQery wicket 10: java 17 + jakarta apis + servlet 5.x + no jQuery ?? - Ursprüngliche Mail - > Von: "Andrea Del Bene" >

Re: Wicket 10 ideas

Hi, we dont use queueing but we use enclosures in quite a few places. Getting rid of it would mean we have to switch to markup containers holding the content and add additonal layer of complexity and boilerplatecode for us. Beside that: can wicket 10 finally get rid of jQuery? Since IE is now

Re: Wicket site with adblocker @ MS Edge

Option 3: 1) wait for MS to apply the switch to the chromium engine (ditching the current edge engine completely - see: https://www.computerworld.com/article/3325333/web-browsers/with-move-to-rebuild-edge-atop-googles-chromium-microsoft-raises-white-flag-in-browser-war.html ) 2) relax while

wicket 8 migration guide errors

Hi, under https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+8.0 I get various errors in the document like "Unable to locate Jira server for this macro. It may be due to Application Link configuration." and "Fehler beim Ausführen des Makros 'jira' Unable to locate Jira

Re: [VOTE] Release Apache Wicket 8.0.0

+1 - Ursprüngliche Mail - > Von: "Emond Papegaaij" > An: dev@wicket.apache.org > Gesendet: Freitag, 18. Mai 2018 11:58:43 > Betreff: Re: [VOTE] Release Apache Wicket 8.0.0 > +1 > > Tested our application with the complete test suite > Checked signatures and

Re: [DISCUSSION] Java future and Wicket

> It should be build with the latest LTS JDK whatever it is at the moment. > The version of EE4J / Servlet specs are also not relevant to Wicket's > version. > > On Mon, Apr 16, 2018 at 4:03 PM, Korbinian Bachl < > korbinian.ba...@whiskyworld.de> wrote: > >> Ma

Re: [DISCUSSION] Wicket 8 Release

+1 to release - Ursprüngliche Mail - > Von: "Maxim Solodovnik" > An: dev@wicket.apache.org > Gesendet: Dienstag, 3. April 2018 16:36:35 > Betreff: [DISCUSSION] Wicket 8 Release > Hello All, > > I believe it is time to release :) > Do we have any blockers? > >

Re: [DISCUSSION] WICKET-6544 mobile browser detection

- Ursprüngliche Mail - >> even in 2009 it was considered bad: https://www.sitepoint.com/why- >> browser-sniffing-stinks/ >> and in case that is not enough, read what the guy that invented modernizr >> has to say: >> http://farukat.es/journal/2011/02/499-lest-we-forget-or- >>

Re: [VOTE] Release Apache Wicket 8.0.0-M9

18 16:48:18 > Betreff: Re: [VOTE] Release Apache Wicket 8.0.0-M9 > Hi, > > I need your help. what's exactly the caveat about WICKET-6498? It uses > javascript events that might not be supported buy browser? > > On Sun, Feb 11, 2018 at 6:16 PM, Korbinian Bachl < > korbin

Re: [VOTE] Release Apache Wicket 8.0.0-M9

mental. > > IMHO this is warning enough. > > Sven > > > Am 11.02.2018 um 20:03 schrieb Andrea Del Bene: >> Good point. We should also underline that WICKET-6498 breaks custom >> response decoration that might be used to place JavaScript inside body >> tag. &

Re: [VOTE] Release Apache Wicket 8.0.0-M9

+1 to release for M9 IMHO a warning should be added with regards to WICKET-6498 as it is not yet working in a reliable way but may break depending on client specifics; - Ursprüngliche Mail - > Von: "Andrea Del Bene" > An: dev@wicket.apache.org > Gesendet: Sonntag,

Re: 8.0.0 blockers

ts/2018-02-12-wicket- >>>>> 8.0.0-released.md >>>>> But news for 2018 are not being generated >>>>> >>>>> Is there any debugger I can use? >>>>> Or maybe I miss something? >>>>> >>>>> Copyright

Re: 8.0.0 blockers

icket 8 (or shortly >> before the 8.0.0 release) is not the right moment for it. >> >> Regards >> Sven >> >> >> >> Am 02.01.2018 um 11:34 schrieb Martin Makundi: >> >>> If configuration option is final solution then yes, otherwise it ope

Re: 8.0.0 blockers

< >>martijn.dasho...@gmail.com> wrote: >> >>> I’m working on restyling the QuickStart to look like the new >>examples. Not >>> a blocker but would be awesome to include. Will work on it 2nd Jan >>> >>> Martijn >>> >>> >&g

Re: 8.0.0 blockers

May I also mention WICKET-6498? https://issues.apache.org/jira/browse/WICKET-6498 - Ursprüngliche Mail - > Von: "Sven Meier" > An: dev@wicket.apache.org > Gesendet: Freitag, 29. Dezember 2017 16:22:47 > Betreff: Re: 8.0.0 blockers > Not strictly necessary, but I

Re: 8.0.0 blockers

l.com> > An: dev@wicket.apache.org > Gesendet: Mittwoch, 29. November 2017 10:08:15 > Betreff: Re: 8.0.0 blockers > I love to help here > But I don't see clear solution . > > > On Wed, Nov 29, 2017 at 4:06 PM, Korbinian Bachl < > korbinian.ba...@whiskyworld.de>

Re: 8.0.0 blockers

nd provide your "minified and optimized JS file from webdesigner" jquery > version as the main one for wicket . > > On Wed, Nov 29, 2017 at 3:57 PM, Korbinian Bachl < > korbinian.ba...@whiskyworld.de> wrote: > >> Yes, you are right - it has to be optio

Re: 8.0.0 blockers

Yes, you are right - it has to be optional at least, something even the current jQuery reference isn't yet (you only can provide an empty one js file - still a request); >From my experience this all is worse than at the time before jQuery was >introduced to wicket as this really slows down the

Re: 8.0.0 blockers

I'd like some comment on WICKET-6498, as that wicket-JS impl. currently is just not good IMHO as its blocking the DOM with JS; Best, KB - Ursprüngliche Mail - > Von: "Maxim Solodovnik" > An: dev@wicket.apache.org > Gesendet: Mittwoch, 29. November 2017 03:32:48

Re: Question regarding WICKET-6497 unify javascript files

Hello, wouldn't option 2 put the Jjqery.js into it? Best, KB - Ursprüngliche Mail - > Von: "Maxim Solodovnik" > An: dev@wicket.apache.org > Gesendet: Mittwoch, 22. November 2017 07:21:22 > Betreff: Question regarding WICKET-6497 unify javascript files > Hello,

wicket 8 - js to asnyc and or defer?

Hi, after WICKET-6492 seems to take care of the bug of minification and even uniting of the Javascript files of wicket, I wonder if wicket cant even get better in the js part. Currently each page having ajax somehow ends up with following in the head: (1) (2) (3) (4 - inline var and not

Re: WICKET-6481

and if you make it Integer.MAX_VALUE - 1 as default? :) - Ursprüngliche Mail - > Von: "Andrea Del Bene" > An: dev@wicket.apache.org > Gesendet: Dienstag, 17. Oktober 2017 12:11:06 > Betreff: Re: WICKET-6481 > On Tue, Oct 17, 2017 at 9:32 AM, Martin Grigorov

Re: wicket8 : wickets js/ jquery integration

g-javascript/ > > Wicket supports the attribute since > https://issues.apache.org/jira/browse/WICKET-5715 > > Have fun > Sven > > > Am 07.10.2017 um 19:49 schrieb Korbinian Bachl: >> Hi, >> >> currently wicket renders all its jQuery and Ajax stuff right into t

wicket8 : wickets js/ jquery integration

Hi, currently wicket renders all its jQuery and Ajax stuff right into the head, and I wonder why. Current best practice seems to defer all javascript till the end of the page just right before the closing tag to let the browser meanwhile get the DOM and do some work and not get blocked by

wicket-8 m8

Hi, due to the problematic bugs in wicket8 up to m7 (2 x pagestore and filesystemresource-leak), would it be possible to release wicket8-m8 anytime soon? Best, Korbinian

Re: Major page store issue found in 7.8.0, release a 7.8.1?

Please also wicket 8 - this one is a real problem - Ursprüngliche Mail - > Von: "Emond Papegaaij" > An: dev@wicket.apache.org > CC: "Martijn Dashorst" > Gesendet: Mittwoch, 30. August 2017 13:10:27 > Betreff: Re: Major page

Re: wicket 8 / javascript

Hi, > >> >> - JS Code is not compressed/ optimized for production; so far only >> comments are stripped out but no real optimization in terms of newline >> (nearly 3k!) and whitespaces are done >> > > Not true! > At >

wicket 8 / javascript

Hi, after deploying our app with wicket 8, I've seen that the javacript files of AJAX are not really optimised. Issues are: - 2 Files - instead of putting out 1 file of JS for wicket, we get 2 (3 if we count jQuery); I dont see this as good especially since 1 of those files is quite small...

Re: [VOTE] Release Apache Wicket 8.0.0-M7

Hello Andrea, currently the jira shows M7 as unreleased with 1 item toDo, see https://issues.apache.org/jira/projects/WICKET/versions/12340604 Best, KB - Ursprüngliche Mail - > Von: "Andrea Del Bene" > An: dev@wicket.apache.org > Gesendet: Samstag, 12. August

Re: Wicket 8 (M7) release

>> >>>> On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <solomax...@gmail.com> >> wrote: >> >>>> >> >>>> Hello All, >> >>>> >> >>>> I would like to u

Re: Wicket 8 (M7) release

Please a thousand +1 (non-binding) :) - Ursprüngliche Mail - > Von: "Andrea Del Bene" > An: dev@wicket.apache.org > Gesendet: Freitag, 4. August 2017 17:12:43 > Betreff: Re: Wicket 8 (M7) release > Hi, > > I think we are ready to promote Wicket 8 to GA but I

wicket 8.0.0-M7? / FROM: [VOTE] Release Apache Wicket 7.8.0

lodovnik" <solomax...@gmail.com> > An: dev@wicket.apache.org > Gesendet: Mittwoch, 12. Juli 2017 12:47:27 > Betreff: Re: [VOTE] Release Apache Wicket 7.8.0 > WICKET-6419 <https://issues.apache.org/jira/browse/WICKET-6419> might be > blocker for 8.0.0 release ... > &

Re: [VOTE] Release Apache Wicket 7.8.0

Would a wicket 8.0.0 release be possible soon? (I know I'm nagging :) ) - Ursprüngliche Mail - > Von: "Andrea Del Bene" > An: dev@wicket.apache.org > Gesendet: Mittwoch, 12. Juli 2017 11:40:57 > Betreff: Re: [VOTE] Release Apache Wicket 7.8.0 > This vote

wicket8 - enclosure & onBeforeRender

Hi, is it intended that any wicket:enclosure breaks if it is depending on a component that is not added in the constructor but in "onBeforeRender"? e.g: Bezeichnung: value with java: public HomePage(final PageParameters parameters) {

examples8x.wicket.apache.org / 503

Hello, http://examples8x.wicket.apache.org/ is giving me a 503 for several days now. Can you please tell me who is in charge of it? Best, Korbinian

wicket 8 - state of it?

Hi, according to jira (https://issues.apache.org/jira/projects/WICKET/versions/12340604) only 1 open issue before wicket8-m7 (WICKET-6406). So I ask myself, humble wicket devs, how the current plan for the release might be. With JAVA 9 out soon (83 days) wouldnt it be time to move wicket8 at

wicket 6348 / now missing parameter

Hi, in https://issues.apache.org/jira/browse/WICKET-6348 the way how to react on onSelectionChanged(Object object) got changed to now a usage of // Wicket 7.x new CheckBox("id", model) { protected boolean wantOnSelectionChangedNotifications() { return true; }

wicket 8 m5?

Hi, is it planned to have a 8-m5 anytime soon? I ask because quite much changed (e.g.: BookmarkableListenerRequestHandler, other JSON) and I really had some time keeping up the current snapshot builds with my project. Also, any idea when can wicket-8.0 be expected? Best, Korbinian

Re: Use jQuery 3.x by default in 8.x

t; > But anyone can replace wicket-ajax-jquery.js with > getJavaScriptLibrarySettings().setWicketAjaxReference(...) ! > > >> >> On Mon, Mar 20, 2017 at 11:33 AM, Korbinian Bachl < >> korbinian.ba...@whiskyworld.de> wrote: >> >> > Hi, >> >

Re: Use jQuery 3.x by default in 8.x

Hi, while I'm not one of the commiters I still like to respond to this. I'm fine with changing from 1.x to 3.x as IE 10 and lower really has no relevance anymore IMHO. However, the real question that came into my mind: Why not just use plain js / vanilla js? When it was decided to go to

Re: WICKET-6088 / breaking of custom markup manipulation

gorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Oct 3, 2016 at 1:50 PM, Korbinian Bachl < > korbinian.ba...@whiskyworld.de> wrote: > >> Hello, >> >> I've just done some debugging work for Ingo Renner. His project is some

WICKET-6088 / breaking of custom markup manipulation

Hello, I've just done some debugging work for Ingo Renner. His project is somehow similar to the brix cms and the way of manipulating the components within the markup stream resolution. This worked in 6.x and 7.0-7.2, but was broken in 7.3+ with commit:

Re: [VOTE] Release Apache Wicket 6.5.0

How can it be published there on 19th of January? That's two (2) days before even the vote was closed! -- Korbinian - Ursprüngliche Mail - Von: Guillaume Smet guillaume.s...@gmail.com An: dev@wicket.apache.org Gesendet: Mittwoch, 23. Januar 2013 01:28:29 Betreff: Re: [VOTE] Release

wicket 6.0 - programmatic HTTPS switch

Hello, is it possible in wicket 6.0 to programatically switch to SSL mode? - I've read that according to the wiki: HttpsMapper has been refactored to make subclassing easier - but couldnt find the jira for it? Reason why I'm asking is that I'm trying to get Brix CMS working with wicket 5 or

Re: Ajax in Wicket.next

Well, I think there is consent that we can say current wicket ajax is quite broken and a big pain in everyday usage. The current ajax means loads of code in java for even trivial things. Triple-checking that a component knows its ajax and so on. So even *if* it will break api in future, I

Re: Ajax in Wicket.next

tetsu, ever tried to: - get an AjaxRequestTarget in a component that was not designed by ajax in mind? - tried to ajaxify a table-row in a dataTable component? - tried ajax with repeaters? - tried to interact with a modal window from inside in case you have a pure non-ajax page within it?

Re: Ajax in Wicket.next

Hi Martin, Am 20.09.11 09:59, schrieb Martin Grigorov: ... Well, I think there is consent that we can say current wicket ajax is quite broken and a big pain in everyday usage. Really? Is that broken ? Neither mailing lists questions nor tickets prove that statement. The current ajax means

Re: Ajax in Wicket.next

Heya, Am 20.09.11 11:37, schrieb Martin Grigorov: ... Ok, well, wicket consists of components. So basically it is making a page full of a tree with components. Wicket now could scan the component if it has any Ajax on it - then auto add what it needs like the setOuput... - so we got rid of

Re: Ajax in Wicket.next

Am 20.09.11 12:30, schrieb Martin Grigorov: On Tue, Sep 20, 2011 at 1:11 PM, Korbinian Bachl - privat korbinian.ba...@whiskyworld.de wrote: ... Wrong approach IMHO. The question is: Do we need outprinted Id's to find an element in DOM? Answer is: No, we don't as long as we know the path

Re: Ajax in Wicket.next

Am 20.09.11 13:11, schrieb Pointbreak: I'm completely agreeing with Martin on this one. The things you are suggesting imho have the following consequences: - Wicket implementation becomes way more complicated, because Wicket has to translate between component hierarchy and browser DOM-tree,

Re: Roadmap for Wicket 6

My wish list: 1. Java 6 2. JEE6 where possible like e.g. CDI; 3. Modularization using OSGI 4. AJAX overhaul: currently Ajax is a pain in case it gets more complicated as one - needs to add components to target AND page hierarchy; - needs to do .setOutputId(true) all over - can't touch

Re: JRebel and wicket

Hi, I don't use jRebel but the differentiation of the add and addOrReplace method is something that I still don't understand what it's good for. Actually if you do in java: String foo; foo = new String(world); no one ever would think about throwing an error because one does foo = new

Re: [vote] release Wicket 1.4.13

+1 release this time :) Am 27.10.10 09:08, schrieb Jeremy Thomerson: This vote is to release wicket 1.4.13. This is a bugfix release on the 1.4.x (stable) branch. Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13/ Artifacts:

Re: 1.4.13 release?

Regarding a release the following issue is a complete showstopper that has to be cleared first: https://issues.apache.org/jira/browse/WICKET-3112 Best Korbinian PS: this is same as Brian Toppings mentioned issue but now existing in wicket JIRA Am 16.10.10 08:32, schrieb Jeremy Thomerson:

Re: ComponentTag#append()

Hi, from a logical point its required IMHO so +1 from me Best Am 28.07.10 15:37, schrieb Martin Grigorov: Hi, Since recently we have ComponentTag#append(). It will be included in 1.4.10. Do we need #prepend() as well ? I can see users starting asking for this.

wicket examples on WicketStuff

Hello, the first three examples here http://www.wicketstuff.org/wicket14/repeater/ seem to be broken. At least when accessing it I get an Internal Error. Could someone with please have a look at this? Best, Korbinian

Re: wicket 1.5 build is failing because of 1.6 deps...

+1 to move to 1.6; IMHO wicket 1.5 should be state of art in all terms and in case you stuck to JDK 1.5 you still can use wicekt 1.4; IMHO it makes no sense to aim at a plattform thats already EOL like 1.5 is; (and 1.7 will be out by the time wicket 1.5 is release IMHO) my 2cents,

Re: wicket 1.5 build is failing because of 1.6 deps...

1.5 will be a major one, not minor - so where's the point? Best, Korbinian Carl-Eric Menzel schrieb: Because, from their (admittedly conservative) point of view, you don't move essential systems to a platform before you really know it. Or before your tool vendor finally manages to update

WICKET-1597 clearing

Hi, IMHO WICKET-1597 should be applied soon, however there seems 1 last question from Juergen Donnerstag needed to be clearified (and maybe implemented): Applied the change and modified the test cases. Since I wasn't sure if /a/?param is the same as /a?param, I didn't commit it but attached

Re: WICKET-1597 clearing

recall exactly but I think I was under the impression that Wicket didn't make a difference. /a?.. seemed to return the same result as /a/?.. Whether is by intention or by accident is what I wasn't sure about. -Juergen On Thu, Jun 11, 2009 at 11:19 AM, Korbinian Bachl - privatkorbinian.ba

Re: i want to crate new help system to my existing application

Martijn, that won't happen - you forgot to add your bank account details! *SCNR* Martijn Dashorst schrieb: Hi, I really want to help you implement what you want. My daily rate is €2000 excluding tax. I would like to receive the first three days in advance. While waiting for the wire transfer

SpringBean DataProvider / LoadableDetachableModels

Hi, is there a reason that SpringBean is not working automatically within IDataProvider LoadableDetachableModel (you'll need to call InjectorHolder.getInjector().inject(this); explicitely)? If no I would create a jira request for it. Best, Korbinian

Re: Enterprise Application

There is also a german based travel agency that has deployed 20-30 sites based on one Wicket code base iirc. Der.de, Dertour.de or meiers-weltreisen.de are mentioned there, too i think the use tapestry in main parts, so they are not a good example. mm:) don't think *sigh*... look at the

Re: security article on TSS (partly covering wicket)

, Korbinian Martijn Dashorst schrieb: How is HiddenField insecure in your opinion? Martijn On Wed, Jul 30, 2008 at 10:59 PM, Korbinian Bachl - privat [EMAIL PROTECTED] wrote: HI, under http://www.theserverside.com/tt/articles/article.tss?l=AreJavaWebApplicationsSecure is an article covering java WebApps

Re: security article on TSS (partly covering wicket)

Hi Eelco, towards you, but if they were, I guess that's the danger of being the messenger ;-) yeah the messenger... damn job :P I mean, I also dont think the rection on theserverside was a good choice. Honestly, even the writers didnt know wicket well enough to things like crypted URLs

security article on TSS (partly covering wicket)

HI, under http://www.theserverside.com/tt/articles/article.tss?l=AreJavaWebApplicationsSecure is an article covering java WebApps security; On part 2 it also looks at webframeworks for java including wicket 1.3.x - it mentions Wicket has only one component (HiddenField) vulnerable to

Re: Swarm Wicket 1.4 m2

. I am afraid your only option at this time is to check out the entire wicket security project from svn and patch it to compile against wicket 1.4 Again sorry for the inconvenience. Maurice On Sun, Jul 6, 2008 at 8:19 PM, Korbinian Bachl - privat [EMAIL PROTECTED] wrote: Hello, I just spend some

Swarm Wicket 1.4 m2

Hello, I just spend some time to change my app (on wicket 1.4) to use the SWARM implementation of WASP. However, it seems that WASP 1.3.0 as well as the current 1.3-Snapshot (1.3.1) wont work with 1.4; The error is nearly allways the same: 1.3.1: java.lang.NoSuchMethodError:

Swarm + Wicket 1.4m2

Hello, I just spend some time to change my app (on wicket 1.4) to use the SWARM implementation of WASP. However, it seems that WASP 1.3.0 as well as the current 1.3-Snapshot (1.3.1) wont work with 1.4; The error is nearly allways the same: 1.3.1: java.lang.NoSuchMethodError:

Re: About the coupling between design and code

Hello Radev, I've also developed some applications with Lotus, and there the abstraction between the design and the code is bound only by the name of the elements. There is no need to know anything about nesting of the elements. Such decoupling between the design and code could make the

Re: Id on Components

Thanks for clear answer; In case i I add a feature request: would it even be possible to change the Id at a later time? I catch me regularly to add Components like Links, Panels etc. to a ListComponent and have them rendered later on to different Markups in different ListViews - and that

Re: Id on Components

great News! Thx, Korbinian Johan Compagner schrieb: Configuring the prefix wicket is something on my todo for 1.5 On 4/12/08, Korbinian Bachl - privat [EMAIL PROTECTED] wrote: Thanks for clear answer; In case i I add a feature request: would it even be possible to change the Id at a later

Re: Id on Components

it to the listitem? Martijn On 4/12/08, Korbinian Bachl - privat [EMAIL PROTECTED] wrote: Thanks for clear answer; In case i I add a feature request: would it even be possible to change the Id at a later time? I catch me regularly to add Components like Links, Panels etc. to a ListComponent

Re: Id on Components

Hi Matej, sorry for this noobish question, but could you please give me an example of your factories idea? Best, Korbinian Matej Knopp schrieb: On Sat, Apr 12, 2008 at 10:24 AM, Korbinian Bachl - privat [EMAIL PROTECTED] wrote: Thanks for clear answer; In case i I add a feature request

Id on Components

Hi, short question: Why isn't it possible to have a setId(String id) on the components? - Is it really necessary that they know their id at creation-time? Regards, Korbinian

ModalWindow + Submit

Hello, I've noticed that a Form inside a ModalWindow can't be submitted using the onSubmit function (and dislikes a standard submit button) but instead requires an AjaxButton to call the action - why is this so? It makes my life currently somehow hard as I need 2 nearly identical forms - one

Re: ModalWindow + Submit

is talking about in a new page for your modal window. Maurice On Tue, Apr 8, 2008 at 2:59 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: Korbinian Bachl - privat wrote: Hello, I've noticed that a Form inside a ModalWindow can't be submitted using the onSubmit

Re: ModalWindow + Submit

Vazquez Wael [EMAIL PROTECTED] wrote: Korbinian Bachl - privat wrote: Hello, I've noticed that a Form inside a ModalWindow can't be submitted using the onSubmit function (and dislikes a standard submit button) but instead requires an AjaxButton to call the action - why is this so? It makes my

AjaxLink/ AjaxFallbackLink ?

Hello, wicket has two AjaxLinks: AjaxLink + AjaxFallbackLink Why are those 2 needed? IMHO the behaviour of the AjaxFallbacklink should be the same as AjaxLink (degrade if no JS is available) and I wonder if in wicket 1.4 AjaxLink could degrade by default and AjaxFallbackLink could be made

  1   2   >