I tried 2 ways as per your recommendation
1st Approach:-
1.) Standalone.xml as
<datasource jndi-name="java:jboss/datasources/Oracle_LPBridge_DS" pool-name="Oracle_LPBridge_DS" enabled="true" use-java-context="true">
<connection-url>jdbc:oracle:thin:@xx.xx.xx.xx:1233:dsdsds1</connection-url>
<driver>oracle</driver>
<security>
<user-name>xxxx</user-name>
<password>xxxxxxxxxxx</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"></valid-connection-checker>
<stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"></stale-connection-checker>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"></exception-sorter>
</validation>
</datasource>
2.)jboss-web.xml
<jboss-web>
<resource-ref>
<description>DB Connection</description>
<res-ref-name>CARMADS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:jboss/datasources/Oracle_LPBridge_DS</jndi-name>
<res-auth>Container</res-auth>
</resource-ref>
</jboss-web>
3.) web.xml
<resource-ref>
<res-ref-name>CARMADS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
4.)
applicationContext.xml
<jee:jndi-lookup id="dataSourcelpbridge" jndi-name="CARMADS"/>
Exception Logs :-
12:28:05,481 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
12:28:05,809 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
12:28:05,908 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
12:28:08,080 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found chaplin-boilerplate-master.war in deployment directory. To trigger deployment create a file called chaplin-boilerplate-master.war.dodeploy
12:28:08,081 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found bridge.war in deployment directory. To trigger deployment create a file called bridge.war.dodeploy
12:28:08,113 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1
12:28:08,115 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:28:08,119 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
12:28:08,127 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.18.GA-redhat-1
12:28:08,172 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
12:28:08,197 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
12:28:08,234 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
12:28:08,251 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
12:28:08,275 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013170: Current PicketBox version=4.0.19.SP2-redhat-1
12:28:08,327 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
12:28:08,371 INFO [org.jboss.as.connector.logging] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.23.Final-redhat-1)
12:28:08,414 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
12:28:08,422 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:28:08,808 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 10.2)
12:28:08,967 INFO [org.apache.coyote.http11] (MSC service thread 1-3) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
12:28:08,978 INFO [org.apache.coyote.http11] (MSC service thread 1-3) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
12:28:09,078 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "chaplin-boilerplate-master.war" (runtime-name: "chaplin-boilerplate-master.war")
12:28:09,081 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "bridge.war" (runtime-name: "bridge.war")
12:28:09,082 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\502312813\Documents\LP Bridge\Installables\jboss-eap-6.2.0.1\jboss-eap-6.2\standalone\deployments
12:28:09,130 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
12:28:09,134 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:4447
12:28:09,469 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final-redhat-1
12:28:09,491 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/Oracle_LPBridge_DS]
12:28:15,361 WARN [org.jboss.as.ee] (MSC service thread 1-8) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
12:28:15,364 WARN [org.jboss.as.ee] (MSC service thread 1-8) JBAS011006: Not installing optional component org.eclipse.jetty.continuation.Servlet3Continuation$1 due to an exception (enable DEBUG log level to see the cause)
12:28:15,364 WARN [org.jboss.as.ee] (MSC service thread 1-8) JBAS011006: Not installing optional component org.eclipse.jetty.continuation.Servlet3Continuation$2 due to an exception (enable DEBUG log level to see the cause)
12:28:15,437 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
12:28:15,495 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /bridge
12:28:15,520 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) No Spring WebApplicationInitializer types detected on classpath
12:28:15,541 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) Initializing Spring root WebApplicationContext
12:28:19,500 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) JBWEB000287: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSourcelpbridge': Invocation of init method failed; nested exception is javax.naming.NameNotFoundException; remaining name 'CARMADS'
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1488) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:524) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:461) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:608) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:389) [spring-web-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294) [spring-web-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) [spring-web-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_55]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: javax.naming.NameNotFoundException; remaining name 'CARMADS'
at org.eclipse.jetty.jndi.local.localContextRoot.lookup(localContextRoot.java:432) [jetty-jndi-8.1.14.v20131031.jar:8.1.14.v20131031]
at org.eclipse.jetty.jndi.local.localContextRoot.lookup(localContextRoot.java:536) [jetty-jndi-8.1.14.v20131031.jar:8.1.14.v20131031]
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_55]
at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:104) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:201) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:187) [spring-context-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1547) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1485) [spring-beans-3.2.2.RELEASE.jar:3.2.2.RELEASE]
... 23 more
12:28:19,506 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) Set web app root system property: 'webapp.root' = [C:\Users\502312813\Documents\LP Bridge\Installables\jboss-eap-6.2.0.1\jboss-eap-6.2\standalone\deployments\bridge.war\]
12:28:19,508 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) Set web app root system property: 'webapp.root' = [C:\Users\502312813\Documents\LP Bridge\Installables\jboss-eap-6.2.0.1\jboss-eap-6.2\standalone\deployments\bridge.war\]
12:28:19,509 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) Initializing log4j from [classpath:log4j.properties]
12:28:19,597 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 65) JBWEB001103: Error detected during context /bridge start, will stop it
12:28:19,612 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) Shutting down log4j
12:28:19,613 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/bridge]] (ServerService Thread Pool -- 65) Closing Spring root WebApplicationContext
12:28:19,620 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 65) MSC000001: Failed to start service jboss.web.deployment.default-host./bridge: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./bridge: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_55]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161)
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60)
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93)
... 6 more
12:28:20,085 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "chaplin-boilerplate-master.war" (runtime-name : "chaplin-boilerplate-master.war")
12:28:20,086 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "bridge.war" (runtime-name : "bridge.war")
12:28:20,087 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.Oracle_LPBridge_DS (missing) dependents: [service jboss.naming.context.java.module.chaplin-boilerplate-master.chaplin-boilerplate-master.env.Oracle_LPBridge_DS]
JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./bridge: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./bridge: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
12:28:20,138 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:28:20,139 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:28:20,139 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 15158ms - Started 432 of 507 services (12 services failed or missing dependencies, 62 services are passive or on-demand)
It didnt works.Second appproach in post below.