mNo edit summary |
(Add tracker bug) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 24: | Line 24: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | ||
WildFly 8 is the next version of the application server previously known as JBoss Application Server. With the version 8 it makes it possible to run your Java EE 7 applications and much more! | |||
== Owner == | == Owner == | ||
| Line 32: | Line 34: | ||
* Name: [[User:Goldmann| Marek Goldmann]] | * Name: [[User:Goldmann| Marek Goldmann]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: mgoldman@redhat.com | * Email: [mailto:mgoldman@redhat.com mgoldman@redhat.com] | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
| Line 40: | Line 42: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/20 | Fedora 20 ]] | * Targeted release: [[Releases/20 | Fedora 20 ]] | ||
* Last updated: [[User:Goldmann|Marek Goldmann]] ([[User talk:Goldmann|talk]]) 12: | * Last updated: [[User:Goldmann|Marek Goldmann]] ([[User talk:Goldmann|talk]]) 12:05, 9 September 2013 (UTC) | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
| Line 49: | Line 51: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1008494 #1008494] | ||
== Detailed Description == | == Detailed Description == | ||
=== New name === | |||
While the name may be new, WildFly is the eigth version of the project previously known as JBoss AS. | |||
Picking up where JBoss AS 7 left off, Wildfly 8 is JBoss' new community project for rapidly driving forward java application server innovation. | |||
=== Unparalleled Speed === | |||
Experience ground breaking startup speed! | |||
In the highly optimized boot process of WildFly 8, services are started concurrently to eliminate unnecessary waits and to tap into the power of multi-core processors. Non-critical services are kept on ice until first use. | |||
Subsequent boots save additional time by leveraging cached or indexed metadata. | |||
As a result, WildFly offers a 10-fold reduction in startup time over previous versions and even gives Jetty and Tomcat a run for their money. | |||
=== Modular Design === | |||
Hierarchical classloaders are problematic, often causing failed deployments and quirky behavior. The time has come to say goodbye to the parent delegation model and find the path to modularity (i.e. sane classloading). | |||
WildFly does classloading right. It uses JBoss Modules to provide true application isolation, hiding server implementation classes from the application and only loading the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module. Visibility rules have sensible defaults, yet can be customized. | |||
=== Exceptionally Lightweight === | |||
WildFly takes an aggressive approach to memory management to minimize garbage collector pauses, only loads JAR files it needs and uses indexed metadata over full parses. All this keeps the memory footprint exceptionally small. | |||
These optimizations enable AS 7 to run with stock JVM settings and on small devices. It also leaves more headroom for application data and supports higher scalability. | |||
Server profiles can be used to trim unneeded capabilities, allowing you to make the server as lean as possible. | |||
=== Strict Compliance === | |||
JBoss has always been committed to application portability to prevent vendor lock-in. That's why we are aiming to make WildFly Java EE 7 certified. But we didn't stop there! | |||
WildFly boasts an internal test suite based on Arquillian that achieves even more strict compliance to the portability expectations of our community of users. | |||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
Wildfly 8 is the latest and greatest version of the application server developed by Red Hat. This release gives access to the latest technology, including Java EE 7. WildFly available in Fedora would make Fedora strong in the application server space making the platform of choice for system administrators. | |||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the change in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Proposal owners: | The work on making WildFly available to Fedora requires two things: | ||
# Upgrading many packages, since WildFly uses newer versions of the jboss-as dependencies, | |||
# New packages need to reviewed and added into Fedora. | |||
All of above is already done and the wildfly package is available in both Rawhide and Fedora 20 repos. | |||
* Proposal owners: [[User:Goldmann| Marek Goldmann]] | |||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 128: | Line 176: | ||
--> | --> | ||
[[Category: | Fedora 20 includes the [http://wildfly.org/ WildFly] 8 Application Server (formerly JBoss Application Server), a very popular Java EE platform. WildFly is a very fast, modular and lightweight server. WildFly makes it easy to run and manage cluster of servers with many applications deployed. | ||
[[Category:ChangeAcceptedF20]] | |||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 15:29, 16 September 2013
WildFly 8
Summary
WildFly 8 is the next version of the application server previously known as JBoss Application Server. With the version 8 it makes it possible to run your Java EE 7 applications and much more!
Owner
- Name: Marek Goldmann
- Email: mgoldman@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 20
- Last updated: Marek Goldmann (talk) 12:05, 9 September 2013 (UTC)
- Tracker bug: #1008494
Detailed Description
New name
While the name may be new, WildFly is the eigth version of the project previously known as JBoss AS.
Picking up where JBoss AS 7 left off, Wildfly 8 is JBoss' new community project for rapidly driving forward java application server innovation.
Unparalleled Speed
Experience ground breaking startup speed!
In the highly optimized boot process of WildFly 8, services are started concurrently to eliminate unnecessary waits and to tap into the power of multi-core processors. Non-critical services are kept on ice until first use.
Subsequent boots save additional time by leveraging cached or indexed metadata.
As a result, WildFly offers a 10-fold reduction in startup time over previous versions and even gives Jetty and Tomcat a run for their money.
Modular Design
Hierarchical classloaders are problematic, often causing failed deployments and quirky behavior. The time has come to say goodbye to the parent delegation model and find the path to modularity (i.e. sane classloading).
WildFly does classloading right. It uses JBoss Modules to provide true application isolation, hiding server implementation classes from the application and only loading the classes your application needs. Modules, packaged as collections of classes, are peers that remain isolated unless explicitly defined as a dependency of another module. Visibility rules have sensible defaults, yet can be customized.
Exceptionally Lightweight
WildFly takes an aggressive approach to memory management to minimize garbage collector pauses, only loads JAR files it needs and uses indexed metadata over full parses. All this keeps the memory footprint exceptionally small.
These optimizations enable AS 7 to run with stock JVM settings and on small devices. It also leaves more headroom for application data and supports higher scalability.
Server profiles can be used to trim unneeded capabilities, allowing you to make the server as lean as possible.
Strict Compliance
JBoss has always been committed to application portability to prevent vendor lock-in. That's why we are aiming to make WildFly Java EE 7 certified. But we didn't stop there!
WildFly boasts an internal test suite based on Arquillian that achieves even more strict compliance to the portability expectations of our community of users.
Benefit to Fedora
Wildfly 8 is the latest and greatest version of the application server developed by Red Hat. This release gives access to the latest technology, including Java EE 7. WildFly available in Fedora would make Fedora strong in the application server space making the platform of choice for system administrators.
Scope
The work on making WildFly available to Fedora requires two things:
- Upgrading many packages, since WildFly uses newer versions of the jboss-as dependencies,
- New packages need to reviewed and added into Fedora.
All of above is already done and the wildfly package is available in both Rawhide and Fedora 20 repos.
- Proposal owners: Marek Goldmann
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)
Release Notes
Fedora 20 includes the WildFly 8 Application Server (formerly JBoss Application Server), a very popular Java EE platform. WildFly is a very fast, modular and lightweight server. WildFly makes it easy to run and manage cluster of servers with many applications deployed.