1 2 Previous Next 28 Replies Latest reply: Aug 13, 2012 6:25 PM by Ivo Neskovic Go to original post RSS
  • 15. Re: arquillian and jboss 7.1
    jaikiran pai Master

    Riccardo Pasquini wrote:

     

    running my test adds this information:

     

    Exception in thread "Thread-1" java.lang.ArrayIndexOutOfBoundsException: 6

            at org.apache.maven.surefire.util.internal.ByteBuffer.append(ByteBuffer.java:45)

            at org.apache.maven.surefire.booter.ForkingRunListener.info(ForkingRunListener.java:223)

            at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.writeTestOutput(ConcurrentReporterManager.java:175)

            at org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:88)

            at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer$ConsoleConsumer.run(ManagedDeployableContainer.java:250)

            at java.lang.Thread.run(Thread.java:662)

     


    http://jira.codehaus.org/browse/SUREFIRE-775

     

    So try upgrading to 2.11 version of surefire plugin in the pom.xml

  • 16. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    and i get the same of the other test... mmm...

     

    Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [30] s

  • 17. Re: arquillian and jboss 7.1
    Martin Heinemann Newbie

    Hi,

    after all i have the same problem with JBoss 7.1.0.Final.

    Running Arquillian tests agains this server i get the same error stating the "Invalid option '-mbeanserverbuildermodule'" error. The tests were fine with JBoss 7.1.0.CR1b

     

    Here is my arquillian.xml:

     

    <?xml version="1.0" encoding="UTF-8"?>
    <arquillian xmlns="http://jboss.org/schema/arquillian"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://jboss.org/schema/arquillian
                http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
    
        <!-- Uncomment to have test archives exported to the file system for inspection -->
        <!-- <engine> -->
        <!-- <property name="deploymentExportPath">target/</property> -->
        <!-- </engine> -->
    
        <!-- Example configuration for a remote JBoss AS 7 instance -->
        <defaultProtocol type="Servlet 3.0" />
        <container qualifier="jboss" default="true">
    <!--         <protocol type="jmx-as7"> -->
            <protocol type="Servlet 3.0">
                <property name="executionType">MANAGED</property>
            </protocol>
            <configuration>
                <property name="serverConfig">target/test-classes/arquillian_standalone.xml</property>
                <property name="javaVmArguments">-Xmx512m -XX:MaxPermSize=128m -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</property>
                <property name="allowConnectingToRunningServer">true</property>            
            </configuration>
        </container>
    
    </arquillian>
    
    

     

     

    and the error message:

     

     

    2012-02-24 15:38:21 xnio [INFO] XNIO Version 3.0.0.CR7
    2012-02-24 15:38:21 nio [INFO] XNIO NIO Implementation Version 3.0.0.CR7
    Listening for transport dt_socket at address: 8787
    2012-02-24 15:38:21 remoting [INFO] JBoss Remoting version 3.2.0.CR8
    WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
    Invalid option '-mbeanserverbuildermodule'
    Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]
           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]
           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]
           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]
    where <module-spec> is a valid module specification string
    and options include:
        -help         Display this message
        -modulepath <search path of directories>
        -mp <search path of directories>
                      A list of directories, separated by ':', where modules may be located
                      If not specified, the value of the "module.path" system property is used
        -class        Specify that the final argument is a
                      class to load from the class path; not compatible with -jar
        -cp,-classpath <search path of archives or directories>
                      A search path for class files; implies -class
        -dep,-dependencies <module-spec>[,<module-spec>,...]
                      A list of module dependencies to add to the class path;
                      requires -class or -cp
        -jar          Specify that the final argument is the name of a
                      JAR file to run as a module; not compatible with -class
        -config <config-location>
                      The location of the module configuration.  Either -mp or -config
                      may be specified, but not both
        -jaxpmodule <module-name>
                      The default JAXP implementation to use of the JDK
        -version      Print version and exit
    

     

     

    and the arquillian dependencies:

     

     

     

    <dependency>
                    <groupId>org.jboss.arquillian</groupId>
                    <artifactId>arquillian-bom</artifactId>
                    <version>1.0.0.CR7</version>
                    <type>pom</type>
                    <scope>import</scope>
    </dependency>
    
    <dependency>
                <groupId>org.jboss.arquillian.junit</groupId>
                <artifactId>arquillian-junit-container</artifactId>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.jboss.as</groupId>
                <artifactId>jboss-as-arquillian-container-managed</artifactId>
                <version>7.1.0.CR1b</version>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.jboss.arquillian.protocol</groupId>
                <artifactId>arquillian-protocol-servlet</artifactId>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.jboss.shrinkwrap.resolver</groupId>
                <artifactId>shrinkwrap-resolver-impl-maven</artifactId>
                <scope>test</scope>
            </dependency>
    
    
  • 18. Re: arquillian and jboss 7.1
    Stephen Coy Master

    This particular problem is happening because the JBoss AS Arquillian components need to be updated to 7.1.0.Final.

     

    One of the tests then fails because of changes in JBoss AS 7.1.0.Final security configuration. I'll try to get to the bottom of that problem in the next few days and update the demo.

  • 19. Re: arquillian and jboss 7.1
    Stephen Coy Master

    The sample code at Testing secured EJBs on JBoss AS7.1.x with Arquillian is now working correctly on JBossAS 7.1.0.Final.

     

    Note that you must add the following configuration to your standalone.xml file:

     

    <security-domain name="demo" cache-type="default">
              <authentication>
                        <login-module code="UsersRoles" flag="sufficient"/>
              </authentication>
    </security-domain>
    

     

     

    as the "other" security-domain was changed substantially between CR1b and Final.

     

    Note that the article content itself still needs updating.

     

    Also I'm somewhat new to Git, so let me know if you can't access the source code for some reason.

  • 20. Re: arquillian and jboss 7.1
    b69 Newbie

    I updated the standalone.xml as shown above, but the problem persist. Surefire-report:

    org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container

        at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:170)

        at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:78)

        at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

        at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

        at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)

        at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

        at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)

        at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

        at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

        at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68)

        at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)

        at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)

        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)

        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)

        at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)

        at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)

        at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)

        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)

    Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [30] s

        at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:166)

        ... 68 more

     

    Fighting arquillian still for a while to use it in my own project without success, I decided to download and install jboss as 7.1.1 and the kitchen-sink example.

    running on windows 7 64, eclipse indigo sp2 and the latest jboss tools.

    arquillian.xml contains:

     

       <container qualifier="jboss" default="true">

          <!-- If you want to use the JBOSS_HOME environment variable, just delete the jbossHome property -->

          <configuration>

             <property name="jbossHome">D:\programs\jbossAS7</property>

          </configuration>

       </container>

    No white spaces, no special characters on server home!

     

    Kitchen-sink on the server works, but this is not the point! The goal is to have arquillian running!

    To get arquillian up and running some help is really appreciated!

     

    Thanks

     

    Juerg

  • 21. Re: arquillian and jboss 7.1
    Stephen Coy Master

    Did you look at the arquillian.xml file from my example above?

     

    It only has a fleeting resemblence to yours:

     

    <?xml version="1.0" encoding="UTF-8"?>
    <arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns="http://jboss.org/schema/arquillian"
        xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
        <container qualifier="jboss7" default="true">
            <protocol type="jmx-as7" >
                <property name="executionType">REMOTE</property>
            </protocol>
            <configuration>
                <property name="javaVmArguments">-Xmx512m -XX:MaxPermSize=128m -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</property>
            </configuration>
        </container>
    </arquillian>
    

     

  • 22. Re: arquillian and jboss 7.1
    b69 Newbie

    Hi,

    I like your "fleeting resemblence", very flattering!

    No, I havent seen the previous version of arquillian.xml As I entered the thread lately, I was not able to see the relationship.

    So, I applied your suggestion, and I got a shift of error messages. at least a deployment seems to happen. But:

    even before I copied I asked me about the reason and meaning of <protocol type="jmx-as7" >.

     

    java.lang.reflect.UndeclaredThrowableException

        at $Proxy17.runTestMethod(Unknown Source)

        at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:69)

        at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:120)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

        at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)

        at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

        at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)

        at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

        at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

        at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

        at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

        at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

        at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)

        at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)

        at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)

        at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)

        at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)

        at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)

        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)

        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)

        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)

        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)

        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)

        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)

        at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)

        at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)

        at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)

        at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)

        at org.junit.runners.ParentRunner.run(ParentRunner.java:236)

        at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)

        at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)

        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)

        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)

        at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)

        at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)

        at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)

        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)

    Caused by: java.io.IOException: Failed operation: "JBAS014739: No handler for invoke-mbean-raw at address [(\"subsystem\" => \"jmx\")]"

        at org.jboss.as.arquillian.container.TunneledMBeanServerConnection.invoke(TunneledMBeanServerConnection.java:166)

        at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)

        ... 82 more

     

    The JUnit is complaining about that. If you have a hint, it may be helpful.

     

    I include the server-log too. Apart of some Hibernate related ERRORS, it looks not so bad to me. But you may be able to see some thing I overlooked.

     

    09:34:44,878 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

    09:34:44,905 INFO  [org.jboss.as.security] (MSC service thread 1-12) JBAS013100: Current PicketBox version=4.0.7.Final

    09:34:44,912 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

    09:34:44,925 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

    09:34:44,946 INFO  [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service

    09:34:44,955 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

    09:34:45,055 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

    09:34:45,068 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-10) JBoss Web Services - Stack CXF Server 4.0.2.GA

    09:34:45,181 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080

    09:34:45,246 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "mysql-connector-java-5.1.18-bin.jar"

    09:34:45,250 INFO  [org.jboss.as.remoting] (MSC service thread 1-12) JBAS017100: Listening on /127.0.0.1:4447

    09:34:45,250 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /127.0.0.1:9999

    09:34:45,250 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-9) JBAS015012: Started FileSystemDeploymentService for directory D:\programs\jbossAS7\standalone\deployments

    09:34:45,337 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-10) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

    09:34:45,401 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-12) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

    09:34:45,414 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/jdbc/MonteRosa]

    09:34:45,431 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "mysql-connector-java-5.1.18-bin.jar"

    09:34:45,469 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

    09:34:45,470 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 1611ms - Started 157 of 235 services (76 services are passive or on-demand)

    09:35:30,251 INFO  [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location D:\programs\jbossAS7\standalone\data\content\49\ce4771bb745d8fd47f69724bd03dfab29f8904\content

    09:35:30,262 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "arquillian-service"

    09:35:30,347 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-15) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.

    09:35:30,350 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-15) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.

    09:35:30,353 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-15) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.osgi:main") which may be changed or removed in future versions without notice.

    09:35:30,356 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-15) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.jandex:main") which may be changed or removed in future versions without notice.

    09:35:30,359 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-15) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.osgi.framework:main") which may be changed or removed in future versions without notice.

    09:35:30,439 INFO  [org.jboss.as.server] (management-handler-thread - 1) JBAS018559: Deployed "arquillian-service"

    09:35:30,618 INFO  [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location D:\programs\jbossAS7\standalone\data\content\db\2819636e638a3b06bb926039124b5942082ab0\content

    09:35:30,622 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015876: Starting deployment of "test.war"

    09:35:30,677 INFO  [org.jboss.as.jpa] (MSC service thread 1-14) JBAS011401: Read persistence.xml for primary

    09:35:30,747 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment test.war

    09:35:30,753 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named MemberRegistration in deployment unit deployment "test.war" are as follows:

     

        java:global/test/MemberRegistration!org.jboss.as.quickstarts.kitchensink.controller.MemberRegistration

        java:app/test/MemberRegistration!org.jboss.as.quickstarts.kitchensink.controller.MemberRegistration

        java:module/MemberRegistration!org.jboss.as.quickstarts.kitchensink.controller.MemberRegistration

        java:global/test/MemberRegistration

        java:app/test/MemberRegistration

        java:module/MemberRegistration

     

    09:35:30,860 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: test.war

    09:35:30,907 INFO  [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71)

    09:35:30,933 INFO  [org.jboss.as.arquillian] (MSC service thread 1-5) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."test.war",unit=test.war,tests=[org.jboss.as.quickstarts.kitchensink.test.MemberRegistrationTest]]

    09:35:30,957 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [jboss/datasources/KitchensinkQuickstartTestDS]

    09:35:30,961 INFO  [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011402: Starting Persistence Unit Service 'test.war#primary'

    09:35:31,050 INFO  [org.hibernate.annotations.common.Version] (MSC service thread 1-5) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}

    09:35:31,056 INFO  [org.hibernate.Version] (MSC service thread 1-5) HHH000412: Hibernate Core {4.0.1.Final}

    09:35:31,058 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-5) HHH000206: hibernate.properties not found

    09:35:31,061 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-5) HHH000021: Bytecode provider name : javassist

    09:35:31,078 INFO  [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-5) HHH000204: Processing PersistenceUnitInfo [

        name: primary

        ...]

    09:35:31,219 INFO  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-5) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider

    09:35:31,394 INFO  [org.hibernate.dialect.Dialect] (MSC service thread 1-5) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect

    09:35:31,400 WARN  [org.hibernate.dialect.H2Dialect] (MSC service thread 1-5) HHH000431: Unable to determine H2 database version, certain features may not work

    09:35:31,405 INFO  [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-5) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4

    09:35:31,413 INFO  [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-5) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory

    09:35:31,418 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-5) HHH000397: Using ASTQueryTranslatorFactory

    09:35:31,445 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-5) Hibernate Validator 4.2.0.Final

    09:35:31,647 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-5) HHH000227: Running hbm2ddl schema export

    09:35:31,658 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-5) HHH000389: Unsuccessful: drop sequence hibernate_sequence

    09:35:31,661 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-5) Sequenz "HIBERNATE_SEQUENCE" nicht gefunden

    Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:

    drop sequence hibernate_sequence [90036-161]

    09:35:31,666 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-5) HHH000230: Schema export complete

    09:35:31,686 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016008: Starting weld service for deployment test.war

    09:35:31,989 INFO  [org.jboss.web] (MSC service thread 1-9) JBAS018210: Registering web context: /test

    09:35:32,023 INFO  [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war"

    09:35:32,097 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war

    09:35:32,105 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'test.war#primary'

    09:35:32,106 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export

    09:35:32,111 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete

    09:35:32,114 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010409: Unbound data source [jboss/datasources/KitchensinkQuickstartTestDS]

    09:35:32,127 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015877: Stopped deployment test.war in 53ms

    09:35:32,186 INFO  [org.jboss.as.repository] (management-handler-thread - 1) JBAS014901: Content removed from location D:\programs\jbossAS7\standalone\data\content\db\2819636e638a3b06bb926039124b5942082ab0\content

    09:35:32,188 INFO  [org.jboss.as.server] (management-handler-thread - 1) JBAS018558: Undeployed "test.war"

    09:35:32,231 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015877: Stopped deployment arquillian-service in 30ms

    09:35:32,287 INFO  [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location D:\programs\jbossAS7\standalone\data\content\49\ce4771bb745d8fd47f69724bd03dfab29f8904\content

    09:35:32,289 INFO  [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "arquillian-service"

     

    Would be nice to get a running system

  • 23. Re: arquillian and jboss 7.1
    Kabir Khan Master

    Caused by: java.io.IOException: Failed operation: "JBAS014739: No handler for invoke-mbean-raw at address [(\"subsystem\" => \"jmx\")]"

        at org.jboss.as.arquillian.container.TunneledMBeanServerConnection.invoke(TunneledMBeanServerConnection.java:166)

        at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)

        ... 82 more

     

     

    As far as I know the invoke-mbean-raw stuff was in an older version of the AS, so it looks like you are not using arquillian jars corresponding to your server version. Any arquillian artifact whith the group id org.jboss.as MUST be the same as the target AS version

  • 24. Re: arquillian and jboss 7.1
    Stephen Coy Master

    Kabir Khan wrote:

     

    ...

    As far as I know the invoke-mbean-raw stuff was in an older version of the AS, so it looks like you are not using arquillian jars corresponding to your server version. Any arquillian artifact whith the group id org.jboss.as MUST be the same as the target AS version

     

    Indeed. In fact I had to update these dependencies from the 7.1CR1b release to 7.1.0.Final because even the difference there was significant.

  • 25. Re: arquillian and jboss 7.1
    b69 Newbie

    thanks, but "ups!", we may have a problem. I'm using:

     

    <dependency>

      <groupId>org.jboss.arquillian</groupId>

      <artifactId>arquillian-bom</artifactId>

      <version>1.0.0.CR7</version>

      <scope>import</scope>

      <type>pom</type>

    </dependency>

     

    to resolve my arquillian dependencies. If this cause the mentioned conflict, I should know which version runs with what, and where to change!

    Thanks in advance.

  • 26. Re: arquillian and jboss 7.1
    Stephen Coy Master

    Is it really that hard to look at the example?

     

    That's not the only arquillian dependency...

  • 27. Re: arquillian and jboss 7.1
    b69 Newbie

    Sorry, It's not that hard to look at the example, but to copy the right part out! Consequence of doing more than one thing at the time.

     

    Here is the real pom now with which the version conflict exist.

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

    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

       <modelVersion>4.0.0</modelVersion>

     

       <groupId>org.jboss.as.quickstarts</groupId>

       <artifactId>jboss-as-kitchensink</artifactId>

       <version>7.1.1-SNAPSHOT</version>

       <packaging>war</packaging>

       <name>JBoss AS Quickstarts: kitchensink</name>

       <description>A starter Java EE 6 webapp project for use on JBoss AS 7 / EAP 6, generated from the jboss-javaee6-webapp archetype</description>

     

       <properties>

          <!-- Explicitly declaring the source encoding eliminates the following

             message: -->

          <!-- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered

             resources, i.e. build is platform dependent! -->

            

          <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

         

          <!-- Define the version of JBoss' Java EE 6 APIs and Tools we want to import.  -->

         

          <javaee6.with.tools.version>1.0.0.M1</javaee6.with.tools.version>

         

          <!-- Alternatively, comment out the above line, and un-comment the line below to

            use version 3.0.0.Beta1-redhat-1 which is a release certified

          to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 maven repository. -->

          <!--

          <javaee6.spec.version>3.0.0.Beta1-redhat-1</javaee6.spec.version>

          -->

       </properties>

     

       <dependencyManagement>

          <dependencies>

            <!-- JBoss distributes a complete set of Java EE 6 APIs including a Bill

              of Materials (BOM). A BOM specifies the versions of a "stack" (or a collection)

              of artifacts. We use this here so that we always get the correct versions

              of artifacts. Here we use the jboss-javaee-6.0-with tools stack (you can read this as

              the JBoss stack of the Java EE 6 APIs, with some extras tools for your project, such

              as Arquillian for testing) -->

             <dependency>

                <groupId>org.jboss.bom</groupId>

                <artifactId>jboss-javaee-6.0-with-tools</artifactId>

                <version>${javaee6.with.tools.version}</version>

                <type>pom</type>

                <scope>import</scope>

             </dependency>

          </dependencies>

       </dependencyManagement>

     

       <dependencies>

     

          <!-- First declare the APIs we depend on and need for compilation.

             All of them are provided by JBoss AS 7 -->

     

          <!-- Import the CDI API, we use provided scope as the API is included

             in JBoss AS 7 -->

          <dependency>

             <groupId>javax.enterprise</groupId>

             <artifactId>cdi-api</artifactId>

             <scope>provided</scope>

          </dependency>

     

          <!-- Import the Common Annotations API (JSR-250), we use provided scope

             as the API is included in JBoss AS 7 -->

          <dependency>

             <groupId>org.jboss.spec.javax.annotation</groupId>

             <artifactId>jboss-annotations-api_1.1_spec</artifactId>

             <scope>provided</scope>

          </dependency>

     

          <!-- Import the JAX-RS API, we use provided scope as the API is included

             in JBoss AS 7 -->

          <dependency>

             <groupId>org.jboss.spec.javax.ws.rs</groupId>

             <artifactId>jboss-jaxrs-api_1.1_spec</artifactId>

             <scope>provided</scope>

          </dependency>

     

          <!-- Import the JPA API, we use provided scope as the API is included

             in JBoss AS 7 -->

          <dependency>

             <groupId>org.hibernate.javax.persistence</groupId>

             <artifactId>hibernate-jpa-2.0-api</artifactId>

             <scope>provided</scope>

          </dependency>

     

          <!-- Import the EJB API, we use provided scope as the API is included

             in JBoss AS 7 -->

          <dependency>

             <groupId>org.jboss.spec.javax.ejb</groupId>

             <artifactId>jboss-ejb-api_3.1_spec</artifactId>

             <scope>provided</scope>

          </dependency>

     

          <!-- JSR-303 (Bean Validation) Implementation -->

          <!-- Provides portable constraints such as @Email -->

          <!-- Hibernate Validator is shipped in JBoss AS 7 -->

          <dependency>

             <groupId>org.hibernate</groupId>

             <artifactId>hibernate-validator</artifactId>

             <version>4.2.0.Final</version>

             <scope>provided</scope>

             <exclusions>

                <exclusion>

                   <groupId>org.slf4j</groupId>

                   <artifactId>slf4j-api</artifactId>

                </exclusion>

             </exclusions>

          </dependency>

     

          <!-- Import the JSF API, we use provided scope as the API is included

             in JBoss AS 7 -->

          <dependency>

             <groupId>org.jboss.spec.javax.faces</groupId>

             <artifactId>jboss-jsf-api_2.0_spec</artifactId>

             <scope>provided</scope>

          </dependency>

     

          <!-- Now we declare any tools needed -->

     

          <!-- Annotation processor to generate the JPA 2.0 metamodel classes

             for typesafe criteria queries -->

          <dependency>

             <groupId>org.hibernate</groupId>

             <artifactId>hibernate-jpamodelgen</artifactId>

             <version>1.1.1.Final</version>

             <scope>provided</scope>

          </dependency>

     

          <!-- Needed for running tests (you may also use TestNG) -->

          <dependency>

             <groupId>junit</groupId>

             <artifactId>junit</artifactId>

             <scope>test</scope>

          </dependency>

     

          <!-- Optional, but highly recommended -->

          <!-- Arquillian allows you to test enterprise code such as EJBs and

             Transactional(JTA) JPA from JUnit/TestNG -->

          <dependency>

             <groupId>org.jboss.arquillian.junit</groupId>

             <artifactId>arquillian-junit-container</artifactId>

             <scope>test</scope>

          </dependency>

         

          <dependency>

             <groupId>org.jboss.arquillian.protocol</groupId>

             <artifactId>arquillian-protocol-servlet</artifactId>

             <scope>test</scope>              

          </dependency>

     

       </dependencies>

     

       <build>

          <!-- Maven will append the version to the finalName (which is the name

             given to the generated war, and hence the context root) -->

          <finalName>${project.artifactId}</finalName>

          <plugins>

             <!-- Compiler plugin enforces Java 1.6 compatibility and activates

                annotation processors -->

             <plugin>

                <artifactId>maven-compiler-plugin</artifactId>

                <version>2.3.1</version>

                <configuration>

                   <source>1.6</source>

                   <target>1.6</target>

                </configuration>

             </plugin>

             <plugin>

                <artifactId>maven-war-plugin</artifactId>

                <version>2.1.1</version>

                <configuration>

                   <!-- Java EE 6 doesn't require web.xml, Maven needs to catch

                      up! -->

                   <failOnMissingWebXml>false</failOnMissingWebXml>

                </configuration>

             </plugin>

             <!-- The JBoss AS plugin deploys your war to a local JBoss AS container -->

             <!-- To use, run: mvn package jboss-as:deploy -->

             <plugin>

                <groupId>org.jboss.as.plugins</groupId>

                <artifactId>jboss-as-maven-plugin</artifactId>

                <version>7.1.0.Final</version>

             </plugin>

          </plugins>

       </build>

     

       <profiles>

          <profile>

             <!-- The default profile skips all tests, though you can tune it

                to run just unit tests based on a custom pattern -->

             <!-- Seperate profiles are provided for running all tests, including

                Arquillian tests that execute in the specified container -->

             <id>default</id>

             <activation>

                <activeByDefault>true</activeByDefault>

             </activation>

             <build>

                <plugins>

                   <plugin>

                      <artifactId>maven-surefire-plugin</artifactId>

                      <version>2.4.3</version>

                      <configuration>

                         <skip>true</skip>

                      </configuration>

                   </plugin>

                </plugins>

             </build>

          </profile>

     

          <profile>

             <!-- An optional Arquillian testing profile that executes tests

                in your JBoss AS instance -->

             <!-- This profile will start a new JBoss AS instance, and execute

                the test, shutting it down when done -->

             <!-- Run with: mvn clean test -Parq-jbossas-managed -->

             <id>arq-jbossas-managed</id>

             <dependencies>

                <dependency>

                   <groupId>org.jboss.as</groupId>

                   <artifactId>jboss-as-arquillian-container-managed</artifactId>

                   <scope>test</scope>

                </dependency>

             </dependencies>

          </profile>

          <profile>

             <!-- An optional Arquillian testing profile that executes tests

                in a remote JBoss AS instance -->

             <!-- Run with: mvn clean test -Parq-jbossas-remote -->

             <id>arq-jbossas-remote</id>

             <dependencies>

                <dependency>

                   <groupId>org.jboss.as</groupId>

                   <artifactId>jboss-as-arquillian-container-remote</artifactId>

                   <scope>test</scope>

                </dependency>

             </dependencies>

          </profile>

         

          <profile>

             <!-- When built in OpenShift the 'openshift' profile will be used when invoking mvn. -->

             <!-- Use this profile for any OpenShift specific customization your app will need. -->

             <!-- By default that is to put the resulting archive into the 'deployments' folder. -->

             <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environments.html -->

             <id>openshift</id>

             <build>

                <plugins>

                   <plugin>

                      <artifactId>maven-war-plugin</artifactId>

                      <version>2.1.1</version>

                      <configuration>

                         <outputDirectory>deployments</outputDirectory>

                         <warName>ROOT</warName>

                      </configuration>

                   </plugin>

                </plugins>

             </build>

          </profile>

     

       </profiles>

    </project>

  • 28. Re: arquillian and jboss 7.1
    Ivo Neskovic Newbie

    Hi All,

     

    You need to make sure that the arquillian as container dependency matches your version of AS7. For AS7.1.1 final you need to specifiy this dependency:

     

    <dependency>

         <groupId>org.jboss.as</groupId>

         <artifactId>jboss-as-arquillian-container-managed</artifactId>

         <version>7.1.1.Final</version>

         <scope>test</scope>

    </dependency>

     

    Hope this works for you!

     

    /ivo

1 2 Previous Next