ansaurus

Question

Answer 1

+1 A:

Have you checked your classpath? Based on what you have above it looks like while trying to load the class org.icepush.servlet.MainServlet it failed while trying to look up the class org.jboss.seam.faces.component.FormValidationTypeOverrideExtension. Do you have the jar that contains this class in your EAR? Is it at the right level for your application to find it? (ie, EAR level, WAR level, in the WAR lib dir, etc.)

Usually when I get a ClassNotFoundException it is because I am missing a jar, or the jar is at the wrong location within my app so it can't load it appropriately.

Chris Aldrich 2010-10-27 17:45:50

Thank you for the reply! The WAR is getting org.jboss.seam.faces.component.FormValidationTypeOverrideExtension through the Seam Faces JAR; I can't see anything wrong there. As far as org.icepush.servlet.MainServlet is concerned, it's just a warning that an optional feature of ICEfaces is disabled. I tried enabling it, but it doesn't help.

Nick 2010-10-27 18:06:27

@Nick - where in your application is the jar located? That might be part of it. The other thing I started to think of was the fact that Seam likes to do dependency injection. I'm not familiar with ICEFaces, although I know it to be another JSF implementation. Does it also attempt to do dependency injection? Just wondering because I am reminded of some articles I read in the past about Seam and Spring and how to config them so they don't conflict with each other as each wants to be the main dependency injector. Not sure if you have that going on here to or not? Just some other thoughts.

Chris Aldrich 2010-10-27 18:17:53

The JAR is bundled with the WAR. As far as I know, ICEfaces doens't implement JSF; it uses Mojarra, and it doesn't do dependency injection. Thanks!

Nick 2010-10-27 18:21:27

Answer 2

+2 A:

Based on this trace, I'm guessing that something is preventing proper discovery of beans when CDI starts up. Based on the fact that the issue only appears when Seam Faces is on the ClassPath, I'd have to say I'm not sure what.

Which version of Seam Faces are you using? 3.0.0.Alpha3 shouldn't have any problems on GF 3.0.1-b22

Lincoln 2010-10-27 20:29:27

I upgraded to GlassFish 3.1b25 (from 3.0.1b22) and the latest Seam Faces 3.0.0 snapshot (October 23, 2010) and am getting different errors now; I'll let you know how it works. Now I'm getting a java.lang.ClassNotFoundException: org.jboss.logging.Logger on deploy.

Nick 2010-10-27 23:00:30

Ok, the answer to this is to include JBoss logging - which is the new logging solution for Seam, we are no longer using SLF4j, so you need to include:

Lincoln 2010-10-28 02:03:20

<dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging</artifactId> <version>1.0.0.Beta4</version></dependency>

Lincoln 2010-10-28 02:05:27

<repository> <id>jboss-public-repository-group</id> <url>http://repository.jboss.org/nexus/content/groups/public</url></repository>

Lincoln 2010-10-28 02:05:50

Thank you, Lincoln! (I assume you meant 3.0.0.Beta4, not 1.0.0.Beta4). That clears up the logging issue, but I'm still getting the original WELD-001308 error. I'm also getting a few other new errors, all of which look like they have something to do with class loading. I'll work on it a bit and keep you abreast of what I've found.

Nick 2010-10-29 20:30:17

ansaurus

tags:

views:

answers:

Seam Faces causes a deploy-time error.

related questions