I guess I should have made it a bit more clear. When we created the project
a year and a half ago, we took the latest app fuse and ported what we could
quickly into maven 2 since the rest of our multi-module project was using
maven 2.
Basically, in saying it's appfuse 1.9.3, I'm saying we started with appfuse
webwork 1.9.3 when we created our web application.
I don't really think this has much to do with appfuse itself. I was hoping
someones experience with using the maven jetty plugin for appfuse 2 could
help me figure this problem out.
Thanks,
Skip
mraible wrote:
>
> Did you port your 1.9.3 application to use Maven?
>
> On 9/18/07, SkipWalker <[EMAIL PROTECTED]> wrote:
>>
>>
>> I've just set up my webwork-hibernate-sitemesh-spring appfuse 1.9.3 based
>> webapp to use the maven-jetty-plugin. Everything for the most part is
>> working. The ssl connector is correctly configured.
>>
>> However, I'm having an issue that I can't narrow down. Certain
>> actions/jsps
>> (most importantly my login.jsp) render with what I'll call gobbly gook (
>> e.g.
>> "[EMAIL PROTECTED]") while others work just fine. At first I
>> thought this might be an ssl issue, but other pages render just fine
>> through
>> SSL. I imagine this is some sort of encoding issue, but I'm not
>> particularly familiar with these type of issues and I can't narrow down
>> what
>> that is or more importantly how to fix it.
>>
>> All of my webwork actions, and jsps are renderered in a sitemesh
>> default.jsp
>> wrapper which includes the following directive to set the encoding.
>>
>> <%@ page language="java" errorPage="/error.jsp" pageEncoding="UTF-8"
>> contentType="text/html;charset=UTF-8" %>
>>
>> My plugin configuration is at the bottom
>>
>>
>> If anyone has any suggestions on correcting the problem, they are greatly
>> appreciated.
>>
>> Thanks,
>> Skip
>>
>>
>> <plugin>
>> <groupId>org.mortbay.jetty</groupId>
>> <artifactId>maven-jetty-plugin</artifactId>
>> <version>6.1.5</version>
>> <configuration>
>> <contextPath>/voyant</contextPath>
>>
>> <jettyEnvXml>${basedir}/src/main/webapp/WEB-INF/jetty-env.xml
>> </jettyEnvXml>
>> <scanIntervalSeconds>10</scanIntervalSeconds>
>> <connectors>
>> <connector
>> implementation="org.mortbay.jetty.nio.SelectChannelConnector">
>> <port>8080</port>
>> <maxIdleTime>3600000</maxIdleTime>
>> </connector>
>> <connector
>> implementation="org.mortbay.jetty.security.SslSocketConnector">
>> <port>8443</port>
>> <maxIdleTime>3600000</maxIdleTime>
>>
>> <keystore>${basedir}/metadata/ssl/jetty.keystore</keystore>
>> <password>password</password>
>> <keyPassword>password</keyPassword>
>> </connector>
>> </connectors>
>> </configuration>
>> </plugin>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-jetty-plugin-output-encoding-issues--tf4477905s2369.html#a12768494
>> Sent from the AppFuse - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> http://raibledesigns.com
>
>
--
View this message in context:
http://www.nabble.com/maven-jetty-plugin-output-encoding-issues--tf4477905s2369.html#a12778465
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
