-
1. Re: Stop parameter propagation.
admin.admin.email.tld Sep 30, 2008 9:45 PM (in response to luxspes)you could use h:outputLink with a4j:support to call actions...
-
2. Re: Stop parameter propagation.
luxspes Sep 30, 2008 9:59 PM (in response to luxspes)Now that is an strange combination... to what event in h:outputLink do you suggest I bind the a4j:support? I don't think this will work... could you elaborate on your suggestion?
-
3. Re: Stop parameter propagation.
admin.admin.email.tld Sep 30, 2008 10:14 PM (in response to luxspes)event="onclick"
-
4. Re: Stop parameter propagation.
sjmenden Sep 30, 2008 10:36 PM (in response to luxspes)I replied in the other post so just for completeness here it is again:
To stop parameter propagation you need to include the param like so:
<h:commandButton ... > <f:param name="param1" /> <f:param name="param2" /> </h:commandButton>
ie, there is no great way currently to disable parameter propagation, so you have to define it without a value like above.
-
5. Re: Stop parameter propagation.
luxspes Sep 30, 2008 10:36 PM (in response to luxspes)Wouldn't that call action before the url of the outputLink is actually accessed?
-
6. Re: Stop parameter propagation.
luxspes Sep 30, 2008 10:44 PM (in response to luxspes)I was going to reply you there,but thanks for posting it here.
Thats kind of a... how could I put it politely... mmmm... really ugly solution?
There should be a page-parameter-propagation="off" option in s:conversationPropagation... don't you think?
I would do it myself but I have no experience creating JSF tags...
This might be too much to ask for, but, can you provide me with some guidance on which files from seam source code should I copy to separate project in order to create my own enhanced s:conversationPropagation?
Or is there some way to alter the html code some (but not all) s:links it produce? perhaps with a renderer?
-
7. Re: Stop parameter propagation.
luxspes Oct 1, 2008 1:05 AM (in response to luxspes)It is also not a solution for a menu, because the menu may call different pages with some shared parameters, and some very different ones, and I may need to clear different parameters depending on from which page to which page I am going. Therefore I need a way to plain stop page parameter propagation.
-
8. Re: Stop parameter propagation.
sjmenden Oct 1, 2008 2:18 AM (in response to luxspes)Yeah it's not pretty, create a JIRA for something like page-parameter-propagation="false" and vote for it. Not sure where to point you to in the source, you'll have to do some extended digging unless Pete can chime in.
-
9. Re: Stop parameter propagation.
luxspes Oct 1, 2008 3:01 AM (in response to luxspes)It seems that this problem has alredy been discussed a long time ago (Nov/2007) in the old forum, and a JIRA JBSEAM-2310 has already been filed.
Of course, it is not as specific as the one I might file asking for a page-parameter-propagation="false" but it was filed because back then Pete Muir posted that:
There probably needs to be a way of removing parameters from links. File a feature request in JIRA
.Mmmmm, I am not sure if I should file my own JIRA...
-
10. Re: Stop parameter propagation.
luxspes Oct 1, 2008 3:10 AM (in response to luxspes)I decided that I will just add a comment to JBSEAM-2310 saying that it could be implemented by: adding a page-parameter-propagation="false" attribute to s:link and s:conversationPropagation to stop page parameter propagation
Please, if you need a new conversation each time an option in your menu, please vote for JBSEAM-2310.
-
11. Re: Stop parameter propagation.
luxspes Oct 1, 2008 3:51 AM (in response to luxspes)In org.jboss.seam.ui.component.UISeamCommandBase in the method public String getUrl() throws UnsupportedEncodingException in this fragment:
if (viewId != null) { Map<String, Object> pageParameters = Pages.instance().getStringValuesFromModel(context, viewId, usedParameters); for (Map.Entry<String, Object> me : pageParameters.entrySet()) { UIParameter uip = new UIParameter(); uip.setName(me.getKey()); uip.setValue(me.getValue()); url.addParameter(uip); } }
I think that is the code that I need to
wrap
inside an if and only let it execute if page-parameter-propagation="true" but I need more guidance on how to achieve that. -
12. Re: Stop parameter propagation.
terryb Oct 1, 2008 4:13 AM (in response to luxspes)Thanks for voting on the issue; I've been waiting on it for a long time. I guess may need to request for mass voting.
I also think PARAM tag in .page.xml should support
if
attribute. I have filed JIRA for this one too, please vote https://jira.jboss.org/jira/browse/JBSEAM-3483.And, I would also be really useful if f:param used in xhtml etc supports
rendered
attribute; because s:fragment can not be used within some/many tags which do accept f:param. Anyone knows where to lodge request for enhancements to f:param? -
13. Re: Stop parameter propagation.
jamesjmp Oct 1, 2008 4:13 PM (in response to luxspes)I agree with you two this would be very useful. I´ve voted for
JBSEAM-3483 as well as for JBSEAM-2310.Hope a mass voting to happen! -
14. Re: Stop parameter propagation.
pmuir Oct 1, 2008 4:53 PM (in response to luxspes)Attach patches, and we can review and apply, I'm happy about the concepts.