JavaEE and Eclipse: Setting up JPA with EAR (EJB JBA WAR) - eclipse

I am trying to create an Java Enterprise Application using Eclipse IDE with JBoss 7.0 Server. I already had experience developing such applications but using NetBeans IDE. The main problem for me are the differences between these two IDEs. Currently, Eclipse's giving me headaches about adding JPA to EAR.
I already configured Enterprise Application (EAR) that has two containers:
-- EJB
-- WAR
Those two are configured to work together (Java Build Paths, Manifest and Deployment assembly are set for those two) so when I run EAR on the server it all works properly.
Problem:
The next thing I would like to configure is JPA. I want to add JPA container to my EAR and so I did. I've created JPA 2.1 (with EclipseLink 2.5.x and MySQL), added to EAR, I've add the changes to EJB project (right click on project->properties->deployment assembly->add jpa project).
After this point when I try to run EAR again I got HTTP Status 404 - The requested resource (/eLearningJJ-war/) is not available and my stacktrace looks like as down bellow.
Punch line
I wonder do I have to configure something extra in order to avoid this error after adding JPA to my EAR project.
If you need more details about the project please let me know,
Thank you.
Console
18:51:41,833 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA
18:51:42,224 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
18:51:42,280 INFO [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting
18:51:43,186 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
18:51:43,202 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
18:51:43,202 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
18:51:43,217 INFO [org.jboss.as.logging] Removing bootstrap log handlers
18:51:43,233 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
18:51:43,280 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
18:51:43,452 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
18:51:43,468 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
18:51:43,468 INFO [org.jboss.as.naming] (MSC service thread 1-6) Starting Naming Service
18:51:43,530 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
18:51:43,546 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
18:51:43,561 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
18:51:43,593 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
18:51:43,999 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.8.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\MinGW\bin;C:\msys\1.0\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;.
18:51:43,999 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
18:51:44,452 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /127.0.0.1:9999
18:51:44,585 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-6) Starting remote JMX connector
18:51:44,675 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
18:51:44,847 INFO [org.jboss.as.connector] (MSC service thread 1-6) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
18:51:44,907 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:jboss/datasources/ExampleDS]
18:51:44,927 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory C:\Users\Milan\jboss-as-7.0.1.Final\standalone\deployments
18:51:44,975 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 3626ms - Started 93 of 148 services (55 services are passive or on-demand)
18:51:45,022 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found eLearningJJ-ear.ear in deployment directory. To trigger deployment create a file called eLearningJJ-ear.ear.dodeploy
18:51:45,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "eLearningJJ-ear.ear"
18:51:45,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "eLearningJJ-war.war"
18:51:45,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "eLearningJJ-ejb.jar"
18:51:45,897 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry in "/C:/Users/Milan/jboss-as-7.0.1.Final/standalone/deployments/eLearningJJ-ear.ear/lib/testjpa.jar" does not point to a valid jar for a Class-Path reference.
18:51:46,101 INFO [org.jboss.jpa] (MSC service thread 1-3) read persistence.xml for testjpa
18:51:46,458 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-4) Encountered invalid class name "com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor" for service type "com.sun.faces.spi.injectionprovider"
18:51:46,459 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-4) Encountered invalid class name "com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection" for service type "com.sun.faces.spi.injectionprovider"
18:51:46,526 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-ear.ear
18:51:46,528 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)
18:51:46,528 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added org.hibernate dependency to application deployment
18:51:46,533 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-ejb.jar
18:51:46,533 INFO [org.jboss.as.jpa] (MSC service thread 1-7) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-war.war
18:51:46,704 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named UserTest in deployment unit subdeployment "eLearningJJ-ejb.jar" of deployment "eLearningJJ-ear.ear" are as follows:
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserTest!com.test.UserTest
java:app/eLearningJJ-ejb/UserTest!com.test.UserTest
java:module/UserTest!com.test.UserTest
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserTest!com.test.UserTestLocal
java:app/eLearningJJ-ejb/UserTest!com.test.UserTestLocal
java:module/UserTest!com.test.UserTestLocal
18:51:46,704 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named UserStateless in deployment unit subdeployment "eLearningJJ-ejb.jar" of deployment "eLearningJJ-ear.ear" are as follows:
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:app/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:module/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStateless
java:app/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStateless
java:module/UserStateless!com.elearningjj.beans.UserStateless
18:51:48,392 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:51:48,399 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:51:48,712 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.0.4 (FCS b09-jbossorg-4) for context '/eLearningJJ-war'
18:51:53,821 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /eLearningJJ-war
18:51:54,055 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "eLearningJJ-ear.ear" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"eLearningJJ-ear.ear#testjpa\" missing [ jboss.data-source.java:/ ]"]}
18:51:54,180 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment eLearningJJ-ejb.jar in 131ms
18:51:54,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment eLearningJJ-war.war in 140ms
18:51:54,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment eLearningJJ-ear.ear in 144ms
18:51:54,195 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"eLearningJJ-ear.ear#testjpa\" missing [ jboss.data-source.java:/ ]"]}}}
Solution
The main problem was improperly configured JPA's persistance.xml file. In my case, concrete problem was related to the jta-data-source which wasn't properly configured.
The solution for this is checking the JBoss Administration Console for more details about Datasource Configurations, Registered Datasources, etc. Regarding to this source of information, my persistance.xml file looks like down bellow:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
<persistence-unit name="eLearningJJ-jpa">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>
<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.HSQLDialect"/>
<property name="hibernate.hbm2ddl.auto" value="create-drop"/>
</properties>
</persistence-unit>
</persistence>

Related

Deploy failed - missing depedencies When i am using annotations

i am not so familiar with ejb. I had hard time to set up realm authorization at wildfly, (13) all the time i had same error:
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
After this i have removed #Singleton Annotation from "ProgrammaticScheduler" and with out it my realm authentication works well. But than my scheduler doesnt work at all. When i remove lane with
exampleApplicationDomain
Scheduler works, realm doesnt. Where is the point? This two componenst dont have any common classes.. (well.. i dont know about any). Any one have some ideas? I have seen many familiar problems here but almost all of them were about missing or wrong line in standalone.xml.
Ps. I had another class with #stateless annotation and this class was in error too, but i didnt need it and jsut removed it. Full error log, standalone, jboss-web.xml below. Hope some will find solution
standalone.xml
<security-domains>
<security-domain name="ApplicationDomain" default-realm="ApplicationRealm" permission-mapper="default-permission-mapper">
<realm name="ApplicationRealm" role-decoder="groups-to-roles"/>
<realm name="local"/>
</security-domain>
<security-domain name="ManagementDomain" default-realm="ManagementRealm" permission-mapper="default-permission-mapper">
<realm name="ManagementRealm" role-decoder="groups-to-roles"/>
<realm name="local" role-mapper="super-user-mapper"/>
</security-domain>
<security-domain name="jdbcdomain" default-realm="jdbcRealm">
<realm name="jdbcRealm"/>
</security-domain>
<security-domain name="exampleDbSD" default-realm="exampleDbRealm" permission-mapper="default-permission-mapper">
<realm name="exampleDbRealm" role-decoder="groups-to-roles"/>
</security-domain>
</security-domains>
ProgrammaticScheduler
#Singleton
public class ProgrammaticScheduler {
#Schedule(hour="20", minute="33")
public void removeExpiredSearches() throws IOException{
System.out.println("Kick off!");
}
#Timeout()
public void onTimeout(Timer timer){
}
}
Error log
20:33:34,908 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
20:33:36,349 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
20:33:36,373 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
20:33:36,662 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) starting
20:33:40,940 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
20:33:41,000 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
20:33:41,004 INFO [org.wildfly.security] (ServerService Thread Pool -- 7) ELY00001: WildFly Elytron version 1.3.3.Final
20:33:41,220 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found RaportGeneratorEE-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called RaportGeneratorEE-0.0.1-SNAPSHOT.war.dodeploy
20:33:41,324 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
20:33:41,409 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.6.3.Final
20:33:41,421 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.6.3.Final
20:33:41,674 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem
20:33:41,683 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension
20:33:41,666 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
20:33:41,677 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 47) WFLYRS0016: RESTEasy version 3.5.1.Final
20:33:41,682 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.2.Final
20:33:41,705 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
20:33:41,718 INFO [org.jboss.as.ee] (ServerService Thread Pool -- 41) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
20:33:41,737 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 45) WFLYCLINF0001: Activating Infinispan subsystem.
20:33:41,743 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem
20:33:41,818 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.9.Final starting
20:33:41,863 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
20:33:41,885 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
20:33:41,932 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
20:33:42,046 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
20:33:42,056 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
20:33:42,419 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path 'C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
20:33:42,886 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 46) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
20:33:42,904 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
20:33:42,913 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
20:33:43,056 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.7.Final
20:33:43,060 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
20:33:43,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
20:33:43,112 INFO [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
20:33:43,226 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
20:33:43,236 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\deployments
20:33:43,265 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "mysql" (runtime-name: "mysql-connector-java-5.1.44-bin.jar")
20:33:43,271 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name: "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:43,301 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
20:33:43,345 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
20:33:44,142 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
20:33:44,619 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
20:33:44,801 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.1.Final (Apache CXF 3.2.4.jbossorg-1)
20:33:45,530 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:45,536 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:45,705 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:45,706 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
20:33:45,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/MysqlXADS]
20:33:45,745 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/examplePostgresDS]
20:33:47,033 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Gaina' 9.2.4.Final
20:33:48,039 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
20:33:52,002 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry serializer.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:53,000 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment RaportGeneratorEE-0.0.1-SNAPSHOT.war
20:33:53,923 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
20:33:54,036 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'ProgrammaticScheduler' in deployment unit 'deployment "RaportGeneratorEE-0.0.1-SNAPSHOT.war"' are as follows:
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:module/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
ejb:RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:module/ProgrammaticScheduler
20:33:54,485 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:54,490 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:54,500 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
20:33:54,539 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.0.4 (Final)
20:33:54,721 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:54,722 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.jdbc.Driver_5_1
20:33:54,724 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.cj.jdbc.Driver_8_0
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
20:33:55,057 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "mysql" (runtime-name : "mysql-connector-java-5.1.44-bin.jar")
20:33:55,058 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name : "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:55,064 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.security.security-domain.exampleApplicationDomain (missing) dependents: [service jboss.deployment.unit."RaportGeneratorEE-0.0.1-SNAPSHOT.war".component.ProgrammaticScheduler.CREATE]
WFLYCTL0448: 225 additional services are down due to their dependencies being missing or failed
There is need to add aplication-security-domain (using security-domain) in ejb3 services:
subsystem=ejb3/application-security-domain=exampleApplicationDomain:add(security-domain=exampleDbSD)

JBOSS EAP7 and eclipse, HTTP 403 Forbidden::The website declined to show this webpage

I am new to JBOSS EAP and trying to run a basic web application on this.Below is the process I did:
Downloaded and installed JBOSS EAP 7
Downloaded Eclipse mars.
Downloaded jdk 1.8
JAVA_HOME set in the env variable and java path variable set.
Open eclipse
Configuration JBOSS EAP server in eclipse
a. Define a new Server
b. Select Red Hat JBoss Enterprise Application Platform 7.x
Server's host name = localhost
Server Name = Red Hat JBoss EAP 7.x
c.Clicked on next button and finish.
7.Right click and started the server ( server started successfully).
I am able to open (http://localhost:8080/), without any issue.
Creating Web Application in eclipse
a. Open New Project => Dynamic web Project
b. Project name given : HelloApp
c. I didn't select checkbox for "Generate web.xml deployment descriptor".
d. Create new HTML file (Index.html), inside HelloApp/WebContent folder
e. Added Hello in the body part of the HTML.
Running HelloApp Project.
a. Right Click and select run as sever
b. Select Red Hat JBoss EAP 7.x
c. Adding HelloApp to configured tab.
d. Finish button
Below is the jboss logs:
13:29:11,462 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
13:29:11,887 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
13:29:12,019 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) starting
13:29:14,178 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found MyWebApp.war in deployment directory. To trigger deployment create a file called MyWebApp.war.dodeploy
13:29:14,246 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
13:29:14,326 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
13:29:14,343 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
13:29:14,410 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
13:29:14,419 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
13:29:14,434 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
13:29:14,434 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
13:29:14,438 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
13:29:14,446 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
13:29:14,456 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
13:29:14,504 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=4.9.6.Final-redhat-1
13:29:14,551 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:29:14,687 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final-redhat-1)
13:29:14,690 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final-redhat-1 starting
13:29:14,694 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.21.Final-redhat-1 starting
13:29:14,710 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
13:29:14,779 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
13:29:14,783 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
13:29:15,030 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\Users\AVIKUMAR\JBOSS-EAP-7.0.0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
13:29:15,181 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
13:29:15,184 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
13:29:15,489 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
13:29:15,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
13:29:15,500 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.18.Final-redhat-1
13:29:15,588 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
13:29:15,729 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\AVIKUMAR\JBOSS-EAP-7.0.0\standalone\deployments
13:29:15,861 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "MyWebApp.war" (runtime-name: "MyWebApp.war")
13:29:16,247 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
13:29:16,250 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
13:29:16,463 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
13:29:17,751 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: /MyWebApp
13:29:17,798 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "MyWebApp.war" (runtime-name : "MyWebApp.war")
13:29:18,056 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
13:29:18,056 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
13:29:18,057 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started in 7216ms - Started 336 of 627 services (382 services are lazy, passive or on-demand)
19:36:12,928 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found HelloApp.war in deployment directory. To trigger deployment create a file called HelloApp.war.dodeploy
19:36:12,953 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "HelloApp.war" (runtime-name: "HelloApp.war")
19:36:13,048 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0021: Registered web context: /HelloApp
19:36:13,134 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "HelloApp.war" (runtime-name : "HelloApp.war")
In the eclipse browser getting below error
The website declined to show this webpage.
More information
This error (HTTP 403 Forbidden) means that this program was able to connect to the website, but it does not have permission to view the webpage.
See the quickstart example below follow step by step process:
http://www.jboss.org/quickstarts/eap/helloworld/

Why JBoss doesn't deploy first artefact by IDEA

My problem is that from time to time JBoss doesn't want deploy 1st artifact (ear) on the list, but after restarting or redeploying all is OK.
This problem happens not only with my machine, so maybe someone knows cause of this? It takes time to redeploy all my artifacts because IDEA sometimes don't want to deploy only one and begins to make whole project without maven.
P.S. It seems like problem with IDEA deployment tool - I got this string in console
...
Detected server admin port: 9999
Artifact int-bus-nsi-service-ear:ear: Server is not connected. Deploy is not available.
Detected server http port: 8080
Artifact int-bus-ppa-service-ear:ear: Server is not connected. Deploy is not available.
Artifact nsi-rest:war: Server is not connected. Deploy is not available.
Artifact ppa-rest:war: Server is not connected. Deploy is not available.
Artifact ppa-service-ear:ear: Server is not connected. Deploy is not available.
Artifact nsi-service-ear:ear: Server is not connected. Deploy is not available.
Connected to the target VM, address: '127.0.0.1:35251', transport: 'socket'
INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
...
Then deployment starts...
...
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "eventjournal.war" (runtime-name: "eventjournal.war")
INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "int-bus-nsi-service-ear.ear" (runtime-name: "int-bus-nsi-service-ear.ear")
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/hcsebds]
...
After binding to data sources:
...
INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment int-bus-nsi-service-impl.jar
INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named NsiFacade in deployment unit subdeployment "int-bus-nsi-service-impl.jar" of deployment "int-bus-nsi-service-ear.ear" are as follows:
java:global/int-bus-nsi-service-ear/int-bus-nsi-service-impl/NsiFacade!ru.lanit.hcs.intbus.nsi.api.NsiFacade
java:app/int-bus-nsi-service-impl/NsiFacade!ru.lanit.hcs.intbus.nsi.api.NsiFacade
java:module/NsiFacade!ru.lanit.hcs.intbus.nsi.api.NsiFacade
...
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("add") failed - address: ([("deployment" => "int-bus-nsi-service-ear.ear")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"int-bus-nsi-service-ear.ear\")]"
INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016009: Stopping weld service for deployment int-bus-nsi-service-ear.ear
INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment null (runtime-name: int-bus-nsi-service-impl.jar) in 592ms
INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) started (with errors) in 71396ms - Started 4397 of 4548 services (19 services failed or missing dependencies, 103 services are passive or on-demand)
INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment int-bus-nsi-service-ear.ear (runtime-name: int-bus-nsi-service-ear.ear) in 1250ms
INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018558: Undeployed "int-bus-nsi-service-ear.ear" (runtime-name: "int-bus-nsi-service-ear.ear")
INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment int-bus-ppa-service-ear.ear
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: int-bus-ppa-service-impl.jar) in 126ms
Artifact int-bus-nsi-service-ear:ear: Error during artifact deployment. See server log for details.
Artifact int-bus-nsi-service-ear:ear: java.lang.Exception: JBAS014803: Duplicate resource [("deployment" => "int-bus-nsi-service-ear.ear")]
...

JBoss startup warning : MSC service thread ... Invalid class name

I want to get rid of the WARN messages in the following JBoss console output.
08:46:53,653 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "IodLogin.war"
08:46:53,670 INFO [org.jboss.as.remoting] (MSC service thread 1-12) JBAS017100: Listening on 127.0.0.1:9999
08:46:53,670 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
08:46:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
08:46:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
08:46:54,596 INFO [org.jboss.weld.deployer] (MSC service thread 1-15) JBAS016002: Processing weld deployment IodLogin.war
08:46:54,815 INFO [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS016005: Starting Services for CDI deployment: IodLogin.war
08:46:54,858 INFO [org.jboss.weld.Version] (MSC service thread 1-10) WELD-000900 1.1.10 (redhat)
08:46:54,901 INFO [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.IodLogin.war:main" from Service Module Loader
08:46:54,904 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016008: Starting weld service for deployment IodLogin.war
08:46:55,269 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-13) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
08:46:55,327 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Initializing Mojarra 2.1.13-jbossorg-1 20121010-0442 for context '/IodLogin'
08:46:55,933 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-13) Hibernate Validator 4.2.0.Final-redhat-2
08:46:56,281 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Monitoring jndi:/default-host/IodLogin/WEB-INF/faces-config.xml for modifications
This is "just" a warning message, and I doubt it has any direct negative effect, but I try to avoid warning messages that might distract me and others from a warning that shouldn't be ignored -- the "Boy who cried 'Wolf'" parable.
I'm not using Tomcat or Jetty, but it looks like some configuration file or code is referring to classes specific to those environments. I've verified that none of the XML files refer to them directly.
I'm running JBoss EAP 6.0.1.GA. So far, this JSF 2.0 application is pretty simple -- just one page and a few classes. I'm using Eclipse, without Maven. Elsewhere on SO, I found a reference to org.jboss.shrinkwrap, but I don't see how that applies to my situation.
Update: My question is along the line of "how do I make this symptom of a non-problem go away so it doesn't mask a real problem". I'm not looking for a mistake in my code, just an improvement in the configuration.
Any suggestions about where I should look?

How to start JBoss AS 7?

I run the standalone.bat
I encounter a page 404 error when accessing
http://127.0.0.1:8080/
May i know what is wrong?
Below is the server startup logs
Config file not found C:\software\JBoss\bin\standalone.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\software\JBoss
JAVA: C:\Program Files\Java\jdk1.6.0_25\bin\java
JAVA_OPTS: -Dprogram.name=standalone.bat -server
===============================================================================
20:10:34,077 INFO [org.jboss.modules] JBoss Modules version 1.0.0.Beta17
20:10:34,406 INFO [org.jboss.msc] JBoss MSC version 1.0.0.Beta8
20:10:34,468 INFO [org.jboss.as] JBoss AS 7.0.0.Beta3 "Salyut" starting
20:10:35,296 INFO [org.jboss.as.server] Activating core services
20:10:35,468 INFO [org.jboss.as] creating native management service using netwo
rk interface (default) port (9999)
20:10:35,484 INFO [org.jboss.as] creating http management service using network
interface (default) port (9990)
20:10:35,499 INFO [org.jboss.as.arquillian] Activating Arquillian Subsystem
20:10:35,515 INFO [org.jboss.as.ee] Activating EE subsystem
20:10:35,577 INFO [org.jboss.as.naming] Activating Naming Subsystem
20:10:35,781 INFO [org.jboss.as.connector.subsystems.datasources] Deploying JDB
C-compliant driver class org.h2.Driver (version 1.2)
20:10:35,796 INFO [org.jboss.as.osgi] Activating OSGi Subsystem
20:10:36,202 INFO [org.jboss.as.webservices] Activating WebServices Extension
20:10:36,468 INFO [org.jboss.as.logging] Removing bootstrap log handlers
20:10:36,468 INFO [org.jboss.as.naming] Starting Naming Service
20:10:36,484 INFO [org.jboss.as.deployment] (MSC service thread 1-3) Started Fi
leSystemDeploymentService for directory C:\software\JBoss\standalone\deployments
20:10:36,499 INFO [org.jboss.wsf.common.management.AbstractServerConfig] (MSC s
ervice thread 1-4) JBoss Web Services - Stack CXF Server 4.0.0.Alpha4
20:10:36,531 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting
version 3.1.0.Beta2
20:10:36,593 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-
1) Starting remote JMX connector
20:10:36,593 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service
thread 1-3) The Apache Tomcat Native library which allows optimal performance in
production environments was not found on the java.library.path: C:\Program File
s\Java\jdk1.6.0_25\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Tortois
eSVN\bin
20:10:36,609 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC ser
vice thread 1-3) Unable to set the URLStreamHandlerFactory
20:10:36,609 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC ser
vice thread 1-3) Unable to set the ContentHandlerFactory
20:10:36,749 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service
thread 1-2) live server is starting..
20:10:36,765 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-3) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
20:10:36,984 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JC
A Subsystem (JBoss IronJacamar 1.0.0.Beta5)
20:10:37,015 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-3) Bound JDBC Data-source [java:/H2DS]
20:10:37,124 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC ser
vice thread 1-2) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445
for CORE protocol
20:10:37,140 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC ser
vice thread 1-2) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455
for CORE protocol
20:10:37,140 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service
thread 1-2) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
20:10:37,218 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta3
"Salyut" started in 3391ms - Started 100 of 147 services (47 services are passiv
e or on-demand)
In the alphas and betas of JBoss 7 there were no welcome page deployed. There are and will be in the final release.
To get a page there simply deploy a war named ROOT.war or a war with / as its context root.
I suppose that there is no web application that can be executed.
You can connect to console using these address: http://localhost:9990/console/.
There's simply no default web page there. Try deploying your web app and accessing it.