Need a working example of Tomcat 5 clustering
Has anyone gotten clustering to work? In an example I saw on the O'Reilly site at http://www.onjava.com/lpt/a/4702 I couldn't get the load balancer instance to forward requests on to the cluster node instances. = Steve Burns __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Difference found with jsp:include when migrating from 4.1.X to 5.0.18
In our deployment we have hundreds of jsp files with static include statements, like !-- style 1 -- jsp:include page=SomeOtherJspFile.jsp flush=true /jsp:include Instead of shortening this to: !-- style 2 -- jsp:include page=SomeOtherJspFile.jsp flush=true/ we decided in our jsp coding standard that the include should have a separate closing tag in case a jsp:param .../ had to be added later on. The jsp compiler chokes on these include statements using style 1 (see above) with the error: 2004-02-17 16:46:12 ApplicationDispatcher[/deployment20040217a] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: /path/NameOfJsp.jsp(60,0) Expecting jsp:param standard action with name and value attributes Of course if the jsp is changed to use style 2 (see above), there is no error. We are very reluctant to change all of these jsps, since Weblogic and Websphere and earlier versions of Tomcat had no problem with this syntax. Can someone point out why this syntax is no longer supported by Tomcat 5? = Steve Burns __ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Parsing error with jsp:include when migrating from 4.1.X to 5.0.18 on jsp files that have worked for years
In our deployment we have hundreds of jsp files with static include statements, like !-- style 1 -- jsp:include page=SomeOtherJspFile.jsp flush=true /jsp:include Instead of shortening this to: !-- style 2 -- jsp:include page=SomeOtherJspFile.jsp flush=true/ we decided in our jsp coding standard that the include should have a separate closing tag in case a jsp:param .../ had to be added later on. The jsp compiler chokes on these include statements using style 1 (see above) with the error: 2004-02-17 16:46:12 ApplicationDispatcher[/deployment20040217a] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: /path/NameOfJsp.jsp(60,0) Expecting jsp:param standard action with name and value attributes Of course if the jsp is changed to use style 2 (see above), there is no error. We are very reluctant to change all of these jsps, since Weblogic and Websphere and earlier versions of Tomcat had no problem with this syntax. Can someone point out why this is considered bad syntax after all these years? = Steve Burns __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
