jboss-eap-6

I am migrating an application with Java WS from Jboss 5.1.0 to Jboss 6.3.0 EAP. It works fine with Jboss 5.1.0 but I am getting error while deploying the same in Jboss 6.3.0 EAP. 14:42:10,887 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deploy ment.unit."my-app.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."dtm-banking. war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "dtm-banking.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService

I am trying to understand how to use JBoss EAP6 with Spring applications. I have a sample OpenShift application and it contains a jboss-deployment-structure.xml file. I found some documentation about this file, but I am not clear why and when one should use those files with Spring applications. The content is the following: <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0"> <deployment> <dependencies> <module name="com.h2database.h2"/> <module name="org.codehaus.jackson.jackson-core-asl"/> <module name="org.codehaus.jackson.jackson-mapper-asl"/> <module name="org.slf4j"/>

How do I bind an arbitrary string to JNDI in JBoss EAP 6? I used to do it through org.jboss.naming.JNDIBindingServiceMgr MBean in previous EAP version. Is there anything similar to org.jboss.naming.JNDIBindingServiceMgr in JBoss EAP 6? We are migrating applications from jboss-5.1.EAP to jboss-eap-6.1. We need to bind some things into JNDI, so applications can look up values of environment variables. Many thanks. You can do the following: standalone.xml: <subsystem xmlns="urn:jboss:domain:naming:1.2"> <bindings> <simple name="java:global/user" value="newUser"/> </bindings> </subsystem> and in

Similar questions: How to use bean validation 1.1 in JBoss EAP 6.4.0? How to change bean-validation version on jboss EAP 6.3? Can you use bean validation 1.1 (JSR 349) in JBoss EAP 6.4.4? There seems to be some uncertainty if we can use Bean Validation 1.1 in JBoss 6.x. My current jboss-deployment-structure.xml: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0"> <deployment> <dependencies> <!-- list of modules taken from https://access.redhat.com/articles/1122333 --> <module name="javax.activation.api" /> <module name="javax