[jira] [Closed] (TAP5-1494) PageRenderLinkSource should provide an addParameter(String, Object) method that uses ValueEncoder to coerce the Object to string automatically
[ https://issues.apache.org/jira/browse/TAP5-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Drobiazko closed TAP5-1494. Resolution: Invalid Check this out: http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/Link.html#addParameterValue%28java.lang.String,%20java.lang.Object%29 PageRenderLinkSource should provide an addParameter(String, Object) method that uses ValueEncoder to coerce the Object to string automatically Key: TAP5-1494 URL: https://issues.apache.org/jira/browse/TAP5-1494 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.3 Reporter: Robert Zeigler Assignee: Robert Zeigler Priority: Minor Currently, PageRenderLinkSource provides an addParameter(String, String) object. This is nice for allowing the fullest control over what ultimately is placed into the URL, but it is not uncommon to have something along the lines of: ValueEncoderSource encoderSource; ... link.addParameter(myparam, encoderSource.getValueEncoder(MyClass.class).toClient(myvalue)); It would be nice for PageRenderLinkSource to have an addParameter(String, Object) method in addition to the addParameter(String, String) method. Users needing absolute control of the way parameters appear would retain that control, and the rest of us can write less code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1495) tapestry expressions should support a map creation
[
https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13014998#comment-13014998
]
Igor Drobiazko commented on TAP5-1495:
--
What is actually the use case?
Currently there is a coercion String-SelectModel:
t:select value=paymentType model=literal:cc=Credit Card,bt=Bank Transfer,
ca=Cash,pp=PayPal/
Maybe we could provide same for String - Map
tapestry expressions should support a map creation
--
Key: TAP5-1495
URL: https://issues.apache.org/jira/browse/TAP5-1495
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.3
Reporter: Robert Zeigler
Assignee: Robert Zeigler
Currently, tapestry expressions support property access, method calls, null
checks (?.), and quick list creation (['a',b,...]), but there is no support
for map creation.
It would be nice to be able to write:
{a=b,c=d}
to quickly and easily create maps.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1494) PageRenderLinkSource should provide an addParameter(String, Object) method that uses ValueEncoder to coerce the Object to string automatically
[ https://issues.apache.org/jira/browse/TAP5-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015037#comment-13015037 ] Robert Zeigler commented on TAP5-1494: -- Heh. Nice. My bad... I noticed the gap while working on a Tapestry 5.1 project. That'll learn me to double check the current source! PageRenderLinkSource should provide an addParameter(String, Object) method that uses ValueEncoder to coerce the Object to string automatically Key: TAP5-1494 URL: https://issues.apache.org/jira/browse/TAP5-1494 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.3 Reporter: Robert Zeigler Assignee: Robert Zeigler Priority: Minor Currently, PageRenderLinkSource provides an addParameter(String, String) object. This is nice for allowing the fullest control over what ultimately is placed into the URL, but it is not uncommon to have something along the lines of: ValueEncoderSource encoderSource; ... link.addParameter(myparam, encoderSource.getValueEncoder(MyClass.class).toClient(myvalue)); It would be nice for PageRenderLinkSource to have an addParameter(String, Object) method in addition to the addParameter(String, String) method. Users needing absolute control of the way parameters appear would retain that control, and the rest of us can write less code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1495) tapestry expressions should support a map creation
[
https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015040#comment-13015040
]
Howard M. Lewis Ship commented on TAP5-1495:
That's not the syntax I'd prefer, as it won't work well inside an XML document
such as a Tapestry template: Maybe something more like JSON syntax.
{ 'a': b, 'c': d}
tapestry expressions should support a map creation
--
Key: TAP5-1495
URL: https://issues.apache.org/jira/browse/TAP5-1495
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.3
Reporter: Robert Zeigler
Assignee: Robert Zeigler
Currently, tapestry expressions support property access, method calls, null
checks (?.), and quick list creation (['a',b,...]), but there is no support
for map creation.
It would be nice to be able to write:
{a=b,c=d}
to quickly and easily create maps.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1495) tapestry expressions should support a map creation
[
https://issues.apache.org/jira/browse/TAP5-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015042#comment-13015042
]
Robert Zeigler commented on TAP5-1495:
--
Igor: By that argument, what's the use case for list/array creation support in
the property language? We could have provided a coercion from String to List...
Howard: Yeah, the syntax was more just to get the idea down. Json-like syntax
might work nicely.
tapestry expressions should support a map creation
--
Key: TAP5-1495
URL: https://issues.apache.org/jira/browse/TAP5-1495
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.3
Reporter: Robert Zeigler
Assignee: Robert Zeigler
Currently, tapestry expressions support property access, method calls, null
checks (?.), and quick list creation (['a',b,...]), but there is no support
for map creation.
It would be nice to be able to write:
{a=b,c=d}
to quickly and easily create maps.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1489) Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications)
[ https://issues.apache.org/jira/browse/TAP5-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Canfield reassigned TAP5-1489: --- Assignee: Josh Canfield Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications) Key: TAP5-1489 URL: https://issues.apache.org/jira/browse/TAP5-1489 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.3.0, 5.2.5 Reporter: Howard M. Lewis Ship Assignee: Josh Canfield Priority: Minor It's great that Tapestry has the re-storage logic built in, but it's only necessary to deal with a gap in how replicated sessions are synchronized across nodes of a cluster. In the more typical case, Tapestry is being used in a single node (no cluster), or using sticky sessions with no session replication, and the extra work of analyzing and re-storing attributes is not necessary. It should default on; users should have to explicitly disable the support. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1489) Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications)
[ https://issues.apache.org/jira/browse/TAP5-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015080#comment-13015080 ] Josh Canfield commented on TAP5-1489: - I'm working on session storage now for TAP5-1355. Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications) Key: TAP5-1489 URL: https://issues.apache.org/jira/browse/TAP5-1489 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.3.0, 5.2.5 Reporter: Howard M. Lewis Ship Assignee: Josh Canfield Priority: Minor It's great that Tapestry has the re-storage logic built in, but it's only necessary to deal with a gap in how replicated sessions are synchronized across nodes of a cluster. In the more typical case, Tapestry is being used in a single node (no cluster), or using sticky sessions with no session replication, and the extra work of analyzing and re-storing attributes is not necessary. It should default on; users should have to explicitly disable the support. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
