[
https://issues.apache.org/jira/browse/TAPESTRY-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2313.
------------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
I'm really adverse to mixing and matching the different bindings; anything
complicated should go in Java code.
The AssetSource can help with what you want, but isn't quite ideal; perhaps if
it had an extra method or two for conveniently obtaining assets from the
context. Worse, the same code that handles the asset: binding prefix also has
to handle @Inject @Path private Asset foo (that is, the AssetObjectProvider
inside the MasterObjectProvider chain of command). Expansions and symbols
share the same syntax which would be very confusing (that ${...} is a symbol
only for asset: or something along those lines).
You can instead inject the AssetFactory (with marker annotation
@ContextProvider).
> Make usage of expansion within Asset injection and template definition
> ----------------------------------------------------------------------
>
> Key: TAPESTRY-2313
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2313
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Environment: Any
> Reporter: Massimo Lusetti
> Assignee: Howard M. Lewis Ship
>
> It would be great if we could provide a way to use Asset with a dynamic path,
> known only at runtime.
> Typical usage is for asset relative to a product in a online shot where i got
> the id of the prodcut beeing displayed and want to display the relative image
> via Asset to benefit of caching and others.
> For the records, now the problem is solved using and an action link as the
> src attribute of img tag and from the action event handler returning a
> StreamResposne.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
