Bug 779300 (SOA-1688)

Commented on enclosed .odt file (thanks to Burr for supplying the document)

Attachment: Added: commented_Beta_Release_Notes_v2.odt

5.0.0 Beta1 doc is available on http://redhat.com/docs/JBoss_SOA_Platform/

Darrin - the release notes are not ready for review yet - will you be adding the new feature list in this doc?

Section: 1. Overview

Text: Warning - This is a Beta Release

Comment: Remove this note.   ;-)

-----------------------------------

Not a technical review comment - but I think it's worth changing the opening of the first chapter from this:

==============
JBoss Enterprise SOA Platform is a certified, tested, and supported platform for developing Enterprise Application Integration and Service Oriented Architecture solutions.

It integrates several stable and scalable open source frameworks and solutions including Hibernate, Seam, JBoss Transactions, JBoss Clustering, the JBoss Application Server, and JBoss Enterprise Service Bus (ESB) to provide an infrastructure for enterprise SOA applications.

These community developed and enterprise certified and supported products have been combined and tested to provide a solid, robust, and scalable platform. Powered by legendary JBoss innovation and backed by Red Hat engineering and quality assurance, JBoss Enterprise SOA Platform is the platform of choice for a new generation of enterprise applications.
==============

To this:

==============
JBoss Enterprise SOA Platform is a certified platform for developing Enterprise Application Integration and Service Oriented Architecture solutions.

The Platform integrates several stable open source frameworks and community developed products including Hibernate, Seam, JBoss Transactions, JBoss Clustering, the JBoss Application Server, and JBoss Enterprise Service Bus (ESB) to provide a solid, robust, and scalable infrastructure for enterprise SOA applications.

Powered by JBoss innovation and backed by Red Hat engineering, quality assurance and support, JBoss Enterprise SOA Platform is the platform of choice for a new generation of enterprise applications.

-----------------------------------

Section 2 - New Features in 5.0

Text: 
The JBoss ESB now uses Apache jUDDI version 3 as its UDDI registry. This new version
implements the UDDIv3 specification and includes a subscription API in addition to a new web console. These new capabilities are detailed in the new jUDDI User Guide.

Comment: 
If we reference the jUDDI guide - then we need at least an initial draft of the guide at GA.

Text:
JBoss SOA Administration Console (JOPR)

Comment:
I could not find any direct reference to JOPR in the EAP 5.0 docs - can you check and see how they described the console? Was there a deliberate reason to not reference JOPR?

-----------------------------------

2.1. Technology Previews

Text: 
JBoss Rules Fusion

Comment: It's worth referencing Fusion as a CEP implementation.

-----------------------------------

Section: 3. Components of the 5.0.0 Release

Text:
Apache jUDDI 3.0

Comment:
Should be 3.0.1

-----------------------------------

Not looking at this section as it is out-of-date: 8. Known Issues in this release

2. New Features in 5.0

Message Level Alerting
    This new capability provides monitoring and alerting at both the action and service level. Any individual message that exceeds a defined processing time or size can provide an event that is available through the new Administration Console or the JMX console.
--
It's not possible to have events showing up in the Admin Console - this feature is available only through JON.
Moreover alerts disappear in the JMX Console (SOA-1660)

I've left a comment already for the admin guide in SOA-1531, however maybe it would be good to have this also in the release notes.

Although JON can run under JDK 1.5 and 1.6, the ESB plugin will only work with 1.6. We have tested on both, Sun and OpenJDK, however AFAICT JON is not officially supported on OpenJDK 1.6. 

The ESB plugin can be compiled with either 1.5 or 1.6, but I believe the current SOA build only uses 1.6.

Re: items above

1) Issues without JIRAs: 

* Databases - Customers have to use the new DBs created by SOA-P 5.0
MIGRATION ISSUES as SOA-1196

* Drools - all rules should work, compiled rule packages (*.pkg files) will need to be
MIGRATION ISSUES as SOA-1874

re: items above 2)

* SOA-1549 (JBPAAP-3002, JBWS-2630), Backwards incompatibility in deployment - Invalid
RESOLVED NO NEED TO DOCUMENT

* SOA-1569, Security implication of switch of default profile from "production" to
  "default." In 4.3, the "default" server profile included an exposed "/upload" servlet.
  This servlet must be explictly exposed in 5.0.
REMOVED FROM KNOWN ISSUES AS PER SOA-1932 

* SOA-1645 (JBESB-3002), Smooks does not support parameter addToList anymore.
MIGRATION ISSUES DONE

* SOA-1818, Groovy backwards compatibility 1.0 -> 1.5.4, We are shipping new versions of
  Smooks and Groovy. But, we cannot vet customers' own coding.
MIGRATION ISSUES DONE

* SOA-1874, SOA-P 5 not compatible with BRMS 5.0 (it is compatible with 5.0.1 - mentioned
  above)
DOCUMENTED AS ABOVE

* SOA-1913 (JBPAPP-3618), JBoss Native version 1.1.17 release - SOA-P 5.0 users should not
  install
KNOWN ISSUES DONE

* SOA-1915, CXF - Technical Preview - has not been verified to work with SOA-P 5.0
KNOWN ISSUES DONE

updated New Features: Message Level Alerting 

This new feature provides monitoring and alerting at both the action and service level. Any individual message that exceeds a defined processing time or size can generate an Message Alert that can be accessed using the JMX Console. The JBoss Operations Network Server (JON) ESB plugin collects the Message Alerts and generates JON Events.

Be sure to add https://jira.jboss.org/jira/browse/SOA-1550 to the known open bug list - it WILL NOT be fixed for GA. 

See JBWS-2630 for details.