| Item |
Section |
Comment |
Response |
| hong-1 |
3.1 Problem Area, #2, WebLogic deployment descriptor support |
What kind of tooling support do we plan to have for web logic deployment descriptors? Editing the deployment descriptor files or there is more to it? |
addressed in changes to document |
| hong-2 |
4.4 Out of Scope |
Can you clarify this "Users will not be able to leverage the application versioning feature as part of their project development workflow."? Is this project development workflow something built in the NetBeans IDE? ::: For the new content added, one more clarification please, when you say alternate source directory, you meant we will use different source directories for the versioning support, right? As the versioning with directory deployment requires the source comes from a different directory for each version. |
addressed in changes to document |
| arun-1 |
Section 2.2, Assumption 4 |
Since we are not investing in Dynamic Languages anymore, have we taken an explicit decision to not bundle GlassFish in the Ruby bundle ? I'm fine with it but I think we should just clarify it. |
addressed in changes to document |
| arun-2 |
3.1 |
will there be a capability to deploy an OSGi bundle directly to GlassFish ? |
addressed in changes to document |
| arun-3 |
4.4 |
Will the users still be able to specify a name + version when deploying an application ? This might be a useful feature. |
The use of the word still is incorrect in your comment. Users have NEVER had the ability to specify a name and version for a Java EE project in NetBeans. addressed in changes to document |
| arun-4 |
3.1 |
Any ability to run a Java EE app in GlassFish Embedded ? |
addressed in changes to document |
