gmane.comp.java.wicket.devel

Re: WebSockets don't work in Safari

Martin Grigorov — 2012-05-24T16:19:44

http://jfarcand.wordpress.com/2012/05/16/safaris-websocket-implementation-and-java-problematic/

On Thu, May 24, 2012 at 6:56 PM, Martijn Dashorst
<martijn.dashorst-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

WebSockets don't work in Safari

Martijn Dashorst — 2012-05-24T15:56:43

While testing the upcoming release of Wicket 6-beta2, I tried testing
the websockets example, but it fails with the following serverside
error (using mvn jetty:run)

ERROR - AsynchronousProcessor      - failed to timeout resource null
java.lang.NullPointerException
at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:354)
at org.atmosphere.cpr.AsynchronousProcessor$AsynchronousProcessorHook.timedOut(AsynchronousProcessor.java:578)
at org.atmosphere.websocket.WebSocketProcessor.close(WebSocketProcessor.java:216)
at org.atmosphere.container.JettyWebSocketHandler.onClose(JettyWebSocketHandler.java:132)
at org.eclipse.jetty.websocket.WebSocketConnectionD00.onClose(WebSocketConnectionD00.java:227)
at org.eclipse.jetty.websocket.WebSocketServletConnectionD00.onClose(WebSocketServletConnectionD00.java:99)
at org.eclipse.jetty.server.AbstractConnector.connectionClosed(AbstractConnector.java:1145)
at org.eclipse.jetty.server.nio.SelectChannelConnector.endPointClosed(SelectChannelConnector.java:274)
at org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager.endPointClosed(SelectChannelConnector.java:301)
at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.destroyEndPoint(SelectorManager.java:848)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.doUpdateKey(SelectChannelEndPoint.java:585)
at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:463)
at org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:285)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
at java.lang.Thread.run(Thread.java:680)
ERROR - Jetty8WebSocket            - WebSocket Redirect not supported

Is this expected (< at >papegaaij) behavior in that Safari is not yet a
supported platform for atmosphere?

As wicket-atmosphere is experimental, I don't want this to hold back
the release, so expect a vote coming up soon...

Martijn

Re: git commit: Assembly plugin completely disabled

Martin Grigorov — 2012-05-23T15:18:19

On Wed, May 23, 2012 at 6:02 PM, Martijn Dashorst
<martijn.dashorst-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

mvn5 is an alias to something that runs on *your* machine, so it could
be anything.
I made two releases so far.


But when we will have -beta2 ?
It is just ridiculous that the vote has been canceled because of a
simple change in the version of wicket-atmosphere, and almost two
weeks later we
do not move at all ...

I'm not sure whether you realize but this just frustrates me.
If there is another reason not to release -beta2 then please let me know.
Otherwise I suggest to set manually the version of wicket-atmosphere
to 0.1, do the release as before, then set it to 0.2-SNAPSHOT and then
you will have your time to rework the release procedure.

Re: git commit: Assembly plugin completely disabled

Martijn Dashorst — 2012-05-23T15:02:53

The current release scripts depend on Java 5 AFAICT, at least they
claim to do so (mvn5). They should not work in the first place.


Dropping them altogether should be good enough for trunk. Wicket 1.5
can still use them though.

Martijn

Re: git commit: Assembly plugin completely disabled

Martin Grigorov — 2012-05-23T14:30:43

Maybe you should do this in a branch.
It seems it will take you some time until you are ready with the new
release procedure.

With this commit I think the currently used release.sh scripts wont be
able to create the .tar.gz and .zip for Apache downloads
(http://archive.apache.org/dist/wicket/).

I suggest to drop the old release scripts once we have the new one
stabilized, i.e. after few releases.

On Wed, May 23, 2012 at 5:21 PM,  <dashorst< at >apache.org> wrote:

wicket pull request: WICKET-4219: Enable markup escaping of WizardStep's la...

Git at Apache — 2012-05-23T07:30:01

Github user tgoetz closed the pull request at:

    https://github.com/apache/wicket/pull/9

wicket pull request: WICKET-4219: Enable markup escaping of WizardStep's la...

Git at Apache — 2012-05-23T07:29:59

Github user tgoetz closed the pull request at:

    https://github.com/apache/wicket/pull/9

wicket pull request: WICKET-4219: Enable markup escaping of WizardStep's la...

Git at Apache — 2012-05-23T07:29:40

Github user tgoetz closed the pull request at:

    https://github.com/apache/wicket/pull/10

wicket pull request: WICKET-4219: Enable markup escaping of WizardStep's la...

Git at Apache — 2012-05-23T07:29:38

Github user tgoetz closed the pull request at:

    https://github.com/apache/wicket/pull/10

wicket pull request: Javadoc corrections

Git at Apache — 2012-05-23T07:18:23

Github user tgoetz closed the pull request at:

    https://github.com/apache/wicket/pull/11

wicket pull request: Javadoc corrections

Git at Apache — 2012-05-23T07:18:24

Github user tgoetz closed the pull request at:

    https://github.com/apache/wicket/pull/11

wicket pull request: Javadoc corrections

Git at Apache — 2012-05-22T20:56:59

GitHub user tgoetz opened a pull request:

    https://github.com/apache/wicket/pull/11

    Javadoc corrections

    Several javadoc corrections

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tgoetz/wicket javadoc

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/wicket/pull/11.patch

----
commit a2f73926097ddb14819dc85aa6f4db184f5a9e21
Author: Thomas GoÌtz <tom-IRwnrYQUMquELgA04lAiVw< at >public.gmane.org>
Date:   2012-05-22T13:51:18-07:00

    Javadoc corrections

----

wicket pull request: Javadoc corrections

Git at Apache — 2012-05-22T20:57:00

GitHub user tgoetz opened a pull request:

    https://github.com/apache/wicket/pull/11

    Javadoc corrections

    Several javadoc corrections

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tgoetz/wicket javadoc

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/wicket/pull/11.patch

----
commit a2f73926097ddb14819dc85aa6f4db184f5a9e21
Author: Thomas GoÌtz <tom-IRwnrYQUMquELgA04lAiVw< at >public.gmane.org>
Date:   2012-05-22T13:51:18-07:00

    Javadoc corrections

----

Re: [Vote] Release Apache Wicket 6.0.0-beta2

Martijn Dashorst — 2012-05-16T15:26:33

I strive to build a release tomorrow, but family might interfere (it's
a holiday tomorrow).

Martijn

On Wed, May 16, 2012 at 5:13 PM, Martin Grigorov <mgrigorov-1oDqGaOF3Lkdnm+yROfE0A< at >public.gmane.org> wrote:

Re: [Vote] Release Apache Wicket 6.0.0-beta2

Martin Grigorov — 2012-05-16T15:13:19

Any progress on a solution for the problem with the release of
wicket-atmosphere module ?

On Tue, May 15, 2012 at 4:37 PM, Martin Grigorov <mgrigorov-1oDqGaOF3Lkdnm+yROfE0A< at >public.gmane.org> wrote:

Re: [Vote] Release Apache Wicket 6.0.0-beta2

Martin Grigorov — 2012-05-15T14:37:40

wicket-cdi is more mature, imo it may be included directly with 6.x version

but I think that new modules like wicket-atmo can have their own
release cycle until they are included in the big group. there is no
reason why wicket-atmo:0.2 should wait for 6.0.0-beta3

but of course this will add some more pain in the release process

On Tue, May 15, 2012 at 4:30 PM, Igor Vaynberg <igor.vaynberg-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: [Vote] Release Apache Wicket 6.0.0-beta2

Igor Vaynberg — 2012-05-15T14:30:20

if the whole idea is to release these modules why move wicket-cdi in
there and disable its releasing?

-igor

On Tue, May 15, 2012 at 12:51 AM, Martijn Dashorst
<martijn.dashorst-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

wicket pull request: WICKET-4219: Enable markup escaping of WizardStep's la...

Git at Apache — 2012-05-15T09:21:30

GitHub user tgoetz opened a pull request:

    https://github.com/apache/wicket/pull/10

    WICKET-4219: Enable markup escaping of WizardStep's labels by default due to security aspects

    Applied to 1.5.x branch

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tgoetz/wicket wicket-1.5.x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/wicket/pull/10.patch

----
commit 1543047dda1158504c98502d73f5e8e6535e9bd9
Author: Thomas GoÌtz <tom-IRwnrYQUMquELgA04lAiVw< at >public.gmane.org>
Date:   2012-05-15T02:16:53-07:00

    WICKET-4219: Enable markup escaping of WizardStep's labels by default due to security aspects

----

wicket pull request: WICKET-4219: Enable markup escaping of WizardStep's la...

Git at Apache — 2012-05-15T09:21:32

GitHub user tgoetz opened a pull request:

    https://github.com/apache/wicket/pull/10

    WICKET-4219: Enable markup escaping of WizardStep's labels by default due to security aspects

    Applied to 1.5.x branch

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tgoetz/wicket wicket-1.5.x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/wicket/pull/10.patch

----
commit 1543047dda1158504c98502d73f5e8e6535e9bd9
Author: Thomas GoÌtz <tom-IRwnrYQUMquELgA04lAiVw< at >public.gmane.org>
Date:   2012-05-15T02:16:53-07:00

    WICKET-4219: Enable markup escaping of WizardStep's labels by default due to security aspects

----

Re: [Vote] Release Apache Wicket 6.0.0-beta2

Martijn Dashorst — 2012-05-15T07:51:58

The whole idea is that we release these modules as part of our normal
releases to give them exposure. Therefore rerolling the release with
proper 0.1 versioning for the experimentals is necessary IMO.

Martijn

Re: [Vote] Release Apache Wicket 6.0.0-beta2

Martin Grigorov — 2012-05-15T07:43:59

+1 to release it

tested most of wicket-examples

the broken module is not in the staging repo. i.e. there wont be
0.1-SNAPSHOT in Maven central

On Mon, May 14, 2012 at 3:06 PM, Emond Papegaaij
<emond.papegaaij-F3d6P0JCqsnz+pZb47iToQ< at >public.gmane.org> wrote: