Hi Anissa,
Sorry haven't gotten to this yet. Here you go -

" The Admin Console will be using the Woodstock components, a JSF component set. Since this is an unsupported product, the GUI team has created a branch for our own use and maintains it. It is assumed that this version will not have major fault that prevents the Admin Console from utilizing it or spend significant time in maintaining it."

Not really relevant to the one pager feedback, but there was an issue with the woodstock components in the way it generates sessions. Can we fix that for this release? I had filed an issue for this some time back. Will try to find it and send it to you.

Anisa: Are you referring to https://github.com/javaee/glassfish/issues/10945 ?
Fix Woodstock to use RFC 2109 compliant cookie names.
This is P3, we will look into this for this release.


"The Admin Console is written on top of the JSFTemplating framework, which is a java.net open source project. It is assumed that JSFTemplating will continue to evolve with features to support the Admin Console. However, no major features have been identified for this release."

JSFTemplating builds on jsf-extensions I think. Is there any plan of moving away from jsf-extensions? Cos that is also not really supported and all the features in it are in theory supposed to be in JSF 2.0.

KenPaulsen: JSFTemplating no longer depends on jsf-extensions and hasn't for some time. FYI, We use JSF 2.0 Ajax for most of our Ajax. In some cases (for full page requests, and in cases where we're not using JSF – i.e. the Online Help), we're using plain JS-based Ajax w/o JSF support.


Grizzly enhancement - we should probably have a meeting some time to go over the information you may need. Justin has sent out a write up to the dev alias. Please look at it if you haven't done that and let us know what else you need.
Anissa: Yes, we do need a meeting to discuss this. I will contact you after i read it through.
thanks.
Anissa.

  • Rajiv