I’m just started the migration to T5.4. TAP5-2170 is still open and I wondered
if there’s any non-internal interface that I could use to migrate to the new
API.
Am 07.09.2013 um 20:23 schrieb Lenny Primak :
> It worked... Also, I may have found an easier way,
> just use Asset.toClientURL() and
It worked... Also, I may have found an easier way,
just use Asset.toClientURL() and don't need to worry about asset path at all.
On Sep 4, 2013, at 1:45 PM, Howard Lewis Ship wrote:
> StreamableResource is a kind of wrapper around Resource that includes
> additional information needed to generate
JIRA created:
https://issues.apache.org/jira/browse/TAP5-2170
On Sep 2, 2013, at 3:48 PM, Lenny Primak wrote:
> I am trying to migrate to T5.4, and so far I don't understand how to use
> constructAssetPath()
> It now requires a third parameter, StreamableResource.
>
> What I am trying to do is
StreamableResource is a kind of wrapper around Resource that includes
additional information needed to generate asset URLs and a bunch of other
related concerns.
There's a StreamableResourceSource service.
Oops, that's unfortunate; you'll need the internal ResourceChangeTracker
service (which imp
I am trying to migrate to T5.4, and so far I don't understand how to use
constructAssetPath()
It now requires a third parameter, StreamableResource.
What I am trying to do is get a path for application asset to a non-tapestry
module of the app.
Does anyone have an example of how to use construc
