On 13/01/2017 15:02, Martin Grigorov wrote:
On Fri, Jan 13, 2017 at 10:46 AM, Emond Papegaaij <
I was wondering if we still need to support Tomcat 7.0 with native
As far as I can see, Tomcat 8.0 and 8.5 both support JSR 356 and Tomcat 7.0
does not support Servlet 3.1, which is required for Wicket 8. Therefore, I
think we should drop the wicket-native-websocket-tomcat module. Perhaps we
should also merge javax into core and place the examples with the other
With websockets becomming more and more standard, I'm not sure we still
wicket-atmosphere. wicket-native-websocket provides the same functionallity
and more. Also, Atmosphere has a history of bugs and problems. I wouldn't
recommend anyone to use it.
On maandag 31 oktober 2016 14:41:12 CET Martin Grigorov wrote:
What other improvements do we need in 8.x/master before promoting it to
8.0.0 final ?
we still have:
- new DateTime APIs for wicket-datetime *WICKET-6105
<https://issues.apache.org/jira/browse/WICKET-6105>* - I'll give this
more try but the problem is that I don't believe this is the proper way
this demotivates me.
If someone else wants to give it a try - please assign it to yourself!
- Better SEO for stateful pages - the only way I see this is by using
ServiceWorker to add the pageId as a request header to all requests
Recently I wondered whether Redux.js could be in use for Wicket.
I don't have much experience with it, but both React and AngularJs
communities use it to manage the state for their components.
There are some Java impls, even a standard is coming:
What else ?
Wicket Training and Consulting