it looks like that some of the dependencies are missing in Maven Central
. This does not matter if using Maven to resolve artifacts but fails
with Gradle that is ignoring <repository> element in pom.xml files.
Any chance that org.jboss:staxmapper:jar:1.1.0.Final can be synced to
Maven Central? Or its newer version?
[INFO] +- org.jboss.as:jboss-as-controller:jar:7.2.0.Final:compile
[INFO] | +- org.jboss.modules:jboss-modules:jar:1.2.0.CR1:compile
[INFO] | +- org.jboss.msc:jboss-msc:jar:1.0.4.GA:compile
[INFO] | \- org.jboss:staxmapper:jar:1.1.0.Final:compile
I've released WildFly Core 1.0.0.Alpha11 and integrated it into the
master branch of full WildFly.
We'll shoot to get back on the weekly release cadence previously
discussed on this list.
Senior Principal Software Engineer
JBoss by Red Hat
JDK 9 Early Access with Project Jigsaw build b36 is available on
The goal of Project Jigsaw  is to design and implement a standard
module system for the Java SE Platform,
and to apply that system to the Platform itself and to the JDK.
As described in JEP 220 , this build provides a new runtime image
structure. For example, this new runtime
image does not install an rt.jar file or a tools.jar file.
Please refer to Project Jigsaw's updated project pages  &  and
Mark Reinhold's announcement email 
for further details.
We are very interested in your experiences testing this build. Comments,
questions, and suggestions are
welcome on the jigsaw-dev mailing list or else submit bug reports via
Note: If you haven’t already subscribed to that mailing list then please
do so first, otherwise
your message will be discarded as spam.
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
For management clients it is tedious and awkward to read resources / attributes in big domains (e.g. return the state of all running servers across all hosts which are part of server group "foo"). Today this requires to setup multiple composite operations *on the client* which need to be executed in a specific order. This proposal suggests a new operation which collects all relevant information *on the server* and returns only the relevant data in one go to the client.
In the admin console we often need to read specific attributes across a domain or across a deeply nested resource:
- List all enabled data sources of the current profile
- Show the port offset of all running servers across all hosts
- Get all users which belong to role Operator
Even for small domains with two server groups and a small number of servers this procedure is awkward and error prone. What makes it even more difficult is the asynchronous nature of the admin console. Soon you end up in a deeply nested callback-hell. Besides that these 'queries' lead to poor performance for big domains with tens of groups, hosts and servers.
# Proposal / Prototype
The GitHub repository at  contains a more detailed description of the problem statement and a working prototype. This includes details such as how to address the requested resources, how the information is retrieved and how to handle errors.
The proposal also includes a way to filter and reduce the resources against a list of attributes and values *before* the response is sent to the client.
 https://github.com/hpehl/map-reduce <https://github.com/hpehl/map-reduce>
JBoss by Red Hat
Generated an app as ...
mvn archetype:generate -DgroupId=test -DartifactId=test
The app has the following files:
- beans.xml and faces-config.xml are using java.sun.com-style
namespaces instead of xmlns.jcp.org-style namespaces.
Filed as https://issues.jboss.org/browse/WFLY-4030
- What is the purpose of test-ds.xml ? It contains:
<!-- The datasource is bound into JNDI at this location. We reference
this in META-INF/persistence.xml -->
This is anyway the default Java EE 7 data source in WildFly.
- src/main/META-INF/persistence.xml refers to this datasource. That
can be removed as well because of the default Java EE 7 data source.
Seems like these are left overs from previous time ?
Can this be cleaned up ? Xavier and I are planning to use this
archetype for our talk at Devoxx in the next few days and would like a
cleaner generated app.