I‘m afraid it was grabbed a longer time ago at least end of 2017 maybe from some of the suggestions back then: Estonia .ee Top Level Domain WHOIS server
Domain:
name: jakarta.ee
status: ok (paid and in zone)
registered: 2017-12-11 15:30:48 +02:00
changed: 2017-12-11 15:30:49 +02:00
expire: 2018-12-12
outzone:
delete:
Registrant:
name: MARCARIA.COM
org id: P07026363
country: US
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: 2017-06-06 09:48:18 +03:00
Administrative contact:
name: FUENTEALBA Francisco
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: 2016-05-12 16:34:56 +03:00
Technical contact:
name: FUENTEALBA Francisco
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: 2016-05-12 16:34:56 +03:00
Registrar:
name: NETIM
url:
phone:
changed: 2016-01-04 18:20:26 +02:00
Name servers:
nserver: ns03.trademarkarea.com
nserver: ns02.trademarkarea.com
nserver: ns01.trademarkarea.com
changed: 2017-12-11 15:30:49 +02:00
Estonia .ee Top Level Domain WHOIS server
More information at http://internet.ee Again, it’s Eclipse/EE4J problem not ours, if they are happy to support someone in Estonia, they might get it. Javax. Is strictly to a JSR, if we do not file that and I don’t know if it makes sense with a project that leans so much to the “Cloud Native”, Big Data or “Serverless” side, all the things Oracle no longer wants JSRs for. Javax.sql was and still is closely related to OpenJDK. Although you may use JNoSQL in a desktop or RCP environment, too, I don’t see OpenJDK accepting anything new now that they throw all Java EE related modules out. Werner Sent from Mail for Windows 10 I more like jakarta.ee domain with package ee.jakarta.* than jakartaee.org. Since jakarta.ee is redirecting to a post on tomitribe blog, I assume that is owned by tomitribe which is better than other domaingrabbers :). so wait and watch!
On Thu, Feb 15, 2018 at 8:39 AM, Werner Keil <werner.keil@xxxxxxx> wrote: Manik, +1 I think this makes most sense now. Stay on org.jnosql. Until it is clear, if there should be a new Namespace like org.eclipse.ee4j, org.eclipse.jakartaee or similar (Jakarta.org belongs to the Island of Jakarta and someone on GoDaddy just grabbed https://www.whois.com/whois/jakartaee.org hopefully Eclipse Foundation, but if it is a Domaingrabber, Eclipse Foundation will have to deal with them) Regards, Werner Considering JNoSQL not being part of JCP now, I don’t think we can use javax for any new non-jcp oriented specifications. EE4J and Oracle seems to be clear about who can and who cannot use javax package. Any existing JavaEE APIs that ever led through JCP can retain javax but all new specifications that are not derived by JCP, cannot use javax if it has to be part of new EE4J umbrella. And I am not sure if JCP process is ideal choice now for any new JavaEE targeted APIs. If the plan is to ultimately be part of EE4J umbrella , then my suggestion would be to stay on org.jnosql and wait for the EE4J package finalization. Hopefully before JNoSQL 1.0 is released, move to the new EE4J package whatever it would be. In short, wait for some more time.
I think we should submit a JSR and wait for Eclipse Foundation definition about EE4J process. Eclipse is discussing about EE4J and maybe we can use javax.nosql or just maintain org.jnosql
2018-02-15 9:01 GMT-02:00 Otávio Gonçalves de Santana <otaviopolianasantana@xxxxxxxxx>: Right now, we're stuck in the specification process. Briefly, Java EE has moved to Eclipse Foundation and them still discussion about their process yet. So, there're questions that still remain: - Should we submit a JSR then EE4J?
- What about the package name API? Should we submit a JSR just to keep the javax.nosql?
- What is the submission lifecycle? Could we use a JSR as a template?
ps: I'm sending these question to EE4J too. -- Otávio Gonçalves de Santana
_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev
_______________________________________________ jnosql-dev mailing list jnosql-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jnosql-dev
_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev
|
