Topics

New javaserverfaces.com

Neil Griffin
 

Hi Kito,

Thanks indeed for doing this. It is very important to have a modern look and updated content.

But the number of sites and URLs are just too much, too much:

* The site you are updating which has easy to remember URLs:
http://www.javaserverfaces.com (also dot org)

* The Mojarra site, which has a URL that isn't quite as easy to remember:
https://javaserverfaces.github.io/

* The Spec site, which has a URL that is difficult (for me, at least) to remember:
https://javaee.github.io/javaserverfaces-spec/

I vote for #2 in order to unify all the sites with an easy to remember URL.


Neil

On 10/31/17 8:05 AM, Josh Juneau wrote:
Hi Kito,
Thanks for doing this!  I really like the look of the updated site.  It provides a fresh and modern feel, and I think it is exactly the face lift that JSF needs.  I personally think it is important to have a user-facing site for JSF, like the one you've created, and still maintain a project spec site separately.  In my opinion, the users of JSF do not necessarily have to get into the nitty gritty details of the specification work, so the sites should be separate, or at a minimum there should be a separate section of the site devoted to the specification work for those who wish to see that level of detail.
Nice work, and I vote for either 1 or 2 in your list.  One question would remain if we chose #2 is if the other specifications for EE4J will be following a similar strategy for their web presence.  It would be good to try and maintain a similar strategy across the platform specs in my opinion.  So if the others are going to choose single location to host spec sites (GitHub perhaps) then JSF should do the same in my opinion.  That is still not yet decided though and I think it will be a while before decisions like that are made.  So in the meantime, I vote for moving forward with a site like the one you've created for the user-facing site.
Josh Juneau
juneau001@... <mailto:juneau001@...>
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
On Tue, Oct 31, 2017 at 6:39 AM, Kito Mann <kito.mann@... <mailto:kito.mann@...>> wrote:
Hello,
As many of you know, javaserverfaces.com <http://javaserverfaces.com> has been out of date for quite some time. I had a contractor of mine create a new version of the site using Jekyll and github so we could have something more collaborative and easy to maintain. The first draft of the site is finished, but still needs to be updated with new content and cleaned up a bit: http://dev.javaserverfaces.com. I started this initiative before the EE4J news, in order to give the community an easy way to update the site. However, with the move to EE4J, it's possible the main JSF spec site may be easier for the community to edit collaboritvely. So, basically, I see three options here:
(1) Update javaserverfaces.com <http://javaserverfaces.com> as originally planned; separate from the JSF spec site
(2) Use javaserveraces.com <http://javaserveraces.com> as the starting point for the new JSF spec site once it has been moved to EE4J
(3) Scrap javaserverfaces.com <http://javaserverfaces.com> and update the spec site collaboratively (once it moves to EE4J?)
Thoughts?
___
Kito D. Mann | @kito99
Expert training and consulting: PrimeFaces, PrimeNG, JSF, Java EE, Polymer, Web Components, Angular
Virtua, Inc. | virtua.tech <http://virtua.tech>
JSFCentral.com <http://JSFCentral.com> | @jsfcentral
+1 203-998-0403 <tel:(203)%20998-0403>
* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com <http://enterprisejavanews.com/>

Kito Mann
 

Hello,

As many of you know, javaserverfaces.com has been out of date for quite some time. I had a contractor of mine create a new version of the site using Jekyll and github so we could have something more collaborative and easy to maintain. The first draft of the site is finished, but still needs to be updated with new content and cleaned up a bit: http://dev.javaserverfaces.com. I started this initiative before the EE4J news, in order to give the community an easy way to update the site. However, with the move to EE4J, it's possible the main JSF spec site may be easier for the community to edit collaboritvely. So, basically, I see three options here:

(1) Update javaserverfaces.com as originally planned; separate from the JSF spec site
(2) Use javaserveraces.com as the starting point for the new JSF spec site once it has been moved to EE4J
(3) Scrap javaserverfaces.com and update the spec site collaboratively (once it moves to EE4J?)

Thoughts?

___

Kito D. Mann | @kito99
Expert training and consulting: PrimeFaces, PrimeNG, JSF, Java EE, Polymer, Web Components, Angular
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral 

* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


 

Hello Kito,

Thanks for reactivating that site. I hate to be the spoilsport here, but based on empirical observations, names that start with "java" tend to be at risk for Oracle asserting their right to use that name. Therefore, I can only advise option 3:

KM> (3) Scrap javaserverfaces.com and update the spec site collaboratively (once it moves to EE4J?)

Thanks,

Ed

Arjan Tijms
 

Hi,

As for the domain name, I have to agree with Ed and be careful about using anything with the name “java” in it.

Once tEE4J (or whatever name the actual project will get) is fullly established, I’d love to see sub domains being used to somewhat emphasise the correlation between the specs.

Eg 


Etc

(The JSF and jpa names are not decided either but just as placeholder)

Just my 2 cents

Kind regards,
Arjan Tijms


On Tuesday, October 31, 2017, Ed Burns <edburns@...> wrote:
Hello Kito,

Thanks for reactivating that site.  I hate to be the spoilsport here, but based on empirical observations, names that start with "java" tend to be at risk for Oracle asserting their right to use that name.  Therefore, I can only advise option 3:

KM> (3) Scrap javaserverfaces.com and update the spec site collaboratively (once it moves to EE4J?)

Thanks,

Ed



Kito Mann
 

Hey Ed,

I think it's fair to point out that javaserverfaces.com/org has been up and running for several years without any complaints with Oracle, and that was before all of the Java EE drama of the past few years.

With respect to the spec site, will there be more extensive collaboration before the EE4J move?

___

Kito D. Mann | @kito99
Expert training and consulting: PrimeFaces, PrimeNG, JSF, Java EE, Polymer, Web Components, Angular
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral 

* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com



On Tue, Oct 31, 2017 at 12:51 PM, Ed Burns <edburns@...> wrote:
Hello Kito,

Thanks for reactivating that site.  I hate to be the spoilsport here, but based on empirical observations, names that start with "java" tend to be at risk for Oracle asserting their right to use that name.  Therefore, I can only advise option 3:

KM> (3) Scrap javaserverfaces.com and update the spec site collaboratively (once it moves to EE4J?)

Thanks,

Ed




Michael Müller
 

Java is an island, isn't is? ;-)


Herzliche Grüße - Best Regards,

Michael Müller
Brühl, Germany
blog.mueller-bruehl.de
it-rezension.de
@muellermi


Read my books
  "Web Development with Java and JSF" (available for short time only): https://leanpub.com/jsf
  "Practical JSF in Java EE 8" (from 2018): http://www.apress.com/us/book/9781484230299
  "Java Lambdas and Parallel Streams": http://www.apress.com/de/book/9781484224861
  "Visitors" a photographic image book: https://leanpub.com/visitors


On 02.11.2017 17:26, Arjan Tijms wrote:
Hi,

As for the domain name, I have to agree with Ed and be careful about using anything with the name “java” in it.

Once tEE4J (or whatever name the actual project will get) is fullly established, I’d love to see sub domains being used to somewhat emphasise the correlation between the specs.

Eg 


Etc

(The JSF and jpa names are not decided either but just as placeholder)

Just my 2 cents

Kind regards,
Arjan Tijms

On Tuesday, October 31, 2017, Ed Burns <edburns@...> wrote:
Hello Kito,

Thanks for reactivating that site.  I hate to be the spoilsport here, but based on empirical observations, names that start with "java" tend to be at risk for Oracle asserting their right to use that name.  Therefore, I can only advise option 3:

KM> (3) Scrap javaserverfaces.com and update the spec site collaboratively (once it moves to EE4J?)

Thanks,

Ed




Kito Mann
 

Ed,

Is there a particular reason you think Oracle would act differently regarding javaserverfaces.com than they have since Dan Allen and co put up the site many, many years ago?

___

Kito D. Mann | @kito99
Expert training and consulting: PrimeFaces, PrimeNG, JSF, Java EE, Polymer, Web Components, Angular
Virtua, Inc. | virtua.tech 
JSFCentral.com | @jsfcentral 

* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com



On Tue, Oct 31, 2017 at 12:51 PM, Ed Burns <edburns@...> wrote:
Hello Kito,

Thanks for reactivating that site.  I hate to be the spoilsport here, but based on empirical observations, names that start with "java" tend to be at risk for Oracle asserting their right to use that name.  Therefore, I can only advise option 3:

KM> (3) Scrap javaserverfaces.com and update the spec site collaboratively (once it moves to EE4J?)

Thanks,

Ed




Edward Burns
 

On Mon, 13 Nov 2017 10:19:08 -0500, "Kito Mann" <kito.mann@...> said:
KM> Is there a particular reason you think Oracle would act differently
KM> regarding javaserverfaces.com than they have since Dan Allen and co put up
KM> the site many, many years ago?

I am not party to that side of the business but I can say that it seems
reasonable that part of the business would be paying more attention to
this sort of thing now, given the desire to do the Java EE to EE4J
transition correctly for all stakeholders.

Thanks,

Ed

--
| 10 business days until CodeEurope Poland 2017
| 56 business days until JavaLand 2018
| @edburns | office: +1 407 458 0017