Page History

...

Components learn about assets via injection. The Inject @Inject annotation allows Assets to be injected into components as read-only properties. The path to the resource is specified using the Path annotation.

...

Assets are located within domains; these domains are identified by the prefix on the Path @Path annotation's value.

If the prefix is omitted, the value will be interpreted as a path relative to the Java class file itself, within the "classpath:" domain. This is often used when creating component libraries, where the assets used by the components are packaged in the JAR with the components themselves.

Unlike elsewhere in Tapestry, case matters. This is because Tapestry is dependenent dependent on the Servlet API and the Java runtime to access the underlying files, and those APIs, unlike Tapestry, are case sensitive. Be aware that some operating systems (such as Windows) are case insenitiveinsensitive, which may mask errors that will be revealed at deployment (if the deployment operating system is case sensitive, such as Linux).

...

In addition, Tapestry will GZIP compress the content of all assets (if the asset is compressablecompressible, and the client supports it).

...

Because Tapestry directly exploses exposes files on the classpath to the clients, some thought has gone into ensuring that malicious clients are not able to download assets that should not be visible to them.

...