Bill, Arch team,
EJB enhancement for GlassFish 3.1 proposes support for retaining SFSB /
EJB Timer state across redeployment (see section 4.1.5 in
http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishv3.1EJBOnePager).
The original proposal was to add a new CLI option to 'asadmin redeploy'
for this purpose called 'keepEjbState' in addtion to the existing
'keepSession' option.
While having two separate options clearly identifies the intent of the
operation, it can be confusing to the user who has both, a web component
and an ejb component in their application (in particular with Java EE 6
allowing to combine both in a single WAR). On the other hand, eusing
'keepSession' option for both purposes can be confusing for applications
that do not have a web component.
One more question: would it make sense to rename 'keepEjbState' to
'keepState' for future (non-EJB) extensions? If yes, would it be even
more confusing to have both options around?
Here are the choices that we are looking at:
1. Add 'keepEjbState' in addtion to 'keepSession'
2a. Add 'keepState' in addtion to 'keepSession'
2b. Deprecate 'keepSession', and use 'keepState' instead
3. Reuse 'keepSession' for any 'keep' option.
Please advice.
thanks,
-marina