|
Hi Ivar,
I have created a pull request
#3 with below changes:
- Changed http://xmlns.eclipse.org/xml/ns/jakartaee to https://jakarta.ee/xml/ns/jakartaee in all files
- Changed Java EE to Jakarta EE
- Renamed ejb-jar_3_2.xsds to ejb-jar_4_0.xsds
- Changed version from 3.2 to 4.0 in ejb-jar_4_0.xsds
- Changed EJB to Enterprise Beans in content and comments
- Updated tests to validateAgainst ejb-jar_4_0.xsd
- Changed all tests to resolve schema location in build directory since https://jakarta.ee/xml/ns/jakartaee does not exist
Please review and let me know if further changes are required.
Thanks
Hussain
From: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx <jakartaee-spec-project-leads-bounces@xxxxxxxxxxx> on behalf of Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, March 18, 2020 04:20 PM
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Subject: Re: [jakartaee-spec-project-leads] XML namespace under Jakarta
Hi,
I have created a spreadsheet with a list of the schemas for Jakarta EE 9 and the projects responsible for them.
Please have a look and add/edit where needed.
Ivar
Scott,
We don't have a Platform call tomorrow. Tomorrow's time slot is reserved for the PMC.
As long as the adopted name doesn't directly affect how it is hosted, then I'm good with this direction. I've posted this question to the Issue:
https://github.com/jakartaee/jakarta.ee/issues/592#issuecomment-581576314
Thanks.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Scott Stark <starksm64@xxxxxxxxx>
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date: 02/03/2020 12:16
Subject: [EXTERNAL] Re: [jakartaee-spec-project-leads] XML namespace under Jakarta
Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
This issue is holding up RC releases as one cannot have a proposed final release without the schemas having a proper namespace. Can we just bring this up for a decision on tomorrow's platform call and move to adopt https://xmlns.jakarta.ee/xml/ns/jakartaee xas
the namespace? The details of the 592 issue regarding how this is hosted under the
jakarta.eewebsite
can be resolved in parallel.
On Wed, Jan 15, 2020 at 9:01 AM Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
Hi all,
Thanks, Bill and Gunnar for providing input!
I have created an issue here: https://github.com/jakartaee/jakarta.ee/issues/592
Please comment on this issue if you see something I have missed or that is wrong...
Ivar
On Wed, Jan 15, 2020 at 8:28 AM Gunnar Morling <gmorling@xxxxxxxxxx> wrote:
Thanks for the info, nice timing :)
If it actually should be a resolveable URL, I'd suggest to go for http*s*, so to play nicely with the general trend towards TLS by default.
That said, does it really have to be a resolveable URL to begin with, or was it also considered to use an URN namespace (https://www.w3.org/TR/uri-clarification/#urn-namespaces)?
Such as "urn:jakartaee:validation:configuration"?
I've been bitten a few times in the past where misconfigured tools or libraries would try and download a schema from the given namespace URL instead of using a local version of the file. That issue is avoided by using URN namespaces which don't create the perception
of being resolveable URLs to begin with.
Both would work from my PoV, but I thought I'd bring it up so do see what others here think.
Best,
--Gunnar
----- Original Message -----
> From: "Bill Shannon" <bill.shannon@xxxxxxxxxx>
> To: "JakartaEE Spec Project Leadership discussions"
> <jakartaee-spec-project-leads@xxxxxxxxxxx>, "Steve Millidge (Payara)"
> <steve.millidge@xxxxxxxxxxx>
> Sent: Wednesday, 15 January, 2020 8:22:22 AM
> Subject: Re: [jakartaee-spec-project-leads] XML namespace under Jakarta
> Just for the record, the proposed path was
> to replace http://xmlns.jcp.org/xml/ns/javaee/...
with
> http://jakarta.ee/xml/ns/jakartaee/...
> So if the old URL has "javaee" in the file name part of the path,
> it would be replaced by "jakartaee" in the file name part of the new
> path, and the host would change to jakarta.ee.
> But we need to wait for Ivar and Eclipse to make a final decision.
> They might decide that they want a subdomain (xmlns.jakarta.ee)
> to better be able to split the traffic based on load.
> Steve Millidge (Payara) wrote on 1/14/20 2:05 PM:
> > This was discussed on the platform call today. My recollection is that Ivar
> > was going to discuss internally at Eclipse and get a resolvable URL we can
> > use on the Jakarta.ee website and once that is agreed we'll put out a
> > namespace recommendation. I think the idea was to add also add jakartaee
> > in the path before the spec name as well as the hostname.
> >
> > Steve
> >
> > -----Original Message-----
> > From: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
> > <jakartaee-spec-project-leads-bounces@xxxxxxxxxxx> On Behalf Of Gunnar
> > Morling
> > Sent: 14 January 2020 21:43
> > To: JakartaEE Spec Project Leadership discussions
> > <jakartaee-spec-project-leads@xxxxxxxxxxx>
> > Subject: [jakartaee-spec-project-leads] XML namespace under Jakarta
> >
> > All,
> >
> > Is there already an agreed on shared namespace prefix for XML descriptors
> > of the different specs?
> >
> > E.g. in Bean Validation we have
> > http://xmlns.jcp.org/xml/ns/validation/configurationand
> > http://xmlns.jcp.org/xml/ns/validation/mapping;
is there any pattern to
> > adopt for Jakarta EE 9?
> >
> > If there's none yet, something like
> > https://xmlns.jakarta.ee/xml/ns/validation/configurationmight
be a first
> > idea? Or rather something that doesn't indicate an actually resolveable
> > URL?
> >
> > Thanks,
> >
> > --Gunnar
> >
> > _______________________________________________
> > jakartaee-spec-project-leads mailing list
> > jakartaee-spec-project-leads@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
> > from this list, visit
> > https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
> > _______________________________________________
> > jakartaee-spec-project-leads mailing list
> > jakartaee-spec-project-leads@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
> > from this list, visit
> > https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
> >
> _______________________________________________
> jakartaee-spec-project-leads mailing list
> jakartaee-spec-project-leads@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
--
Ivar Grimstad
Jakarta EE Developer Advocate |
Eclipse Foundation, Inc.
Eclipse
Foundation: The Platform for Open Innovation and Collaboration
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
--
Ivar Grimstad
Jakarta EE Developer Advocate |
Eclipse Foundation, Inc.
Eclipse
Foundation: The Platform for Open Innovation and Collaboration
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original
message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law,
this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance
on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
|
