Hi Keren,
for a long time we did not have a remote OSGi container other than WildFly. The WildFly
ARQ containers had OSGi support build in - so there was no need to maintain a separate
remote OSGi container. If you like, you can resurect the remote OSGi container - I'll
lend a hand when you get stuck. It relies on OSGi JMX functionality to be installed in
your remote running framework.
cheers
--thomas
On Jul 16, 2013, at 7:09 PM, DONG Keren <dongkeren(a)gmail.com> wrote:
Dear Thomas,
I have been trying to use Arquillian to test our OSGi based system, but stuck with
getting it running against remote container. I try to look at the code and found this
commit:
Commit: 186d0c10d245f7cd1e25739e03f6d6aee49962c9 [186d0c1]
Parents: a7ac6594ca
Author: Thomas Diesler <thomas.diesler(a)jboss.com>
Date: May 23, 2012 12:53:23 PM GMT+01:00
[ARQ-954] Remove dependency on jboss-logging in OSGi Bundle
Retire remote container
Where you removed the remote container. Can you please update me what happened and why
did you retire the remote container?
Thanks in advance.
Best,
Keren
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx