[JBoss JIRA] (ARQ-938) Introduce debug property for managed containers
by Dan Allen (JIRA)
Dan Allen created ARQ-938:
-----------------------------
Summary: Introduce debug property for managed containers
Key: ARQ-938
URL: https://issues.jboss.org/browse/ARQ-938
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: GlassFish Containers, JBoss AS Containers, Tomcat Containers
Reporter: Dan Allen
It's currently too tedious and inconsistent across managed containers to enable debugging with the VM set to suspend on startup. This task requires hacking on the VM arguments, which is too low level for casual users.
Managed containers should offer a configuration property named "debug" that will enable the proper JVM switch to enable debugging with the VM set to suspend on startup. The suspend flag, of course, gives the developer an opportunity to connect the debugger before the tests begin executing.
We can either make the debug flag a boolean or we can make it a three state toggle: true, suspend, false. In the latter case, a value of true enables debugging but not suspend, a value of suspend enables debugging and suspend and a value of false disables debugging.
This should be implemented for the following containers:
JBoss AS 5 - 6
GlassFish 3.1
Tomcat 6 - 7
An issue needs to be filed in the JBoss AS 7 issue tracker after this issue is resolved (so that we settle on the "standard" before lobbying for the feature in AS 7).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (ARQ-1089) Warp should avoid depending on 'provided' container libs on client side
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1089:
----------------------------------
Summary: Warp should avoid depending on 'provided' container libs on client side
Key: ARQ-1089
URL: https://issues.jboss.org/browse/ARQ-1089
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Reporter: Aslak Knutsen
Priority: Minor
Warp require Servlet api jars on client side to package it self.
The AuxiliaryArchiveAppender should be able to package it self without requiring 'provided' libs.
{code}
java.lang.NoClassDefFoundError: javax/servlet/Filter
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at org.jboss.arquillian.warp.DeploymentEnricher.createAuxiliaryArchive(DeploymentEnricher.java:86)
{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
12 years, 2 months
[JBoss JIRA] (ARQ-1222) @OperateOnDeployment ignores value and operates on random deployment in in-container test
by Ron Šmeral (JIRA)
Ron Šmeral created ARQ-1222:
-------------------------------
Summary: @OperateOnDeployment ignores value and operates on random deployment in in-container test
Key: ARQ-1222
URL: https://issues.jboss.org/browse/ARQ-1222
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployable Containers SPI
Affects Versions: 1.0.3.Final
Environment: EAP 6.0.1.ER3, JDK 1.7.0_07
Reporter: Ron Šmeral
The following (in-container) test sometimes passes and other times fails with {{java.lang.NoClassDefFoundError}} for {{B}}.
It seems that the order of declaration of {{@Deployment}} methods has influence on the frequency of failures.
{{A}} and {{B}} are empty dummy classes.
{code:title=OperateOnDeploymentTest.java}
@RunWith(Arquillian.class)
public class OperateOnDeploymentTest {
@Deployment(name = "A")
public static Archive<?> deployA() {
return ShrinkWrap.create(WebArchive.class).addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml").
.addClass(A.class);
}
@Deployment(name = "B")
public static Archive<?> deployB() {
return ShrinkWrap.create(WebArchive.class).addAsWebInfResource(EmptyAsset.INSTANCE, "beans.xml").
.addClass(B.class);
}
@Test
@OperateOnDeployment("B")
public void testB() {
B.class.getName();
}
}
{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
12 years, 2 months