Module for EL
by Gunnar Morling
Hi all,
I'm currently working on updating the AS module for Hibernate Validator to
the latest release (HV 5.x, Bean Validation 1.1, see [1]).
As of this release, Hibernate Validator has a new dependency to the Unified
EL. So I have added this to the HV module descriptor:
<module name="javax.el.api"/>
Based on test failures I'm seeing ("javax.el.ELException: Provider
org.apache.el.ExpressionFactoryImpl not found"), I think I need to add a
dependency for the actual EL implementation as well. I don't know though
which module that would be.
Does anyone know which is the right one or has an example of other modules
depending on EL?
Thanks,
--Gunnar
[1] https://issues.jboss.org/browse/AS7-6665
11 years, 7 months
can't run the integration tests (current upstream)
by Wolf-Dieter Fink
Hi,
I'm not able to run the integration tests due to missing dependencies.
I pulled the current upstream and start with a fresh maven repository,
but still no success :(
Any idea?
- Wolf
[wfink jboss-as]$ ./integration-tests.sh
/data/devel/github/AS7/jboss-as/tools/maven/bin/mvn -s
../tools/maven/conf/settings.xml install -Dts.smoke
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator
[INFO] JBoss Application Server Test Suite: Integration
[INFO] JBoss Application Server Test Suite: Integration - Smoke
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building JBoss Application Server Test Suite: Aggregator
8.0.0.Alpha1-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @
jboss-as-testsuite ---
[WARNING]
Dependency convergence error for
org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ejb3:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-jpa-spi:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.ws.native:jbossws-native-core:4.1.1.Final
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.1.Final
[WARNING]
Dependency convergence error for org.apache.juddi:uddi-ws:3.1.3 paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:juddi-client:3.1.3
+-org.apache.juddi:uddi-ws:3.1.3
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi.scout:scout:1.2.6
+-org.apache.juddi:uddi-ws:3.0.2
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:uddi-ws:3.1.3
[WARNING]
Dependency convergence error for
org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
paths to dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-javax.enterprise:cdi-api:1.0-SP4
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ee:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.weld:weld-core:1.1.12.Final
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
[WARNING] Rule 1:
org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Failed while enforcing releasability the error(s) are [
Dependency convergence error for
org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ejb3:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-jpa-spi:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.ws.native:jbossws-native-core:4.1.1.Final
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.1.Final
,
Dependency convergence error for org.apache.juddi:uddi-ws:3.1.3 paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:juddi-client:3.1.3
+-org.apache.juddi:uddi-ws:3.1.3
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi.scout:scout:1.2.6
+-org.apache.juddi:uddi-ws:3.0.2
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:uddi-ws:3.1.3
,
Dependency convergence error for
org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
paths to dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-javax.enterprise:cdi-api:1.0-SP4
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ee:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.weld:weld-core:1.1.12.Final
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator ... FAILURE [8.057s]
[INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8.714s
[INFO] Finished at: Fri Apr 12 15:57:38 CEST 2013
[INFO] Final Memory: 56M/404M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.2:enforce
(ban-bad-dependencies) on project jboss-as-testsuite: Some Enforcer
rules have failed. Look above for specific messages explaining why the
rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
11 years, 7 months
7.2.0.Final boot time NPE
by Ales Justin
Just in case this can help fixing this in AS8.
---
https://gist.github.com/alesj/5377690
---
java.lang.IllegalArgumentException: className is null
at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:59)
at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:33)
at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:173)
at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:576)
at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:629)
at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:541)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:480)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:96)
at org.jboss.as.logging.logmanager.ConfigurationPersistence.configure(ConfigurationPersistence.java:128)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:262)
at java.util.logging.LogManager$2.run(LogManager.java:267)
at java.util.logging.LogManager$2.run(LogManager.java:265)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:265)
at java.util.logging.LogManager.getLogManager(LogManager.java:248)
at java.util.logging.Logger.<init>(Logger.java:225)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1289)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1287)
at java.util.logging.LogManager$1.run(LogManager.java:179)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:156)
at org.jboss.modules.Main.main(Main.java:313)
11:12
11 years, 7 months
Can not run testsuite (current AS8 upstream)
by Wolf-Dieter Fink
Hi,
I'm not able to run the integration tests due to missing dependencies.
I pulled the current upstream and start with a fresh maven repository,
but still no success :(
Any idea?
- Wolf
[wfink jboss-as]$ ./integration-tests.sh
/data/devel/github/AS7/jboss-as/tools/maven/bin/mvn -s
../tools/maven/conf/settings.xml install -Dts.smoke
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator
[INFO] JBoss Application Server Test Suite: Integration
[INFO] JBoss Application Server Test Suite: Integration - Smoke
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building JBoss Application Server Test Suite: Aggregator
8.0.0.Alpha1-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @
jboss-as-testsuite ---
[WARNING]
Dependency convergence error for
org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ejb3:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-jpa-spi:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.ws.native:jbossws-native-core:4.1.1.Final
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.1.Final
[WARNING]
Dependency convergence error for org.apache.juddi:uddi-ws:3.1.3 paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:juddi-client:3.1.3
+-org.apache.juddi:uddi-ws:3.1.3
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi.scout:scout:1.2.6
+-org.apache.juddi:uddi-ws:3.0.2
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:uddi-ws:3.1.3
[WARNING]
Dependency convergence error for
org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
paths to dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-javax.enterprise:cdi-api:1.0-SP4
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ee:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.weld:weld-core:1.1.12.Final
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
[WARNING] Rule 1:
org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Failed while enforcing releasability the error(s) are [
Dependency convergence error for
org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ejb3:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-jpa-spi:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.2.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.ws.native:jbossws-native-core:4.1.1.Final
+-org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:1.0.1.Final
,
Dependency convergence error for org.apache.juddi:uddi-ws:3.1.3 paths to
dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:juddi-client:3.1.3
+-org.apache.juddi:uddi-ws:3.1.3
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi.scout:scout:1.2.6
+-org.apache.juddi:uddi-ws:3.0.2
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.apache.juddi:uddi-ws:3.1.3
,
Dependency convergence error for
org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
paths to dependency are:
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-javax.enterprise:cdi-api:1.0-SP4
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-ee:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.1.Final
and
+-org.jboss.as:jboss-as-testsuite:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.as:jboss-as-build:8.0.0.Alpha1-SNAPSHOT
+-org.jboss.weld:weld-core:1.1.12.Final
+-org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Beta1
]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator ... FAILURE [8.057s]
[INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8.714s
[INFO] Finished at: Fri Apr 12 15:57:38 CEST 2013
[INFO] Final Memory: 56M/404M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.2:enforce
(ban-bad-dependencies) on project jboss-as-testsuite: Some Enforcer
rules have failed. Look above for specific messages explaining why the
rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
11 years, 7 months
as7-master-testsuite-ip6 - Build # 7262 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 7262 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/7262
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
4 tests failed.
FAILED: org.jboss.as.test.integration.autoignore.AutoIgnoredResourcesDomainTestCase.test23_RestartDomainAndReloadReadOnlyConfig
Error Message:
null
FAILED: org.jboss.as.test.integration.autoignore.AutoIgnoredResourcesDomainTestCase.test30_ChangeServerGroupSocketBindingGroupGetsPushedToSlave
Error Message:
java.lang.IllegalStateException
FAILED: org.jboss.as.test.integration.autoignore.AutoIgnoredResourcesDomainTestCase.test31_ChangeServerGroupProfileGetsPushedToSlave
Error Message:
java.lang.IllegalStateException
FAILED: org.jboss.as.test.integration.autoignore.AutoIgnoredResourcesDomainTestCase.test40_ChangeServerGroupProfileAndGetDeployment
Error Message:
java.io.IOException: java.lang.IllegalStateException
11 years, 7 months
Web Console: Project Consolidation
by Heiko Braun
Looking at the all the assets we've created in the past year, we've reached a point where it seems reasonable move the web console project to a custom repository and consolidate modules that did exist at various locations.
Beginning with AS8 we'll maintain the web console in a dedicated repository at github.com that contains the other assets as well:
https://github.com/hal
Currently this breaks down into:
- release-stream: Release stream for HAL that can be used across projects and products.
- core: Core Console & SPI
- ballroom: Common JBoss Widgets and Look&Feel
- launchpad: Development utility
- dmr.js: DMR in plain JS
What does it mean for developers?
- Maven coordinates
The maven artefact names remain the same.
- Issue tracking
The console project will become a custom issue tracker to simplify maintenance of the various components.
- Release Coordination
The web console always used to be an external component to the AS and this remains the same.
- Top Level Project (i.e. http://jboss.org/hal)
No, probably not. Unless we start to see a growing demand in the community.
FAQ
Q: Why is the project called HAL?
A: No 9000 computer has ever made a mistake or distorted information. We are all, by any practical definition, foolproof and incapable of error.
11 years, 7 months
Naming Issues
by Eduardo Martins
Hi all, I have been looking at whole code of service based naming stores, and we have several more issues (beyond the injection without lookup), some which may motivate deep changes on the logic:
1. Subcontext created not stored
InitialContext context = new InitialContext();
context.createSubcontext("a");
Context a = (Context) context.lookup("a");
The lookup above fails, and this due to not creating sub contexts on the store. I discussed this briefly with David last week, seems a bug, but it could also be done this way as a feature. As it is now implemented, a context only exists if there a child entry.
Obviously by not having sub contexts we also fail on managing sub contexts environments, it is always null, when it should start as the parent context's one, and store changes on its own.
Note that this implementation choice was clearly made on purpose, there is no destroyContext() impl at all (other than name validation and check for writable store type).
This implementation choice saves the storing of a few msc services, but that also means no dependencies to contexts will exist
2. (Re)Bind without parent context
Context a = null;
InitialContext context = new InitialContext();
try {
a = (Context) context.lookup("a");
} catch (NameNotFoundException e) {
context.bind("a/b",new Object());
}
The bind above will succeed, i.e. we allow binds without parent context, but according to Context javadocs bind or rebind require that the parent context exists.
3. Linkrefs madness
Currently the lookup logic, wrt links is more or less: lookup a msc service with the provided name, and if nothing found look for a parent msc service, which if exists and is a link then we try again with link value + remaining name. Then on bind we do not follow links, we bind directly to the provided name, so:
InitialContext context = new InitialContext();
context.bind("a1",new LinkRef("a2"));
context.bind(new CompositeName("a2","b"),new Object());
context.bind(new CompositeName("a1","b"),new Object());
context.lookup(new CompositeName("a1","b"));
context.lookup(new CompositeName("a2","b"));
This will bind 2 values to the same "logic" name, and both lookups will work, yet return the different values. To fix this on bind we should first lookup the parent context, which if follows links correctly, would have failed context.bind(new CompositeName("a1","b"),new Object())
There are also obvious link related issues on msc deps: if something is bound using a name that contains a link, lookup deps will only work if use the name used in bind. Fixing this part may be scary, msc would need to know that when a link is bound, deps to both linksource/x and linktarget/y may become satisfied. Still on msc topic, rebind support is also a problem.
4. Other issues
There are other issues, for instance rebind does unbind+bind, and this would mean that any state (such as env on the old entry) is lost, msc deps get screwed, etc. but I did not check these with testing yet, and we can probably target these later.
5. So, how do we fix all of this?
Well, for a start should we fix it? I know some people may want to avoid these kind of changes, but naming is not quite something that is going away any soon, and imho our naming is broken at so many ways...
IF we go for fixing it, start by adding and requiring the missing contexts, while at same time provide an option for create these automatically on bind, to be used on everything besides direct jndi app code, avoiding changes on binding code everywhere on AS projects.
And then reverse the bind/lookup logic wrt links, first lookup the parent, to follow links properly, and only then bind/lookup the terminal part of the name. Wrt implementation this would also mean that we probably would make it much faster by having each context with a map of terminal name childs, dunno about memory... Currently we have in each store a ConcurrentSkipListSet, and use lower/ceiling functionally to navigate through it.
Wrt MSC, we could for a start try to not fix all at once, as I have been saying to David, thus ignore the existence of links targets, BUT ensuring all understand the limitations for dependencies if links are used. Anyway I believe David wants to go further on this so I will just leave it for him to comment.
--E
11 years, 7 months
JSF Groovy support in AS8?
by ssilvert＠redhat.com
Mojarra has supported Groovy for quite some time now. It's kind of neat
because you can prototype JSF artifacts with Groovy and achieve dynamic
reloading of these artifacts during development. Here is the original
introduction to this feature from way back in 2008.
https://blogs.oracle.com/rlubke/entry/groovy_mojarra
Today, if you want to use this feature with AS you have to download
Groovy and package it with your WAR.
I have the code already written to add Groovy support to AS8 and it
works well. The only downside is that it introduces a module for
groovy-all.jar, which is about 6MB.
Any thoughts?
Stan
11 years, 7 months
