[ https://jira.jboss.org/jira/browse/JBSEAM-3281?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez updated JBSEAM-3281: ------------------------------------------------- Description: An alternative to seam/remoting/interface.js (other url like seam/remoting/idiomatic_interface.js, perhaps enabled by a components.xml option) that transparently receives associative arrays and returns associative arrays when the @WebRemote returns (or has a parameter of type) java.util.Map or a POJO (like DWR does). This would be specially helpful for porting ajax enabled applations built with other remoting technologies, but also to make it easier for those coders that prefer JavaScript to Java to feel comforatable (and dot put objections) to the use of Seam Remoting vs other options to do ajax/remoting. (was: An alternative to seam/remoting/interface.js (other url like seam/remoting/idiomatic_interface.js, perhaps enabled by a components.xml option) that transparently receives associative arrays and returns associative arrays when the @WebRemote returns (or has a parameter of type) java.util.Map or a POJO (like DWR does). This would be specially helful for porting ajax enable applations built with other remoting techmologies, but also to make it easier for those coders that prefer JavaScript to Java to feel comforable (and dot put objections) to the use of Seam Remoting vs other options to do ajax/remoting.) Fixed several typos -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3281?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez updated JBSEAM-3281: ------------------------------------------------- Description: An alternative to seam/remoting/interface.js (other url like seam/remoting/idiomatic_interface.js, perhaps enabled by a components.xml option) that transparently receives associative arrays and returns associative arrays when the @WebRemote returns (or has a parameter of type) java.util.Map or a POJO (like DWR does). This would be specially helpful for porting Ajax enabled applications built with other remoting technologies, but also to make it easier for those coders that prefer JavaScript to Java to feel comfortable (and don't put objections) to the use of Seam Remoting vs other options to do ajax/remoting. (was: An alternative to seam/remoting/interface.js (other url like seam/remoting/idiomatic_interface.js, perhaps enabled by a components.xml option) that transparently receives associative arrays and returns associative arrays when the @WebRemote returns (or has a parameter of type) java.util.Map or a POJO (like DWR does). This would be specially helpful for porting ajax enabled applations built with other remoting technologies, but also to make it easier for those coders that prefer JavaScript to Java to feel comforatable (and dot put objections) to the use of Seam Remoting vs other options to do ajax/remoting.) Fixed typos -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3281?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez commented on JBSEAM-3281: ------------------------------------------------------ I object to this rejection because: -First because this feature request does not ask for the removal of support for Seam.Remoting.Map, it asks for adding transparent support for associative arrays -And second because the majority of the cases people use strings as keys, Seam Remoting is making it hard for the majority and convenient for few rare cases. -And third: this kind of thinking is the same that is drove people away from J2EE: Lets give the API a lot of power for advanced stuff but make it hard to do the common simple stuff. There is no advantage in doing that. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3281?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez commented on JBSEAM-3281: ------------------------------------------------------ It could, for example detect if a method has the map defined using generics as Map<String,Object> and allow for it to be used as an associative array. -- 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