-
Notifications
You must be signed in to change notification settings - Fork 55
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.
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
Faces 4.0: rename xmlns.jcp.org taglib URIs #1553
Comments
Should this values be prefixed with "urn:"? Not totally sure what XML allows. |
+1 |
As an expedient, the relevant xsd documents could be revised and uploaded to jakarta.ee/xml/ns/faces (or something suitable) i.e. check them in here. At least, that would be consistent with other Jakarta EE Specs (JakartaEE, JSONB, JSONP, etc. Some IDEs do validate in real-time from the URL locations (Intellij for example). |
There are no XSD documents in first place. Hence the proposal to use URN instead of URL. |
@edbratt Just to emphasise this, for the taglib URIs there are no XSD documents. Because it was the norm to use URLs for them, many people believed there were XSD documents backing them, but this is a totally different concept from say web.xml or faces-config.xml documents. |
Implemented now. Jakarta Tags namespaces have also been remapped.
All old namespaces retain their backwards compatibility. |
@BalusC @arjantijms Could we just introduce our own namespace here for the JSTL tags? We could then completely get rid of the jstl and JSP usage. Just a special case for supporting jakarta.servlet.jsp.jstl.sql.Result. |
I've already coined
@arjantijms already removed it from |
Porting Jakarta EE Tutorial from '9.1' to '10'. Jakarta Faces. Faces 4.0: "Rename xmlns.jcp.org taglib URIs" (jakartaee/faces#1553)
Porting Jakarta EE Tutorial from '9.1' to '10'. Jakarta Faces. Faces 4.0: "Rename 'http://xmlns.jcp.org/jsf/*' URL to 'jakarta.faces.*' URN ((jakartaee/faces#1553))
Since Jakarte EE Faces 4 the xmls namespaces were changed from `http://xmlns.jcp.org/jsf` to `jakarta.*`. (see jakartaee/faces#1553) This change adds new namespace support for: * Generation of new JSF pages * Tag suggestion in faces xhtml editor view * Automatical addition of missing namespace decleration when new taglib is used Reference: apache#6069
Since Jakarte EE Faces 4 the xmls namespaces were changed from `http://xmlns.jcp.org/jsf` to `jakarta.*`. (see jakartaee/faces#1553) This change adds new namespace support for: * Generation of new JSF pages * Tag suggestion in faces xhtml editor view * Automatic addition of missing namespace decleration when new taglib is used In order to support the JSF 4.0 namespaces the `enum` `JsfVersion` in `web.jsfapi` module was introduced. It's used to map the taglib namespaces based on the projects detected JSF version. Note: There's already an enum `JSFVersion` which is not part of the api. Both enums might be merged in the future. Reference: apache#6069
Since Jakarte EE Faces 4 the xmls namespaces were changed from `http://xmlns.jcp.org/jsf` to `jakarta.*`. (see jakartaee/faces#1553) This change adds new namespace support for: * Generation of new JSF pages * Tag suggestion in faces xhtml editor view * Automatic addition of missing namespace decleration when new taglib is used In order to support the JSF 4.0 namespaces the `enum` `JsfVersion` in `web.jsfapi` module was introduced. It's used to map the taglib namespaces based on the projects detected JSF version. Note: There's already an enum `JSFVersion` which is not part of the api. Both enums might be merged in the future. Reference: apache#6069
Since Jakarte EE Faces 4 the xmls namespaces were changed from `http://xmlns.jcp.org/jsf` to `jakarta.*`. (see jakartaee/faces#1553) This change adds new namespace support for: * Generation of new JSF pages * Tag suggestion in faces xhtml editor view * Automatic addition of missing namespace declaration when new taglib is used In order to support the JSF 4.0 namespaces the `enum` `JsfVersion` in `web.jsfapi` module was introduced. It's used to map the taglib namespaces based on the projects detected JSF version. Note: There's already an enum `JSFVersion` which is not part of the api. Both enums might be merged in the future. Reference: apache#6069
Signed-off-by: Jianguo Ma <jiangma@microsoft.com>
Signed-off-by: Jianguo Ma <jiangma@microsoft.com>
Signed-off-by: Jianguo Ma <jiangma@microsoft.com>
…ks Bing AI. (#44) * On branch edburns-msft-ibm-524-update-to-ee-10 Fix indentation. modified: java-app/pom.xml modified: java-app/src/main/liberty/config/server.xml modified: java-app/src/main/resources/META-INF/persistence.xml modified: java-app/src/main/webapp/WEB-INF/faces-config.xml modified: java-app/src/main/webapp/WEB-INF/web.xml Signed-off-by: Ed Burns <edburns@microsoft.com> * fix formatting * On branch edburns-msft-ibm-524-update-to-ee-10 Upgrade to EE 10, but it does not yet build. modified: java-app/pom.xml modified: java-app/src/main/java/cafe/model/CafeRepository.java modified: java-app/src/main/java/cafe/model/entity/Coffee.java modified: java-app/src/main/java/cafe/web/rest/CafeResource.java modified: java-app/src/main/java/cafe/web/view/Cafe.java modified: java-app/src/main/liberty/config/server.xml modified: java-app/src/main/resources/META-INF/persistence.xml modified: java-app/src/main/webapp/WEB-INF/faces-config.xml modified: java-app/src/main/webapp/WEB-INF/web.xml modified: java-app/src/main/webapp/index.xhtml ```bash [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.10:install-feature (package-server) on project javaee-cafe: Error installing features for server defaultServer: CWWKF1299E: The following features could not be obtained: jaxb-4.0 restfulws-3.0 enterprisebeanslite-4.0 cdi-4.0 persistence-3.0 faces-4.0 io.openliberty.emptyHandleListContext-1.0 com.ibm.websphere.appserver.ejbliteJNDI-1.0 com.ibm.websphere.appserver.javaeePlatform7.0-jndi1.0 io.openliberty.ejbliteJPA-2.0 io.openliberty.restfulWS3.0-xmlBinding3.0 com.ibm.websphere.appserver.ejbComponentMetadataDecorator-1.0 com.ibm.websphere.appserver.jakarta-transactionContext-1.0 com.ibm.websphere.appserver.classloaderContext-1.0. Ensure that the features are valid for Open Liberty. -> [Help 1] ``` Signed-off-by: Ed Burns <edburns@microsoft.com> * On branch edburns-msft-ibm-524-update-to-ee-10 With help from @Nathanrauh, got past the problem in #43 (comment) modified: java-app/src/main/liberty/config/server.xml Signed-off-by: Ed Burns <edburns@microsoft.com> * ignore the local coffee.xml * add jsonb-3.0 to enable json binding Signed-off-by: Jianguo Ma <jiangma@microsoft.com> * Use Faces 4.0 URNs, see jakartaee/faces#1553 Signed-off-by: Jianguo Ma <jiangma@microsoft.com> --------- Signed-off-by: Ed Burns <edburns@microsoft.com> Signed-off-by: Jianguo Ma <jiangma@microsoft.com> Co-authored-by: Jianguo Ma <jiangma@microsoft.com>
Signed-off-by: Jianguo Ma <jiangma@microsoft.com>
Proposal: use URNs instead of URLs as URLs are more prone to confuse people.
Rename
http://xmlns.jcp.org/jsf
tojakarta.faces
Rename
http://xmlns.jcp.org/jsf/facelets
tojakarta.faces.facelets
Rename
http://xmlns.jcp.org/jsf/core
tojakarta.faces.core
Rename
http://xmlns.jcp.org/jsf/html
tojakarta.faces.html
Rename
http://xmlns.jcp.org/jsf/passthrough
tojakarta.faces.passthrough
Rename
http://xmlns.jcp.org/jsf/composite
tojakarta.faces.composite
Rename
http://xmlns.jcp.org/jsf/component
tojakarta.faces.component
Thoughts?
The text was updated successfully, but these errors were encountered: