Representation of boolean attribute in our XML configuration
by Jeff Mesnil
Out of curiosity, have we made a decision about the XML representation of boolean attributes in the next-generation of our management API?
At the moment, we have 3 different styles:
1. as a empty element <expose-resolved-model/>
2. as an attribute <append value="true”/>
3. as an element text child <backup>true</backup>
What’d be the default style in the next version?
That’s more a question for Tomaz but he’s in PTO :)
jeff
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/
10 years, 3 months
Two More CLI Nice To Haves
by Darran Lofthouse
Just suggesting a couple more items that would be nice to have in the CLI: -
1 - Tab completion at the following point: -
./core-service=management/security-realm=LDAPRealm/authorization=ldap/username-to-dn=
When adding there is only a finite number of child resources that can be
added.
2 - Show the default values for attributes displayed for tab completion: -
[standalone@localhost:9999 / #]
./core-service=management/security-realm=LDAPRealm/authorization=ldap/username-to-dn=username-filter:add(
attribute= base-dn= force= recursive=
user-dn-attribute=
Anyway just a couple of ideas ;-)
Regards,
Darran Lofthouse.
10 years, 3 months
wildfly-core testsuite issues
by Alexey Loubyansky
While moving the cli tests (those that can be) from the wildfly
testsuite to the core, I stumbled upon a couple of puzzling issue which
I don't see running the tests locally but the PR doesn't get a green light.
One of them is maven-based module loading. Some of the tests start the
CLI as a process providing all the command line arguments. These tests
fail with
Failed to resolve artifact
'org.wildfly.core:wildfly-cli:1.0.0.Alpha6-SNAPSHOT'
Looks like it's not installed before the testsuite run. As a workaround,
I, temporarily, pointed jboss.dist to core-dist/target/...
The second problem is establishing a connection to the controller.
Trying to connect, as in wildfly, using
- http-remoting
- TestSuiteEnvironment.getServerAddress()
- TestSuiteEnvironment.getServerPort()
fails with 'The controller is not available at [::1]:9990'.
Any ideas how to fix this?
Thanks,
Alexey
10 years, 3 months
Renaming wildfly-sasl back to jboss-sasl
by Darran Lofthouse
Now that the SASL mechanisms have been moved from wildfly-sasl to
wildfly-elytron I am going to rename the wildfly-sasl project back to
jboss-sasl.
At the same time I am going to rename the 1.x maintenance branch master.
From this point on the jboss-sasl project will remain around for the
purpose of creating 1.x maintenance releases but all upstream work will
be in wildfly-elytron.
The main reason for this notification is to point out that this means
the history on master is not linear as it is being reset to a previous
revision.
Regards,
Darran Lofthouse.
10 years, 3 months
ts.secman: failure since today
by Frank Langelage
Could someone please have a look at this problem, caused by commit
https://github.com/wildfly/wildfly/commit/31220c8aa3a3264651fda0305f95a15...
today (PR https://github.com/wildfly/wildfly/pull/6538).
stuartwdouglas?
kwart?
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
wildfly-ts-integ-secman ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to
/home/jboss/WildFly-9.0/wildfly/testsuite/integration/secman/target/test-classes
[WARNING] CAL10NAnnotationProcessor 0.8.1 initialized
[WARNING] Supported source version 'RELEASE_5' from annotation processor
'ch.qos.cal10n.verifier.processor.CAL10NAnnotationProcessor' less than
-source '1.7'
[INFO]
[INFO] --- maven-checkstyle-plugin:2.12.1:checkstyle (check-style) @
wildfly-ts-integ-secman ---
[INFO] Starting audit...
/home/jboss/WildFly-9.0/wildfly/testsuite/integration/secman/src/test/java/org/jboss/as/testsuite/integration/secman/servlets/CallPermissionUtilServlet.java:51:83:
Unable to get class information for ServletException.
/home/jboss/WildFly-9.0/wildfly/testsuite/integration/secman/src/test/java/org/jboss/as/testsuite/integration/secman/servlets/JSMCheckServlet.java:55:83:
Unable to get class information for ServletException.
/home/jboss/WildFly-9.0/wildfly/testsuite/integration/secman/src/test/java/org/jboss/as/testsuite/integration/secman/servlets/PrintSystemPropertyServlet.java:50:83:
Unable to get class information for ServletException.
Audit done.
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WildFly Test Suite: Aggregator ..................... SUCCESS
[03:11 min]
[INFO] WildFly Test Suite: Integration .................... SUCCESS [
9.882 s]
[INFO] WildFly Test Suite: Integration - Web .............. SUCCESS
[01:50 min]
[INFO] WildFly Test Suite: Integration - Smoke ............ SUCCESS
[03:54 min]
[INFO] WildFly Test Suite: Integration - Security Manager . FAILURE [
12.331 s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 09:25 min
[INFO] Finished at: 2014-08-27T20:24:31+02:00
[INFO] Final Memory: 100M/302M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:checkstyle
(check-style) on project wildfly-ts-integ-secman: An error has occurred
in Checkstyle report generation. Failed during checkstyle execution:
There are 3 checkstyle errors. -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :wildfly-ts-integ-secman
10 years, 3 months
WildFly SASL and WildFly Elytron are Merging
by Darran Lofthouse
Just a FYI, originally we had the jboss-sasl project as a standalone set
of SASL mechanisms - then we started working on WildFly ELytron and
renamed the SASL project wildfly-sasl.
We have now reached the point that dependencies are becoming more
complicated between Elytron and SASL, rather than introducing one or two
additional projects we have decided to take the opposite approach and
merge the SASL project over to Elytron.
David is in the middle of merging the two repositories, once merged it
will all be available at: -
https://github.com/wildfly-security/wildfly-elytron
Note: This does not in any way prevent the SASL mechanisms from being
used as pure SASL mechanisms.
Regards,
Darran Lofthouse.
10 years, 3 months
JDBC stats, clarification needed
by Heiko Braun
I am trying to make sense of the data source stats and need some help. Can someone explain these figures to me? The hit count is smaller then the access count. I would expect the other accesses to show up in the miss count, but they don't. Is it a bug or do I misinterpret these numbers?
[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS/statistics=jdbc:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"PreparedStatementCacheAccessCount" => "41",
"PreparedStatementCacheAddCount" => "6",
"PreparedStatementCacheCurrentSize" => "6",
"PreparedStatementCacheDeleteCount" => "0",
"PreparedStatementCacheHitCount" => "35",
"PreparedStatementCacheMissCount" => "0",
"statistics-enabled" => true
}
}
Regards, Heiko
10 years, 3 months
Splitting up the build, next steps
by Stuart Douglas
Hi all,
So now the core split has been in place for a while we are going to
start to look at splitting the build up further, as per the original plan.
As such the next logical step is to introduce a wildfly-web repo, which
corresponds to the web-build feature pack in the wildfly repo. This
feature pack will basically be a servlet container (think Tomcat or
Jetty), as well as containing core EE and JNDI functionality.
I am hoping to start on this early next week, and don't imagine it will
take too much time, so if anyone has any concerns or questions please
let me know.
Stuart
10 years, 3 months
