Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] Status of GF 5.1.0?

 

Hi Bill,  Thanks for the update. 


Regarding the memory leak issue, it appears that the PR that was discussed wasn’t for eclipse-ee4 fork of the source, hence the issue is still open.  I’ve not been able to locate the changes but they might be in the payara or javaee forks.    


On that subject, are you aware that the javaee repository is still being updated? 


The other issue listed above is regarding the OSGI meta-data.  This is more of an issue for our application as we deploy services into the OSGI container.  In that context, if the meta-data is incorrect then services throw runtime exceptions.  A good example of this the Json-p implementation as the API and service have been split into separate bundles.  As a result, it throws an exception when used by services that are deployed into the OSGI context.  However this doesn’t appear to be a problem for applications deployed in the web context (I.e. war files) 


I’m still a newbie when comes to using Github, as such I'm not familiar with submitting PRs.  Once I figure it out, I’ll update the tickets as appropriate. 


Cheers 

Paul


From: Bill Shannon <bill.shannon@xxxxxxxxxx>
Sent: 06 December 2018 22:27
To: glassfish developer discussions; Paul Stanley
Subject: Re: [glassfish-dev] Status of GF 5.1.0?
 
The focus for the Eclipse GlassFish 5.1 release is simply to replace all the Oracle components with Eclipse components and for the result to pass the Java EE 8 CTS.

If there's bugs in Oracle GlassFish 5.0.1 that also exist in Eclipse GlassFish 5.1, that's ok.  Obviously we'd like any serious bugs to be fixed, but that's not the primary focus.  Bug-for-bug compatible is fine.  If new bugs have been introduced since 5.0.1, we need to evaluate their severity and the cost to fix them.

Hopefully there will be an Eclipse GlassFish 5.1.1 or 5.2 release that can apply more polish and clean up some of these more serious bugs.

For #22539, the discussion mentions a Pull Request, but I don't see it.  A Pull Request against Eclipse GlassFish to fix this issue would make it more likely that the issue would be fixed in 5.1, especially if the fix comes with a unit test or dev test verifying the fix.

Ditto #22635, which doesn't seem serious, but a PR would help.

I wouldn't expect TCK testing to detect either of the above bugs.


Paul Stanley wrote on 12/6/18 7:00 AM:

Hello,  
 
I’m just wondering what the status of the Glassfish project is?  The 5.1.0RC1 release at the end of October, but since then there doesn’t appear to be any attempt to fix any of the issues which have been raised.  For instance the memory leak in the http stack (#22539).   I’ve also come across of a number of features that simply do not work due to incorrect or missing osgi meta-data.  These include JSON-P, ldap-booster-pack-extensions (#22635), jersey-client and the tyrus-client. I would have assumed that these will have been picked up by the Jakarta TCK testing, but I've not seen anything.

 

I realise that everyone is working flat out for the 5.1.0 release so I'm not expecting miracle's, but I was wondering if there was a list of critical issues that will be addressed? 

 
Kind regards, 
Paul 



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

Back to the top