Chris,
On 27.10.2013 2:47, Chris Arnold wrote:
This is both possible, only if you plan to use either BIO or NIO HTTP
connector. If you plan to use APR, connector configuration is completely
different.
Not sure what either of these are. I just need secure tomcat
Let us first determine which
On 26/10/2013 16:44, Johan Compagner wrote:
I've just started looking at the javax.websocket implementation in tomcat 8
and I have a question about how one integrates an endpoint with application
code. Using servlets as an analogy, web.xml allows configuration
information to be passed to
It appears that there is a problem in Tomcat's static UpgradeUtil.doUpgrade
logic when handling concurrent connection/upgrade requests that rely on a
custom ServerEndpointConfig.Configurator.modifyHandshake to grab
[per-upgrade-request] client header values and inject them into the wsSession
and i have a follow up question about this, with a servlet or a filter
you
can do: getServletContext() then you have access to the resources of the
web application and stuff like that
How is that possible in an websocket endpoint?
The ServerEndpointConfig will have the modifyHandshake()
On 26 October 2013 21:59, Violeta Georgieva violet...@apache.org wrote:
This release contains a number of bug fixes and improvements compared to
version 7.0.42. The notable changes include:
- Back-port the JSR-356 Java WebSocket 1.0 implementation from Apache
Tomcat 8.
- Deprecate the
On 27/10/2013 12:36, Johan Compagner wrote:
and i have a follow up question about this, with a servlet or a filter
you
can do: getServletContext() then you have access to the resources of the
web application and stuff like that
How is that possible in an websocket endpoint?
The
On 25.10.2013 11:54, Konstantin Kolinko wrote:
2013/10/25 Web2 Solutions m...@web2-solutions.com:
Hallo All,
I've installed tomcat 7.0.42 and due heavy use my catalina.out and
localhost_access-jjj-mm-dd.txt grows quit big.
I've successfully configured logrotate to rotate both files. I've
2013/10/27 Johan Compagner jcompag...@servoy.com
On 26 October 2013 21:59, Violeta Georgieva violet...@apache.org wrote:
This release contains a number of bug fixes and improvements compared to
version 7.0.42. The notable changes include:
- Back-port the JSR-356 Java WebSocket 1.0
Thanks for the replies Mark.
It does seem to me that most developers using websockets under tomcat are going
to want that integration with the J2EE container. Maybe I'm wrong, but it
seems like the plumbing to make the servlet context available to the
EndpoingConfig will be messy because the
On Sun, Oct 27, 2013 at 4:46 PM, Neil Martin nsm...@gmail.com wrote:
Thanks for the replies Mark.
It does seem to me that most developers using websockets under tomcat are
going to want that integration with the J2EE container. Maybe I'm wrong,
but it seems like the plumbing to make the
On 27 October 2013 16:09, Niki Dokovski nick...@gmail.com wrote:
On Sun, Oct 27, 2013 at 4:46 PM, Neil Martin nsm...@gmail.com wrote:
Thanks for the replies Mark.
It does seem to me that most developers using websockets under tomcat are
going to want that integration with the J2EE
i guess this page should now be updated:
http://tomcat.apache.org/whichversion.html
Thanks for pointing that.
It should be fixed now.
only that the minimum version of Tomcat 7 is now not always java 6 ;)
Hello My name is Marcelo, i have a little web site and i am using apache
tomcat 8.0.0-RC5 and making use of JSR-356 websocket api ... (i followed
the ChatAnnotation example) ...
I almost finished the development when i found 2 problems ...
1) Is it possible to get the remote ip of the client on
Hello everybody.
I just downloaded 7.0.47 and updated one web application that I developed
in order to use the new standard JSR 356 websocket implementation.
With this new implementation, I noticed that during the processing of
incoming websocket events, it's not possible to access the JNDI
2013/10/28 Francesco Bassi fvba...@gmail.com:
Hello everybody.
I just downloaded 7.0.47 and updated one web application that I developed
in order to use the new standard JSR 356 websocket implementation.
With this new implementation, I noticed that during the processing of
incoming
15 matches
Mail list logo