-
1. Re: Seam Faces 3.0.0Beta1 on Glassfish 3.0.1
kernstock Nov 30, 2010 12:05 PM (in response to kernstock)I managed to include myFaces CODI and got the needed @ViewScope now. Nevertheless I would like to use some Seam 3 Modules/Features too, but can't manage to deploy them on Glassfish V3.0.1.
This is Easy to reproduce:
I used Eclipse Helios and the m2Plugin to
1) create a new Mavenproject - ArtefactID: weld-jsf-jee-minimal 1.0.0.-BETA1 and deployed and ran it without problems to on my Glassfish installation.
2) I added the Seam3 Faces dependency to my pom:<dependency> <groupId>org.jboss.seam.faces</groupId> <artifactId>seam-faces</artifactId> <version>3.0.0.Beta1</version> </dependency>
3) I created a lib directory in WEB-INF and copied jboss-logging-3.0.0.Beta4.jar, slf4j-api-1.5.10.jar, slf4j-simple-1.5.10.jar from my local maven repositiory because I couldn't manage to add the dependecies to my pom - . (I'm neither a maven specialist nor a maven friend)
4) I deploy the project and get the folloing error:SCHWERWIEGEND: Exception while loading the app org.glassfish.deployment.common.DeploymentException: WELD-001408 Injection point has unsatisfied dependencies. Injection point: field org.jboss.weld.extensions.resourceLoader.ResourceProducer.resourceLoaderManager; Qualifiers: [@javax.enterprise.inject.Default()] at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:181) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125) at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:239) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:339) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) at java.lang.Thread.run(Thread.java:619) Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Injection point has unsatisfied dependencies. Injection point: field org.jboss.weld.extensions.resourceLoader.ResourceProducer.resourceLoaderManager; Qualifiers: [@javax.enterprise.inject.Default()] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:276) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:122) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:141) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:331) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:317) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:399) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:178) ... 30 more
Do I miss something here or is it simply a bug ?
Has anybody already deployed Seam 3 Faces to a Glassfish server ?Thanx
Thomas
-
2. Re: Seam Faces 3.0.0Beta1 on Glassfish 3.0.1
mimik789 Dec 6, 2010 9:45 AM (in response to kernstock)You neeed GlassFish 3.1 (which uses newer CDI implementation - Weld 1.1.0.Beta2
please read top note: http://seamframework.org/Seam3/FacesModule
Note: This project requires CDI/Weld version 1.1.0 (GlassFish 3.1, JBoss 6, JBoss 7) and JBoss-Logging 3.0.0.Beta4 or higher.but probably you'll run into truble because of not working weld-extensions (Seam Solder) on Glassfish 3.1 (tested on b30)
see:
http://seamframework.org/Community/DeploymentExceptionWithSeamFaces300Beta1
jira @ Glassfish
http://java.net/jira/browse/GLASSFISH-14808
jira @ Seam Solder
https://jira.jboss.org/browse/SOLDER-47as workaround
try deploying on Jboss AS CR1