-1 from me, too much change.
With appfuse2 release there will inevitablably be plenty of problems to
overcome. More variables in the equation makes it harder to work out what is
going wrong. Surely sticking to as many knows as possible until after
appfuse2 is released and settled would be sensible?
my 2c
mraible wrote:
>
> All,
>
> I've done some testing with Tomcat 6.0.10 and AppFuse 2.0. Everything
> works fine, including Cargo, but it does have some issues with JSF.
> The solution seems to be removing the el-api dependency.
>
> Does anyone see a problem with making Tomcat 6 the default? For those
> that want to deploy a JSF application on Tomcat 5.5, you'd only need
> to add the following dependency to your pom.xml.
>
> <dependency>
> <groupId>javax.el</groupId>
> <artifactId>el-api</artifactId>
> <version>${el.version}</version>
> </dependency>
>
> Of course, then your app wouldn't work with Tomcat 6. Fricken' JSF. ;-)
>
> I imagine this problem will go away after folks have started playing
> with Tomcat 6, but that's the current situation.
>
> Making the above change also allows us to upgrade to Jetty 6.1.1.
>
> http://www.nabble.com/forum/ViewPost.jtp?post=9255028&framed=y
>
> Thanks,
>
> Matt
>
> --
> http://raibledesigns.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Tomcat-6.0.10-tf3328869s2369.html#a9262640
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
