On 5/30/07, Steve Tynor <[EMAIL PROTECTED]> wrote:
Thanks Matt!
With that, I'm able to get much further along with "mvn
integration-test" with my JSF 1.2 port (via myfaces-1.2.0-SNAPSHOT). I
was never able to get the .action tests to work with the shale-test
framework (see previous posts), so I've had to remove those five unit
tests.
integration-test reveals a compatibility problem with myfaces-1.2 vs.
1.1.x -- the hidden form link name has regressed back to _link_hidden_
(had been changed to _idcl in myfaces-1.1.5 for compatibility with the
Sun RI -- https://issues.apache.org/jira/browse/MYFACES-1539).
Apparently this fix has not made it into the 1.2-SNAPSHOT yet. Changing
the appfuse .xhtml to use the _link_hidden_ name instead of _idcl makes
integration-test work better.
However, I'm not out of the woods yet. While all the basic screens
display correctly (and even the ajax4jsf demo page works properly),
Canoo fails on the first form submit (line 95 of web-tests.xml - pushing
the Save button on the Edit Profile page). When this button is pressed,
the backing bean UserForm.save() function is never called (and the test
fails since the form refreshes itself rather than displaying the main
menu).
Have you tried debugging UserForm.java to make sure this method is never
called? I'd set breakpoints on edit() and save() to see if either is getting
called. You can zip up your project and send it to me if you like too. I'd
like to help you get this solved.
Matt
Ideas?
Steve
On 5/30/2007 3:15 PM, Matt Raible wrote:
> You should use tomcat5x as the container id and just change the
> cargo.container.url to point to the new version. For example:
>
> <profile>
> <id>tomcat6</id>
> <properties>
> <cargo.container>tomcat5x</cargo.container>
>
> <cargo.container.home>${env.CATALINA_HOME}</cargo.container.home>
> <cargo.container.url>
>
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.10/bin/apache-tomcat-6.0.10.zip
> </cargo.container.url>
> </properties>
> </profile>
>
> Matt
>
> On 5/30/07, *Steve Tynor* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
> Interesting. tomcat6x was the first variant I tried, but was unable
to
> get it to work. Your blog doesn't show any special pom.xml magic,
so
> I'm not sure if there was anything other than changing
cargo.container
> to tommcat6x and cargo.container.url to a tomcat 6 zip. But I've
tried
> both with and without adding <type>embedded</type> to the cargo
config,
> and get a "no registered configuration" when I try to use tomcat6x.
> What might I be missing?
>
> org.codehaus.cargo.container.ContainerException: Cannot create
> configuration. There's no registered configuration for the
> parameters(container [id = [tomcat6x], type = [installed]],
> configuration type [standalone]). Actually there are no valid types
> registered for this configuration. Maybe you've made a mistake
> spelling it?
>
> Thanks,
> Steve
>
> On 5/30/2007 2:43 PM, Matt Raible wrote:
> > You could use Tomcat 6, I've tested that and know that it works
with
> > Cargo and AppFuse. Note that I did have to make some adjustments
> for JSF.
> >
> > http://raibledesigns.com/rd/entry/upgrading_to_tomcat_6
> > <http://raibledesigns.com/rd/entry/upgrading_to_tomcat_6>
> >
> > Matt
> >
> > On 5/30/07, *Steve Tynor* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>>
> > wrote:
> >
> > FWIW, log4j is already listed as a cargo dependency by the
> > appfuse-generated pom.xml. I've tried removing it, to no
> effect. I'll
> > try using jboss4x with the new JBoss 4.2-GA and see what
happens.
> >
> > Steve
> >
> > On 5/30/2007 2:33 PM, Matt Raible wrote:
> > > You might try adding log4j as a dependency in Cargo's
plugin
> > > configuration. AFAIK, the only containers that work
> reliably with
> > Cargo
> > > are Tomcat and JBoss.
> > >
> > > Matt
> > >
> > > On 5/30/07, * Steve Tynor* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>>
> > > wrote:
> > >
> > > I'm trying to run mvn integration-test with a JSP 2.1
> > container, so
> > > trying to use jetty6x -- here's the relevant pom.xml
> config:
> > >
> > > < cargo.container>jetty6x</cargo.container>
> > >
> > > <
> > >
> >
> cargo.container.url>http://dist.codehaus.org/jetty/jetty-6.1.3.zip
> <http://dist.codehaus.org/jetty/jetty-6.1.3.zip
></cargo.container.url>
> > >
> > >
> > > Caused by:
> org.apache.commons.logging.LogConfigurationException :
> > > org.apache.comm
> > > ons.logging.LogConfigurationException : No suitable
Log
> > constructor
> > > [Ljava.lang.C
> > > lass;@196076f for
> org.apache.commons.logging.impl.Log4JLogger
> > (Caused by
> > > java.la <http://java.la> <http://java.la> <
http://java.la>
> > > ng.NoClassDefFoundError: org/apache/log4j/Category)
> (Caused by
> > > org.apache.common
> > > s.logging.LogConfigurationException: No suitable Log
> constructor
> > > [Ljava.lang.Cla
> > > ss;@196076f for
> org.apache.commons.logging.impl.Log4JLogger
> > (Caused by
> > > java.lang
> > > .NoClassDefFoundError: org/apache/log4j/Category))
> > > at
> > >
> > org.apache.commons.logging.impl.LogFactoryImpl.newInstance
> (LogFactory
> > > Impl.java:543)
> > > at
> > >
org.apache.commons.logging.impl.LogFactoryImpl.getInstance
> > (LogFactory
> > > Impl.java:235)
> > > at
> > >
> >
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance
(LogFactory
> > > Impl.java:209)
> > > at
> > > org.apache.commons.logging.LogFactory.getLog
> > (LogFactory.java:351)
> > > at
> > >
> >
> com.opensymphony.clickstream.ClickstreamListener
.<clinit>(Clickstream
> > > Listener.java:24)
> > > ... 29 more
> > >
> > > Matt posted a similar error to the cargo mailing list
> back in
> > November
> > > (
> > >
> >
>
http://www.nabble.com/Issues-with-Maven-2,-Cargo-and-Jetty-t2661661.html),
> > > but I can't find any resolution to his problem. Is
> there a
> > > configuration fix or workaround?
> > >
> > > Thanks,
> > > Steve
> > >
> > >
> >
>
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>
> > > <mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>>
> > > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]> <mailto:
> [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>
> > > <mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>>
> > >
> > >
> > >
> > >
> > > --
> > > http://raibledesigns.com
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>
> > For additional commands, e-mail:
> [EMAIL PROTECTED] <mailto:
[EMAIL PROTECTED]>
> > <mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>
> >
> >
> >
> >
> > --
> > http://raibledesigns.com <http://raibledesigns.com>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
>
>
>
>
> --
> http://raibledesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://raibledesigns.com