2014-11-11 15 views
8

questo è il mio jboss-deployment-structure.xml del progetto EAR.jboss-deployment-structure.xml non carica le dipendenze nel mio progetto EAR

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

<jboss-deployment-structure > 

<deployment> 

    <dependencies> 
     <module name="org.javassist" export="true" /> 
     <module name="org.apache" export="true"/> 
     <module name="org.antlr" export="true"/> 
     <module name="org.dom4j" export="true"/> 
     <module name="org.apache" export="true"/> 
     <module name="org.hibernate" export="true"/> 

    </dependencies> 

</deployment> 


</jboss-deployment-structure> 

e il progetto EAR hanno i miei altri progetti nel percorso di distribuzione. alcuni sono JARS e uno è WAR. e il mio uno di Project utilizza le dipendenze nella lib del progetto EAR. ora sto rimuovendo i jar dalla cartella lib e aggiunto sopra jboss-deployment-structure.xml. Immagino che i barattoli non vengano caricati e dia l'errore di non trovare i barattoli necessari. questo è lo StackTrace

08:54:05,555 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SBOS_Online].[resteasy-servlet]] (http--0.0.0.0-8080-1) Servlet.service() for servlet resteasy-servlet threw exception: org.jboss.resteasy.spi.UnhandledException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userBusinessImpl' defined in class path resource [config/applicationContext.xml]: Cannot resolve reference to bean 'userHibernateDAOImpl' while setting bean property 'userDAO'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userHibernateDAOImpl' defined in class path resource [config/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.scs.sbos.dao.hibernate.impl.UserHibernateDAOImpl]: Constructor threw exception; nested exception is java.lang.Error: Unresolved compilation problems: 
The import org.hibernate.Query cannot be resolved 
The import org.hibernate.Session cannot be resolved 
The import org.hibernate.SessionFactory cannot be resolved 
The import org.hibernate.Transaction cannot be resolved 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
Transaction cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
Transaction cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
Transaction cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Query cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Query cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Query cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Session cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
Query cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
SessionFactory cannot be resolved to a type 
SessionFactory cannot be resolved to a type 

at  org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:340) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:540) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.2.Final.jar:] 
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.2.Final.jar:] 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] 
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] 
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] 
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] 
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] 

Significa non vengono aggiunti vasetti Hibernate, ma perché questo è il problema.

risposta

15

Un jboss-deployment-structure.xml deve essere definito all'interno della distribuzione di primo livello. Cioè, se stai distribuendo direttamente un file WAR, potrebbe contenere un descrittore. Se si configura WAR in un file EAR, è necessario spostare il contenuto del descrittore e definirlo all'interno di jboss-deployment-structure.xml del file EAR.

Hai bisogno di andare con un sub-distribuzione:

<jboss-deployment-structure> 
    <sub-deployment name="myapp.war"> 
     <dependencies> 
     <module name="org.javassist" export="true" /> 
     <module name="org.apache" export="true"/> 
     <module name="org.antlr" export="true"/> 
     <module name="org.dom4j" export="true"/> 
     <module name="org.apache" export="true"/> 
     <module name="org.hibernate" export="true"/> 
     </dependencies> 
    </sub-deployment> 
</jboss-deployment-structure> 

C'è una buona descrizione di on the JBoss Docs

+0

grazie per il rply. sì, l'ho letto anche io. ma il problema è che tutte quelle dipendenze sono usate dal mio unico Progetto che è un "JAR" e quando lo distribuisco dà errore. guarda la traccia plz. Ho modificato la domanda –

+0

In questo modo di specificare le dipendenze JAR possiamo specificare anche la versione? –

1

Si dovrebbe aggiungere le dipendenze Moudle nel file MANIFEST.MF sotto distribuzioni tag del file jar . Questo dovrebbe funzionare bene.

+0

Un paio di problemi che ho con manifest.mf. Inizia rapidamente a essere difficile da leggere se ci sono troppe voci. Il numero di caratteri è limitato. – Koekiebox