| Item |
Type |
Comment |
Response |
| 2.1 |
Clarification |
I assume this file layout applies to all distributions building on top of the Open Source Edition (Oracle GlassFish Server, Java EE SDK, ...) and cannot be modified by products layers on top of it |
Yes, this is true for IPS image based distributions derived from Open Source Edition - I made an attempt to clarify this aspect in current revision. |
| 4.5.1.1 |
Additional description |
lib/ directory is also meant for legacy/compatibility JARs such as appserv-rt.jar |
Note added in current revision. |
| 4.5.1.1 |
Question |
should directories such as monitor/ be grouped in a value-add/ directory (name TBD) to convey that they're not part of the initial distro and potentially not open source |
Actually, glassfish/lib/monitor contains btrace monitoring implementation which is available in open source edition distribution. We do have similarly named value-add feature (cough  ) but file layout for value-add components will be specifically discussed in internal file layout and packaging document which will be available shortly. This one-pager is strictly limited to Open Source Edition content. |
| 4.5.1.1 |
Clarification |
As mentioned on the users alias, it can be a good practice to keep the domains directory separate from the rest of the GlassFish binaries. This used to be supported via the AS_DEF_DOMAINS_PATH variable in config/asenv.conf. Since that domain is under IPS' control, will this still be possible and a supported configuration? |
Well, the domain itself is not under IPS control, so yes, this will be perfectly possible. Only glassfish/domains directory is referenced in IPS (and if you remember, this was done to prevent blowing away whole domains content if someone installs and then uninstalls IPS controlled preconfigured domain). Domain1 and everything underneath is created on the fly at build time (for zip distributions) or at install time (for installer distributions) so if someone sets alternative AS_DEF_DOMAINS_PATH value, blows away domain1 directory and then installs an update through pkg/updatetool, everything will still work - domain1 will not get magically resurrected and even the modified asenv.conf will be left in place since we specify preserve flag on that file. The only thing we don't have answer for in this case are potential preconfigured/predeployed domains installed from UC as part of some future addon package, since pkg can handle only content within the same install image directory... |
