[JAVASERVERFACES_SPEC_PUBLIC-1242] Remove OpenAjax hub from Specification Created: 17/Dec/13  Updated: 12/Aug/15  Resolved: 12/Aug/15

Status: Resolved
Project: javaserverfaces-spec-public
Component/s: Documentation: Javadoc, TLDDoc, RenderkitDoc, PDF
Affects Version/s: 2.0, 2.1, 2.2
Fix Version/s: 2.3

Type: Task Priority: Critical
Reporter: Ed Burns Assignee: Manfred Riem
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File changebundle.txt    


My question here in this group is: should we remove our mention and
usage of OpenAjax in the JSF spec?

EB> 13.2 JavaScript Namespacing

EB> JavaScript objects that are not enclosed within a namespace are global,
EB> which means they run the risk of interfering, overriding and/or
EB> clobbering previously defined JavaScript objects. This section defines
EB> the requirements for implementations intending to use the JavaServer
EB> Faces 2.0 JavaScript API.

EB> The Open Ajax Alliance is an organization of leading vendors, open
EB> source projects, and companies using Ajax. Their prime objective is to
EB> accelerate customer success with Ajax, through the use of open
EB> standards. The Open Ajax Registry is an industry-wide Ajax registration
EB> authority managed by the OpenAjax Alliance. The Registry maintains
EB> industry- wide lists of Ajax runtime libraries to help prevent object
EB> collisions.

EB> There is a top level namespace jsf that is registered with the Open Ajax
EB> Alliance:

EB> Java Ajax:

Unknown macro: {EB> namespaceURI}

EB> [P1-start openajax registration]If the OpenAjax library is available,
EB> libraries must register themselves using OpenAjax.registerLibrary() at
EB> the time when the JavaScript files are fetched and parsed by the
EB> browser\u2019s JavaScript engine. [P1-end]

EB> if (typeof OpenAjax != "undefined" &&
EB> typeof OpenAjax.hub.registerLibrary != "undefined")

Unknown macro: {EB> OpenAjax.hub.registerLibrary("jsf", "www.sun.com", "1.0",EB> null); }

EB> –
EB> 8<---------------

EB> Unfortunately, I now see this text on the website:

EB> "The following organizations were Members of OpenAjax Alliance at the
EB> time OpenAjax Alliance terminated formal operations:" A little research
EB> revealed this email about the termination:

EB> http://openajax.org/pipermail/steeringcommittee/2012q4/001015.html

EB> And this article, now nearly four years old.

EB> https://devcentral.f5.com/articles/5-years-later-openajax-who#.UqdusoG7liw

EB> Basically, it seems OpenAjax is dead. Anyone care to comment on whether
EB> we should bother with it in JSR-362?

Comment by Ed Burns [ 01/Aug/14 ]

Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

Comment by Ed Burns [ 13/Aug/14 ]

FWIW, I just updated the wikipedia page for Open Ajax Alliance to state that it has terminated operations.

Comment by Manfred Riem [ 12/Aug/15 ]

Implementation changes

Comment by Manfred Riem [ 12/Aug/15 ]

Applied to 2.3 trunk,

svn commit -m "Fixes https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1242, Remove OpenAjax hub from Specification (implementation side)"
Sending jsf-api/src/main/resources/jsf.js
Transmitting file data .
Committed revision 14997.

Comment by Manfred Riem [ 12/Aug/15 ]

Applied to 2.3 spec,

svn commit -m "Fixes https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1242, Remove OpenAjax hub from Specification"
Sending spec/frame/ajaxIntegration.fm
Transmitting file data .
Committed revision 1169.

Generated at Mon Feb 20 07:30:57 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.