May 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1749) Retrieve httpPort from MBean when not provided in configuration

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1749: ------------------------------ Summary: Retrieve httpPort from MBean when not provided in configuration (was: auto discover httpPort from Container) > Retrieve httpPort from MBean when not provided in configuration > --------------------------------------------------------------- > > Key: ARQ-1749 > URL: https://issues.jboss.org/browse/ARQ-1749 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml. > The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1749) auto discover httpPort from Container

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.s... ] Gerhard Poul reassigned ARQ-1749: --------------------------------- Assignee: Gerhard Poul > auto discover httpPort from Container > ------------------------------------- > > Key: ARQ-1749 > URL: https://issues.jboss.org/browse/ARQ-1749 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml. > The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1781) Add support for multiple bootstrap complete services

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1781?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1781: --------------------------------- Description: Add support for both master and 4.2 branches. (was: Add support both for master and 4.2 branches.) > Add support for multiple bootstrap complete services > ---------------------------------------------------- > > Key: ARQ-1781 > URL: https://issues.jboss.org/browse/ARQ-1781 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Add support for both master and 4.2 branches. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1781) Add support for multiple bootstrap complete services

by Martin Basovnik (JIRA)

Martin Basovnik created ARQ-1781: ------------------------------------ Summary: Add support for multiple bootstrap complete services Key: ARQ-1781 URL: https://issues.jboss.org/browse/ARQ-1781 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler Add support both for master and 4.2 branches. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.s... ] Martin Basovnik edited comment on ARQ-1778 at 5/23/14 9:40 AM: --------------------------------------------------------------- Feature is implemented for karaf managed container. was (Author: mbasovni): I would like to create a unit test for this feature but I do not want to modify {{arquillian.xml}} file. I have created *ResourceProvider* for container configuration class but injection into my test works only in _client_ tests ({{@RunAsClient}}). When I modify the configuration in client test and then execute another _in-container_ test, some classes are missing in deployed bundle (e.g. {{KarafManagedContainerConfiguration}} and others). Why? I do not use this class in this test, only in that client test. How can I inject configuration via {{@ArquillianResource}} (it is already implemented) into in-container test? Or how to make a client test independent of in-container test? > Add OSGi container support for bundle autostart > ----------------------------------------------- > > 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 > > Add OSGi container support for bundle autostart. > Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1778: --------------------------------- Description: Add OSGi container support for bundle autostart. Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. was: Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive<?> archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. Property type will be {{boolean}} and default value {{false}}. > Add OSGi container support for bundle autostart > ----------------------------------------------- > > 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 > > Add OSGi container support for bundle autostart. > Container configuration will contain new property *autostartBundle*. This will cause autostart of every deployed bundle. Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1778) Add OSGi container support for bundle autostart

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1778: --------------------------------- Summary: Add OSGi container support for bundle autostart (was: Add global container setting for bundle autostart after deployment.) > Add OSGi container support for bundle autostart > ----------------------------------------------- > > 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 deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now. > Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive<?> archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value. > Property type will be {{boolean}} and default value {{false}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1776) Create branch for OSGi containers compatible with OSGi 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: We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/]. (was: 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?) > Create branch for OSGi containers compatible with OSGi 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 > > We need to support OSGi API [4.2|http://www.osgi.org/javadoc/r4v42/]. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1776) Create branch for OSGi containers compatible with OSGi 4.2

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/ARQ-1776?page=com.atlassian.jira.plugin.s... ] Martin Basovnik updated ARQ-1776: --------------------------------- Summary: Create branch for OSGi containers compatible with OSGi 4.2 (was: Make class KarafManagedDeployableContainer compatible with OSGi API 4.2 ) > Create branch for OSGi containers compatible with OSGi 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 commented on ARQ-1777: ------------------------------------- I debugged this and it happens in copy method of IOUtils. The reason for that is setting of setFixedLengthStreamingMode and then using buffer of 4096 size. This causes problem. Removal of setFixedLengthStreamingMode fixes the issue. Can existing contributors fix this? > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2014