[arquillian-issues] [JBoss JIRA] (ARQ-1924) Bad behaviour on Shrinkwrap.addAsServiceProvider
[
https://issues.jboss.org/browse/ARQ-1924?page=com.atlassian.jira.plugin.s...
]
Antonin Stefanutti commented on ARQ-1924:
-----------------------------------------
I've been facing the same issue in
https://github.com/astefanutti/further-cdi/blob/b490b41747b70b0e5a28f05ba....
In my case, the extension added with {{addAsServiceProvider}} is not deployed by the CDI
container managed by the {{arquillian-weld-ee-embedded-1.1}} adapter when I create an EAR,
while that works when I create a WAR.
As mentioned in the description, the extension is deployed as expected in the CDI
container managed by the {{wildfly-arquillian-container-managed}} adapter.
I'd suggest to update the title to be more specific so that users don't lose too
much time trying to troubleshoot why extensions are not properly deployed when being added
with {{addAsServiceProvider}}.
Bad behaviour on Shrinkwrap.addAsServiceProvider
------------------------------------------------
Key: ARQ-1924
URL: https://issues.jboss.org/browse/ARQ-1924
Project: Arquillian
Issue Type: Bug
Components: OpenWebBeans Containers, Weld Containers
Affects Versions: 1.0.0.CR8, 1.1.7.Final
Reporter: Rafael Benevides
Attachments: arquillian-test.zip
The attached maven project contains two tests:
1 - ExtensionInJarTest - This adds a Service through .addAsServiceProvider to an JAR that
is placed inside a WAR
2 - ExtensionInWarTest - This add a Service through .addAsServiceProvider directly to a
WAR
If you run the tests inside Wildfly:
{code}
mvn clean test -Parq-wildfly-remote //it works
{code}
If you run the tests using Weld or OWB:
{code}
mvn clean test -PWeld //it fails on ExtensionInJarTest
mvn clean test -POWB //it fails on ExtensionInJarTest
{code}
The expected behaviour is that Weld and OWB shouldn't fail.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)