[JBoss JIRA] (AS7-6440) EmbeddedDeployableContainer should support multiple module paths
by Galder Zamarreño (JIRA)
Galder Zamarreño created AS7-6440:
-------------------------------------
Summary: EmbeddedDeployableContainer should support multiple module paths
Key: AS7-6440
URL: https://issues.jboss.org/browse/AS7-6440
Project: Application Server 7
Issue Type: Bug
Reporter: Galder Zamarreño
AS7 Arquillian EmbeddedDeployableContainer is making the wrong assumptions about the module path. The module path can be made out of several paths separated with a ':'. The following module path fails to start with Embedded container:
{code}/var/folders/vk/g4jts68n6nd37lgvynmtrwxh0000gn/T/test-module:./build/target/jboss-as/modules:./build/target/jboss-as/thirdparty-modules{code}
It fails with:
{code}java.lang.IllegalStateException: Invalid modules directory: /var/folders/vk/g4jts68n6nd37lgvynmtrwxh0000gn/T/test-module:./build/target/jboss-as/modules:./build/target/jboss-as/thirdparty-modules
at org.jboss.as.arquillian.container.embedded.EmbeddedDeployableContainer.setupModuleLoader(EmbeddedDeployableContainer.java:89)
at org.jboss.as.arquillian.container.embedded.EmbeddedDeployableContainer.setup(EmbeddedDeployableContainer.java:65)
at org.jboss.as.arquillian.container.embedded.EmbeddedDeployableContainer.setup(EmbeddedDeployableContainer.java:40)
at org.jboss.arquillian.container.impl.ContainerImpl.setup(ContainerImpl.java:180){code}
The same path works without problems with the Managed Container.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6431) Incorrectly evaluated expression when property is defined after the expression in xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6431?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-6431:
---------------------------------------
I'm surprised reload helps.
> Incorrectly evaluated expression when property is defined after the expression in xml
> -------------------------------------------------------------------------------------
>
> Key: AS7-6431
> URL: https://issues.jboss.org/browse/AS7-6431
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
>
> There is problem in evaluation of expression in case that property for evaluation is defined after the expression.
> In case of using DMR the order of property and expression definition is not taken in consideration and substitution works fine.
> When you define system properties in xml like:
> {code}
> <system-properties>
> <property name="qa.test.property" value="${qa.test.exp:defaultValue}"/>
> <property name="qa.test.exp" value="expression.value"/>
> </system-properties>
> {code}
> you start the container and then you can check the expression evaluation in jboss-cli.sh with command:
> {code}
> :resolve-expression(expression="${qa.test.property}")
> {code}
> The expression will be evaluated as "defaultValue" what is not correct because the "qa.test.exp" is defined.
> When you switch definitions of properties (switch <property> tags) then the expression will be evaluated correctly (as "expression.value).
--
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
11 years, 3 months