[JBoss JIRA] (ARQ-1249) Deployment to GF fails if .war extension is missing
by Fabian Schwarzer (JIRA)
Fabian Schwarzer created ARQ-1249:
-------------------------------------
Summary: Deployment to GF fails if .war extension is missing
Key: ARQ-1249
URL: https://issues.jboss.org/browse/ARQ-1249
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: GlassFish Containers
Reporter: Fabian Schwarzer
If you try to deploy a WebArchive like so,
{code:borderStyle=solid}
final WebArchive archive = ShrinkWrap.create( WebArchive.class, "ArquillianTest" );
{code}
you will get a NPE, that does not give you any clue about how to fix the problem.
In order to fix it, you have to write "ArquillianTest.war" and not "ArquillianTest".
It would be nice if there was a error message that pointed you to the error, instead of a meaningless NPE.
--
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, 9 months
[JBoss JIRA] (ARQ-1248) Add Derby to the testing matrix
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1248:
-----------------------------------
Summary: Add Derby to the testing matrix
Key: ARQ-1248
URL: https://issues.jboss.org/browse/ARQ-1248
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
Integration tests should be ran against Apache Derby, it's quite popular for testing.
--
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, 9 months
[JBoss JIRA] (ARQ-1247) Test cases not working in current builds
by John Ament (JIRA)
John Ament created ARQ-1247:
-------------------------------
Summary: Test cases not working in current builds
Key: ARQ-1247
URL: https://issues.jboss.org/browse/ARQ-1247
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Warp
Reporter: John Ament
Current tutorials point to an alpha2 snapshot. However, it doesn't seem to work. Even building from github results in a similar error:
Caused by: java.lang.NoClassDefFoundError: org/jboss/arquillian/warp/ftest/inspe
ction/innerclasses/TestInspectionCreatesStaticInnerClass
at java.lang.Class.getDeclaringClass(Native Method) [rt.jar:1.6.0_35]
at java.lang.Class.getEnclosingClass(Class.java:1085) [rt.jar:1.6.0_35]
at java.lang.Class.getSimpleBinaryName(Class.java:1220) [rt.jar:1.6.0_35
]
at java.lang.Class.isMemberClass(Class.java:1210) [rt.jar:1.6.0_35]
at org.jboss.weld.util.reflection.Reflections.getNesting(Reflections.jav
a:132) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.jboss.weld.introspector.jlr.WeldConstructorImpl.<init>(WeldConstr
uctorImpl.java:99) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.jboss.weld.introspector.jlr.WeldConstructorImpl.of(WeldConstructo
rImpl.java:66) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.jboss.weld.introspector.jlr.WeldClassImpl.<init>(WeldClassImpl.ja
va:205) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:1
18) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.ap
ply(ClassTransformer.java:49) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.ap
ply(ClassTransformer.java:40) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueRe
ference.compute(ComputingConcurrentHashMap.java:355)
at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment
.compute(ComputingConcurrentHashMap.java:184)
at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment
.getOrCompute(ComputingConcurrentHashMap.java:153)
at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(Com
putingConcurrentHashMap.java:69)
at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdap
ter.get(ComputingConcurrentHashMap.java:393)
at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.
java:149) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
... 11 more
Caused by: java.lang.ClassNotFoundException: org.jboss.arquillian.warp.ftest.ins
pection.innerclasses.TestInspectionCreatesStaticInnerClass from [Module "deploym
ent.test.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:
190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Con
currentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(Concu
rrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(Concu
rrentClassLoader.java:423)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentCl
assLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoad
er.java:120)
... 28 more
17:09:58,811 INFO [org.jboss.web] (MSC service thread 1-5) JBAS018210: Register
ing web context: /test
17:09:58,833 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018
559: Deployed "test.war"
17:09:58,842 INFO [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS01600
9: Stopping weld service for deployment test.war
17:09:58,860 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JB
AS015877: Stopped deployment test.war in 20ms
17:09:58,880 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBA
S014901: Content removed from location C:\Users\JohnAment\Documents\GitHub\arqui
llian-extension-warp\ftest\target\jboss-as-7.1.1.Final\standalone\data\content\3
0\1cc9d9d937b607788de9aff1fcb02d0cb88ced\content
17:09:58,881 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018
558: Undeployed "test.war"
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.285 sec <<< FA
ILURE!
Running org.jboss.arquillian.warp.ftest.provider.TestResourceProviders
17:09:59,347 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBA
S014900: Content added at location C:\Users\JohnAment\Documents\GitHub\arquillia
n-extension-warp\ftest\target\jboss-as-7.1.1.Final\standalone\data\content\f2\d7
8ac78c863060ab7537eefa7086f9df4362fd\content
17:09:59,350 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JB
AS015876: Starting deployment of "test.war"
17:10:00,029 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002
: Processing weld deployment test.war
17:10:00,037 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016005
: Starting Services for CDI deployment: test.war
17:10:00,039 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016008
: Starting weld service for deployment test.war
17:10:00,088 INFO [org.jboss.web] (MSC service thread 1-16) JBAS018210: Registe
ring web context: /test
17:10:00,108 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018
559: Deployed "test.war"
17:10:00,119 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009
: Stopping weld service for deployment test.war
17:10:00,142 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JB
AS015877: Stopped deployment test.war in 24ms
17:10:00,160 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBA
S014901: Content removed from location C:\Users\JohnAment\Documents\GitHub\arqui
llian-extension-warp\ftest\target\jboss-as-7.1.1.Final\standalone\data\content\f
2\d78ac78c863060ab7537eefa7086f9df4362fd\content
17:10:00,161 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018
558: Undeployed "test.war"
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.271 sec <<< FA
ILURE!
Results :
Tests in error:
org.jboss.arquillian.warp.ftest.BasicWarpTest: java.lang.IllegalStateException
: standard-sockets -> http -> bound-port is undefined
org.jboss.arquillian.warp.ftest.failure.TestBigResponsePayload: java.lang.Ille
galStateException: standard-sockets -> http -> bound-port is undefined
org.jboss.arquillian.warp.ftest.failure.TestInspectionFailurePropagation: java
.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined
org.jboss.arquillian.warp.ftest.inspection.inheritance.TestSuperClassInspectio
n: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is un
defined
org.jboss.arquillian.warp.ftest.inspection.innerclasses.TestDeploymentContains
UnlinkableStaticInnerClass: java.lang.IllegalStateException: standard-sockets ->
http -> bound-port is undefined
org.jboss.arquillian.warp.ftest.inspection.innerclasses.TestInspectionCreatesS
taticInnerClass: java.lang.IllegalStateException: standard-sockets -> http -> bo
und-port is undefined
org.jboss.arquillian.warp.ftest.provider.TestResourceProviders: java.lang.Ille
galStateException: standard-sockets -> http -> bound-port is undefined
Tests run: 7, Failures: 0, Errors: 7, Skipped: 0
--
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, 9 months
[JBoss JIRA] (ARQ-964) Verify that all tests in ServerAssertion has been called - prevents false negatives
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-964?page=com.atlassian.jira.plugin.sy... ]
Lukáš Fryč reassigned ARQ-964:
------------------------------
Assignee: Lukáš Fryč
> Verify that all tests in ServerAssertion has been called - prevents false negatives
> -----------------------------------------------------------------------------------
>
> Key: ARQ-964
> URL: https://issues.jboss.org/browse/ARQ-964
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: warp_1.0.0.Alpha2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> For {{Alpha1}}, if you don't install _Phaser_, and run the assertion from Phaser, it will pass all tests even though not all tests will be run.
> It would be handy to verify that all tests has passed.
> I suggest to add annotation, which will mark lifecycle event annotations like {{@BeforePhase}} and runtime will need to verify all the assertion methods were ran.
--
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, 9 months
[JBoss JIRA] (ARQ-1246) Warp: single execution should observe only first request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1246?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved ARQ-1246.
-----------------------------
Resolution: Done
> Warp: single execution should observe only first request
> --------------------------------------------------------
>
> Key: ARQ-1246
> URL: https://issues.jboss.org/browse/ARQ-1246
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Default Warp execution mode in Alpha1 was enhancing just first request in Warp execution cycle.
> In Alpha2 with introduction of WarpGroups, this behavior was changed, so user needs to define observer for almost each request for complex pages which loads multiple requests, otherwise Warp fails with message that there are too much requests.
> Default behavior in single execution scenario (which means without using request groups) is that only first request matching criteria is enhanced with Warp.
> This will also preserve backward compatibility.
--
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, 9 months