Ah que estas en el de puertos también.
Ahora te quito no te preocupes.
El 09/04/15 a las 14:59, Christopher Schultz escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mukund,
On 4/8/15 11:33 PM, Mukundaraman Valakumaresan wrote:
I have deployed an application in Apache tomcat 7.0.59.
Hi,
I'm trying to upgrade websocket application which is using Tomcat 7 to
Tomcat 8.0.20(Which supports javax.websocket v1)
In the current implementation we have extended the WebSocketServlet
Is there a way that I can access the servletContext in the new websocket
implementation?
As I understand
On 09/04/2015 19:50, George Sexton wrote:
Chris
On 4/9/2015 10:06 AM, Christopher Schultz wrote:
Just my two cents, but any server that works the way you want is
not compliant with the servlet specification. It states that all
requests for a context must be passed to the container.
??
On 4/9/2015 3:06 PM, George Sexton wrote:
On 4/9/2015 12:58 PM, Caldarale, Charles R wrote:
From: George Sexton [mailto:geor...@mhsoftware.com]
Subject: Re: Rendering JSP files through Apache
My reading of it says that any request that matches a known context path
must be routed to the web
On 4/9/2015 10:06 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
George,
On 4/9/15 10:52 AM, George Sexton wrote:
On 4/8/2015 6:15 PM, Leggio, Andrew wrote:
This contains both HTML and JSP. I would like the HTML to be
handled through Apache and JSP pages to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew,
On 4/8/15 3:07 PM, Leggio, Andrew wrote:
Thank you for responding. I changed the mod_proxy_ajp.c to
mod_proxy_ajp.so which is the module that is being loaded. Now my
html pages are rendering fine; however, when I go the jsp pages
Chris
On 4/9/2015 10:06 AM, Christopher Schultz wrote:
Just my two cents, but any server that works the way you want is
not compliant with the servlet specification. It states that all
requests for a context must be passed to the container.
??
The servlet spec doesn't apply to environments,
On 4/9/2015 1:10 PM, David kerber wrote:
You can argue about whether it's smart to map servlets into .html, but
again my reading of the spec is that unequivocally, if the request path
matches a deployed context, the request must be routed to the
context/container.
Then your reading is
From: George Sexton [mailto:geor...@mhsoftware.com]
Subject: Re: Rendering JSP files through Apache
My reading of it says that any request that matches a known context path
must be routed to the web application. It seems pretty cut and dried to me.
That's true only when the request is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/2015 12:18 PM, George Sexton wrote:
On 4/9/2015 1:10 PM, David kerber wrote:
You can argue about whether it's smart to map servlets into
.html, but
again my reading of the spec is that unequivocally, if the
request path matches a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew,
On 4/8/15 8:15 PM, Leggio, Andrew wrote:
This contains both HTML and JSP. I would like the HTML to be
handled through Apache and JSP pages to be handled by TOMCAT.
Okay. Just curious: why?
How do I accomplish this?
- From your other
Looks like we have two potential root causes. 1. Spring Framework 4.0.0 and jdk
1.7.0_51 are used which might be one of the root causes according to a Spring
Framework bug.. The fix is to upgrade the Spring Framework version.2. The
codecache is too small in 1.7.0_51 and leads to performance/cpu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
George,
On 4/9/15 10:52 AM, George Sexton wrote:
On 4/8/2015 6:15 PM, Leggio, Andrew wrote:
This contains both HTML and JSP. I would like the HTML to be
handled through Apache and JSP pages to be handled by TOMCAT.
How do I accomplish this?
On 4/9/2015 12:58 PM, Caldarale, Charles R wrote:
From: George Sexton [mailto:geor...@mhsoftware.com]
Subject: Re: Rendering JSP files through Apache
My reading of it says that any request that matches a known context path
must be routed to the web application. It seems pretty cut and dried to
On 4/9/2015 3:03 PM, George Sexton wrote:
On 4/9/2015 10:06 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
George,
On 4/9/15 10:52 AM, George Sexton wrote:
On 4/8/2015 6:15 PM, Leggio, Andrew wrote:
This contains both HTML and JSP. I would like the HTML to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Salam,
On 4/8/15 5:24 PM, Salam Y. Elias wrote:
I downloaded 8.0.21, created three directories, each one with its
own Tomcat, chnaged some ports in server.xml and all 3 applications
are running like a charm.
If you have a complete Tomcat
On 09/04/2015 20:18, George Sexton wrote:
On 4/9/2015 1:10 PM, David kerber wrote:
You can argue about whether it's smart to map servlets into .html, but
again my reading of the spec is that unequivocally, if the request path
matches a deployed context, the request must be routed to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mukund,
On 4/8/15 11:33 PM, Mukundaraman Valakumaresan wrote:
I have deployed an application in Apache tomcat 7.0.59.
When I copy the war to webapps folder and start tomcat. Tomcat
hangs and I coudln't see the admin screen as well for the
On 4/8/2015 6:15 PM, Leggio, Andrew wrote:
This contains both HTML and JSP. I would like the HTML to be handled through
Apache and JSP pages to be handled by TOMCAT. How do I accomplish this?
Just my two cents, but any server that works the way you want is not
compliant with the servlet
On 4/9/2015 3:18 PM, George Sexton wrote:
On 4/9/2015 1:10 PM, David kerber wrote:
You can argue about whether it's smart to map servlets into .html, but
again my reading of the spec is that unequivocally, if the request path
matches a deployed context, the request must be routed to the
From: George Sexton [mailto:geor...@mhsoftware.com]
Subject: Re: Rendering JSP files through Apache
The problem is then that as a system, the container isn't compliant.
What you're in essence saying is that the compliance of the system
isn't a concern. My belief is that as a system, the
Hi,
I have setup Tomcat to authenticate users against openldap. I want
roles to be retrieved from the user record itself.
Realm className=org.apache.catalina.realm.JNDIRealm
connectionURL=ldap://127.0.0.1:389;
userPattern=uid={0},ou=users,dc=admin,dc=company,dc=com
userRoleName=ou
/
22 matches
Mail list logo
