| ID |
Date |
Section |
Comment |
Status |
| km-000 |
16 Oct 2008 |
Overall |
Excellent Efforts! |
RESOLVED  %% |
| km-001 |
16 Oct 2008 |
Pg.9/Section on Default Paths/as-install |
Check with Snjezana@dev.java.net about default path for Windows. It has changed, recently. Also in configuration files, this is represented as $
Unknown macro: {com.sun.aas.installRoot}
|
RESOLVED |
| km-001 |
16 Oct 2008 |
Pg.9/Section on Default Paths/domain-root-dir |
You should say this is the location where a domain is created (using asadmin create-domain command) by default. |
RESOLVED |
| km-002 |
16 Oct 2008 |
Pg.9/Section on Default Paths/domain-dir |
There is no default value for this. It's the name of the "folder" where a domain's configuration will be stored on the file system of your computer. Also, change to description to say that "In configuration files, this is represented as $
Unknown macro: {com.sun.aas.instanceRoot}
". |
RESOLVED |
| km-003 |
16 Oct 2008 |
Pg.9/Section on Default Paths/instance-dir |
Remove this. It does not apply to Prelude. |
RESOLVED |
| km-004 |
16 Oct 2008 |
Pg.13/Notes |
It is better to say it does not support EJB's rather than EJB modules, since EJB's now can be placed in a web application. |
UNRESOLVED Not sure how to resolve this one, but it's low priority. |
| km-005 |
16 Oct 2008 |
Overall |
I think it is very important for people to realize two things: 1. There is no schema or DTD for domain.xml in v3. 2. The server's configuration is dictated by the Java interfaces with appropriate annotations and domain.xml serves as a seed for that configuration. At any point in time, the overall structure of an XML element present in domain.xml is clearer when one sees the Java interface in the package (com.sun.enterprise.config.serverbeans). Thus these Java interfaces take the place of DTD in previous releases. |
RESOLVED |
