October 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-200) Enhance Graphene's guards to wait until page fully updates

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-200?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-200: ----------------------------------- But if you feel there is some issue with request guards, let us know and we can study your case. > Enhance Graphene's guards to wait until page fully updates > ---------------------------------------------------------- > > Key: ARQGRA-200 > URL: https://issues.jboss.org/browse/ARQGRA-200 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha2 > Reporter: Jiří Štefek > > It would be nice if Graphene's guards (guardXhr, guardHttp and guardNoRequest) can be used to wait until page fully updates after the the request. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1130) Upgrade dependencies of arquillian and shrinkwrap-container-openejb-31

by Marcos Bermudez (JIRA)

Marcos Bermudez created ARQ-1130: ------------------------------------ Summary: Upgrade dependencies of arquillian and shrinkwrap-container-openejb-31 Key: ARQ-1130 URL: https://issues.jboss.org/browse/ARQ-1130 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: openejb_1.0.0.next Environment: All envoronements Reporter: Marcos Bermudez Upgrade dependencies of arquillian and shrinkwrap-container-openejb-31. In order to use the arquillian-container-openejb with the version of Arquilian 1.0.2.Final Upgrade dependencies of : * shrinkwrap-container-openejb-31 to 1.0.0 (released yesterday) * version.arquillian to 1.0.2.Final -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] (ARQGRA-200) Enhance Graphene's guards to wait until page fully updates

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-200?page=com.atlassian.jira.plugin... ] Jiří Štefek commented on ARQGRA-200: ------------------------------------ Thanks for the informations. So, should I (always) use some explicit waiting after guarded request? What are the use-cases of the guards now? > Enhance Graphene's guards to wait until page fully updates > ---------------------------------------------------------- > > Key: ARQGRA-200 > URL: https://issues.jboss.org/browse/ARQGRA-200 > Project: Arquillian Graphene > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha2 > Reporter: Jiří Štefek > > It would be nice if Graphene's guards (guardXhr, guardHttp and guardNoRequest) can be used to wait until page fully updates after the the request. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1122) ServletRuntime lookup only returns servlets of first web application found

by Ralph Abbink (JIRA)

Ralph Abbink created ARQ-1122: --------------------------------- Summary: ServletRuntime lookup only returns servlets of first web application found Key: ARQ-1122 URL: https://issues.jboss.org/browse/ARQ-1122 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: WebLogic Containers Affects Versions: 1.0.2.Final Environment: Weblogic 12c Reporter: Ralph Abbink Assignee: Vineet Reynolds After enriching our regular maven built .ear i noticed the following exception: {noformat}ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer.{noformat} It appears the lookup for servletRuntimes only returns the servlets of the first web application in the deployment. In our .ear we have several web modules and the first one found wasn't the module i enriched using Arquillian. {code:title=WebLogicJMXClient.java} private ObjectName[] findServletRuntimes(ObjectName wlServerRuntime, String deploymentName) throws Exception { ObjectName[] applicationRuntimes = (ObjectName[]) connection.getAttribute(wlServerRuntime, "ApplicationRuntimes"); for(ObjectName applicationRuntime: applicationRuntimes) { String applicationName = (String) connection.getAttribute(applicationRuntime, "Name"); if(applicationName.equals(deploymentName)) { ObjectName[] componentRuntimes = (ObjectName[]) connection.getAttribute(applicationRuntime, "ComponentRuntimes"); for(ObjectName componentRuntime : componentRuntimes) { String componentType = (String) connection.getAttribute(componentRuntime, "Type"); if (componentType.toString().equals("WebAppComponentRuntime")) { ObjectName[] servletRuntimes = (ObjectName[]) connection.getAttribute(componentRuntime, "Servlets"); return servletRuntimes; } } } } throw new DeploymentException( "The deployment details were not found in the MBean Server. Possible causes include:\n" + "1. The deployment failed. Review the admin server and the target's log files.\n" + "2. The deployment succeeded partially. The deployment must be the Active state. Instead, it might be in the 'New' state.\n" + " Verify that the the admin server can connect to the target(s), and that no firewall rules are blocking the traffic on the admin channel."); } {code} {code:title="Returning all servlets found" WebLogicJMXClient.java} private List<ObjectName> findServletRuntimes(ObjectName wlServerRuntime, String deploymentName) throws Exception { ObjectName[] applicationRuntimes = (ObjectName[]) connection.getAttribute(wlServerRuntime, "ApplicationRuntimes"); for(ObjectName applicationRuntime: applicationRuntimes) { String applicationName = (String) connection.getAttribute(applicationRuntime, "Name"); if(applicationName.equals(deploymentName)) { List<ObjectName> servletRuntimes = new ArrayList<ObjectName>(); ObjectName[] componentRuntimes = (ObjectName[]) connection.getAttribute(applicationRuntime, "ComponentRuntimes"); for(ObjectName componentRuntime : componentRuntimes) { String componentType = (String) connection.getAttribute(componentRuntime, "Type"); if (componentType.toString().equals("WebAppComponentRuntime")) { servletRuntimes.addAll(Arrays.asList((ObjectName[]) connection.getAttribute(componentRuntime, "Servlets"))); } } return servletRuntimes; } } throw new DeploymentException( "The deployment details were not found in the MBean Server. Possible causes include:\n" + "1. The deployment failed. Review the admin server and the target's log files.\n" + "2. The deployment succeeded partially. The deployment must be the Active state. Instead, it might be in the 'New' state.\n" + " Verify that the the admin server can connect to the target(s), and that no firewall rules are blocking the traffic on the admin channel."); } } {code} -- 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

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] (ARQ-1133) Upgrade to Arquillian core 1.0.2.Final for WebLogic Containers

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-1133: ------------------------------------ Summary: Upgrade to Arquillian core 1.0.2.Final for WebLogic Containers Key: ARQ-1133 URL: https://issues.jboss.org/browse/ARQ-1133 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: WebLogic Containers Affects Versions: wls_1.0.0.Alpha2 Reporter: Vineet Reynolds Assignee: Vineet Reynolds Fix For: wls_1.0.0.next Update the WebLogic containers to Arquillian Core 1.0.2.Final. This is more to ensure that the tests for the container adapter can use the {{Testable}} API to define the archive to test. -- 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

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] (ARQ-1159) Add support for Felix/Equinox testing

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1159: ----------------------------------- Summary: Add support for Felix/Equinox testing Key: ARQ-1159 URL: https://issues.jboss.org/browse/ARQ-1159 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_1.0.3.Final -- 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

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] (ARQ-1153) Add support for multiple bundle deployments per test case

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1153: ----------------------------------- Summary: Add support for multiple bundle deployments per test case Key: ARQ-1153 URL: https://issues.jboss.org/browse/ARQ-1153 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_1.0.3.Final -- 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

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-468) Automatically add test super classes for OSGi

by Thomas Diesler (JIRA)

Automatically add test super classes for OSGi --------------------------------------------- Key: ARQ-468 URL: https://issues.jboss.org/browse/ARQ-468 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Super classes should be added automatically and work as the injection target for the OSGi enricher -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] (ARQ-1152) Add support for OSGi types as ArquillianResource

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1152: ----------------------------------- Summary: Add support for OSGi types as ArquillianResource Key: ARQ-1152 URL: https://issues.jboss.org/browse/ARQ-1152 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_1.0.3.Final -- 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

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] (ARQ-1154) parameter "servletName" not used

by Arne Plöse (JIRA)

Arne Plöse created ARQ-1154: ------------------------------- Summary: parameter "servletName" not used Key: ARQ-1154 URL: https://issues.jboss.org/browse/ARQ-1154 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.Final Reporter: Arne Plöse in org.jboss.arquillian.protocol.servlet.ServletUtil.public static URI determineBaseURI(ServletProtocolConfiguration config, HTTPContext context, String servletName) the parameter servletName is not used, instead ServletMethodExecutor.ARQUILLIAN_SERVLET_NAME is fixed wired as servletName... -- 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

13 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2012