[
http://jira.jboss.com/jira/browse/JBSEAM-354?page=all ]
Gavin King closed JBSEAM-354.
-----------------------------
Resolution: Rejected
Negative, this is already available with @RequestParameter, which is the only time it is
useful (and is exactly the example you use). You will never need it any other time you use
@In.
Better support for JSF-style managed properties
-----------------------------------------------
Key: JBSEAM-354
URL:
http://jira.jboss.com/jira/browse/JBSEAM-354
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.0.1
Reporter: Adam Brod
Priority: Minor
The @In annotation should support the same syntax as JSF managed properties. That means
that If I have this annotation in my Bean:
@In("#{param.fileId}")
Long fileId
Seam should automatically inject that property performing the correct JSF conversion. In
Shale I can do that with the @Value or @Property annotation. It is very confusing that I
need a specialized annotation that doesn't support the EL just for request parameters
when JSF doesn't make that distinction.
I believe this could be implemented with a few small changes to Component. Inside
Component.getInstanceToInject(...), the logic which first checks to see if the name is an
EL (line 1358 in Seam 1.0.1) could also check to see if the expression begins with
"#{param.", if so, then it can call to Component.convertRequestParameter(...) to
convert the type.
This is a small change to Component, but it makes the overall Seam API more consistent.
It allows me to use the EL anywhere I want. I don't have to worry about using @In or
@RequestParameter, I just use the EL.
--
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