| Item |
Type |
Comment |
Response |
| 2.1 |
Clarification |
need to spell out that (a) if an app runs in "standard" GlassFish, it'll run in embedded and (b) no clustering will be supported |
(a) That is 2.1(2). Improved wording to clarify scope. (b) See 4.4, out of scope. |
| 2.2 |
Need further investigation |
We do have real users... Try EHCache (Greg Luck) and Arquillian (Aslak Knutsen) |
I got one requirement from Greg Luck, which is now implemented. Do not have more details of other customer use cases yet. |
| 4.1.1 |
Clarification |
will those two modes allow for the use of a custom domain.xml? |
Yes. Updated 4.1.1 |
| 4.1.1 |
Clarification |
sample deployment mechanisms: Java Web Start, with an installer, with a simple Zip, as a native OS package (RPM, deb, IPS) |
Update 4.1.1 |
| 4.1.3 |
Priorities |
Do we really need ant tasks? Fallback would be the app launcher feature (java -jar glassfish.jar application.war) |
This is needed just to run devtests in embedded mode. This is mentioned in 4.1.3 |
| 4.10.2 |
Suggestion |
glassfish-embedded-all.jar, glassfish-embedded-web and glassfish-embedded-nucleus.jar could also be made available via the GlassFish update center (/contrib most likely as this is for developers only). Same goes for ant tasks. |
Updated 4.10.2 |
