Libs da Aplicação no JBOSS 7

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

Estou tentando migrar uma aplicação que utiliza JBoss 4 para o JBoss 7.
A aplicação utiliza diversas bibliotecas, .jar pro Jasper, Lucene, etc.

Andei lendo sobre os módulos do novo JBoss e vi que algumas bibliotecas já estão integradas como "módulo", por exemplo API do Apache Commons.
E no caso, bastaria setar no MANIFEST como depedência e pronto.

Até ai deu certo, mas e as Libs que não estão como módulo?
Achei que fosse simplesmente colocar na pasta standalone/deployment/lib mas não deu certo.
Quando subo o server aparece logo um ClassNotFoundException.

Alguém sabe o que precisa fazer para minhas libs que já funcionavam no JBoss anterior funcionar no novo também?

Valeu

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

Resolvi o problema criando meu próprio módulo, com todas as libs que a minha aplicação utiliza.

Entusiasta Java Membro desde: 25/07/2008 14:27:02 Mensagens: 15 Offline

danilowz wrote:Resolvi o problema criando meu próprio módulo, com todas as libs que a minha aplicação utiliza.

Tenho exatamente o mesmo problema que foi descrito no início deste post, porém eu tenho a limitação de não poder cadastrar meus módulos no diretório modules, pois só tenho permissão de leitura.

Alguém conhece alguma forma de carregar os módulos direto do WEB-INF/lib da aplicação?

Obrigado.

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

cara, se você não pode trabalhar como módulo,
acho que só resta pra você colocar as libs no WEB-INF/lib no caso de .war e ear/lib no caso do .EAR
funciona normalmente.
o chato é ficar "replicando" biblioteca se você tiver várias app.

Entusiasta Java Membro desde: 25/07/2008 14:27:02 Mensagens: 15 Offline

danilowz wrote:cara, se você não pode trabalhar como módulo,
acho que só resta pra você colocar as libs no WEB-INF/lib no caso de .war e ear/lib no caso do .EAR
funciona normalmente.
o chato é ficar "replicando" biblioteca se você tiver várias app.

Danilowz, obrigado por responder.

É um projeto war e deixei todos os jars dentro do WEB-INF/lib, como faria com o Tomcat, só que o JBoss AS 7.1, não acha nenhuma classe e não deixa nem fazer o deploy...

Não sei se está faltando algum arquivo de configuração ou coisa do tipo, no Glassfish 3.1.1 o problema é o mesmo.

No link abaixo tem mais detalhes do problema.
http://www.guj.com.br/java/267293-webapp-deploy-jboss-as-71glassfish-311

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

Que erro você está tendo ao deployar?

Bem cara, eu não cheguei a subir um .war, eu subi um .EAR que tinha um .war dentro
No caso eu tinha algumas bibliotecas de core do EAR, e algumas libs de view no .war
rolou sem problemas.

Creio que não deveria ter problemas rodando um .war sozinho, ainda mais que na nova especificação você não precisa mais empacotar um .war pra rodar EJB (por exemplo).
Eu tentaria:

- Subir o .war sozinho, setando no MANIFEST o Class-Path para toda as /libs

se não der, tente empacotar seu .war em um .ear (é estranho funfar assim e não sozinho, mas vale a pena tentar)

Entusiasta Java Membro desde: 25/07/2008 14:27:02 Mensagens: 15 Offline

Esse é o erro na hora do deploy:

14:33:54,797 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found JEE.war in deployment directory. To trigger deployment create a file called JEE.war.dodeploy
14:33:54,797 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "JEE.war"
14:33:55,328 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry WEB-INF/lib/h3.jar in "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war"  does not point to a valid jar for a Class-Path reference.
14:33:55,625 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment JEE.war
14:33:55,844 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
14:33:55,859 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: JEE.war
14:33:55,906 INFO  [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.5 (AS71)
14:33:55,938 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment JEE.war
14:33:56,469 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."JEE.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."JEE.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]
	at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_10]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_10]
	at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_10]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]
	at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
	at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
	at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
	at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
	at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
	at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
	at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
	at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
	at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
	... 5 more

14:33:56,687 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "JEE.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"JEE.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JEE.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]"}}
14:33:56,719 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment JEE.war in 25ms
14:33:56,719 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."JEE.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."JEE.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]

14:33:56,719 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"JEE.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JEE.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]"}}}}

JEE/WebContent/META-INF/MANIFEST.MF está assim:

Classe que está dentro do h3.jar, que o Weld deveria ter enxergado para ser injetada:

package org.testejee.integracao.persistencia.h3.dao.hibernate;

import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.AnnotationConfiguration;

import org.testejee.patterns.Observer;

public class HibernateSessionFactory implements Observer {

protected SessionFactory factory;
	static protected HibernateSessionFactory instance = null;

protected HibernateSessionFactory() {
		criaSessionFactory();
	}

static public HibernateSessionFactory getInstance() {
		if (instance == null)
			instance = new HibernateSessionFactory();

return instance;
	}

private void criaSessionFactory() {
		System.out.println("Instanciando Fábrica de Sessions");

try {
			// configuracao de annotatios
			// instancia da classe Configuration do Hibernate
			AnnotationConfiguration configuration = new AnnotationConfiguration();

// mapeamento das entitidades
			configuration.configure();

// obtem instacia da fabrica do Hibernate
			factory = configuration.buildSessionFactory();

} catch (Throwable e) {
			e.printStackTrace();
			throw new RuntimeException(
					"HIBERNATE - Erro ao criar a fabrica : Sem acesso ao BD ou tabelas diferentes das classes",
					e);

}
	}

public void inicializaPersistencia() {
		HibernateSessionFactory.getInstance();
	}

public void finalizaPersistencia() {
		factory.close();
	}

public Session getHibernateSession() {
		return factory.getCurrentSession();

}
}

A interface que está no projeto Web:

A classe que deveria ter recebido injeção:

package org.testejee.web.controller;

import javax.annotation.PostConstruct;
import javax.enterprise.inject.Produces;
import javax.enterprise.inject.spi.Annotated;
import javax.enterprise.inject.spi.Bean;
import javax.enterprise.inject.spi.InjectionPoint;
import javax.inject.Inject;

import org.testejee.integracao.persistencia.h3.dao.hibernate.HibernateSessionFactory;
import org.testejee.patterns.Observer;

public class GeradorDeApontamentoNegocio {

@Inject
	private Bean bean;
	@Inject
	private Annotated annotated;
	@Inject
	private Observer observer;
	
	@PostConstruct
	private void beans() {
		System.out.println("ok, construiu...");
		
		System.out.println("Tentando instanciar HibernateSessionFactory...");
	}
	
	public void sysout() {
		System.out.println("bean... " + bean);
		System.out.println("annotated... " + annotated);		
		
		System.out.println("observer... " + observer);		
	}
	
	@Produces public Bean carregaBean(InjectionPoint injectionPoint) {
		Bean<?> bean = injectionPoint.getBean();

System.out.println("bean.beanClass " + bean.getBeanClass());
        System.out.println("bean.injectionPoints " + bean.getInjectionPoints());
        System.out.println("bean.name " + bean.getName());
        System.out.println("bean.qualifiers " + bean.getQualifiers());
        System.out.println("bean.scope " + bean.getScope());
        System.out.println("bean.stereotypes " + bean.getStereotypes());
        System.out.println("bean.types " + bean.getTypes());

return bean;
	}
	
	
	@Produces public Annotated carregaAnnoted(InjectionPoint injectionPoint) {
		Annotated annotated = injectionPoint.getAnnotated();
		
		System.out.println("annotated.annotations " + annotated.getAnnotations());
		System.out.println("annotated.annotations " + annotated.getBaseType());
		System.out.println("annotated.typeClosure " + annotated.getTypeClosure());
		
		return annotated;
	}

}

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

cara, existe algum motivo especial para vc instanciar manualmente seu EntityManagerFactory ?

você podia aproveitar que está usando um servidor de aplicação e utilizar o @PersistenceContext ou até mesmo usar o Seam Persistence pra container Web.

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

bem, quanto ao erro.
isso não está parecendo falta de biblioteca do CDI.
se não teria dado pau nos outros dois @Inject também, mas aí diz que só foi no atributo "observer".

o que tá estranho, é esse construtor padrão protected da classe HibernateSessionFactory.
deixa ele público que talvez o CDI não consiga instanciar assim.

Entusiasta Java Membro desde: 25/07/2008 14:27:02 Mensagens: 15 Offline

danilowz wrote:cara, existe algum motivo especial para vc instanciar manualmente seu EntityManagerFactory ?

você podia aproveitar que está usando um servidor de aplicação e utilizar o @PersistenceContext ou até mesmo usar o Seam Persistence pra container Web.

Danilowz, concordo com tudo o que você disse, as implementações não estão como deveriam. Tanto que assim que conseguir superar o problema atual de deploy, a maior parte desse código vai ser refatorado.

Alterei o Manifest para adicionar os outros jars que talvez estejam fazendo falta na implementação concreta do Observador:

Também aumentei o nível de log do JBoss para o máximo:

15:56:00,850 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found JEE.war in deployment directory. To trigger deployment create a file called JEE.war.dodeploy
15:56:00,866 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "JEE.war"
15:56:01,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WEB-INF/lib/h3.jar in "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war"  does not point to a valid jar for a Class-Path reference.
15:56:01,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WEB-INF/lib/commons-collections-3.1.jar in "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war"  does not point to a valid jar for a Class-Path reference.
15:56:01,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WEB-INF/lib/dom4j-1.6.1.jar in "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war"  does not point to a valid jar for a Class-Path reference.
15:56:01,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WEB-INF/lib/hibernate3.jar in "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war"  does not point to a valid jar for a Class-Path reference.
15:56:01,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WEB-INF/lib/mysql-connector-java-5.1.18-bin.jar in "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war"  does not point to a valid jar for a Class-Path reference.
15:56:01,663 DEBUG [org.jboss.weld.deployer] (MSC service thread 1-4) Found beans.xml: "/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/beans.xml"
15:56:01,897 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment JEE.war
15:56:01,959 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
15:56:01,959 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: JEE.war
15:56:02,006 INFO  [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 1.1.5 (AS71)
15:56:02,053 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment JEE.war
15:56:02,178 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000103 Enabled alternatives for Manager
Enabled alternatives: [] []
Registered contexts: [interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.Dependent, interface javax.enterprise.context.ApplicationScoped, interface javax.inject.Singleton, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped]
Registered beans: 0
: [] []
15:56:02,178 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000104 Enabled decorator types for Manager
Enabled alternatives: [] []
Registered contexts: [interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.Dependent, interface javax.enterprise.context.ApplicationScoped, interface javax.inject.Singleton, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped]
Registered beans: 0
: []
15:56:02,194 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000105 Enabled interceptor types for Manager
Enabled alternatives: [] []
Registered contexts: [interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.Dependent, interface javax.enterprise.context.ApplicationScoped, interface javax.inject.Singleton, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped]
Registered beans: 0
: []
15:56:02,194 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000103 Enabled alternatives for Manager
Enabled alternatives: [] []
Registered contexts: [interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.Dependent, interface javax.enterprise.context.ApplicationScoped, interface javax.inject.Singleton, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped]
Registered beans: 0
: [] []
15:56:02,194 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000104 Enabled decorator types for Manager
Enabled alternatives: [] []
Registered contexts: [interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.Dependent, interface javax.enterprise.context.ApplicationScoped, interface javax.inject.Singleton, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped]
Registered beans: 0
: []
15:56:02,209 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000105 Enabled interceptor types for Manager
Enabled alternatives: [] []
Registered contexts: [interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.Dependent, interface javax.enterprise.context.ApplicationScoped, interface javax.inject.Singleton, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped]
Registered beans: 0
: []
15:56:02,444 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.http.HttpRequestContext
15:56:02,444 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Implicit Bean [javax.enterprise.inject.spi.InjectionPoint] with qualifiers [@Default]
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.bound.BoundConversationContext
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.DependentContext
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Implicit Bean [javax.enterprise.inject.Instance] with qualifiers [@Default]
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.ejb.EjbRequestContext
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.http.HttpConversationContext
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [java.security.Principal] with qualifiers [@Default]
15:56:02,459 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.ApplicationContext
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Implicit Bean [javax.enterprise.event.Event] with qualifiers [@Default]
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-javax.enterprise.context.Conversation
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.bound.BoundRequestContext
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.RequestContext
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [javax.validator.ValidatorFactory] with qualifiers [@Default]
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.http.HttpSessionContext
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.SingletonContext
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [javax.validator.Validator] with qualifiers [@Default]
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [javax.transaction.UserTransaction] with qualifiers [@Default]
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-org.jboss.as.weld.deployment.WeldDeployment.additionalClasses-Built-in-org.jboss.weld.context.bound.BoundSessionContext
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-javax.enterprise.context.Conversation
15:56:02,475 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.bound.BoundConversationContext
15:56:02,491 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [javax.validator.Validator] with qualifiers [@Default]
15:56:02,491 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Revisor] with qualifiers [@Any @Default]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Producer Method [Bean<T>] with qualifiers [@Any @Default] declared as [[method] @Produces public org.testejee.web.controller.GeradorDeApontamentoNegocio.carregaBean(InjectionPoint)]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Aplicacao] with qualifiers [@Any @Default]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.web.controller.ApontamentoController] with qualifiers [@Any @Default]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.web.controller.GeradorDeApontamentoNegocio] with qualifiers [@Any @Default]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.RequestContext
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.bound.BoundSessionContext
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Producer Method [Annotated] with qualifiers [@Any @Default] declared as [[method] @Produces public org.testejee.web.controller.GeradorDeApontamentoNegocio.carregaAnnoted(InjectionPoint)]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.bound.BoundRequestContext
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.DependentContext
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [java.security.Principal] with qualifiers [@Default]
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.ApplicationContext
15:56:02,506 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.http.HttpSessionContext
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.http.HttpConversationContext
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Artefato] with qualifiers [@Any @Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Implicit Bean [javax.enterprise.inject.spi.InjectionPoint] with qualifiers [@Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.negocios.ComentarioNegocio] with qualifiers [@Any @Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.web.controller.GeradorDeApontamentoNegocioTest] with qualifiers [@Any @Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [javax.transaction.UserTransaction] with qualifiers [@Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Implicit Bean [javax.enterprise.inject.Instance] with qualifiers [@Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Arquivo] with qualifiers [@Any @Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Comentario] with qualifiers [@Any @Default]
15:56:02,522 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.web.filter.FiltroAplicacao] with qualifiers [@Any @Default]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Implicit Bean [javax.enterprise.event.Event] with qualifiers [@Default]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Built-in Bean [javax.validator.ValidatorFactory] with qualifiers [@Default]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.web.controller.ArquivoController] with qualifiers [@Any @Default @Named]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Demanda] with qualifiers [@Any @Default]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.ejb.EjbRequestContext
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Apontamento] with qualifiers [@Any @Default]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.SingletonContext
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: Managed Bean [class org.testejee.modelo.Pacote] with qualifiers [@Any @Default]
15:56:02,537 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000106 Bean: org.jboss.weld.bean-JEE.war/C:/java/JBOSS/jboss-as-7.1.0.Final/standalone/deployments/JEE.war/WEB-INF/classes-Built-in-org.jboss.weld.context.http.HttpRequestContext
15:56:02,553 DEBUG [org.jboss.weld.Reflection] (MSC service thread 1-2) WELD-000601 interface javax.inject.Named is missing @Target. Weld will use this annotation, however this may make the application unportable.
15:56:02,569 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000100 Weld initialized. Validating beans
15:56:02,584 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."JEE.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."JEE.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]
	at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_10]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_10]
	at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_10]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]
	at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:275)
	at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:244)
	at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:107)
	at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:127)
	at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:346)
	at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:331)
	at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
	at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
	at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
	... 5 more

15:56:02,803 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "JEE.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"JEE.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JEE.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]"}}
15:56:02,834 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment JEE.war in 23ms
15:56:02,834 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."JEE.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."JEE.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]

15:56:02,834 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"JEE.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JEE.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Observer] with qualifiers [@Default] at injection point [[field] @Inject private org.testejee.web.controller.GeradorDeApontamentoNegocio.observer]"}}}}

Mas mesmo com esse nível de log, ainda não tenho pistas de onde está o problema. Talvez seja a falta de algum arquivo xml de configuração exclusivo do JBoss no diretório WEB-INF, pois tenho apenas: beans.xml (vázio), faces-config.xml e o web.xml.

Entusiasta Java Membro desde: 25/07/2008 14:27:02 Mensagens: 15 Offline

danilowz wrote:bem, quanto ao erro.
isso não está parecendo falta de biblioteca do CDI.
se não teria dado pau nos outros dois @Inject também, mas aí diz que só foi no atributo "observer".

o que tá estranho, é esse construtor padrão protected da classe HibernateSessionFactory.
deixa ele público que talvez o CDI não consiga instanciar assim.

Eu também desconfiei disso, e utilizei o JBoss Aquillian Junit (http://www.jboss.org/arquillian) para testar se ele poderia ser injetado desta forma. O teste passa sem nenhum erro:

package org.testejee.web.inject;

import static org.junit.Assert.*;

import java.util.List;

import javax.inject.Inject;

import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.shrinkwrap.api.ArchivePaths;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.JavaArchive;
import org.junit.Test;
import org.junit.runner.RunWith;

import org.testejee.integracao.persistencia.h3.dao.hibernate.HibernateSessionFactory;
import org.testejee.integracao.persistencia.h3.infra.impl.InfraRepositorioApontamentoHibernate;
import org.testejee.modelo.Apontamento;
import org.testejee.patterns.Observer;
import org.testejee.web.controller.ArquivoController;

@RunWith(Arquillian.class)
public class InjecaoDeDepencenciasComArquillianTest {
	
	@Inject
	private Observer observer;

@Deployment
	public static JavaArchive createTestArchive() {
		return ShrinkWrap.create(JavaArchive.class, "test.jar")

.addClasses(
						HibernateSessionFactory.class,)

.addAsManifestResource(

EmptyAsset.INSTANCE,

ArchivePaths.create("beans.xml"));
	}	
	
	@Test
	public void testHibernateSessionFactoryObserver() {
		assertNotNull(observer);
		observer.inicializaPersistencia();
		observer.finalizaPersistencia();
	}
}

Se eu copiar o package com a classe HibernateSessionFactory, dentro da aplicação web, o deploy é feito com sucesso.

danilowz, você pode mostrar a estrutura de como fez seu module?

as pastas e o xml.. só um exemplo.. porque acho que isso pode resolver um problema que estou tendo.

Obrigado

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

thiago-dev

aquelas classes "Bean" e "Annoted" estão no mesmo projeto dessa classe que está dando pau? todas estão no h3.jar?

digaoneves

cria uma estrutura de pastas, ex: /jboss7/modules/br/com/teste/main
dentro da pasta main/, cria um arquivo module.xml com a estrutura:

<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.0" name="br.com.teste">
<resources>
<resource-root path="biblioteca1.jar"/>
<resource-root path="biblioteca2.jar"/>
</resources>
</module>

e ai coloca a biblioteca1.jar e biblioteca2.jar dentro da mesma main/ também junto com o module.xml

para criar o módulo é só isso,
depois quando for utilizar o módulo em algum app.
no META-INF/MANIFEST dessa aplicação deve conter uma linha: "Dependencies: br.com.teste" que é o nome do módulo criado.

Entusiasta Java Membro desde: 25/07/2008 14:27:02 Mensagens: 15 Offline

danilowz wrote:thiago-dev

aquelas classes "Bean" e "Annoted" estão no mesmo projeto dessa classe que está dando pau? todas estão no h3.jar?

digaoneves

cria uma estrutura de pastas, ex: /jboss7/modules/br/com/teste/main
dentro da pasta main/, cria um arquivo module.xml com a estrutura:

<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.0" name="br.com.teste">
<resources>
<resource-root path="biblioteca1.jar"/>
<resource-root path="biblioteca2.jar"/>
</resources>
</module>

e ai coloca a biblioteca1.jar e biblioteca2.jar dentro da mesma main/ também junto com o module.xml

para criar o módulo é só isso,
depois quando for utilizar o módulo em algum app.
no META-INF/MANIFEST dessa aplicação deve conter uma linha: "Dependencies: br.com.teste" que é o nome do módulo criado.

Não, elas pertencem ao container JEE dentro do package javax.enterprise.inject.spi.

É uma pena eu não ter permissão de escrita nessa pasta modules, ai o problema já estaria resolvido...

JavaBaby Membro desde: 08/10/2009 17:12:03 Mensagens: 75 Offline

thiago-dev

engraçado, a classe injetada no mesmo projeto rola?

cara, não quer tentar empacotar seu .war num .EAR ?
pega esse projeto h3.jar e transforma em módulo tbm.

eles estando no mesmo .EAR funciona perfeitamente, pq isso já cheguei a fazer, tudo bem que era um módulo EJB, mas pelo menos pra tentar descobrir o erro você podia ver se funciona ai também.

outra coisa que tive que fazer, é criar um META-INF/beans.xml dentro do módulo EJB tbm.
não sei o porquê mas não tava rolando se não tivesse o beans.xml nos dois módulos.

Notícias, artigos e o maior fórum brasileiro sobre Java