You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the arquillian sample there is the "wildfly-managed-arquillian" profile which tries to use the standalone-full.xml configuration (line 179 of the pom.xml).
Arquillian ignore this and uses the standalone.xml
This can be easily verified, by adding to the arquillian test an injection to the default JMS connection factory, (for instance: @Resource private ConnectionFactory factory;) which cause a name not found exception.
I have not found an workaround to start the embedded widlfly using the standalone-full.xml
The text was updated successfully, but these errors were encountered:
In the arquillian sample there is the "wildfly-managed-arquillian" profile which tries to use the standalone-full.xml configuration (line 179 of the pom.xml).
Arquillian ignore this and uses the standalone.xml
This can be easily verified, by adding to the arquillian test an injection to the default JMS connection factory, (for instance:
@Resource private ConnectionFactory factory;
) which cause a name not found exception.I have not found an workaround to start the embedded widlfly using the standalone-full.xml
The text was updated successfully, but these errors were encountered: