Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ch2 WildFly and Java EE 6 #117

Open
mmatloka opened this issue Apr 8, 2014 · 1 comment
Open

Ch2 WildFly and Java EE 6 #117

mmatloka opened this issue Apr 8, 2014 · 1 comment

Comments

@mmatloka
Copy link
Contributor

mmatloka commented Apr 8, 2014 

WildFly

The latest community edition of the application server offered by JBoss has recently been renamed to WildFly, and this will be the default target runtime for our examples. Written from the ground up, WildFly (previously known as JBoss Application Server 7) was designed with the following goals at the core:

Speed
Startup, deployment, and request-processing demands leverage a concurrent-state machine and constant-time class loading.

Efficiency
Memory usage is kept to a minimum.

Modularity
Application libraries and server libraries are isolated from one another to avoid runtime conflicts.

Administration
Centralized settings via web interface, HTTP, Java, and command-line APIs.

Compliance
Java EE6 Full Profile Certification.

WildFly was designed rather with Java EE 7 goal.
@aslakknutsen
Copy link
Member

oops.. seems we forgot to get this one upstream #108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mmatloka @aslakknutsen