[jboss-jira] [JBoss JIRA] (WFLY-2020) ARQ container cannot fetch deployment from client side any more
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Fri Sep 6 07:57:03 EDT 2013
[ https://issues.jboss.org/browse/WFLY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802244#comment-12802244 ]
Thomas Diesler commented on WFLY-2020:
--------------------------------------
To reproduce you can checkout https://github.com/tdiesler/jbosgi/tree/next and run
{code}
mvn -Dtarget.container=wildfly800 clean test
{code}
you should see failures in the example test suite. The osgi patched wildfly instance is in the target directory of the respective test module. The wildfly/build/target directory contains the wildfly-osgi patch in case you want to work with your wildfly instance.
The test can be run against a running server if you start it like this
{code}
bin/standalone.sh -c standalone-osgi.xml
{code}
> ARQ container cannot fetch deployment from client side any more
> ---------------------------------------------------------------
>
> Key: WFLY-2020
> URL: https://issues.jboss.org/browse/WFLY-2020
> Project: WildFly
> Issue Type: Bug
> Reporter: Thomas Diesler
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 8.0.0.Beta1
>
>
> This is likely due to a change in the JMX layer. All tests fail here
> {code}
> @ArquillianResource
> public Deployer deployer;
> InputStream input = deployer.getDeployment(BUNDLE_A);
> {code}
> AFACS, there is only plain ARQ and JMX code involved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list