-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 9/27/16 11:57 AM, Fuchs, John J. wrote:
> Certainly late on the SHA-2 move from SHA-1 SSL certificates but
> ours hadn't expired yet and wasn't causing any issues. Our
> environment is Windows Server 2008 R2, JVM 1.6.0_22-b04 and Apache
Hi all:
Certainly late on the SHA-2 move from SHA-1 SSL certificates but ours hadn't
expired yet and wasn't causing any issues. Our environment is Windows Server
2008 R2, JVM 1.6.0_22-b04 and Apache Tomcat 6.0.26
I'm testing replacement of my soon to expire SHA-1 certificate with an SHA-2.
Thank you! This does resolve the issues.
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Friday, March 12, 2010 5:56 PM
To: Tomcat Users List
Subject: RE: Issues with Tomcat 6.0.26
From: Erick Lichtas [mailto:elich...@linoma.com]
Subject: RE
I was waiting on a fix for Jasper (48627) and found that 6.0.26
includes this fix. When we tested the individual patch for this fix
applied to 6.0.24, things seem to have worked fine. After upgrading to
Tomcat 6.0.26, I'm seeing all kinds of errors. Below are the details:
Note: Our application is
2010/3/12 Sai Pullabhotla sai.pullabho...@jmethods.com:
rich:tab label=#{bundle.tabQuickLinks}
h:commandLink action=browseProjects title=#{node.longDescription}
styleClass=#{node.selected ? 'SelectedCategoryNode' :
'CategoryNode'} actionListener=#{categoryTree.nodeClicked}
What versions of
Thanks for the reply, Konstantin.
If I understood your question correctly, you are asking about the
headers in the taglib for richfaces. I pulled it from the jar file and
here it is:
taglib xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
I am running into same issue on my side using the latest Tomcat 6.0.26 and
JSF. I am using Mojarra 1.2 patch 14 and RichFaces 3.3.2 SR1. I didn't have
any issues with 6.0.24.
Not sure what changed in 6.0.26, but it might have broken JSF 1.2 support.
Hopefully, someone can recommend a workaround.
I forgot to mention the version numbers in my previous mail. Here they are:
Richfaces 3.3.1
MyFaces 1.2.4
Tomahawk 1.1.6
Regards,
Sai Pullabhotla
On Fri, Mar 12, 2010 at 1:16 PM, Sai Pullabhotla
sai.pullabho...@jmethods.com wrote:
Thanks for the reply, Konstantin.
If I understood your
To: Tomcat Users List
Subject: Re: Issues with Tomcat 6.0.26
I am running into same issue on my side using the latest Tomcat 6.0.26 and
JSF. I am using Mojarra 1.2 patch 14 and RichFaces 3.3.2 SR1. I didn't have
any issues with 6.0.24.
Not sure what changed in 6.0.26, but it might have broken JSF 1.2
2010/3/12 Sai Pullabhotla sai.pullabho...@jmethods.com:
I forgot to mention the version numbers in my previous mail. Here they are:
Richfaces 3.3.1
MyFaces 1.2.4
Tomahawk 1.1.6
I have just downloaded trinidad-1.2.13-example.zip and
its trinidad-demo-1.2.13.war works for me in 6.0.26.
-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Friday, March 12, 2010 4:00 PM
To: Tomcat Users List
Subject: Re: Issues with Tomcat 6.0.26
2010/3/12 Sai Pullabhotla sai.pullabho...@jmethods.com:
I forgot to mention the version numbers in my previous mail. Here
You are the man, Konstantin! The issue is with the web app
specification in web.xml is set to 2.4. After I changed it to 2.5, I
see most pages rendering correctly. I will do some more testing and
let you know how it goes. Thanks again for pointing this.
Regards,
Sai Pullabhotla
On Fri, Mar
From: Erick Lichtas [mailto:elich...@linoma.com]
Subject: RE: Issues with Tomcat 6.0.26
5)Start the tomcat server and navigate to
http://host:8080/myfaces-example-simple-1.1.9/sample1.jsf.
You will notice that the many EL expressions are not resolved
properly.
Once the WEB-INF/web.xml
13 matches
Mail list logo