WildFly Application Server
Java XSLT HTML Shell Batchfile PowerShell
Latest commit e10fb05 Feb 25, 2017 @kabir kabir committed on GitHub Merge pull request #9703 from wildfly-security-incubator/WFLY-8225_II
[WFLY-8225] Follow up backport of Elytron Integration Work
Permalink
Failed to load latest commit information.
.mvn [WFLY-7963] Require Maven 3.3.1+ and introduce mvnw Feb 15, 2017
appclient WFLY-8027 appclient not wired up for remote EJB invocations Feb 7, 2017
batch [WFLY-8101] Add access constraints to attributes referencing Elytron … Feb 14, 2017
bean-validation WFLY-7711 Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplat… Dec 5, 2016
build Next is 11.0.0.Alpha1 Jul 26, 2016
client [WFLY-7864] Missing dependency to JMS and EJB client BOM Feb 21, 2017
clustering WFLY-8216 Cannot Specify Attribute 'cluster' Within The cache-contain… Feb 23, 2017
connector [WFLY-8225] Follow up backport of ongoing Elytron integration work. Feb 24, 2017
dist WFLY-6705 Namespaces / schema versions of module.xml are out of sync Sep 23, 2016
ee [WFLY-8227] Ensure principalVsRolesMap always gets processed when usi… Feb 24, 2017
ejb3 Merge pull request #9703 from wildfly-security-incubator/WFLY-8225_II Feb 25, 2017
feature-pack WFLY-5029 EJB, Naming and Transactions over HTTP Feb 24, 2017
iiop-openjdk Fix some EJB/CORBA issues Feb 22, 2017
jaxrs [WFLY-8026 570506e] JBEAP-8064 added flags to generate resteasy confi… Feb 3, 2017
jdr [WFLY-8161] use JDR Santizer to obsecure system property passwords an… Feb 17, 2017
jpa Merge branch 'ladybird' into invocation_integration Jan 21, 2017
jsf [WFLY-7908] Bulk update components Jan 21, 2017
jsr77 WFLY-8027 appclient not wired up for remote EJB invocations Feb 7, 2017
legacy [WFLY-8083] WebMigrateOperation shouldn't analyze the add ops until a… Feb 12, 2017
mail WFLY-8070 Passwords and credential-reference should be mutually exclu… Feb 16, 2017
messaging-activemq [WFLY-8140] Fix anonymous authentication for Elytron Feb 22, 2017
mod_cluster WFLY-8119 NPE in mod_cluster stopping Feb 15, 2017
naming WFLY-5029 EJB, Naming and Transactions over HTTP Feb 24, 2017
picketlink WFLY-7711 Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplat… Dec 5, 2016
pojo Next is 11.0.0.Alpha1 Jul 26, 2016
rts WFLY-7786 The getInstance cannot be executed during startup as it tri… Dec 15, 2016
sar WFLY-7711 Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplat… Dec 5, 2016
security [WFLY-7764] - Seting discard attribute checker for initialize-jacc at… Feb 15, 2017
servlet-build Next is 11.0.0.Alpha1 Jul 26, 2016
servlet-dist WFLY-6705 Namespaces / schema versions of module.xml are out of sync Sep 23, 2016
servlet-feature-pack WFLY-5029 EJB, Naming and Transactions over HTTP Feb 24, 2017
spec-api WFLY-5542 Use apache upstream JSTL instead of jboss fork of java.net … Oct 25, 2016
system-jmx Next is 11.0.0.Alpha1 Jul 26, 2016
testsuite WFLY-5029 EJB, Naming and Transactions over HTTP Feb 24, 2017
transactions WFLY-5029 EJB, Naming and Transactions over HTTP Feb 24, 2017
undertow WFLY-5029 EJB, Naming and Transactions over HTTP Feb 24, 2017
web-common Add graceful shutdown support to WebDeploymentBuilder Nov 24, 2016
webservices [WFLY-7998]:Fix NPE in org.jboss.as.webservices.invocation.AbstractIn… Feb 6, 2017
weld WFLY-8210 Fix implicit bean archive ID Feb 23, 2017
xts JBEAP-8290: missing jboss logging internationalization message in XTS Jan 18, 2017
.gitattributes Enable text conversion Aug 17, 2010
.gitignore [WFLY-8175] mvnw wrapper shouldn't deppend on .m2/wrapper location Feb 21, 2017
README.md [WFLY-7963] Require Maven 3.3.1+ and introduce mvnw Feb 15, 2017
build.bat [WFLY-8175] mvnw wrapper shouldn't deppend on .m2/wrapper location Feb 21, 2017
build.sh Merge pull request #9682 from ppalaga/WFLY-8173 Feb 24, 2017
derby.log Add working tck file, rewritten for ordering Feb 2, 2017
integration-tests.bat [WFLY-8175] mvnw wrapper shouldn't deppend on .m2/wrapper location Feb 21, 2017
integration-tests.sh Merge pull request #9682 from ppalaga/WFLY-8173 Feb 24, 2017
mvnw [WFLY-7963] Require Maven 3.3.1+ and introduce mvnw Feb 15, 2017
mvnw.cmd [WFLY-7963] Require Maven 3.3.1+ and introduce mvnw Feb 15, 2017
pom.xml Merge pull request #9707 from stuartwdouglas/WFLY-5029-2 Feb 25, 2017
zanata.xml Update Zanata configuration for the new 7.1 branch. Also upgrade the … Sep 16, 2016

README.md

WildFly Application Server

http://wildfly.org

  • Fast Startup
  • Small Footprint
  • Modular Design
  • Unified Configuration and Management

And of course Java EE7!

Building

Prerequisites:

  • JDK 8 or newer - check java -version
  • Maven 3.3.1 or newer - check mvn -v
  • On *nix systems, make sure that the maximum number of open files for the user running the build is at least 4096 (check ulimit -n) or more, depending on what other i/o intensive processes the user is running.

To build with your own Maven installation:

mvn install

Alternatively, you can use the Maven Wrapper script that downloads and installs (if necessary) the required Maven version to ~/.m2/wrapper and runs it from there. On Linux, run

./mvnw install

On Windows

mvnw install

Starting and Stopping WildFly

Change to the bin directory after a successful build

$ cd build/target/wildfly-[version]/bin

Start the server in domain mode

./domain.sh

Start the server in standalone mode

./standalone.sh

To stop the server, press Ctrl + C, or use the admin console

./jboss-cli.sh --connect command=:shutdown

More information: https://docs.jboss.org/author/display/WFLY10/Getting+Started+Guide

Contributing

https://developer.jboss.org/wiki/HackingOnWildFly

Build vs. Dist directories

After running mvn install, WildFly will be available in two distinct directories, build and dist.

  • The build directory contains a build of WildFly that is based on Maven artifact resolution for module configuration
  • The dist directory, on the other hand, contains a full distributable build of WildFly

Using the build directory makes iterating with subsystem or module development easier since there is no need to rebuild the whole of WildFly or copy JAR files around on every change.

The dist directory is better suited when a full build of WildFly is needed for development or test purposes.

Running the Testsuite

The testsuite module contains several submodules including the following:

  • "smoke" -- core tests that should be run as part of every build of the AS. Failures here will fail the build.
  • "api" -- tests of features that involve end user use of the public JBoss AS 8 API. Should be run with no failures before any major commits.
  • "cluster" -- tests of the WildFly HA clustering features. Should be run with no failures before any major commits.
  • "domain" -- tests of the domain management features. Should be run with no failures before any major commits.
  • "integration" -- tests of a WildFly standalone server's internals. Should be run with no failures before any major commits.
  • "spec" -- tests of features that only involve end user use of the Java EE 7 spec APIs. Should be run with no failures before any major commits.

For basic smoke tests, simply: mvn test

To run all the tests

mvn install -DallTests

Using Eclipse

  1. Install the latest version of eclipse
  2. Make sure Xmx in eclipse.ini is at least 1280M, and it's using Java 8
  3. Launch eclipse and install the m2e plugin, make sure it uses your repo configs (get it from: http://www.eclipse.org/m2e/ or install "Maven Integration for Eclipse" from the Eclipse Marketplace)
  4. In eclipse preferences Java->Compiler->Errors/Warnings->Deprecated and restricted set forbidden reference to WARNING
  5. In eclipse preferences Java->Code Style, import the cleanup, templates, and formatter configs in ide-configs/eclipse in the wildfly-core repository.
  6. In eclipse preferences Java->Editor->Save Actions enable "Additional Actions", and deselect all actions except for "Remove trailing whitespace"
  7. Use import on the root pom, which will pull in all modules
  8. Wait (m2e takes a while on initial import)

License