[
https://issues.jboss.org/browse/WFLY-2020?page=com.atlassian.jira.plugin....
]
Thomas Diesler commented on WFLY-2020:
--------------------------------------
Its using the same jboss-marshalling-river on the client
{code}
[INFO] +- org.jboss.osgi.wildfly:jbosgi-wildfly-jmx:jar:2.1.1-SNAPSHOT:compile
[INFO] | \- org.wildfly:wildfly-jmx:jar:8.0.0.Beta1-SNAPSHOT:compile
[INFO] | +- org.jboss:jboss-common-core:jar:2.2.22.GA:compile
[INFO] | +- org.jboss.remotingjmx:remoting-jmx:jar:2.0.0.CR1:compile
[INFO] | +- org.jboss.marshalling:jboss-marshalling-river:jar:1.4.0.Final:compile
[INFO] | \- org.wildfly.security:wildfly-security-manager:jar:1.0.0.Beta1:compile
{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: David Lloyd
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}
AFAICS, 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