[ http://issues.apache.org/jira/browse/TAPESTRY-594?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-594:
-------------------------------------------
Resolution: Invalid
Each different type of injection represents a completely different code path and results in very different generated bytecode. The "state:" binding prefix isn't what you want either, since it would inject a boolean value (does the state object exist or not), whereas the type="state" injection will create a read/write property that dynamically obtains (and creates, if necessary) the state object itself.
> Change <inject type="state to <inject obejct="state:
> ----------------------------------------------------
>
> Key: TAPESTRY-594
> URL: http://issues.apache.org/jira/browse/TAPESTRY-594
> Project: Tapestry
> Type: Wish
> Reporter: Ron Piterman
> Priority: Minor
>
> Hi,
> I don't fully understand why injecting a state object does not use the syntax
> <inject object="state:state-object-name"
> This will be conform to all (?) other injecting methods and reduce xml use, making the "type attribute " obsolete.
> Since also state objects are configured from hivemind, why use an extra xml attribute instead of another prefix?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org