May 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-364) Spurious (?) warnings about "More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath"

by Cesar Ricardez (JIRA)

[ https://issues.jboss.org/browse/ARQ-364?page=com.atlassian.jira.plugin.sy... ] Cesar Ricardez commented on ARQ-364: ------------------------------------ I'm going to check the typo... i think the warning is ok like [~aslak] said > Spurious (?) warnings about "More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath" > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ARQ-364 > URL: https://issues.jboss.org/browse/ARQ-364 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Reporter: Bob McWhirter > Priority: Trivial > > In our Arquillian+RSpec (JRuby) integration, everything works, but we repeatedly get this warning: > {noformat} > [WARNING] Feb 8, 2011 10:46:57 AM org.jboss.arquillian.impl.DynamicServiceLoader verifySameImplementation > [WARNING] WARNING: More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath > {noformat} > Would be lovely to have one of: > * Instructions on how to solve the root cause (which classpath? I think we have 3: maven's, jruby's and AS's...) > * Instructions on how to mute the warning -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{(a)org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. was: Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Add support for automatic starting of bundle after installation > --------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after installation now. > Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. > BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Annotation {{(a)org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Bundle is not started automaticly after installation now. Create new container property *autostartBundle*. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{(a)org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. was: Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. Annotation {{(a)org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. > Add support for automatic starting of bundle after installation > --------------------------------------------------------------- > > Key: ARQ-1778 > URL: https://issues.jboss.org/browse/ARQ-1778 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Bundle is not started automaticly after installation now. > Create new container property *autostartBundle*. It's type will be {{boolean}} and default value {{false}}. > BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. > Annotation {{(a)org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation

by Martin Basovnik (JIRA)

Martin Basovnik created ARQ-1778: ------------------------------------ Summary: Add support for automatic starting of bundle after installation Key: ARQ-1778 URL: https://issues.jboss.org/browse/ARQ-1778 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Bundle is not started automaticly after installation now. Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.s... ] Martin Basovnik edited comment on ARQ-1776 at 5/16/14 11:03 AM: ---------------------------------------------------------------- [Pull request|https://github.com/arquillian/arquillian-container-osgi/pull/15] also adds support for setting of multiple bootstrap complete services (property bootstrapCompleteService). These services are delimited by comma. was (Author: mbasovni): Pull request also adds support for setting of multiple bootstrap complete services (property bootstrapCompleteService). These services are delimited by comma. > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-...] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.s... ] Martin Basovnik commented on ARQ-1776: -------------------------------------- Pull request also adds support for setting of multiple bootstrap complete services (property bootstrapCompleteService). These services are delimited by comma. > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-...] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1776: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/15 > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-...] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6

by Pramod Kankure (JIRA)

[ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.s... ] Pramod Kankure updated ARQ-1777: -------------------------------- Description: I have observed that test hangs when executing on tomcat 6 remote container. My arquillian.xml looks like below. ( I don't use authentication for jmx) <?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"> <group qualifier="Grid" default="true"> <defaultProtocol type="Servlet 3.0" /> <container qualifier="remote-tomcat1" default="true"> <configuration> <property name="httpPort">1776</property> <property name="host">localhost</property> <property name="jmxPort">8090</property> </configuration> </container> </group> </arquillian> The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > <?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"> > <group qualifier="Grid" default="true"> > <defaultProtocol type="Servlet 3.0" /> > <container qualifier="remote-tomcat1" default="true"> > <configuration> > <property name="httpPort">1776</property> > <property name="host">localhost</property> > <property name="jmxPort">8090</property> > </configuration> > </container> > </group> > </arquillian> > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6

by Pramod Kankure (JIRA)

Pramod Kankure created ARQ-1777: ----------------------------------- Summary: Test hangs on remote Tomcat 6 Key: ARQ-1777 URL: https://issues.jboss.org/browse/ARQ-1777 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Pramod Kankure -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1776) Make class KarafManagedDeployableContainer compatible with OSGi API 4.2

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1776: --------------------------------- Description: Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-...] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. {code} BundleStateMBean#getBundle(long bundleIdentifier); ServiceStateMBean#listServices(String clazz, String filter); {code} We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? was: Method [KarafManagedDeployableContainer#undeploy|https://github.com/arquillian/ar...] uses following method from class [BundleStateMBean|http://grepcode.com/file/repo1.maven.org/maven2/org.osgi...] which is available from API 5.0. We need to make it compatible with API 4.2. {code} CompositeData getBundle(long bundleIdentifier) throws IOException; {code} Solution is to exchange this method with those available in API 4.2. > Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 > ------------------------------------------------------------------------ > > Key: ARQ-1776 > URL: https://issues.jboss.org/browse/ARQ-1776 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Class [KarafManagedDeployableContainer|https://github.com/arquillian/arquillian-...] uses two methods from JMX API for OSGi [5.0|http://www.osgi.org/javadoc/r5/enterprise/]. > {code} > BundleStateMBean#getBundle(long bundleIdentifier); > ServiceStateMBean#listServices(String clazz, String filter); > {code} > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/] for JMX MBeans. Is it possible to get rid of these methods? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2014