seam-faces 3.0.0.Beta2 gives error in GlassFish

[sebastianovide]

Hi All,

Using seam-faces 3.0.0.Beta2 (from maven repo) I'm getting this erron in GlassFish:

SEVERE: Class [ org/joda/time/DateTimeZone ] not found. Error while loading [ class org.jboss.seam.international.datetimezone.DefaultDateTimeZoneProducer ]

that leads to some exceptions...

Same problem with Beta1 but I do not see any problem with 3.0.0.Alpha3 (from http://repo1.maven.org/maven2/org/jboss/seam/faces/seam-faces/3.0.0.Alpha3/seam-faces-3.0.0.Alpha3.pom)

ideas ?

thanks

[ssachtleben.ssachtleben.gmail.com]

Well i'm not sure about the current state but I heard that the development and deployment on glassfish isnt working properly right now. Maybe you should use jboss 6.0.0.Final untill these issues sorted out.

[bleathem]

Try including Seam Solder Beta 3 with your app - by default Seam Faces Beta 2 includes Seam Solder Beta 1.

[surajchhetry]

Hi All,
When I try to deploy seam-faces i ran into an issue with glassfish 3.1 ( b 43 ) even though i am using Seam Solder 3.0.0.Beta3.

Here is my stack Track


SEVERE: Exception while loading the app
SEVERE: Exception while loading the app : WELD-001408 Unsatisfied dependencies for type [Messages] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.faces.status.MessagesAdapter.messages]
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Messages] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.faces.status.MessagesAdapter.messages]
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305)
        at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139)
        at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
        at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:385)
        at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371)
        at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390)
        at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:190)
        at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
        at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:298)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
        at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
        at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465)
        at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222)
        at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
        at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
        at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
        at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
        at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
        at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
        at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
        at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
        at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
        at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
        at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
        at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
        at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
        at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
        at java.lang.Thread.run(Thread.java:662)

INFO: WEB0169: Created HTTP listener [http-listener-2] on host/port [0.0.0.0:8181]
INFO: Grizzly Framework 1.9.31 started in: 2ms - bound to [0.0.0.0:8181]


Here is POM (Dependency)

<dependencies>
        <dependency>
            <groupId>com.sun.faces</groupId>
            <artifactId>jsf-api</artifactId>
            <version>2.0.2-b10</version>
        </dependency>
        <dependency>
            <groupId>com.sun.faces</groupId>
            <artifactId>jsf-impl</artifactId>
            <version>2.0.2-b10</version>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>jstl</artifactId>
            <version>1.1.2</version>
        </dependency>
        <dependency>
            <groupId>taglibs</groupId>
            <artifactId>standard</artifactId>
            <version>1.1.2</version>
        </dependency>
        <dependency>
            <groupId>joda-time</groupId>
            <artifactId>joda-time</artifactId>
            <version>1.6.2</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.logging</groupId>
            <artifactId>jboss-logging</artifactId>
            <version>3.0.0.Beta4</version>
        
        </dependency>
     
        <dependency>
            <groupId>org.jboss.seam.solder</groupId>
            <artifactId>seam-solder</artifactId>
            <version>3.0.0.Beta3</version>
        </dependency>

        <dependency>
            <groupId>org.jboss.seam.faces</groupId>
            <artifactId>seam-faces</artifactId>
            <version>3.0.0.Beta3</version>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>nlog4j</artifactId>
            <version>1.2.25</version>
        </dependency>
        <dependency>
            <groupId>javax</groupId>
            <artifactId>javaee-web-api</artifactId>
            <version>6.0</version>
            <scope>provided</scope>
        </dependency>

        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>3.8.2</version>
            <scope>test</scope>
        </dependency>

    </dependencies>

[mimik789]

From long time there are known issues regarding Glassfish 3.1 and CDI.

see:
http://java.net/jira/browse/GLASSFISH-15721

http://java.net/jira/secure/ViewProfile.jspa?name=sivakumart

and earlier thread:
http://seamframework.org/Community/DeploymentExceptionWithSeamFaces300Beta1

[mimik789]

I forgot to mention:

Seam3 modules:
    <seam-catch.version>3.0.0.Beta1</seam-catch.version>
    <seam-config-xml.version>3.0.0.Beta2</seam-config-xml.version>
    <seam-faces.version>3.0.0.Beta2</seam-faces.version>
    <seam-international.version>3.0.0.Beta1</seam-international.version>
    <seam-mail.version>3.0.0-SNAPSHOT</seam-mail.version>
    <seam-persistence.version>3.0.0.Beta3</seam-persistence.version>
    <seam-security.version>3.0.0.Beta1</seam-security.version>
    <seam-servlet.version>3.0.0.Beta1</seam-servlet.version>
(and probably more current versions)
work for us in war packaged web-app, when impl part (sources) are extracted from jar and placed next to our source code (src\main\java\org\jboss.seam...), so when compiled they'll go into WEB-INF/classes.

You make sure that you provide resources part (merge them, like for: javax.enterprise.inject.spi.Extension) form each module impl jar
(into src\main\resources\META-INF\services\...).

Finally seam modules api jars can be used as usual - ie. maven deps, that will be copied on package to WEB-INF/lib.


more on that in official GF 3.1 workaround:
http://java.net/jira/browse/GLASSFISH-15721?focusedCommentId=301147&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_301147

There is a fix for weld-core that needs to be replaced on gf 3.1 - but in my opinion it's not working. see: https://issues.jboss.org/browse/WELD-846
our experiences with the fix:
http://java.net/jira/secure/ViewProfile.jspa?name=mimik789

[mimik789]

update:
preceding list missing one more but important:
<seam-solder.version>3.0.0.Beta3</seam-solder.version>

ps
there are other issues when using seam-servlet module, which uses TypeSafe loggers from jbooss-logging, so better exclude this module

or if you want it - manually include these two
    <!-- 3.0.0.Beta4 works, currently used by Seam3 -->
    <dependency>
      <groupId>org.jboss.logging</groupId>
      <artifactId>jboss-logging</artifactId>
      <version>3.0.0.Beta5</version>
    </dependency>
   
    <!-- JBoss Logging annotation processor for generating type-safe loggers, 1.0.0.Beta1 used by Seam3 -->
    <dependency>
      <groupId>org.jboss.logging</groupId>
      <artifactId>jboss-logging-tools</artifactId>
      <version>1.0.0.Beta4</version>
      <scope>provided</scope>
      <optional>true</optional>
    </dependency>

and remove package
src\main\java\org\jboss\logging..
from api and impl of seam-solder

There are few more steps to fix (update) logging in seam-solder that I don't remember now, but if someone is interested I can help with that - until it'll be officially fixed/updated by Seam3 team.

[surajchhetry]

Hi Dominik Sadowski,
  Thanks for your response. I will appreciate if you help me to fix this issue. I want to use seam-faces with glassfish but due to some issue with glassfish iam not able to use it. Please tell me essential step for it...

[mimik789]

I think I provided you enough information about how to workaround glassfish 3.1 CDI issues. But you should try first easier approach:
recently user 'rat king' tested newest builds of seam3 modules and gf3.1 b_43 and fount that they just work.
see:
http://seamframework.org/Community/DeploymentExceptionWithSeamFaces300Beta1#comment149532