Hi all,
I just *built* a websocket sample [3], using java-6. Build was successful.
However as Kasun has mentioned, if we *run* using java-6, tomcat-websocket
features (i.e. Tomcat JSR-356 Java WebSocket 1.0 implementation) don't
work.
This is also being mentioned in [4]
> "The JSR-356 Java WebS
Hi all,
On Fri, Jul 4, 2014 at 10:05 PM, Sriskandarajah Suhothayan
wrote:
> Thats good we'll verify that.
>
I hope to try this. Will post the findings. Thanks Kasun!
Regards,
Dilini
>
> Suho
>
>
> On Fri, Jul 4, 2014 at 5:19 PM, Kasun Gajasinghe wrote:
>
>>
>> AFAIK, you do not need JDK 1.7
Thats good we'll verify that.
Suho
On Fri, Jul 4, 2014 at 5:19 PM, Kasun Gajasinghe wrote:
>
> AFAIK, you do not need JDK 1.7 to compile websocket based webapps.
>
>
> On Fri, Jul 4, 2014 at 4:21 PM, Sriskandarajah Suhothayan
> wrote:
>
>> At runtime that will help. But this is not possible w
AFAIK, you do not need JDK 1.7 to compile websocket based webapps.
On Fri, Jul 4, 2014 at 4:21 PM, Sriskandarajah Suhothayan
wrote:
> At runtime that will help. But this is not possible when compiling and
> releasing the product :(
>
> Suho
>
>
> On Fri, Jul 4, 2014 at 4:17 PM, Kasun Gajasinghe
At runtime that will help. But this is not possible when compiling and
releasing the product :(
Suho
On Fri, Jul 4, 2014 at 4:17 PM, Kasun Gajasinghe wrote:
> Hi,
>
> How Tomcat Websocket works is that if the JDK version is less than 7, it
> disables Websocket feature and the container starts
Hi,
How Tomcat Websocket works is that if the JDK version is less than 7, it
disables Websocket feature and the container starts up. It prints a warning
log pointing out that user is not running in JDK 7. You might want to
follow the same procedure.
Regards,
KasunG
On Fri, Jul 4, 2014 at 3:32 P
Yes, thats an issue.
Because of this we wont be able to build the full platform in one java
version.
So what will be the recommended approach here ?
Regards
Suho
On Fri, Jul 4, 2014 at 3:26 PM, Sagara Gunathunga wrote:
>
>
>
> On Fri, Jul 4, 2014 at 3:07 PM, Sriskandarajah Suhothayan
> wrote
On Fri, Jul 4, 2014 at 3:07 PM, Sriskandarajah Suhothayan
wrote:
> Our idea is to use Tomcat this is jetty is just a quick PoC we did for
> CEP. But even to use Tomcat Web sockets we have to have to build using Java
> 7[1].
> So anyway we have to move to Java 7 to build the CEP repo so that it ca
Our idea is to use Tomcat this is jetty is just a quick PoC we did for CEP.
But even to use Tomcat Web sockets we have to have to build using Java
7[1].
So anyway we have to move to Java 7 to build the CEP repo so that it can
compile the WebSocket servlet
What is our plan on moving the build to Ja
+1. Don't unnecessarily bring in Jetty.
On Fri, Jul 4, 2014 at 2:49 PM, Sagara Gunathunga wrote:
>
>
>
> On Fri, Jul 4, 2014 at 2:40 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> Hi All,
>>
>> Are we planning to do $subject.. ?
>> In CEP, we have developed an adptor which
On Fri, Jul 4, 2014 at 2:40 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:
> Hi All,
>
> Are we planning to do $subject.. ?
> In CEP, we have developed an adptor which supports for websocket. Here we
> are using latest jetty version which only supports Java 1.7 according to
> [1]..
Hi All,
Are we planning to do $subject.. ?
In CEP, we have developed an adptor which supports for websocket. Here we
are using latest jetty version which only supports Java 1.7 according to
[1].. But since we have configured jenkins only with java 1.6, this
components is getting failed. Is it pos
12 matches
Mail list logo
