[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3286) Support for controlled declarative destruction of part (or all) of the ConversationStack
1:52 p.m.
Support for controlled declarative destruction of part (or all) of the ConversationStack
----------------------------------------------------------------------------------------
Key: JBSEAM-3286
URL: https://jira.jboss.org/jira/browse/JBSEAM-3286
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.2.GA
Reporter: Francisco Jose Peredo Noguez
I think the solution proposed in JBSEAM-1943 is insufficient, it should allow for precise
declarative control of how many levels of nested conversations should be destroyed (all of
them or only some of them) using an EL expression, and not just the destruction of the
entire ConversationStack.
For example to end all nested conversation (but not root) (regardless of the nesting
levels) something like:
@End(levels="#{conversation.nestingLevel}")
to end the root conversation (regardless of the nesting levels) something like
@End(levels="#{conversation.nestingLevel+1}")
to end two levels:
@End(levels="#{2}"
Of course that means we would need to add the nestingLevel to conversation component (or
create a new component to deal with this).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3286) Support for controlled declarative destruction of part (or all) of the ConversationStack
[
https://jira.jboss.org/jira/browse/JBSEAM-3286?page=com.atlassian.jira.pl...
]
Francisco Jose Peredo Noguez updated JBSEAM-3286:
-------------------------------------------------
Description:
I think the solution proposed in JBSEAM-1943 is insufficient, it should allow for precise
declarative control of how many levels of nested conversations should be destroyed (all of
them or only some of them) using an EL expression, and not just the destruction of the
entire ConversationStack.
For example to end all nested conversation (but not root) (regardless of the nesting
levels) something like:
@End(levels="#{conversation.nestingLevel}") or <end-conversation
levels="#{conversation.nestingLevel}"/>
to end the root conversation (regardless of the nesting levels) something like
@End(levels="#{conversation.nestingLevel+1}") or <end-conversation
levels="#{conversation.nestingLevel+1}"/>
to end two levels:
@End(levels="#{2}" or <end-conversation levels="#{2}"/>
Of course that means we would need to add the nestingLevel to conversation component (or
create a new component to deal with this).
was:
I think the solution proposed in JBSEAM-1943 is insufficient, it should allow for precise
declarative control of how many levels of nested conversations should be destroyed (all of
them or only some of them) using an EL expression, and not just the destruction of the
entire ConversationStack.
For example to end all nested conversation (but not root) (regardless of the nesting
levels) something like:
@End(levels="#{conversation.nestingLevel}")
to end the root conversation (regardless of the nesting levels) something like
@End(levels="#{conversation.nestingLevel+1}")
to end two levels:
@End(levels="#{2}"
Of course that means we would need to add the nestingLevel to conversation component (or
create a new component to deal with this).
Support for controlled declarative destruction of part (or all) of
the ConversationStack
----------------------------------------------------------------------------------------
Key: JBSEAM-3286
URL: https://jira.jboss.org/jira/browse/JBSEAM-3286
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.2.GA
Reporter: Francisco Jose Peredo Noguez
I think the solution proposed in JBSEAM-1943 is insufficient, it should allow for precise
declarative control of how many levels of nested conversations should be destroyed (all of
them or only some of them) using an EL expression, and not just the destruction of the
entire ConversationStack.
For example to end all nested conversation (but not root) (regardless of the nesting
levels) something like:
@End(levels="#{conversation.nestingLevel}") or <end-conversation
levels="#{conversation.nestingLevel}"/>
to end the root conversation (regardless of the nesting levels) something like
@End(levels="#{conversation.nestingLevel+1}") or <end-conversation
levels="#{conversation.nestingLevel+1}"/>
to end two levels:
@End(levels="#{2}" or <end-conversation levels="#{2}"/>
Of course that means we would need to add the nestingLevel to conversation component (or
create a new component to deal with this).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3286) Support for controlled declarative destruction of part (or all) of the ConversationStack
[
https://jira.jboss.org/jira/browse/JBSEAM-3286?page=com.atlassian.jira.pl...
]
Pete Muir commented on JBSEAM-3286:
-----------------------------------
I'm not sure this enough of a common case to require a declarative solution, but I
would be happy to wrap up the logic in a programmatic call.
Submit a patch :-)
If you are set on a declarative approach, then lets wait to see how popular this issue is
(I would be looking for >10 votes to agree to apply the patch).
Support for controlled declarative destruction of part (or all) of
the ConversationStack
----------------------------------------------------------------------------------------
Key: JBSEAM-3286
URL: https://jira.jboss.org/jira/browse/JBSEAM-3286
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.2.GA
Reporter: Francisco Jose Peredo Noguez
I think the solution proposed in JBSEAM-1943 is insufficient, it should allow for precise
declarative control of how many levels of nested conversations should be destroyed (all of
them or only some of them) using an EL expression, and not just the destruction of the
entire ConversationStack.
For example to end all nested conversation (but not root) (regardless of the nesting
levels) something like:
@End(levels="#{conversation.nestingLevel}") or <end-conversation
levels="#{conversation.nestingLevel}"/>
to end the root conversation (regardless of the nesting levels) something like
@End(levels="#{conversation.nestingLevel+1}") or <end-conversation
levels="#{conversation.nestingLevel+1}"/>
to end two levels:
@End(levels="#{2}" or <end-conversation levels="#{2}"/>
Of course that means we would need to add the nestingLevel to conversation component (or
create a new component to deal with this).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5924
days inactive
5924
days old
2 comments
2 participants
participants (2)
-
Francisco Jose Peredo Noguez (JIRA) -
Pete Muir (JIRA)