|
Replies:
3
-
Last Post:
Jan 13, 2009 11:31 AM
by: hzhang_jn
|
|
|
|
|
|
|
Please review and comment on the GlassFish v3 deployment one-pager
Posted:
Jan 8, 2009 2:03 PM
|
|
|
The one-pager for GlassFish v3 deployment is now available for review and comment. The official review period is one week, so please post your comments and feedback as replies to this forum thread by 15 Jan 2009. We will try to consider feedback that arrives after that but we cannot guarantee we will be able to do so.
You can find the one-pager here: http://wiki.glassfish.java.net/Wiki.jsp?page=gfv3-deployment-one-pager
The one-pager describes two key aspects of deployment for the GlassFish v3 JavaOne 2009 release:
- Extensibility APIs (These are the APIs - SPIs, really - which container developers will implement to add a new container type to GlassFish v3.)
- Application management (post-deployment customization of application configuration)
The page for all one-pagers for GlassFish v3 is here: http://wiki.glassfish.java.net/Wiki.jsp?page=V3FunctionalSpecs
Thank you in advance for your comments.
- Tim and Hong
|
|
|
|
|
|
|
Re: Please review and comment on the GlassFish v3 deployment one-pager
Posted:
Jan 10, 2009 7:42 PM
in response to: tjquinn
|
|
|
These are my comments for http://wiki.glassfish.java.net/Wiki.jsp?page=Gfv3DeploymentOnePager&version=4, which appears to be the most recent version of the wiki page.
I am a bit confused by this page... It appears to be talking about things that were 'done' in the GlassFish v3 Prelude release.
If you are making changes to the interfaces, you may want to focus this document on those particular changes or extensions.
It also seems like a large portion of the discussion is about things that I would expect to find in other one-pagers... like a one-pager for the web container, etc.
Specific comments
Section 4.1 : Extensibility i/fs
What are the things that are changing in this release compared to the stuff that is documented in http://docs.sun.com/app/docs/doc/820-6583/ghmon?a=view?
Since these interfaces exist, could you link to the javadoc?
Section 4.1 : Application Management
The proposed commands....
As best I can tell, none of the commands follow the 'standard form' for asadmin command; they don't have an operand. I guess the most logical operand would be the name.
Can an administrator configure an env-entry or context-param that is in a web app that is part of an enterprise application?
The inclusion of the string '-web-' seems unnecessary. If an app doesn't support env-entry or context-param, a '*-config' command would be able to fail.
I also have to disagree with the command design decisions expressed in the last two paragraphs of this section... since there is help at the asadmin subcommand level, including 'completion', overloading a command, to keep the command set small may not be as critical.
vbk
|
|
|
|
|
|
|
|
|
Re: Please review and comment on the GlassFish v3 deployment one-pager
Posted:
Jan 10, 2009 8:02 PM
in response to: tjquinn
|
|
|
This is a question about what isn't in the one-pager...
I had heard that there was going to be support for the 'directory deployment' of enterprise applications where the component modules were not siblings in a single directory...
Did that idea get dropped?
Will it be possible to 'redeploy' a single component of an enterprise app... instead of redeploying the complete ent app?
Thanks,
vbk
|
|
|
|
|
|
|
|
|
Re: Please review and comment on the GlassFish v3 deployment one-pager
Posted:
Jan 13, 2009 11:31 AM
in response to: vbkraemer
|
|
|
> This is a question about what isn't in the
> one-pager...
In general, the deployment one-pager would only list things we commit to deliver in the corresponding release. In next release of v3 (JavaEE6 release), we will be mostly focusing on implementing JavaEE6 related requirements and would not have much time for new features. Most of the new features will come in the final release of v3. And of course, as usual, because of the resource and time constraint, not all the requested features will be delivered. We will evaluate the requests and decide which features to deliver.
>
> I had heard that there was going to be support for
> the 'directory deployment' of enterprise applications
> where the component modules were not siblings in a
> single directory...
>
> Did that idea get dropped?
Now, specifically about this feature:
No, we did not forget about this request. And we are not sure whether we will be able to get this feature in for v3 JavaEE6 release. The basic support for ear is now being worked on (which is a must go-in thing for JavaEE6) and we are not sure how much time we would have left afterwards. Though from the conversation with Jerome, this is something we should be able to support fairly easily once the ear support comes in. We will keep you updated on the status of this (please file a RFE for this if there is not already one opened for it).
>
> Will it be possible to 'redeploy' a single component
> of an enterprise app... instead of redeploying the
> complete ent app?
Now for this one, it will be fairly difficult to support due to classloading issue and other things. Also even if we can make the classloader work for this, most likely we can only support the redeploying of the web module and not ejb module. As most likely, web module would have references to EJBs inside ejb module, and a reloading of the ejb module would require the web module to be reloaded also.
- Hong
|
|
|
|
|
java.net RSS
