+1 It'll be great to run Roller without any modifications on 2.4.
Cheers,
Amy
Matt Raible wrote:
+1, but only because all the servers I'm running on support 2.4.
I'm willing to bet the ones who object are running it on a container
that doesn't support it. My advice to them - use an open source
server that does. ;-)
Matt
On 2/17/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
Coming back to this now since it's fairly important.
Basically, our web.xml file is broken right now because we have a 2.3 DTD, yet
we have some 2.4 elements in it. We need to fix this one way or the other.
I suggest we go to 2.4 since 2.3 is pretty old now. It's fairly easy to switch
it back for users that need to do so anyways.
I'm +1 for this change. Lets hear some votes.
-- Allen
On Thu, 2005-12-22 at 13:17, Matt Raible wrote:
From what I've seen in my playing with various servlet containers
(Tomcat, Jetty and Resin), Tomcat is the only one that allows
<dispatcher> elements in a 2.3 web.xml. JBoss allows it too - since
it uses Tomcat, and since most Roller users use one of these two -
we've been able to get away with it for quite some time.
Matt
On 12/22/05, Amy Roh <[EMAIL PROTECTED]> wrote:
Hi Dave,
It's not that GlassFish can't do Servlets 2.3, I changed the web.xml to
Servlets 2.4 since it included "dispatcher" elements by default instead
of commenting it out.
See below from web.xml.
<!--
NOTE: Wherever "dispatcher" elements are specified in the filter
mappings, they are
required for Servlet API 2.4 containers, such as Tomcat 5+ and
Resin 3+, but should be
commented out for Servlet API 2.3 containers, like Tomcat 4.x and
Resin 2.x.
-->
<!-- Ensures character encoding set to UTF-8 and JSTL and Struts locales
are in sync.
Note: Any filters preceding this one MUST not cause request parsing. -->
<filter-mapping>
<filter-name>CharEncodingFilter</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
</filter-mapping>
When I had 2.3, validation failed during deployment.
Thanks,
Amy
Dave Johnson wrote:
It's interesting that Glassfish can't do Servlets 2.3.
Should we switch Roller's web.xml over to 2.4 now?
I think the reason we didn't do this before was XDoclet, but we have
upgraded XDoclet since then.
- Dave
On Dec 21, 2005, at 2:53 PM, Amy Roh wrote:
Hi,
After a few changes, I was able to deploy Roller 2.1 on GlassFish.
To address the TLD error, I did the following :
Change web.xml to use version 2.4 from 2.3.
<web-app xmlns="http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
version="2.4">
Change taglibs.jsp to use JSTL1.1 from JSTL 1.0
<%@ taglib uri="http://java.sun.com/jsp/jstl/core"; prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/fmt"; prefix="fmt" %>
Thanks,
Amy
Dave Johnson wrote:
I'm assuming you're using a recent pre-release build of Roller 2.1
and you're doing a fresh install, not an upgrade. So I guess this
might be a database configuration error. Which database are you
using?
- Dave
On Dec 21, 2005, at 12:58 PM, Amy Roh wrote:
Hi,
I have deployed roller on sun application server and am getting
the following error.
Anyone seen this?
ERROR 2005-12-20 16:06:22,031 JDBCExceptionReporter:logExceptions
- Unknown column 'websitedat2_.handle' in 'field list'
FATAL 2005-12-20 16:06:22,046 RollerContext:contextInitialized -
RollerContext initialization failed
org.roller.RollerException
at
org.roller.business.hibernate.HibernatePingTargetManagerImpl.getCommo
nP ingTargets(HibernatePingTargetManagerImpl.java:50)
.......
--- ROOT CAUSE ---
org.hibernate.exception.SQLGrammarException: could not execute query
at
org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter
.j ava:70)
.............
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:210)
Caused by: java.sql.SQLException: Unknown column
'websitedat2_.handle' in 'field list'
Thanks,
Amy
