Issues: 1) maintainance I'd prefer to have less to maintain
2) no users https://github.com/jWeekend/LegUp tried to provide such quickstarts but there was no interest in the community to use/update them Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jan 11, 2016 at 10:14 PM, Martijn Dashorst < [email protected]> wrote: > Would it be better if we created multiple quick starts? I.E. one for > jetty, one for websockets, one for Java EE and one for Spring (Boot)? > > Martijn > > On Mon, Jan 11, 2016 at 9:01 PM, Martin Grigorov (JIRA) <[email protected]> > wrote: > > Martin Grigorov created WICKET-6072: > > --------------------------------------- > > > > Summary: Improve the quickstart to make it easier to use > JSR-356 web sockets > > Key: WICKET-6072 > > URL: https://issues.apache.org/jira/browse/WICKET-6072 > > Project: Wicket > > Issue Type: Improvement > > Components: wicket-quickstart > > Affects Versions: 7.2.0, 8.0.0-M1 > > Reporter: Martin Grigorov > > Assignee: Martin Grigorov > > Priority: Minor > > > > > > To be able to start an embedded Jetty with JSR-356 support the user has > to add some boilerplate that is not very easy to find in the Jetty > documentation. > > > > It would be good if the quickstart comes with this boilerplate commented > out and anyone who needs it just need to uncomment it. > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.4#6332) > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com >
