Re: [grizzly-dev] Dropping the need for grizzly-npn modudule?

[Ed Bratt <ed.bratt@xxxxxxxxxx>]

Right. It's not just one single thing that needs to be updated.  More than likely some of the changes will need to be coordinated across multiple components as well. Regardless, this is fertile ground for the next release.

-- Ed

On 6/22/2018 4:14 PM, arjan tijms wrote:

Hi,

For Payara I already did an initial sweep through my the code a while back. There’s a number of sun.* classes being used, some of which are easy to replace, others which aren’t so easy.

Running on JDK 9 plus does mostly mean that code isn’t jdk 8 compatible anymore. Specifically the options in domain.xml are different as well and no set is compatible with both 8 and 9+.

A number of dependencies use sun.* classes too, which would have to be addressed as well.

On Friday, June 22, 2018, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Hi,

I believe that a more comprehensive Java 9 effort must be undertaken, once we have finished the contribution of all Java EE components.

There are many aspects of GlassFish that are less than ideal (OK, broken) with Java 9. This will need to be addressed at a project level, by the Jakarta Community -- in whatever capacity that community decides to take this on, once the contributions and intellectual property agreements are all settled.

-- Ed

On 6/22/2018 6:11 AM, arjan tijms wrote:

Hi Ed,

Grizzly has already transferred over to Eclipse, see https://github.com/eclipse-ee4j/grizzly

The Tomcat based Servlet engine within GlassFish hasn’t transferred yet though.

On Wednesday, June 13, 2018, Edward Burns <edward.burns@xxxxxxxxxx> wrote:

Hello Grizzly Devs,

I only subscribed to this list to make sure this issue is handed off to
my satisfaction.  I plan to unsubscribe when I have achieved that. 

This is an excerpt from an email I sent to an Oracle internal list
before I was ready to send email to grizzly-dev@xxxxxxxxxxx.

>>>>> On Fri, 27 Apr 2018 07:50:33 -0700, Edward Burns <edward.burns@xxxxxxxxxx> said:

EB> I just received a ping from [a person on the JDK team] asking when
EB> we plan to use the ALPN support in JDK9 in our Servlet 4.0 impl.
EB> This implies we would also stop using the grizzly-npn.jar
EB> bootclasspath approach.  I don't know the answer to that, but I'd
EB> like to file an issue.  I expect this would be filed at Eclipse, but
EB> as far as I know we haven't even donated the Servlet 4.0 impl and/or
EB> Grizzly yet.

So what is the right way for me to file this issue?  Can someone take
this email and file the issue in the right place?

Thanks,

Ed
 
--
| edward.burns@xxxxxxxxxx | office: +1 407 458 0017
_______________________________________________
grizzly-dev mailing list
grizzly-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/grizzly-dev

_______________________________________________
grizzly-dev mailing list
grizzly-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/grizzly-dev