Re: [VOTE] Release Apache Wicket 7.5.0
[X] Yes, release Apache Wicket 7.5.0 (non-binding) [ ] No, don't release Apache Wicket 7.5.0, because ... Tested our main webapp - works fine. cheers, Jonas On Wed, Oct 19, 2016 at 9:28 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > This is a vote to release Apache Wicket 7.5.0 > > Please download the source distributions found in our staging area > linked below. > > I have included the signatures for both the source archives. This vote > lasts for 72 hours minimum. > > [ ] Yes, release Apache Wicket 7.5.0 > [ ] No, don't release Apache Wicket 7.5.0, because ... > > Distributions, changelog, keys and signatures can be found at: > > https://dist.apache.org/repos/dist/dev/wicket/7.5.0 > > Staging repository: > > https://repository.apache.org/content/repositories/ > orgapachewicket-1075/ > > The binaries are available in the above link, as are a staging > repository for Maven. Typically the vote is on the source, but should > you find a problem with one of the binaries, please let me know, I can > re-roll them some way or the other. > > Staging git repository data: > > Repository: g...@github.com:dashorst/wicket.git > Branch: build/wicket-7.5.0 > Release tag: rel/wicket-7.5.0 > > > > > The signatures for the source release artefacts: > > > Signature for apache-wicket-7.5.0.zip: > > -BEGIN PGP SIGNATURE- > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlgHyLgACgkQJBX8W/xy/UVtJQCfazMNKzMMG5y+GTnCNg0YloBB > IB0Amwdp/H6z78kXds8kTJNBXJAVlCVc > =yXrI > -END PGP SIGNATURE- > > Signature for apache-wicket-7.5.0.tar.gz: > > -BEGIN PGP SIGNATURE- > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlgHyLgACgkQJBX8W/xy/UUVtgCgx2kALIRDUGdXHjl1hQwOPhzW > NVYAn0VNdt96cd5VmIW7nIFSb0PidYbH > =ob3v > -END PGP SIGNATURE- > > > > CHANGELOG for 7.5.0: > > ** Sub-task > > * [WICKET-6243] - ResourceReferenceAutolink component resolved by > AutoLinkResolver ignores session locale changes > > ** Bug > > * [WICKET-5972] - Datepicker "Close" text overlays 'x' icon. > * [WICKET-6136] - AutoCompleteTextField issue in Android 5.1.1 > * [WICKET-6192] - Remove recreateBookmarkablePagesAfterExpiry > check in AbstractBookmarkableMapper#mapHandler > * [WICKET-6209] - requesting focus on disabled field fails with error > in IE8 > * [WICKET-6214] - ModalWindow broken on IE > * [WICKET-6215] - Test fail when non empty model is set to > PasswordTextField > * [WICKET-6216] - Problem with queued components and border > * [WICKET-6217] - Enclosure broken within Border/Panel > * [WICKET-6219] - Fragment fails to report an error in development mode > * [WICKET-6221] - WicketTester - missing border path > * [WICKET-6222] - renderHead not called with anonymous inner Border > class > * [WICKET-6225] - Button wrongly sets its model object as 'value' > attribute > * [WICKET-6227] - CharSequenceResource calculates wrong length > when there are unicode symbols > * [WICKET-6230] - Infinite redirection when using > UrlPathPageParametersEncoder > * [WICKET-6231] - wicket:enclosure and getVariation(). > * [WICKET-6232] - When sending binary data from server to client, > wicket-websocket-jquery.js throws error "message.indexOf is not a > function" > * [WICKET-6235] - TableTree#updateNode() fails if no corresponding > node is visible > * [WICKET-6236] - Files.remove() causes a 5 seconds delay instead > of 500ms as was intended > * [WICKET-6237] - PageRequestHandlerTracker doesn't work with > IRequestHandlerDelegate > * [WICKET-6238] - pub2 Wicket example isn't switching the beer images > * [WICKET-6241] - CheckingObjectOutputStream should track the > original instance, before writeReplace() > * [WICKET-6242] - Weak concurrency management in > AuthenticatedWebSession#signedIn > * [WICKET-6244] - Palette does not list unselected options > * [WICKET-6245] - Open up CsrfPreventionRequestCycleListener for > extension > * [WICKET-6249] - Invalid state of LoadableDetachableModel with > exception during load() > * [WICKET-6250] - FileUploadField does not deteach models and > fails to null the reference to the transient fileUploads field if > forceCloseStreamsOnDetach is false > * [WICKET-6254] - Wicket WebSockets problem behind HTTP proxy > without servlet context > > ** Improvement > >
Re: [wicket8] Lambdas everywhere (just models for now)
We experimented with lambda based IModels when Java 8 was released. Bottom line was that serializable Lambdas are quite a problem. Both javac and ecj had (and probably still have) lots of bugs related to serializable lambdas. Another problematic area was obfuscation. There wasn't any easy way to let proguard handle lambda based IModels without actually excluding all those classes from obfuscation. This was what made us finally abandon the idea of lambda based IModels, at least for now. cheers, Jonas On Tue, Oct 6, 2015 at 11:55 PM, Michael Mosmann wrote: > Maybe this is useful: > https://github.com/flapdoodle-oss/de.flapdoodle.wicket/blob/master/models/src/test/java/de/flapdoodle/wicket/model/TestModelTransformations.java > .. The model code should work with java8 and lambdas... > > Mm:) > > Am 6. Oktober 2015 23:37:34 MESZ, schrieb Michael Mosmann < > mich...@mosmann.de>: > >I am not sure about the generic stuff... If you write only lamdas there > >will be no issue..but if you reuse some code, there could be some need > >of 'super' in it.. > > > >But that's nothing i can build in my mind.. I need something like > >eclipse to make it right. So maybe next week.. :) > > > >Mm:) > > > > > >Am 6. Oktober 2015 22:48:32 MESZ, schrieb Martin Grigorov > >: > >>/me likes !!! > >> > >>Once it is buildable with javac: > >> > >>*) Since it doesn't need changes in any of the current Wicket classes > >I > >>think it could be added to WicketStuff 7.x and battle tested until > >>Wicket > >>8.0.0 is out. > >> > >>*) What is the purpose of WriteOnlyModel? > >>My concern is that Wicket will fail every time such model is used in a > >>component when this component is being rendered. > >> > >>*) I think you have to name some of the methods #map and #flatMap, and > >>add > >>"Monad" somewhere in the javadoc. Just to make it more fancy :-) > >> > >>Martin Grigorov > >>Wicket Training and Consulting > >>https://twitter.com/mtgrigorov > >> > >>On Tue, Oct 6, 2015 at 11:15 AM, Martijn Dashorst < > >>martijn.dasho...@gmail.com> wrote: > >> > >>> I've created a Lambdas class that compiles just fine in ECJ but > >fails > >>> using javac. > >>> > >>> https://gist.github.com/dashorst/da876be2f01770e862a5 > >>> > >>> The benefit of this way is that we don't perpetuate SerializableFoo > >>> (Foo==[Function, Consumer, Predicate, Supplier, ...]) but instead > >>> require that the passed in stuff is in fact serializable. > >>> > >>> This way companies that have their own SerializableFunction et al, > >>kan > >>> pass those references into our Lambda models. > >>> > >>> Unfortunately this is currently way beyond the capabilities of > >javac. > >>> > >>> Check out the code above (the signature is quite hard to read, but > >in > >>> use it is awesome, just use Eclipse 4.5.1) > >>> > >>> Martijn > >>> > >>> -- > >>> Become a Wicket expert, learn from the best: > >>http://wicketinaction.com > >>> > > > >-- > >Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail > >gesendet. > > -- > Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail > gesendet. >
Re: [VOTE] Release Apache Wicket 6.18.0
[X] Yes, release Apache Wicket 6.18.0 (non binding) Tested our main webapp, seems to work fine Cheers, Jonas On Fri, Oct 31, 2014 at 12:58 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > This is a vote to release Apache Wicket 6.18.0 > > Please download the source distributions found in our staging area > linked below. > > I have included the signatures for both the source archives. This vote > lasts for 72 hours minimum. > > [ ] Yes, release Apache Wicket 6.18.0 > [ ] No, don't release Apache Wicket 6.18.0, because ... > > Distributions, changelog, keys and signatures can be found at: > > https://dist.apache.org/repos/dist/dev/wicket/6.18.0 > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachewicket-1030/ > > The binaries are available in the above link, as are a staging > repository for Maven. Typically the vote is on the source, but should > you find a problem with one of the binaries, please let me know, I can > re-roll them some way or the other. > > > > > The signatures for the source release artefacts: > > > Signature for apache-wicket-6.18.0.zip: > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlRTb2UACgkQJBX8W/xy/UW1egCg1LOkWMrnD+FJoHKjp7Gulyvm > s+UAoMNN/mgMKo+p33h3vt4fnLTemLGT > =RpfO > -END PGP SIGNATURE- > > Signature for apache-wicket-6.18.0.tar.gz: > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlRTb2UACgkQJBX8W/xy/UVZcACguyKdrM0byfMp5IWqzwFMx5Lo > i6UAn25gHcC0w8QWiNJXV7u99iTHssaP > =+QQW > -END PGP SIGNATURE- > > > > CHANGELOG for 6.18.0: > > > ** Bug > > * [WICKET-5265] - FencedFeedbackPanel is broken with > RefreshingView(and it's implementations) > * [WICKET-5326] - Wicket doesn't encrypt links and Ajax URLs for > mounted pages when CryptoMapper is used > * [WICKET-5689] - Nested Redirects and REDIRECT_TO_BUFFER > * [WICKET-5698] - WebApplication#unmount() unmounts the whole > compound mapper if some of its inner ones matches > * [WICKET-5699] - wicket-atmosphere 0.20 should use wicket-webjars > 0.4.3 > * [WICKET-5701] - WebSocketRequestHandler is not set as a > scheduled and thus RequestCycle#find(AjaxRequestTarget.class) doesn't > work > * [WICKET-5704] - IllegalArgument exception with wicket:child in > ajaxrequest > * [WICKET-5706] - ResourceUtils.getLocaleFromFilename cannot > handle filenames with classifiers > * [WICKET-5711] - OnChangeAjaxBehavior should listen for both > 'inputchange' and 'change' events for TextField and TextArea > * [WICKET-5712] - SecuritySettings.setEnforceMounts() does not > work when the mounted mapper is not in the root compound mapper > * [WICKET-5714] - MockHttpServletRequest.buildRequest() should > work for parameters with multiple values with multipart content type > * [WICKET-5716] - wicket-autocomplete prevents "change"-listener > when leaving input via mouse click > * [WICKET-5717] - Url.parse/toString should support fragment > * [WICKET-5719] - Wicket-atmosphere should warn about phone home > * [WICKET-5720] - Method Strings.join doesn't work correctly if > separator is empty. > * [WICKET-5723] - CheckGroupSelector with disabled checks > * [WICKET-5731] - Using "Submit" button in Ajax DropDownChoice > example leads to broken HTML page > * [WICKET-5736] - Atmosphere Eventbus throws Concurrent > Modification Exception > > ** Improvement > > * [WICKET-5691] - Wicket FileUploadField.getFileUploads() should > never return null. > * [WICKET-5692] - Misleading message in PropertyValidator > * [WICKET-5694] - Add WicketTester assertion methods for > component's markup style, variation and locale > * [WICKET-5710] - StringValidator should set 'minlength' attribute > to input and textarea > * [WICKET-5715] - Allow setting 'async' attribute on reference >
Re: [VOTE] Release Apache Wicket 6.16.0
[X] Yes, release Apache Wicket 6.16.0 (non binding) Tested with our main web app. Seems to work fine. Cheers, Jonas
Re: [VOTE] Release Apache Wicket 6.15.0
[X] Yes, release Apache Wicket 6.15.0 (non binding) Tested with our main web app. Seems to work fine. On Thu, Apr 17, 2014 at 12:56 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > This is a vote to release Apache Wicket 6.15.0 > > Please download the source distributions found in our staging area > linked below. > > I have included the signatures for both the source archives. This vote > lasts for 72 hours minimum. > > [ ] Yes, release Apache Wicket 6.15.0 > [ ] No, don't release Apache Wicket 6.15.0, because ... > > Distributions, changelog, keys and signatures can be found at: > > https://dist.apache.org/repos/dist/dev/wicket/6.15.0 > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachewicket-1014/ > > The binaries are available in the above link, as are a staging > repository for Maven. Typically the vote is on the source, but should > you find a problem with one of the binaries, please let me know, I can > re-roll them some way or the other. > > > > The signatures for the source release artefacts: > > apache-wicket-6.15.0.tar.gz: > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlNPB8AACgkQJBX8W/xy/UUIlgCgsRqpylFm+JIHsfrTfcQI0YZA > XmoAoKZbXv7LfEYmoj/t9wPdr05S5EX1 > =Xbxq > -END PGP SIGNATURE- > > apache-wicket-6.15.0.zip: > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlNPB8AACgkQJBX8W/xy/UUmHQCfRAFaprglWYJS0XMHy/H77y1j > b1AAn1J7i5a+JFzFf3bXGQoiMShG92V5 > =u4er > -END PGP SIGNATURE- > > > > Release Notes - Wicket - Version 6.15.0 > > ** Sub-task > > * [WICKET-5510] - Avoid using jQuery.text() when possible. It is very > slow in IE > * [WICKET-5554] - Disable second level pages store because it is > efficient only when manually configured > > ** Bug > > * [WICKET-5243] - JS: High stack size in Function Executor causes "too > much recursion" > * [WICKET-5284] - Too deep recursion in AbstractHierarchyIterator > * [WICKET-5504] - AjaxRequestTarget.append/prependJavaScript cannot > handle scripts with new-lines anymore > * [WICKET-5505] - DefaultPropertyResolver does not respect JavaBean > conventions > * [WICKET-5506] - DefaultPropertyResolver should resolve the Property > according to the getter first > * [WICKET-5509] - Wicket examples' MailTemplate from Page is broken > * [WICKET-5517] - IE11 returns false for Wicket.Browser.isIE() > * [WICKET-5518] - FormComponent.updateCollectionModel does not handle > unmodifiableList > * [WICKET-5521] - Stateless forms does not work when > RecreateMountedPagesAfterExpiry turned off > * [WICKET-5522] - Failing HTTPS redirect to RequireHttps annotated > pages with ONE_PASS_RENDER strategy > * [WICKET-5523] - Ajax indicator not working when display is set to > none in css > * [WICKET-5532] - NPE calling PackageResource.getResourceStream() if > there is no RequestCycle defined > * [WICKET-5534] - DataTable component must throw an exception when > attached to non- element > * [WICKET-5536] - Error message without parmeters filled. > * [WICKET-5537] - Wicket.DOM.toggleClass is called with additional "#" > inside AutoLabelResolver > * [WICKET-5541] - NullPointerException in > SubscribeAnnotationEventSubscriptionInvoker on remove of component from > page > * [WICKET-5545] - Cannot use redirect in ModalWindow's > page#onInitialize() > * [WICKET-5546] - Adding behavior in component instantiation listener > causes Page.onInitialize() being called even if constructor throws an > exception > * [WICKET-5547] - Javadoc for ReuseIfModelsEqualStrategy should mention > that models must implement hashCode() method > * [WICKET-5548] - Websocket initialization URL is not valid when filter > is not mapped to root. > > ** Improvement > > * [WICKET-5508] - Memory model improvements for Session fields > * [WICKET-5512] - Allow using child selector for JS event bindings > * [WICKET-5520] - improve reusability of DataTable and > AbstractPageableView > * [WICKET-5528] - Allow models of subtypes of Select type parameter in > SelectOption constructor > * [WICKET-5529] - Add WebSocketBehavior/Resource#onPush() callback > method > * [WICKET-5531] - Create new placeholder tag to indicate where header > contributions should appear > * [WICKET-5538] - When using Component.setDefaultModel, only detach the > previous model if the new one is different > * [WICKET-5549] - continueToOriginalDestination() fails after > redirectToInterceptPage() on AjaxRequest > > ** New Feature > > * [WICKET-831] - Return response status 404 when a mapper cannot decode > a request url > * [WICKET-2542] - Prov
Re: [VOTE] Release Apache Wicket 6.14.0 - second try
[X] Yes, release Apache Wicket 6.14.0 (try 2) (non binding) Tested our main webapp, plus verified the jira tracks I've filed (WICKET-5469, WICKET-5493) cheers, Jonas On Fri, Feb 14, 2014 at 4:01 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > This is a vote to release Apache Wicket 6.14.0 - try 2 > > This updated release includes a true fix for 5499, and a better error > log in wicket-ajax.js when binding fails, and a minor improvement for > some javadoc. > > Please download the source distributions found in our staging area > linked below. > > I have included the signatures for both the source archives. This vote > lasts for 72 hours minimum. > > [ ] Yes, release Apache Wicket 6.14.0 > [ ] No, don't release Apache Wicket 6.14.0, because ... > > Distributions, changelog, keys and signatures can be found at: > > https://dist.apache.org/repos/dist/dev/wicket/6.14.0 > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachewicket-1005/ > > The binaries are available in the above link, as are a staging > repository for Maven. Typically the vote is on the source, but should > you find a problem with one of the binaries, please let me know, I can > re-roll them some way or the other. > > > > The signatures for the source release artefacts: > > apache-wicket-6.14.0.zip.asc > > -BEGIN PGP SIGNATURE- > > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > Comment: GPGTools - https://gpgtools.org > > > iEYEABECAAYFAlL+LS0ACgkQJBX8W/xy/UX/8ACgvodMozusdl4w0mZKl0DXjq0W > > +7wAoJ7tamy1sGeP6b5DSNrUVUq5pkp9 > > =BXJk > > -END PGP SIGNATURE- > > apache-wicket-6.14.0.tar.gz.asc > > -BEGIN PGP SIGNATURE- > > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > Comment: GPGTools - https://gpgtools.org > > > iEYEABECAAYFAlL+LSwACgkQJBX8W/xy/UUDiACgjhnZzVRFf7rgKpP0XFmO3KAM > > /MsAnj5qOjKYrVoM15VLMngXF7ONM4AS > > =8NdL > > -END PGP SIGNATURE- > > > > Release Notes - Wicket - Version 6.14.0 > > ** Bug > > * [WICKET-4697] - Autolinking not working as soon as component gets >a wicket:id > > * [WICKET-5043] - Page not mounted with WebApplication#mountPackage > > * [WICKET-5449] - Missing chapter 2 is causing off-by-one page names >in the guides URL links > > * [WICKET-5460] - onBeforeRender called too early on stateless page > > * [WICKET-5462] - Ajax form-component-label repainting fails when >setResponsePage() is used to navigate away from >the page that has previously failed form > validaiton > > * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in > combination with Wizards > > * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws >ComponentNotFoundException as a side-effect > > * [WICKET-5467] - NumberTextField should support "any" as valid step > attribute value > > * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends >"/" after query parameters > > * [WICKET-5469] - ModalWindow unload warning always displayed (even > if window is closed) > > * [WICKET-5472] - PackageResource#internalGetResourceStream() should >return ProcessingResourceStream only when the > resource is existing > > * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions >correctly > > * [WICKET-5477] - CSS class is not applied to for data filter > > * [WICKET-5478] - Wrong JavaDoc for WicketTester > > * [WICKET-5480] - AutoLabelResolver creates null pointer exception > in 6.13 > > * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named >annotations > > * [WICKET-5484] - WebPageRenderer must not render full page in Ajax >requests > > * [WICKET-5486] - WebPageRenderer should honor > RedirectPolicy.ALWAYS_REDIRECT more consistently > > * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning >undefined on IE8, positions calendar out of > viewport > > * [WICKET-5492] - WebApplication ignores a SecurityException when >reading the configuration type > > * [WICKET-5496] - Wrong translation of RangeValidator.minimum and > RangeValidator.maximum > > * [WICKET-5497] - NPE in JsonUtils when the value is null > > * [WICKET-5499] - Page is not touched during initialization > > * [WICKET-5500] - Ignore the path parameters when reading the page > class > > * [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050 > > ** Improvement > > * [WICKET-5288] - Allow
Re: [VOTE] Release wicket 6.14.0
[X] Yes, release Apache Wicket 6.14.0 (non binding) Tested our main webapp, plus verified the jira tracks I've filed (WICKET-5469, WICKET-5493) cheers, Jonas On Wed, Feb 12, 2014 at 9:51 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > This is a vote to release Apache Wicket 6.14.0 > > Please download the source distributions found in our staging area > linked below. > > I have included the signatures for both the source archives. This vote > lasts for 72 hours minimum. > > [ ] Yes, release Apache Wicket 6.14.0 > [ ] No, don't release Apache Wicket 6.14.0, because ... > > Distributions, changelog, keys and signatures can be found at: > > https://dist.apache.org/repos/dist/dev/wicket/6.14.0 > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachewicket-1004/ > > The binaries are available in the above link, as are a staging > repository for Maven. Typically the vote is on the source, but should > you find a problem with one of the binaries, please let me know, I can > re-roll them some way or the other. > > > > The signatures for the source release artefacts: > > apache-wicket-6.14.0.zip.asc > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8 > zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE > =4QkG > -END PGP SIGNATURE- > > apache-wicket-6.14.0.tar.gz.asc > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org > > iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM > KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc > =3DVp > -END PGP SIGNATURE- > > > > Release Notes - Wicket - Version 6.14.0 > > ** Bug > > * [WICKET-4697] - Autolinking not working as soon as component gets > a wicket:id > > * [WICKET-5043] - Page not mounted with WebApplication#mountPackage > > * [WICKET-5449] - Missing chapter 2 is causing off-by-one page names > in the guides URL links > > * [WICKET-5460] - onBeforeRender called too early on stateless page > > * [WICKET-5462] - Ajax form-component-label repainting fails when > setResponsePage() is used to navigate away from > the page that has previously failed form > validaiton > > * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in > combination with Wizards > > * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws > ComponentNotFoundException as a side-effect > > * [WICKET-5467] - NumberTextField should support "any" as valid step > attribute value > > * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends > "/" after query parameters > > * [WICKET-5469] - ModalWindow unload warning always displayed (even > if window is closed) > > * [WICKET-5472] - PackageResource#internalGetResourceStream() should > return ProcessingResourceStream only when the > resource is existing > > * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions > correctly > > * [WICKET-5477] - CSS class is not applied to for data filter > > * [WICKET-5478] - Wrong JavaDoc for WicketTester > > * [WICKET-5480] - AutoLabelResolver creates null pointer exception > in 6.13 > > * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named > annotations > > * [WICKET-5484] - WebPageRenderer must not render full page in Ajax > requests > > * [WICKET-5486] - WebPageRenderer should honor > RedirectPolicy.ALWAYS_REDIRECT more consistently > > * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning > undefined on IE8, positions calendar out of > viewport > > * [WICKET-5492] - WebApplication ignores a SecurityException when > reading the configuration type > > * [WICKET-5496] - Wrong translation of RangeValidator.minimum and > RangeValidator.maximum > > * [WICKET-5497] - NPE in JsonUtils when the value is null > > * [WICKET-5499] - Page is not touched during initialization > > * [WICKET-5500] - Ignore the path parameters when reading the page > class > > * [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050 > > ** Improvement > > * [WICKET-5288] - Allow
Wicket 6.11.0 release date
Hi all, according to JIRA, the Wicket 6.11.0 release was due last friday. While I understand you don't want to release anything on a friday the 13th, I'd like to ask what's the planned release date for that release. Cheers, Jonas
Re: Warnings from RequestCycle.handleException(Exception)
Do you want me to provide a patch? > I agree that this might be a useful default in some cases, but how about > at > > least using a > > separate Logger instance for this, so we can get rid of > > these warnings without silencing all of RequestCycle's logging? > > > > I don't mind doing this change. > >
Re: Warnings from RequestCycle.handleException(Exception)
I agree that this might be a useful default in some cases, but how about at least using a separate Logger instance for this, so we can get rid of these warnings without silencing all of RequestCycle's logging? Cheers, Jonas On Sat, Apr 27, 2013 at 11:12 PM, Igor Vaynberg wrote: > in many cases this exception will lead to the error page, so its not > just debugging information. this is the case i would rather wicket be > loud by default to help while developing and have interested parties > silence the logger in production systems... > > -igor > > On Sat, Apr 27, 2013 at 11:43 AM, Martin Grigorov > wrote: > > ivaynberg: ping > > > > > > On Fri, Apr 26, 2013 at 10:59 AM, Jonas wrote: > > > >> Hi all, > >> > >> after having upgraded to wicket 6.7.0, we get a lot of warnings logged > from > >> RequestCycle.handleException(Exception). Can you please change the > level of > >> 'Handling the following exception' messages to debug, as those warnings > get > >> really annoying. Using level debug, an interested developer still has > the > >> option to see the messages if he's having trouble in that area (by > >> configuring logging accordingly), while you don't nag all other > developers. > >> IMHO log level warn should only be used if it's known something rather > bad > >> is happening, which isn't the case here - this is really just debugging > >> information. > >> > >> Thank you for considering this. > >> > >> Cheers, > >> Jonas > >> > > > > > > > > -- > > Martin Grigorov > > Wicket Training & Consulting > > http://jWeekend.com <http://jweekend.com/> >
Warnings from RequestCycle.handleException(Exception)
Hi all, after having upgraded to wicket 6.7.0, we get a lot of warnings logged from RequestCycle.handleException(Exception). Can you please change the level of 'Handling the following exception' messages to debug, as those warnings get really annoying. Using level debug, an interested developer still has the option to see the messages if he's having trouble in that area (by configuring logging accordingly), while you don't nag all other developers. IMHO log level warn should only be used if it's known something rather bad is happening, which isn't the case here - this is really just debugging information. Thank you for considering this. Cheers, Jonas
Patch for WICKET-2767
Hi, I just submitted a patch for issue 2767 [1], hoping the fix will maybe make it into wicket 1.4.8...? thanks. cheers, Jonas [1] https://issues.apache.org/jira/browse/WICKET-2767
Re: Future of Wicket Security (WASP/SWARM)
[X] keep Wicket security at Wicket Stuff > OT: Maybe at some point adopting some of the best projects from Wicket Stuff > (e.g. inMethod grid) might be good for the community as releases will be > synchronized with releases of Wicket "core". I thought synchronized releases are the idea of WicketStuff Core [1] [1] http://wicketstuff.org/confluence/display/STUFFWIKI/WicketStuff+Core+-+Migration+Guide
Re: wicket 1.5 build is failing because of 1.6 deps...
> I was going to propose a vote in that direction... as JDK 1.5 has been > shelved... While it's true 1.5 has gone eol last october, I don't think there's too much stuff in 1.6 Wicket would actually benefit from. Raising the minimum requirements without much benefit *could* scare off a lot of potential users. ...just to add my two cents on that topic :-)
Re: Request for input on new feature idea: wicket:for attribute
There's already a feature request in jira for this: https://issues.apache.org/jira/browse/WICKET-1469 I tried implementing it once, but I run into trouble with component hierarchy. Only allowing labels for sibling components would probably make the implementation a lot easier, but I'm not sure if this a too big limitation to only allow siblings. Consider the situation when the input field and the label are in different table cells, e.g. but you need to append some attributes to the td tags (e.g. for coloring). If I understood correctly what you suggested, this usecase wouldn't be covered. cheers, Jonas On Sun, Dec 13, 2009 at 2:06 PM, Erik van Oosten wrote: > Hi, > > In the many Wicket applications I have seen, the most frequent error is to > not correctly set the 'for' attribute of an HTML 'label' element. Currently > it is necessary to do this from code. Although a quickly written component > will make this fairly easy, the task is occurring that often that imho > better support by wicket is warranted. > > I therefore propose a new wicket:for attribute that looks as follows: > > Name > > > The rendered markup could for example be: > > Name > > > Some more thoughts on the design of the wicket:for attribute: > - The value of the attribute refers to a component by component id. The > referred component must be a sibling of the same container that provides the > markup with the label element. Referring to a component outside this > container is tricky as then component ids are no longer unique. > - The wicket:for attribute will render the 'for' attribute with the markup > id of the referenced component as value. > - The method setOuputMarkupId(true) will be called on the referenced > component. > > More ideas? > If I would implement such a wicket:for attribute, would it be accepted in > Wicket core? > > Regards, > Erik. > > > -- > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > >
Re: Why is Panel not abstract?
I raised the same question a while ago: http://old.nabble.com/Panel-instances-ts25922356.html#a25922356 seems to be fixed in 1.5, but left as-is in 1.4 in order not to create an api break cheers, Jonas On Wed, Dec 2, 2009 at 12:24 PM, Johan Compagner wrote: > I just got a question about: > > Markup of type 'html' for component > 'org.apache.wicket.markup.html.panel.Panel' not found > > because it used a panel (but he meant to use in this example a > WebMarkupContainer) > But i think he shouldnt be allowed to say new Panel() at all... > I would expect that it would be abstract just like Page or am i missing > something obvious here? > > johan >
Re: Patch submitted for Enum-ification of the runtime configuration types
I thought the plan for 1.5 was going into the opposite direction:
https://issues.apache.org/jira/browse/WICKET-1847
On Wed, Nov 11, 2009 at 3:34 PM, Olivier Croisier
wrote:
> Hi,
>
> I just submitted a patch that converts the runtime configuration types
> ("development", "deployment") into a type-safe Enum.
> See https://issues.apache.org/jira/browse/WICKET-1945
>
> Hope that helps,
> Olivier
>
Panel instances
Hi there, a quick question regarding org.apache.wicket.markup.html.panel.Panel: we recently had a bug in our software because someone directly created an instance of Panel to render 'nothing'. This of course failed miserably because the associated markup for Panel couldn't be found. While the fix was easy (use EmptyPanel, which has default markup, instead), I still wonder if there's any situation where it would be correct to directly instantiate Panel. If there isn't any such situation, I guess it would make sense to declare Panel to be an abstract class. ...or did I miss something here? thanks. cheers, Jonas
Re: 1.4.2 upgrade problem
sounds like a duplicate of https://issues.apache.org/jira/browse/WICKET-2506
On Mon, Oct 12, 2009 at 11:13 PM, Girts Ziemelis
wrote:
> I believe there is a bug in wicket 1.4.2, which stopped me from upgrading :(
> I have created issue for this:
>
> https://issues.apache.org/jira/browse/WICKET-2519
>
> Finally I narrowed it down to adding following to quick start, which works
> fine in 1.4.1 and fails in 1.4.2:
>
> 2 lines to HomePage.html
> />
> />
>
> 2 lines to HomePage.java
> add(new BookmarkablePageLink("logout", HomePage.class));
> add(new BookmarkablePageLink("login", HomePage.class));
> and HomePage.properties
> login=Login
> logout=Logout
>
> I get following stack trace
>
> WicketMessage: Could not find child with id: login in the wicket:enclosure
>
> Root cause:
>
> org.apache.wicket.WicketRuntimeException: Could not find child with id:
> login in the wicket:enclosure
> at
> org.apache.wicket.markup.html.internal.Enclosure.checkChildComponent(Enclosure.java:210)
> at
> org.apache.wicket.markup.html.internal.Enclosure.ensureAllChildrenPresent(Enclosure.java:249)
> at
> org.apache.wicket.markup.html.internal.Enclosure.onComponentTagBody(Enclosure.java:169)
> at org.apache.wicket.Component.renderComponent(Component.java:2626)
> at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
> at org.apache.wicket.Component.render(Component.java:2457)
> at org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:229)
> at
> org.apache.wicket.markup.resolver.EnclosureResolver.resolve(EnclosureResolver.java:61)
> at
> org.apache.wicket.markup.resolver.ComponentResolvers.resolve(ComponentResolvers.java:81)
> at
> org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1418)
> at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1528)
> at org.apache.wicket.Page.onRender(Page.java:1545)
> at org.apache.wicket.Component.render(Component.java:2457)
> at org.apache.wicket.Page.renderPage(Page.java:914)
> at
> org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:262)
> at
> org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)
> at
> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
> at
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:468)
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:301)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:295)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
> at
> org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
>
>
>
>
>
>
Improvement in SelectOptions / Javadoc for Select
Hi all, I've submitted a patch on JIRA that slightly improves SelectOptions by allowing customization of the created SelectOption objects. As an extra goodie, I also extended the javadoc of Select to include an example how to use Select/SelectOptions/SelectOption https://issues.apache.org/jira/browse/WICKET-1293 I was hoping one of the committers could take a look at it and (if it makes sense) include it into the next release? thanks a lot! Jonas
Re: Localizer warning in 1.3.0-beta3
Thanks for that quick fix, a follow-up question though: Localizer uses IStringResourceLoader.loadStringResource(Component component, String key). While most of the IStringResourceLoader implementations correctly handle a null component as parameter, BundleStringResourceLoader doesn't - it needs a component to determine the locale. Wouldn't it make sense to use the Session locale as fallback if we don't have a component there? cheers, Jonas On 8/30/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > Yeah, it's a bug and it's already fixed. Either update to current trunk or > just set the logging treashold for Localizer class to ERROR. > > -Matej > > On 8/30/07, Jonas <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > It (1.3.0-beta3) does complain in if the component isn't added to the > page > > yet, > > but it also complains if the component is null. If I understand this > right > > (and if the javadoc is correct), it shouldn't complain in the latter > case. > > > > cheers, > > Jonas > > > > I'm not sure if this was fixed in 1.3, but the localizer should only > > > complain when the component is not yet added to it's parent (because > the > > > whole hierarchy can't be traversed to find the message). > > > > > >
Re: Localizer warning in 1.3.0-beta3
Hi, It (1.3.0-beta3) does complain in if the component isn't added to the page yet, but it also complains if the component is null. If I understand this right (and if the javadoc is correct), it shouldn't complain in the latter case. cheers, Jonas I'm not sure if this was fixed in 1.3, but the localizer should only > complain when the component is not yet added to it's parent (because the > whole hierarchy can't be traversed to find the message). >
Localizer warning in 1.3.0-beta3
Hi, after having upgraded 1.3.0-beta3, I noticed that the Localizer now complains in the log if getString is called with 'null' as component, even though the javadoc for this method states that the component is optional. I'm not sure if the missing component has any further effects than deactivating the Localizer's cache (is that caching necessary anyway?) - could anyboy shed some light upon me? A related question would be how to use the Localizer when I'm in a context where I have no way of accessing the related component, e.g. for localized Strings in a DynamicImageResource. Shouldn't I use the Localizer in that case, or what's the idea? Thanks, Jonas
