[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3003) maintain insertion order of parameters in UrlBuilder
by Dan Allen (JIRA)
maintain insertion order of parameters in UrlBuilder
----------------------------------------------------
Key: JBSEAM-3003
URL: http://jira.jboss.com/jira/browse/JBSEAM-3003
Project: Seam
Issue Type: Feature Request
Components: JSF Controls
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.1.0.BETA1
Right now it is difficult to create UrlRewrite rules because the order of the parameters jumps around. This happens because the parameters are appended to a plain HashMap (for s:link, s:button, etc), giving no guarantee to their order. My feeling is that parameters should maintain their insertion order, which can be accomplished using a LinkedHashMap.
At first, I thought about having the parameters sorted alphabetically. However, that takes control away from the developer to order the links how they see fit. As long as we can document the order in which Seam appends parameters, then the developer can predict the order the parameters will appear in the URL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2967) Seam example's readme.txt updates
by Jay Balunas (JIRA)
Seam example's readme.txt updates
----------------------------------
Key: JBSEAM-2967
URL: http://jira.jboss.com/jira/browse/JBSEAM-2967
Project: Seam
Issue Type: Task
Components: Documentation Issues, Examples
Affects Versions: 2.0.2.CR2
Reporter: Jay Balunas
Priority: Minor
This is a listing of very minor changes to make the various readme.txt files more consistent. In the "examples/readme.txt" file it have general instructions and referrers to the specific example's readme.txt for differences in ant commands. Most of the items below are related to different ant commands that are needed.
* Groovy booking
- jbosswar.unexplode to undeploy + ant undeploy (to get -ds.xml file)
- no test
* hibernate
- no undeploy must call jboss.undeploy
- no test
* jpa
- no undeploy must call jboss.undeploy
* All remoting examples
- have an "ant test" command, but does not contain tests and shows testng help
* Seamdiscs
- need ant unexplod to remove completely
* Spring
- ant jbosswar.undeploy to undeploy
- no test
* ui
- no test
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months