5:22 p.m.
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:26 p.m.
New subject: [JBoss JIRA] Commented: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-135:
-------------------------------------
What about a conversationPropagation parameter ? Possible values could be end, nest or
join.
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 p.m.
New subject: [JBoss JIRA] Commented: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
Nicklas Karlsson commented on CDI-135:
--------------------------------------
if the functionality would be extended, the parameter should probably be renamed to
something like that, yes. But I'm not sure if nest should be an option since the CDI
spec itself doesn't acknowledge this concept.
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 p.m.
New subject: [JBoss JIRA] Commented: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-135:
-------------------------------------
I prefer having a parameter whose values could be extended later than having a parameter
"nocid" that could be replaced on later specs.
Since put this way, the only possible values for this parameter is "end".
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Updated: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-135:
--------------------------
Fix Version/s: 1.1 (Proposed)
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
Fix For: 1.1 (Proposed)
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Commented: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-135:
-------------------------------
I agree, a conversationPropagation parameter seems more sensible.
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
Fix For: 1.1 (Proposed)
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:31 a.m.
New subject: [JBoss JIRA] Updated: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-135:
--------------------------
Git Pull Request: https://github.com/jboss/cdi/pull/50
See pull request. I only implemented the none propagation for now, as this is actually a
hole in the spec, and not new functionality. I believe it would be possible to implement
other propagations as an extension (George/Nickarls, could you verify this if you get 30
minutes sometime spare?).
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
Fix For: 1.1 (Proposed)
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] Updated: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-135:
--------------------------
Fix Version/s: 1.1 (Confirmed)
(was: 1.1 (Proposed))
Git Pull Request: https://github.com/jboss/cdi/pull/50 (was:
https://github.com/jboss/cdi/pull/50)
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
Fix For: 1.1 (Confirmed)
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:18 p.m.
New subject: [JBoss JIRA] Resolved: (CDI-135) Request parameter for terminating cid propagation
[
https://issues.jboss.org/browse/CDI-135?page=com.atlassian.jira.plugin.sy...
]
Pete Muir resolved CDI-135.
---------------------------
Assignee: Pete Muir
Resolution: Done
Request parameter for terminating cid propagation
-------------------------------------------------
Key: CDI-135
URL: https://issues.jboss.org/browse/CDI-135
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.0
Reporter: Nicklas Karlsson
Assignee: Pete Muir
Fix For: 1.1 (Confirmed)
The specification says the conversation id of non-transient conversations should be
automatically propagated, it would however be handy to be able to stop this propagation on
a per-component basis. If the request token (e.g. named "nocid") would be
present, CDI would interpret this as if no cid was found in the request. This would enable
users to jump from non-transient to non-transient conversations in one step (e.g. by using
a commandLink with a f:param named nocid and an action that would start a new
non-transient conversation.
A further enhancement could be that the parameter value could be "end" and CDI
would terminate the propagated non-transient conversation instead of just abandoning it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4590
days inactive
4702
days old
8 comments
3 participants
participants (3)
-
George Gastaldi (JIRA) -
Nicklas Karlsson (JIRA)
-
Pete Muir (JIRA)