Re: [VOTE] Release Apache Wicket 8.0.0-M7
+1 Tested: 1) signatures 2) compile from sources 3) compile wicketstuff, run several examples 4) Test our main application On Mon, Aug 7, 2017 at 7:15 PM, Maxim Solodovnik wrote: > Sure, thanks! > > On Mon, Aug 7, 2017 at 7:06 PM, Andrea Del Bene wrote: >> The personal GitHub repo is used to host the release code tag. If release >> vote passes, the tag is pushed to the official repo. >> >> I hope I've answered your question. >> >> >> On 07/08/2017 12:55, Maxim Solodovnik wrote: >>> >>> Hello Andrea, >>> >>> why your personal repo displayed here: >>> >>> Staging git repository data: >>> >>> Repository: *g...@github.com:bitstorm/wicket.git* >>> >>> >>> On Mon, Aug 7, 2017 at 5:50 PM, Andrea Del Bene >>> wrote: >>> This is a vote to release Apache Wicket 8.0.0-M7 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 8.0.0-M7 [ ] No, don't release Apache Wicket 8.0.0-M7, because ... Distributions, changelog, keys and signatures can be found at: https://dist.apache.org/repos/dist/dev/wicket/8.0.0-M7 Staging repository: https://repository.apache.org/content/repositories/orgapachewicket-1096 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:bitstorm/wicket.git Branch: build/wicket-8.0.0-M7 Release tag: rel/wicket-8.0.0-M7 The signatures for the source release artefacts: Signature for apache-wicket-8.0.0-M7.zip: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBVYUUP/0T9R8oiLZafZ6bkvKsxWHxp qhdinNhiG3sdsex+9cTNlzvazj0i1B4zmIqQ8+ekkVRPu/+rq/DH/SMTlTUrf9hk 91drZQ5wc8Ido3MdI+SeS0NSFvVvvH36gjXoTwLckCcwrjkUsk2k/f2S+1JYcFFx v+KTcbZJ6Y2M1iBJILlmO/GuyNSj/CXa3UOGkhNNMUU7MEMQDPb8ZvgQndUR3nWQ dxnyB3LE7u8k1bjK75t3RuBme6fz0ASippG5Ph0Ce/BDum/6RILf+Tioc8ZKFtS2 FCGoeFNgYb2Qx6x1Q0kZbfpxRW+SdV9ddYs0eLz2cNr4N2EYS7Y2xWcI0bUSv3gC PXOfAJcUcWNz6LP1vtPhFCzWOAtt9Lt2JAM699AHpvAyl+pPyS163qvUmyrDwaf3 QhBd9Vab9sCMav+OhImuVQL+iRFEyiMNm/kPlpZsz0RN8Zqqu73RT3vcNT/ZlGLm bo1AIwuJesCw/VL34PWzdglOpMVjQzFVlwd6pNzxwbohrq6gFRMLNZYTVQkELREe uII3KDxkY4dnyjCYCNi3Obp/FaphsJ6yvfwpesUrqzQjiX1C8QgMRcaQEpU+4DGo UxejnO5Th1ECsSjYCaCFKok38zilAiaKaQeVPFa66/sM93IqAXe0dXdelirLu59Q DO1Z0EwihlcEIqKmOLGV =EiFe -END PGP SIGNATURE- Signature for apache-wicket-8.0.0-M7.tar.gz: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBV0AoQALOjdIkE7o6t4ZgFO1B/jJvs KgUl4q82vksqiWoGzOob+hkmDSlyDodXaFbZUNiKat79H8Dg5bKU7IUa+d8msPZ6 iIy9DZk6Ty/QFtVNins7SeO9w8qGAN6LSImsskUE8FpfSMEjDmmzFMTy31A+AmWS +L3mddk4JY5CtKA2dPeZHtrlcIFL+hO99t7FueqkEEilrN8ulFmfF1Fz4kyqEBA5 XrWIgtVwUGLhd2iEgS28a/b3d0pZiweHb+MPWrItFDtZYwKzITefx8tfXir1qB2F SPkBdbmW5f67Z+kECUTBR7Bes15vFtv9kThVTDEJ3UhA8rMdS8XmgOablGTbMEfo ggU/raaeA7Ja4dAmxv38yLp4Ow5eoL3z5gsI9z5pUadVFItAtHs0GPMfJ14SnWY9 T0Lz2CK2LRb7RN1il1t4WpIKR8v3QzP+BZA8ZQ+wEI0jtSc9hnIEHJfxxdOvGE4v QSSrWs0/BNg1GrBQnIzsU/RW/Gdii5bSMBAguSkx+nXYwO7ooy25fTsnguPe6Fky cdnl70Cf27GIg5RiLX8ujlATRduaedK7ieA86ym/sPAOJX4slrjVjmwsSpjruvEn vaVvRUP5CcpQVPr0LQxI6jF/qq5V6/MTAdoTtrT/InvH8haZTVYdEenoSkEYezHW Knnl3Uyv25EmO9nlUYJC =PEGU -END PGP SIGNATURE- CHANGELOG for 8.0.0-M7: ** Bug * [WICKET-4324] - [wicket-ioc] LazyInitProxyFactory CGLIB proxies naming strategy may cause java.lang.IllegalAccessError * [WICKET-6366] - Autocomplete race condition makes page unresponsive * [WICKET-6373] - Edge not recognized in UserAgent * [WICKET-6374] - Exception caused by border extending another border with * [WICKET-6376] - Ajax redirects to non http(s)-urls are interpreted as relative * [WICKET-6377] - Autolinking breaks hierarchy for nested elements * [WICKET-6379] - IModel's default models should detach the target model * [WICKET-6386] - Simplification of the code in WICKET-3347 is not consistent with previous behavior * [WICKET-6387] - ModalWindow PageReference broken * [WICKET-6393] - NestedStringResourceLoader ignores hard-coded default values and throws MissingResourceExceptio
Re: [VOTE] Release Apache Wicket 8.0.0-M7
Sure, thanks! On Mon, Aug 7, 2017 at 7:06 PM, Andrea Del Bene wrote: > The personal GitHub repo is used to host the release code tag. If release > vote passes, the tag is pushed to the official repo. > > I hope I've answered your question. > > > On 07/08/2017 12:55, Maxim Solodovnik wrote: >> >> Hello Andrea, >> >> why your personal repo displayed here: >> >> Staging git repository data: >> >> Repository: *g...@github.com:bitstorm/wicket.git* >> >> >> On Mon, Aug 7, 2017 at 5:50 PM, Andrea Del Bene >> wrote: >> >>> This is a vote to release Apache Wicket 8.0.0-M7 >>> >>> 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 8.0.0-M7 >>> [ ] No, don't release Apache Wicket 8.0.0-M7, because ... >>> >>> Distributions, changelog, keys and signatures can be found at: >>> >>> https://dist.apache.org/repos/dist/dev/wicket/8.0.0-M7 >>> >>> Staging repository: >>> >>> https://repository.apache.org/content/repositories/orgapachewicket-1096 >>> >>> 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:bitstorm/wicket.git >>> Branch: build/wicket-8.0.0-M7 >>> Release tag: rel/wicket-8.0.0-M7 >>> >>> >>> >>> >>> The signatures for the source release artefacts: >>> >>> >>> Signature for apache-wicket-8.0.0-M7.zip: >>> >>> -BEGIN PGP SIGNATURE- >>> Version: GnuPG v1 >>> >>> iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBVYUUP/0T9R8oiLZafZ6bkvKsxWHxp >>> qhdinNhiG3sdsex+9cTNlzvazj0i1B4zmIqQ8+ekkVRPu/+rq/DH/SMTlTUrf9hk >>> 91drZQ5wc8Ido3MdI+SeS0NSFvVvvH36gjXoTwLckCcwrjkUsk2k/f2S+1JYcFFx >>> v+KTcbZJ6Y2M1iBJILlmO/GuyNSj/CXa3UOGkhNNMUU7MEMQDPb8ZvgQndUR3nWQ >>> dxnyB3LE7u8k1bjK75t3RuBme6fz0ASippG5Ph0Ce/BDum/6RILf+Tioc8ZKFtS2 >>> FCGoeFNgYb2Qx6x1Q0kZbfpxRW+SdV9ddYs0eLz2cNr4N2EYS7Y2xWcI0bUSv3gC >>> PXOfAJcUcWNz6LP1vtPhFCzWOAtt9Lt2JAM699AHpvAyl+pPyS163qvUmyrDwaf3 >>> QhBd9Vab9sCMav+OhImuVQL+iRFEyiMNm/kPlpZsz0RN8Zqqu73RT3vcNT/ZlGLm >>> bo1AIwuJesCw/VL34PWzdglOpMVjQzFVlwd6pNzxwbohrq6gFRMLNZYTVQkELREe >>> uII3KDxkY4dnyjCYCNi3Obp/FaphsJ6yvfwpesUrqzQjiX1C8QgMRcaQEpU+4DGo >>> UxejnO5Th1ECsSjYCaCFKok38zilAiaKaQeVPFa66/sM93IqAXe0dXdelirLu59Q >>> DO1Z0EwihlcEIqKmOLGV >>> =EiFe >>> -END PGP SIGNATURE- >>> >>> Signature for apache-wicket-8.0.0-M7.tar.gz: >>> >>> -BEGIN PGP SIGNATURE- >>> Version: GnuPG v1 >>> >>> iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBV0AoQALOjdIkE7o6t4ZgFO1B/jJvs >>> KgUl4q82vksqiWoGzOob+hkmDSlyDodXaFbZUNiKat79H8Dg5bKU7IUa+d8msPZ6 >>> iIy9DZk6Ty/QFtVNins7SeO9w8qGAN6LSImsskUE8FpfSMEjDmmzFMTy31A+AmWS >>> +L3mddk4JY5CtKA2dPeZHtrlcIFL+hO99t7FueqkEEilrN8ulFmfF1Fz4kyqEBA5 >>> XrWIgtVwUGLhd2iEgS28a/b3d0pZiweHb+MPWrItFDtZYwKzITefx8tfXir1qB2F >>> SPkBdbmW5f67Z+kECUTBR7Bes15vFtv9kThVTDEJ3UhA8rMdS8XmgOablGTbMEfo >>> ggU/raaeA7Ja4dAmxv38yLp4Ow5eoL3z5gsI9z5pUadVFItAtHs0GPMfJ14SnWY9 >>> T0Lz2CK2LRb7RN1il1t4WpIKR8v3QzP+BZA8ZQ+wEI0jtSc9hnIEHJfxxdOvGE4v >>> QSSrWs0/BNg1GrBQnIzsU/RW/Gdii5bSMBAguSkx+nXYwO7ooy25fTsnguPe6Fky >>> cdnl70Cf27GIg5RiLX8ujlATRduaedK7ieA86ym/sPAOJX4slrjVjmwsSpjruvEn >>> vaVvRUP5CcpQVPr0LQxI6jF/qq5V6/MTAdoTtrT/InvH8haZTVYdEenoSkEYezHW >>> Knnl3Uyv25EmO9nlUYJC >>> =PEGU >>> -END PGP SIGNATURE- >>> >>> >>> >>> CHANGELOG for 8.0.0-M7: >>> >>> ** Bug >>> >>> * [WICKET-4324] - [wicket-ioc] LazyInitProxyFactory CGLIB proxies >>> naming strategy may cause java.lang.IllegalAccessError >>> * [WICKET-6366] - Autocomplete race condition makes page >>> unresponsive >>> * [WICKET-6373] - Edge not recognized in UserAgent >>> * [WICKET-6374] - Exception caused by border extending another >>> border >>> with >>> * [WICKET-6376] - Ajax redirects to non http(s)-urls are interpreted >>> as relative >>> * [WICKET-6377] - Autolinking breaks hierarchy for nested elements >>> * [WICKET-6379] - IModel's default models should detach the target >>> model >>> * [WICKET-6386] - Simplification of the code in WICKET-3347 is not >>> consistent with previous behavior >>> * [WICKET-6387] - ModalWindow PageReference broken >>> * [WICKET-6393] - NestedStringResourceLoader ignores hard-coded >>> default values and throws MissingResourceException >>> * [WICKET-6398] - WICKET-6204 breaks jQuery.noConflict() >>> * [WICKET-6399] - Dequeuing of Border component with nested body >>> fails >>> * [WICKET-6400] - Object with array property fails on NPE when >>> construction JSON object >>> * [WICKET-6402] - OSGi-Manifest: wicket does
Re: [VOTE] Release Apache Wicket 8.0.0-M7
The personal GitHub repo is used to host the release code tag. If release vote passes, the tag is pushed to the official repo. I hope I've answered your question. On 07/08/2017 12:55, Maxim Solodovnik wrote: Hello Andrea, why your personal repo displayed here: Staging git repository data: Repository: *g...@github.com:bitstorm/wicket.git* On Mon, Aug 7, 2017 at 5:50 PM, Andrea Del Bene wrote: This is a vote to release Apache Wicket 8.0.0-M7 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 8.0.0-M7 [ ] No, don't release Apache Wicket 8.0.0-M7, because ... Distributions, changelog, keys and signatures can be found at: https://dist.apache.org/repos/dist/dev/wicket/8.0.0-M7 Staging repository: https://repository.apache.org/content/repositories/orgapachewicket-1096 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:bitstorm/wicket.git Branch: build/wicket-8.0.0-M7 Release tag: rel/wicket-8.0.0-M7 The signatures for the source release artefacts: Signature for apache-wicket-8.0.0-M7.zip: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBVYUUP/0T9R8oiLZafZ6bkvKsxWHxp qhdinNhiG3sdsex+9cTNlzvazj0i1B4zmIqQ8+ekkVRPu/+rq/DH/SMTlTUrf9hk 91drZQ5wc8Ido3MdI+SeS0NSFvVvvH36gjXoTwLckCcwrjkUsk2k/f2S+1JYcFFx v+KTcbZJ6Y2M1iBJILlmO/GuyNSj/CXa3UOGkhNNMUU7MEMQDPb8ZvgQndUR3nWQ dxnyB3LE7u8k1bjK75t3RuBme6fz0ASippG5Ph0Ce/BDum/6RILf+Tioc8ZKFtS2 FCGoeFNgYb2Qx6x1Q0kZbfpxRW+SdV9ddYs0eLz2cNr4N2EYS7Y2xWcI0bUSv3gC PXOfAJcUcWNz6LP1vtPhFCzWOAtt9Lt2JAM699AHpvAyl+pPyS163qvUmyrDwaf3 QhBd9Vab9sCMav+OhImuVQL+iRFEyiMNm/kPlpZsz0RN8Zqqu73RT3vcNT/ZlGLm bo1AIwuJesCw/VL34PWzdglOpMVjQzFVlwd6pNzxwbohrq6gFRMLNZYTVQkELREe uII3KDxkY4dnyjCYCNi3Obp/FaphsJ6yvfwpesUrqzQjiX1C8QgMRcaQEpU+4DGo UxejnO5Th1ECsSjYCaCFKok38zilAiaKaQeVPFa66/sM93IqAXe0dXdelirLu59Q DO1Z0EwihlcEIqKmOLGV =EiFe -END PGP SIGNATURE- Signature for apache-wicket-8.0.0-M7.tar.gz: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBV0AoQALOjdIkE7o6t4ZgFO1B/jJvs KgUl4q82vksqiWoGzOob+hkmDSlyDodXaFbZUNiKat79H8Dg5bKU7IUa+d8msPZ6 iIy9DZk6Ty/QFtVNins7SeO9w8qGAN6LSImsskUE8FpfSMEjDmmzFMTy31A+AmWS +L3mddk4JY5CtKA2dPeZHtrlcIFL+hO99t7FueqkEEilrN8ulFmfF1Fz4kyqEBA5 XrWIgtVwUGLhd2iEgS28a/b3d0pZiweHb+MPWrItFDtZYwKzITefx8tfXir1qB2F SPkBdbmW5f67Z+kECUTBR7Bes15vFtv9kThVTDEJ3UhA8rMdS8XmgOablGTbMEfo ggU/raaeA7Ja4dAmxv38yLp4Ow5eoL3z5gsI9z5pUadVFItAtHs0GPMfJ14SnWY9 T0Lz2CK2LRb7RN1il1t4WpIKR8v3QzP+BZA8ZQ+wEI0jtSc9hnIEHJfxxdOvGE4v QSSrWs0/BNg1GrBQnIzsU/RW/Gdii5bSMBAguSkx+nXYwO7ooy25fTsnguPe6Fky cdnl70Cf27GIg5RiLX8ujlATRduaedK7ieA86ym/sPAOJX4slrjVjmwsSpjruvEn vaVvRUP5CcpQVPr0LQxI6jF/qq5V6/MTAdoTtrT/InvH8haZTVYdEenoSkEYezHW Knnl3Uyv25EmO9nlUYJC =PEGU -END PGP SIGNATURE- CHANGELOG for 8.0.0-M7: ** Bug * [WICKET-4324] - [wicket-ioc] LazyInitProxyFactory CGLIB proxies naming strategy may cause java.lang.IllegalAccessError * [WICKET-6366] - Autocomplete race condition makes page unresponsive * [WICKET-6373] - Edge not recognized in UserAgent * [WICKET-6374] - Exception caused by border extending another border with * [WICKET-6376] - Ajax redirects to non http(s)-urls are interpreted as relative * [WICKET-6377] - Autolinking breaks hierarchy for nested elements * [WICKET-6379] - IModel's default models should detach the target model * [WICKET-6386] - Simplification of the code in WICKET-3347 is not consistent with previous behavior * [WICKET-6387] - ModalWindow PageReference broken * [WICKET-6393] - NestedStringResourceLoader ignores hard-coded default values and throws MissingResourceException * [WICKET-6398] - WICKET-6204 breaks jQuery.noConflict() * [WICKET-6399] - Dequeuing of Border component with nested body fails * [WICKET-6400] - Object with array property fails on NPE when construction JSON object * [WICKET-6402] - OSGi-Manifest: wicket does not declare BSN * [WICKET-6406] - Each path has to be pushed directly * [WICKET-6419] - Localization of PageParameters * [WICKET-6428] - PageProvider#getPageInstance() may return null * [WICKET-6429] - AbstractRequestLogger should not create new Sessions * [WICKET-6434] - Fixed WicketTester to detect components in enclosure when doing isComponentOnAjaxResponse. ** Improvement * [WICKET-6372] - Consider to switch to a sans-serif typeface in the Wicket guide * [WICKET-638
Re: Google Chart integration as candidate for wicketstuff
Maybe it would be possible to update current version? I'm afraid having 2 different Google Chart modules would be too much :) BTW there are also https://github.com/wicketstuff/core/tree/master/jqplot-parent for chart drawing :) On Mon, Aug 7, 2017 at 2:36 PM, Dieter Tremel wrote: > Hello wicket-team, > > for a project visualizing metar weather data I used wicket-charts based > on Highcharts in a former version > (http://tremel-computer.no-ip.org:8080/metarstation/). Due to licensing > of Highcharts I decided to move to Google charts, but found the > implementation in wicketstuf outdated, since it depends on the image > chart API, which is deprecated since 2012. > > So I wrote a Google Charts component based on the actual API. I am > pleased with it, perhaps it could be helpful for other developers, so > I'd like to give it to wicketstuff. > > It is rather lightweight, just enough Java to render the necessary > JavaScript to the page header without knowledge of JavaScript. Knowledge > of the Google API is needed to use it, it does not hide anything of the > API, it should be quite feature complete. It is based at many points on > org.apache.wicket.ajax.json and allows the user to build Java-Objects > from compact JSON-Strings too, for example look at the essential class > ChartOptions. Most of the classes are easy to understand with knowledge > of the Google Charts API, since they are counterparts of the structure > there. Only OptionHelper as container for convenience methods is a bit > clumsy, but I have a different solution as a builder with a fluent > interface in mind. gchart is actually used in a new branch of my weather > app and does it's job there well. > > Perhaps you can have a look at it, if you like it, we can integrate it > in wicketstuff. The ZIP in the attachment has already the structure with > parent, lib and examples. I tried to write useful JavaDoc and some basic > unit tests. The example is a quickstart giving two charts on one page, > first one simple like Googles's Getting Started, the other more complex > with a overview how to use the lib's features. > > Three issues (see TODO lines integrated in the source) are existing, but > two are small, not blocking. The essential one is if the rendering of > JavaScript in Chart#renderHead(final IHeaderResponse response) is > sufficient for refreshing the chart by AJAX, I am not sure if. You can > decide this in a second, I believe, and give me some hints to make the > chart AJAX ready. > > I first wrote to Martin Grigorov since he helped me long ago to > contribute a bit to wicketstuff. He told me he is on vacation and I > should repeat the mail to the list. > > Dieter Tremel > > -- > Tremel Computerhttp://www.tremel-computer.de > Dieter Tremel mailto:tre...@tremel-computer.de > Rebenring 16 Tel +49 871 9357080 > 84032 Altdorf Fax +49 871 9357081 > > -- WBR Maxim aka solomax
Re: [VOTE] Release Apache Wicket 8.0.0-M7
Hello Andrea, why your personal repo displayed here: Staging git repository data: Repository: *g...@github.com:bitstorm/wicket.git* On Mon, Aug 7, 2017 at 5:50 PM, Andrea Del Bene wrote: > This is a vote to release Apache Wicket 8.0.0-M7 > > 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 8.0.0-M7 > [ ] No, don't release Apache Wicket 8.0.0-M7, because ... > > Distributions, changelog, keys and signatures can be found at: > > https://dist.apache.org/repos/dist/dev/wicket/8.0.0-M7 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachewicket-1096 > > 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:bitstorm/wicket.git > Branch: build/wicket-8.0.0-M7 > Release tag: rel/wicket-8.0.0-M7 > > > > > The signatures for the source release artefacts: > > > Signature for apache-wicket-8.0.0-M7.zip: > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBVYUUP/0T9R8oiLZafZ6bkvKsxWHxp > qhdinNhiG3sdsex+9cTNlzvazj0i1B4zmIqQ8+ekkVRPu/+rq/DH/SMTlTUrf9hk > 91drZQ5wc8Ido3MdI+SeS0NSFvVvvH36gjXoTwLckCcwrjkUsk2k/f2S+1JYcFFx > v+KTcbZJ6Y2M1iBJILlmO/GuyNSj/CXa3UOGkhNNMUU7MEMQDPb8ZvgQndUR3nWQ > dxnyB3LE7u8k1bjK75t3RuBme6fz0ASippG5Ph0Ce/BDum/6RILf+Tioc8ZKFtS2 > FCGoeFNgYb2Qx6x1Q0kZbfpxRW+SdV9ddYs0eLz2cNr4N2EYS7Y2xWcI0bUSv3gC > PXOfAJcUcWNz6LP1vtPhFCzWOAtt9Lt2JAM699AHpvAyl+pPyS163qvUmyrDwaf3 > QhBd9Vab9sCMav+OhImuVQL+iRFEyiMNm/kPlpZsz0RN8Zqqu73RT3vcNT/ZlGLm > bo1AIwuJesCw/VL34PWzdglOpMVjQzFVlwd6pNzxwbohrq6gFRMLNZYTVQkELREe > uII3KDxkY4dnyjCYCNi3Obp/FaphsJ6yvfwpesUrqzQjiX1C8QgMRcaQEpU+4DGo > UxejnO5Th1ECsSjYCaCFKok38zilAiaKaQeVPFa66/sM93IqAXe0dXdelirLu59Q > DO1Z0EwihlcEIqKmOLGV > =EiFe > -END PGP SIGNATURE- > > Signature for apache-wicket-8.0.0-M7.tar.gz: > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBV0AoQALOjdIkE7o6t4ZgFO1B/jJvs > KgUl4q82vksqiWoGzOob+hkmDSlyDodXaFbZUNiKat79H8Dg5bKU7IUa+d8msPZ6 > iIy9DZk6Ty/QFtVNins7SeO9w8qGAN6LSImsskUE8FpfSMEjDmmzFMTy31A+AmWS > +L3mddk4JY5CtKA2dPeZHtrlcIFL+hO99t7FueqkEEilrN8ulFmfF1Fz4kyqEBA5 > XrWIgtVwUGLhd2iEgS28a/b3d0pZiweHb+MPWrItFDtZYwKzITefx8tfXir1qB2F > SPkBdbmW5f67Z+kECUTBR7Bes15vFtv9kThVTDEJ3UhA8rMdS8XmgOablGTbMEfo > ggU/raaeA7Ja4dAmxv38yLp4Ow5eoL3z5gsI9z5pUadVFItAtHs0GPMfJ14SnWY9 > T0Lz2CK2LRb7RN1il1t4WpIKR8v3QzP+BZA8ZQ+wEI0jtSc9hnIEHJfxxdOvGE4v > QSSrWs0/BNg1GrBQnIzsU/RW/Gdii5bSMBAguSkx+nXYwO7ooy25fTsnguPe6Fky > cdnl70Cf27GIg5RiLX8ujlATRduaedK7ieA86ym/sPAOJX4slrjVjmwsSpjruvEn > vaVvRUP5CcpQVPr0LQxI6jF/qq5V6/MTAdoTtrT/InvH8haZTVYdEenoSkEYezHW > Knnl3Uyv25EmO9nlUYJC > =PEGU > -END PGP SIGNATURE- > > > > CHANGELOG for 8.0.0-M7: > > ** Bug > > * [WICKET-4324] - [wicket-ioc] LazyInitProxyFactory CGLIB proxies > naming strategy may cause java.lang.IllegalAccessError > * [WICKET-6366] - Autocomplete race condition makes page unresponsive > * [WICKET-6373] - Edge not recognized in UserAgent > * [WICKET-6374] - Exception caused by border extending another border > with > * [WICKET-6376] - Ajax redirects to non http(s)-urls are interpreted > as relative > * [WICKET-6377] - Autolinking breaks hierarchy for nested elements > * [WICKET-6379] - IModel's default models should detach the target > model > * [WICKET-6386] - Simplification of the code in WICKET-3347 is not > consistent with previous behavior > * [WICKET-6387] - ModalWindow PageReference broken > * [WICKET-6393] - NestedStringResourceLoader ignores hard-coded > default values and throws MissingResourceException > * [WICKET-6398] - WICKET-6204 breaks jQuery.noConflict() > * [WICKET-6399] - Dequeuing of Border component with nested body fails > * [WICKET-6400] - Object with array property fails on NPE when > construction JSON object > * [WICKET-6402] - OSGi-Manifest: wicket does not declare BSN > * [WICKET-6406] - Each path has to be pushed directly > * [WICKET-6419] - Localization of PageParameters > * [WICKET-6428] - PageProvider#getPageInstance() may return null > * [WICKET-6429] - AbstractRequestLogger should not create new Sessions > * [WICKET-6434] - Fixed WicketTester to detect components in enclosure > when doing isComponentOnAjaxResponse. > > ** Improvement > > * [WICKET-6372] - Consider to switch to a sans-serif typeface in the > Wicket guide > * [WICKET-6385] - Allow using custom port for web sock
[VOTE] Release Apache Wicket 8.0.0-M7
This is a vote to release Apache Wicket 8.0.0-M7 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 8.0.0-M7 [ ] No, don't release Apache Wicket 8.0.0-M7, because ... Distributions, changelog, keys and signatures can be found at: https://dist.apache.org/repos/dist/dev/wicket/8.0.0-M7 Staging repository: https://repository.apache.org/content/repositories/orgapachewicket-1096 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:bitstorm/wicket.git Branch: build/wicket-8.0.0-M7 Release tag: rel/wicket-8.0.0-M7 The signatures for the source release artefacts: Signature for apache-wicket-8.0.0-M7.zip: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBVYUUP/0T9R8oiLZafZ6bkvKsxWHxp qhdinNhiG3sdsex+9cTNlzvazj0i1B4zmIqQ8+ekkVRPu/+rq/DH/SMTlTUrf9hk 91drZQ5wc8Ido3MdI+SeS0NSFvVvvH36gjXoTwLckCcwrjkUsk2k/f2S+1JYcFFx v+KTcbZJ6Y2M1iBJILlmO/GuyNSj/CXa3UOGkhNNMUU7MEMQDPb8ZvgQndUR3nWQ dxnyB3LE7u8k1bjK75t3RuBme6fz0ASippG5Ph0Ce/BDum/6RILf+Tioc8ZKFtS2 FCGoeFNgYb2Qx6x1Q0kZbfpxRW+SdV9ddYs0eLz2cNr4N2EYS7Y2xWcI0bUSv3gC PXOfAJcUcWNz6LP1vtPhFCzWOAtt9Lt2JAM699AHpvAyl+pPyS163qvUmyrDwaf3 QhBd9Vab9sCMav+OhImuVQL+iRFEyiMNm/kPlpZsz0RN8Zqqu73RT3vcNT/ZlGLm bo1AIwuJesCw/VL34PWzdglOpMVjQzFVlwd6pNzxwbohrq6gFRMLNZYTVQkELREe uII3KDxkY4dnyjCYCNi3Obp/FaphsJ6yvfwpesUrqzQjiX1C8QgMRcaQEpU+4DGo UxejnO5Th1ECsSjYCaCFKok38zilAiaKaQeVPFa66/sM93IqAXe0dXdelirLu59Q DO1Z0EwihlcEIqKmOLGV =EiFe -END PGP SIGNATURE- Signature for apache-wicket-8.0.0-M7.tar.gz: -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAABAgAGBQJZiENjAAoJEAzCjx+CMhBV0AoQALOjdIkE7o6t4ZgFO1B/jJvs KgUl4q82vksqiWoGzOob+hkmDSlyDodXaFbZUNiKat79H8Dg5bKU7IUa+d8msPZ6 iIy9DZk6Ty/QFtVNins7SeO9w8qGAN6LSImsskUE8FpfSMEjDmmzFMTy31A+AmWS +L3mddk4JY5CtKA2dPeZHtrlcIFL+hO99t7FueqkEEilrN8ulFmfF1Fz4kyqEBA5 XrWIgtVwUGLhd2iEgS28a/b3d0pZiweHb+MPWrItFDtZYwKzITefx8tfXir1qB2F SPkBdbmW5f67Z+kECUTBR7Bes15vFtv9kThVTDEJ3UhA8rMdS8XmgOablGTbMEfo ggU/raaeA7Ja4dAmxv38yLp4Ow5eoL3z5gsI9z5pUadVFItAtHs0GPMfJ14SnWY9 T0Lz2CK2LRb7RN1il1t4WpIKR8v3QzP+BZA8ZQ+wEI0jtSc9hnIEHJfxxdOvGE4v QSSrWs0/BNg1GrBQnIzsU/RW/Gdii5bSMBAguSkx+nXYwO7ooy25fTsnguPe6Fky cdnl70Cf27GIg5RiLX8ujlATRduaedK7ieA86ym/sPAOJX4slrjVjmwsSpjruvEn vaVvRUP5CcpQVPr0LQxI6jF/qq5V6/MTAdoTtrT/InvH8haZTVYdEenoSkEYezHW Knnl3Uyv25EmO9nlUYJC =PEGU -END PGP SIGNATURE- CHANGELOG for 8.0.0-M7: ** Bug * [WICKET-4324] - [wicket-ioc] LazyInitProxyFactory CGLIB proxies naming strategy may cause java.lang.IllegalAccessError * [WICKET-6366] - Autocomplete race condition makes page unresponsive * [WICKET-6373] - Edge not recognized in UserAgent * [WICKET-6374] - Exception caused by border extending another border with * [WICKET-6376] - Ajax redirects to non http(s)-urls are interpreted as relative * [WICKET-6377] - Autolinking breaks hierarchy for nested elements * [WICKET-6379] - IModel's default models should detach the target model * [WICKET-6386] - Simplification of the code in WICKET-3347 is not consistent with previous behavior * [WICKET-6387] - ModalWindow PageReference broken * [WICKET-6393] - NestedStringResourceLoader ignores hard-coded default values and throws MissingResourceException * [WICKET-6398] - WICKET-6204 breaks jQuery.noConflict() * [WICKET-6399] - Dequeuing of Border component with nested body fails * [WICKET-6400] - Object with array property fails on NPE when construction JSON object * [WICKET-6402] - OSGi-Manifest: wicket does not declare BSN * [WICKET-6406] - Each path has to be pushed directly * [WICKET-6419] - Localization of PageParameters * [WICKET-6428] - PageProvider#getPageInstance() may return null * [WICKET-6429] - AbstractRequestLogger should not create new Sessions * [WICKET-6434] - Fixed WicketTester to detect components in enclosure when doing isComponentOnAjaxResponse. ** Improvement * [WICKET-6372] - Consider to switch to a sans-serif typeface in the Wicket guide * [WICKET-6385] - Allow using custom port for web socket connections * [WICKET-6388] - MockServletContext should define non-null session tracking modes * [WICKET-6389] - Introduce CsrfPreventionRequestCycleListener that is aware of Web Socket requests * [WICKET-6401] - OSGi-Manifest: wicket-util should decalre its dependency to 'commons-io' and 'commons-fileupload' * [WICKET-6412] - Model#orElse behavior is inconsis
Re: Wicket 8 (M7) release
I have restarted our demo app 3 days ago :( (the version was updated) Will check at the end of the week I have 2 versions of same system: A based on M6 B based on SNAPSHOT B was started just now A is running for 3 days memory consumption almost the same ... On Mon, Aug 7, 2017 at 4:55 PM, Sebastien wrote: > Hi KB, > > Thanks for your inputs! > > The demo app is wicket-jquery-ui-samples: > https://github.com/sebfz1/wicket-jquery-ui > > online here: > http://www.7thweb.net/wicket-jquery-ui/ > > If you want to give a try at profiling, you are very welcome! :) > > In the meantime, I launch the HPROF on the server and I will let it collect > data for some hours. Will see what comes out... > By monitoring the traffic, I also saw queries to the InspectorPage (yes, > I've got the inspector page in "production"! But that's a demo app, that's > why...). > I know the inspector page can be memory consuming, so maybe it's an hit... > > Best regards, > Sebastien > > On Mon, Aug 7, 2017 at 11:42 AM, Korbinian Bachl < > korbinian.ba...@whiskyworld.de> wrote: > >> Hello Sebastien, >> >> that sounds bad - how big is the heap space you gave to your server? >> >> I'm running our app now on a testserver for 10 days and the memory usage >> seems normal - even though I also did some jMeter on it during the last >> week, spawning many many threads and requests; >> >> Heap from 8-Snapshot here reads as follows at the current time: >> >> Heap Memory Usage: >> Memory that Java Virtual Machine initially requested to the Operating >> System: 2.147.483.648 Bytes >> Memory that Java Virtual Machine is guaranteed to receive from the >> Operating System: 2.144.337.920 Bytes >> Maximum Memory that Java Virtual Machine may get from the Operating >> System: 2.144.337.920 Bytes. Note that this is not guaranteed. >> Memory that Java Virtual Machine uses at this time: 1.018.066.976 Bytes >> >> While our production one after nealry 10 weeks uptime reads this: >> >> Heap Memory Usage: >> Memory that Java Virtual Machine initially requested to the Operating >> System: 4.294.967.296 Bytes >> Memory that Java Virtual Machine is guaranteed to receive from the >> Operating System: 4.151.836.672 Bytes >> Maximum Memory that Java Virtual Machine may get from the Operating >> System: 4.151.836.672 Bytes. Note that this is not guaranteed. >> Memory that Java Virtual Machine uses at this time: 1.014.171.432 Bytes >> >> >> >> So far nothing big difference - both are far away from maximumg level; >> >> What kind of demo app is this? >> >> Best, >> >> KB >> -- WBR Maxim aka solomax
Re: Wicket 8 (M7) release
Hi KB, Thanks for your inputs! The demo app is wicket-jquery-ui-samples: https://github.com/sebfz1/wicket-jquery-ui online here: http://www.7thweb.net/wicket-jquery-ui/ If you want to give a try at profiling, you are very welcome! :) In the meantime, I launch the HPROF on the server and I will let it collect data for some hours. Will see what comes out... By monitoring the traffic, I also saw queries to the InspectorPage (yes, I've got the inspector page in "production"! But that's a demo app, that's why...). I know the inspector page can be memory consuming, so maybe it's an hit... Best regards, Sebastien On Mon, Aug 7, 2017 at 11:42 AM, Korbinian Bachl < korbinian.ba...@whiskyworld.de> wrote: > Hello Sebastien, > > that sounds bad - how big is the heap space you gave to your server? > > I'm running our app now on a testserver for 10 days and the memory usage > seems normal - even though I also did some jMeter on it during the last > week, spawning many many threads and requests; > > Heap from 8-Snapshot here reads as follows at the current time: > > Heap Memory Usage: > Memory that Java Virtual Machine initially requested to the Operating > System: 2.147.483.648 Bytes > Memory that Java Virtual Machine is guaranteed to receive from the > Operating System: 2.144.337.920 Bytes > Maximum Memory that Java Virtual Machine may get from the Operating > System: 2.144.337.920 Bytes. Note that this is not guaranteed. > Memory that Java Virtual Machine uses at this time: 1.018.066.976 Bytes > > While our production one after nealry 10 weeks uptime reads this: > > Heap Memory Usage: > Memory that Java Virtual Machine initially requested to the Operating > System: 4.294.967.296 Bytes > Memory that Java Virtual Machine is guaranteed to receive from the > Operating System: 4.151.836.672 Bytes > Maximum Memory that Java Virtual Machine may get from the Operating > System: 4.151.836.672 Bytes. Note that this is not guaranteed. > Memory that Java Virtual Machine uses at this time: 1.014.171.432 Bytes > > > > So far nothing big difference - both are far away from maximumg level; > > What kind of demo app is this? > > Best, > > KB >
Re: Wicket 8 (M7) release
Hello Sebastien, that sounds bad - how big is the heap space you gave to your server? I'm running our app now on a testserver for 10 days and the memory usage seems normal - even though I also did some jMeter on it during the last week, spawning many many threads and requests; Heap from 8-Snapshot here reads as follows at the current time: Heap Memory Usage: Memory that Java Virtual Machine initially requested to the Operating System: 2.147.483.648 Bytes Memory that Java Virtual Machine is guaranteed to receive from the Operating System: 2.144.337.920 Bytes Maximum Memory that Java Virtual Machine may get from the Operating System: 2.144.337.920 Bytes. Note that this is not guaranteed. Memory that Java Virtual Machine uses at this time: 1.018.066.976 Bytes While our production one after nealry 10 weeks uptime reads this: Heap Memory Usage: Memory that Java Virtual Machine initially requested to the Operating System: 4.294.967.296 Bytes Memory that Java Virtual Machine is guaranteed to receive from the Operating System: 4.151.836.672 Bytes Maximum Memory that Java Virtual Machine may get from the Operating System: 4.151.836.672 Bytes. Note that this is not guaranteed. Memory that Java Virtual Machine uses at this time: 1.014.171.432 Bytes So far nothing big difference - both are far away from maximumg level; What kind of demo app is this? Best, KB - Ursprüngliche Mail - > Von: "Sebastien" > An: dev@wicket.apache.org > Gesendet: Montag, 7. August 2017 10:12:51 > Betreff: Re: Wicket 8 (M7) release > Hi, > > Just to let you know: I deployed the wicket8.x of my demo app and it ran > for 5 days before failing down (out of memory) > > SEVERE [ajp-nio-8009-exec-2] > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun > java.lang.OutOfMemoryError: Java heap space >at java.util.Arrays.copyOf(Arrays.java:3332) >at > java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124) >at > java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448) >at java.lang.StringBuilder.append(StringBuilder.java:136) >at org.apache.wicket.Page.checkRendering(Page.java:662) >at org.apache.wicket.Page.onAfterRender(Page.java:805) >at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:209) >at org.apache.wicket.Component.afterRender(Component.java:919) >at org.apache.wicket.Component.render(Component.java:2335) >at org.apache.wicket.Page.renderPage(Page.java:987) >at > org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124) >at > org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236) >at > org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:202) >at > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912) >at > org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65) >at > org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283) >at > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253) >at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) >at > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262) >at > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) >at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) >at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) >at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) >at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) >at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) >at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) >at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) >at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) >at > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) >at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) >at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522) >at > org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868) > > There is nothing else in there. I should really run a profiler... > > Best regards, > Sebastien. > > On Sun, Aug 6, 2017 at 7:34 PM, Maxim Solodovnik > wrote: > >> As far as I can see nothing blocks the release >> +1 :) >> >> On Mon, Aug 7, 2017 at 12:25 AM, Andrea Del Bene >> wrote: >> > I guess now we are ready to start the release of M7, right? >> > >> > >>
Re: Wicket 8 (M7) release
Hi, Just to let you know: I deployed the wicket8.x of my demo app and it ran for 5 days before failing down (out of memory) SEVERE [ajp-nio-8009-exec-2] org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3332) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448) at java.lang.StringBuilder.append(StringBuilder.java:136) at org.apache.wicket.Page.checkRendering(Page.java:662) at org.apache.wicket.Page.onAfterRender(Page.java:805) at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:209) at org.apache.wicket.Component.afterRender(Component.java:919) at org.apache.wicket.Component.render(Component.java:2335) at org.apache.wicket.Page.renderPage(Page.java:987) at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124) at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236) at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:202) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912) at org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522) at org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868) There is nothing else in there. I should really run a profiler... Best regards, Sebastien. On Sun, Aug 6, 2017 at 7:34 PM, Maxim Solodovnik wrote: > As far as I can see nothing blocks the release > +1 :) > > On Mon, Aug 7, 2017 at 12:25 AM, Andrea Del Bene > wrote: > > I guess now we are ready to start the release of M7, right? > > > > > > On 05/08/2017 17:12, Maxim Solodovnik wrote: > >> > >> https://github.com/apache/wicket/pull/228 > >> > >> On Sat, Aug 5, 2017 at 12:04 PM, Maxim Solodovnik > > >> wrote: > >>> > >>> OK, thanks > >>> will prepare PR > >>> > >>> On Sat, Aug 5, 2017 at 11:59 AM, Martin Grigorov > >>> wrote: > > Hi Maxim, > > On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" > wrote: > > Hello All, > > I would like to update version on libraries being used by wicket to > the > most recent versions is it OK? > > > Sure! > > > report can be get as follows (with some exceptions of course): > > mvn versions:display-dependency-updates > > > > On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > > > +1 for M7 > > > > kind regards > > > > Tobias > > > >> Am 04.08.2017 um 18:56 schrieb Korbinian Bachl < > > > > korbinian.ba...@whiskyworld.de>: > >> > >> 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 would wait for > >>> September as August is usually a very quite month (at least in > >>> Europe) > > > > so > >>> > >>> it risks to be overlooked. But I have no objection to prepare a M7 > in > > > > the > >>> > >>> meantim
Google Chart integration as candidate for wicketstuff
Hello wicket-team, for a project visualizing metar weather data I used wicket-charts based on Highcharts in a former version (http://tremel-computer.no-ip.org:8080/metarstation/). Due to licensing of Highcharts I decided to move to Google charts, but found the implementation in wicketstuf outdated, since it depends on the image chart API, which is deprecated since 2012. So I wrote a Google Charts component based on the actual API. I am pleased with it, perhaps it could be helpful for other developers, so I'd like to give it to wicketstuff. It is rather lightweight, just enough Java to render the necessary JavaScript to the page header without knowledge of JavaScript. Knowledge of the Google API is needed to use it, it does not hide anything of the API, it should be quite feature complete. It is based at many points on org.apache.wicket.ajax.json and allows the user to build Java-Objects from compact JSON-Strings too, for example look at the essential class ChartOptions. Most of the classes are easy to understand with knowledge of the Google Charts API, since they are counterparts of the structure there. Only OptionHelper as container for convenience methods is a bit clumsy, but I have a different solution as a builder with a fluent interface in mind. gchart is actually used in a new branch of my weather app and does it's job there well. Perhaps you can have a look at it, if you like it, we can integrate it in wicketstuff. The ZIP in the attachment has already the structure with parent, lib and examples. I tried to write useful JavaDoc and some basic unit tests. The example is a quickstart giving two charts on one page, first one simple like Googles's Getting Started, the other more complex with a overview how to use the lib's features. Three issues (see TODO lines integrated in the source) are existing, but two are small, not blocking. The essential one is if the rendering of JavaScript in Chart#renderHead(final IHeaderResponse response) is sufficient for refreshing the chart by AJAX, I am not sure if. You can decide this in a second, I believe, and give me some hints to make the chart AJAX ready. I first wrote to Martin Grigorov since he helped me long ago to contribute a bit to wicketstuff. He told me he is on vacation and I should repeat the mail to the list. Dieter Tremel -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081
