spec/javaee8_community_survey_results.pdf

Size: px

Start display at page:

Download "spec/javaee8_community_survey_results.pdf"

Terence Lloyd
5 years ago
Views:

1 Title: Mdel- View- Cntrller (MVC 1.0) Specificatin. Summary/Descriptin: This JSR is t develp MVC 1.0, a mdel- view- cntrller specificatin fr Java EE. Duratin: 2 weeks Sectin 1: Identificatin Specificatin Lead: Santiag Pericas- Geertsen E- Mail Address: santiag.pericasgeertsen@racle.cm Telephne Number: Specificatin Lead: Manfred Riem E- Mail Address: manfred.riem@racle.cm Telephne Number: Initial Grup Membership: TBD Supprting this JSR: TBD Sectin 2: Request 2.1 Please describe the prpsed Specificatin: Mdel- View- Cntrller (MVC) is a cmmn pattern in Web framewrks, where it is used predminantly by HTML- based applicatins. The Mdel refers t the applicatin data, the View t the applicatin's data presentatin and the Cntrller t the part f the system respnsible fr managing input and prducing representatins. The ppularity f the MVC pattern, tgether with the data cllected in the recent Java EE survey: spec/javaee8_cmmunity_survey_results.pdf has prmpted the need fr a standard in this area. Web UI framewrks can be categrized as actin- based r cmpnent- based. In an actin- based framewrk, HTTP requests are ruted t cntrllers and

2 turned int actins by applicatin cde; in a cmpnent- based framewrk, HTTP requests are gruped and typically handled by each cmpnent in an independent manner. The framewrk defined by this JSR falls int the actin- based categry and is, therefre, nt intended t be a replacement fr the cmpnent- based JSF, but simply a different apprach t building Web applicatins n the Java EE platfrm. It is a gal f this JSR t, whenever pssible, leverage existing Java EE technlgies. The Mdel part shuld leverage CDI and Bean Validatin and the View part shuld leverage existing view technlgies like JSPs and Facelets. The expert grup will cnsider whether t leverage existing technlgies such as JAX- RS fr the Cntrller part, whether t invent new technlgy fr the Cntrller part, r whether the Cntrller can be defined in a way that is independent f the technlgy used. It is ut f scpe fr this JSR t define a new view template language; instead existing languages shuld be evaluated and, pssibly, an SPI defined as an extensin fr additinal nes t be integrated. 2.2 What is the target Java platfrm? (i.e., desktp, server, persnal, embedded, card, etc.) This specificatin is targeted fr Java SE 8 r higher and Java EE 8 r higher platfrms. 2.3 The Executive Cmmittees wuld like t ensure JSR submitters think abut hw their prpsed technlgy relates t all f the Java platfrm editins. Please prvide details here fr which platfrm editins are being targeted by this JSR, and hw this JSR has cnsidered the relatinship with the ther platfrm editins. This JSR is targeted fr inclusin in the Java EE 8 platfrm. 2.4 What need f the Java cmmunity will be addressed by the prpsed specificatin? See 2.1 abve. 2.5 Why isn't this need met by existing specificatins? See 2.1 abve. 2.6 Please give a shrt descriptin f the underlying technlgy r technlgies: See 2.1 abve. 2.7 Is there a prpsed package name fr the API Specificatin? (i.e., javapi.smething, rg.smething, etc.) In APIs defined by this JSR will use the rt package name javax.mvc. 2.8 Des the prpsed specificatin have any dependencies n specific perating systems, CPUs, r I/O devices that yu knw f? N. 2.9 Are there any security issues that cannt be addressed by the current security mdel?

3 N. This JSR will leverage existing HTTP security mechanisms prvided by the platfrm Are there any internatinalizatin r lcalizatin issues? This JSR will use the I18N supprt in Java SE Are there any existing specificatins that might be rendered bslete, deprecated, r in need f revisin as a result f this wrk? N Please describe the anticipated schedule fr the develpment f this specificatin. Q Expert Grup frmed Q Early Draft Q Public Review Q Prpsed Final Draft Q Final Release 2.13 Please describe the anticipated wrking mdel fr the Expert Grup wrking n develping this specificatin. The primary means f cmmunicatin will be e- mail. We will slicit feedback frm the cmmunity and leverage the pen surce develpment mdel Prvide detailed answers t the transparency checklist, making sure t include URLs as apprpriate: MVC 1.0 will use a prject site ( spec.java.net) fr annuncements and t track all issues and disseminate infrmatin n the prgress f the JSR. Is the schedule fr the JSR publicly available, current, and updated regularly? Yes, the schedule will be available n the prject page fr the JSR at spec.java.net. Can the public read and/r write t a wiki fr the JSR? N, we'll use a public mailing list fr cmments instead (users@mvc- spec.java.net). Is there a publicly accessible discussin bard fr the JSR that yu read and respnd t regularly? The mailing lists available at spec/lists. Have yu spken at cnferences and events abut the JSR recently?

4 We plan t publicly annunce the MVC 1.0 JSR at JavaOne Are yu using pen- surce prcesses fr the develpment f the RI and/r the TCK? The Reference Implementatin will be develped as an pen surce prject n java.net. The final RI will be available frm the dwnlad page. The TCK is nt pen surce. What are the Terms f Use required t use the cllabratin tls yu have prepared t use with the Expert Grup, s that prspective EG members can judge whether they are cmpatible with the JSPA? The java.net terms f use are available at What is the lcatin f yur publicly- accessible Issue list? In rder t enable EC members t judge whether Issues have been adequately addressed, the list must make a clear distinctin between Issues that are still pen, Issues that have been deferred, and thse that are clsed, and must indicate the reasn fr any change f state. All issues related t the specificatin will be tracked in the publicly accessible MVC specificatin prject issue tracker ( The issue tracker link is als accessible frm the JSR prject page. What is the mechanism fr the public t prvide feedback n yur JSR? The user's e- mail alias users@mvc- spec.java.net. Where is the publicly- accessible dcument archive fr yur Expert Grup? Als available at java.net spec/dwnlads. Des the Cmmunity tab fr my JSR have links t and infrmatin abut all public cmmunicatin mechanisms and sites fr the develpment f my JSR? Yes, see spec.java.net/. D yu have a Twitter accunt r ther scial netwrking feed which peple can fllw fr updates n yur JSR? Which specific areas f feedback shuld interested cmmunity members (such as the Adpt- a- JSR prgram) prvide t imprve the JSR (please als pst this t yur Cmmunity tab)? In general, any f the areas listed in Sectin 2.1. Fr mre infrmatin, refer t the Cmmunity tab in the JSR page at jcp.rg Please describe hw the RI and TCK will de delivered, i.e. as part f a prfile r platfrm editin, r stand- alne, r bth. Include versin infrmatin fr the prfile r platfrm in yur answer.

5 The reference implementatin will be made available standalne and als as part f the reference implementatin fr the Java EE 8 platfrm. The TCK will be made available standalne and as part f the Java EE CTS Please state the ratinale if previus versins are available stand- alne and yu are nw prpsing in 2.13 t nly deliver RI and TCK as part f a prfile r platfrm editin (See sectins and f the JCP 2 dcument). N/A Please prvide the full text f the licenses that will apply t yur Final Release Specificatin, Reference Implementatin, and Technlgy Cmpatibility Kit, r prvide links t the same. Prpsed licenses are as fllws: Specificatin license RI license Cmmercial use The RI will be available fr cmmercial use under the CDDL 1.1 pen surce license, the GPLv2 with Classpath Exceptin pen surce license, r this RI license. Nn- Cmmercial use The RI will be available fr nn- Cmmercial use under the CDDL 1.1 pen surce license r the GPLv2 with Classpath Exceptin pen surce license. TCK license Cmmercial use The TCK will be available fr cmmercial use under this TCK license. Nn- Cmmercial use As required by the Java Specificatin Participatin Agreement (JSPA), the TCK will be licensed at n charge withut supprt t qualified nt- fr- prfit. The Cmpatibility Testing Schlarship Prgram will verify such qualificatin. Supprt may als be prvided at n charge with apprval f the schlarship bard. Fr mre infrmatin, please refer t: html 2.18 Please describe the cmmunicatins channel yu have established fr the public t bserve Expert Grup deliberatins, prvide feedback, and view archives f all Expert Grup cmmunicatins

6 The Expert Grup will cnduct business n a publicly readable alias. The public will have an alias n which t prvide feedback and discuss issues related t the JSR. There will als be a publicly accessible JIRA and dcument archive. (See als 2.19 and 2.20 belw.) 2.19 What is the URL f the Issue Tracker that the public can read, and hw des the public lg issues in the Issue Tracker? Please prvide the lcatin f the publicly accessible dcument archive yu have created fr the Expert Grup. spec/dwnlads Sectin 3: Cntributins 3.1 Please list any existing dcuments, specificatins, r implementatins that describe the technlgy. Please include links t the dcuments if they are publicly available. Fr mre infrmatin n the MVC pattern, please refer t: view- cntrller. There are numerus implementatins f this pattern available fr the Java platfrm. An example f such an implementatin is the extensin available in the JAX- RS Reference Implementatin ( guide.html#mvc). 3.2 Explanatin f hw these items might be used as a starting pint fr the wrk. The MVC pattern is mature and well understd by the Java cmmunity. The EG will cnsider existing implementatins and decide which, if any, t use as a starting pint.

JSR Java API for JSON Binding (JSON- B)

JSR Java API for JSON Binding (JSON- B) JSR Java API fr JSON Binding (JSON- B) Title: * Java API fr JSON Binding (JSON- B) Summary: * A standard binding layer (metadata & runtime) fr cnverting Java bjects t/frm JSON messages. Sectin 1: Identificatin