November 2014 - wildfly-dev - Jboss List Archives

Is there a chance to sync org.jboss:staxmapper to Maven Central?

by Karel Piwko

Hi All, it looks like that some of the dependencies are missing in Maven Central [1]. 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? https://repository.jboss.org/nexus/service/local/repositories/releases/co... Thanks, Karel [1] [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

10 years, 12 months

5
9
0 / 0

WildFly Core 1.0.0.Alpha11 Released

by Brian Stansberry

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. Cheers, -- Brian Stansberry Senior Principal Software Engineer JBoss by Red Hat

10 years, 12 months

1
0
0 / 0

Announcing wildfly extension installer maven plugin

by Libor Zoubek

Hello, I'm happy to announce maven plugin capable of installing JBoss module to WildFly. It provides helpful mojo to: - lay down JBoss module - register extension - setup subsystem - setup socket binding It may become useful for developing/testing WildFly subsystems. If interested, please see blogpost http://lzoubek.blogspot.com/2014/10/wildfly-extension-installer-maven-plu... or documentation http://lzoubek.github.io/wildfly-extension-maven-plugin/ Regards, Libor Zoubek

10 years, 12 months

2
1
0 / 0

JDK 9 Early Access with Project Jigsaw build b36 is available on java.net

by Rory O'Donnell Oracle, Dublin Ireland

Hi Jason/Tomaz, JDK 9 Early Access with Project Jigsaw build b36 is available on java.net [1] The goal of Project Jigsaw [2] 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 [3], 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 [2] & [4] and Mark Reinhold's announcement email [5] 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 bugs.java.com. Note: If you haven’t already subscribed to that mailing list then please do so first, otherwise your message will be discarded as spam. [1] https://jdk9.java.net/jigsaw/ [2] http://openjdk.java.net/projects/jigsaw/ [3] http://openjdk.java.net/jeps/220 [4] http://openjdk.java.net/projects/jigsaw/ea [5] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2014-November/003878.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

10 years, 12 months

1
0
0 / 0

Map / reduce for management operations

by Harald Pehl

TL;DR 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. -------------------- # Background: 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 [1] 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. [1] https://github.com/hpehl/map-reduce <https://github.com/hpehl/map-reduce> --- Harald Pehl JBoss by Red Hat http://hpehl.info

10 years, 12 months

5
14
0 / 0

Issues in wildfly-javaee7-webapp-blank-archetype

by Arun Gupta

Generated an app as ... mvn archetype:generate -DgroupId=test -DartifactId=test -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-javaee7-webapp-blank-archetype -DarchetypeVersion=8.1.0.Final The app has the following files: ./src/main/webapp/WEB-INF/beans.xml ./src/main/webapp/WEB-INF/faces-config.xml ./src/main/webapp/WEB-INF/test-ds.xml - 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: <datasources xmlns="http://www.jboss.org/ironjacamar/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema http://docs.jboss.org/ironjacamar/schema/datasources_1_0.xsd">  <datasource jndi-name="java:jboss/datasources/testDS" pool-name="test" enabled="true" use-java-context="true"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_ON_EXIT=FALSE;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> </datasources> 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. Arun -- http://blog.arungupta.me http://twitter.com/arungupta

10 years, 12 months

5
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev November 2014