THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
That's it! Autoloading plus the virtual folders for components and for assets takes care of all the issues related to components. Just build your JARs, setup the JAR Manifest, and drop them into your applications.
| Since | ||
|---|---|---|
| ||
Added in 5.2 | ||
A note about Assets
Tapestry automatically creates a mapping for assets inside your JAR. In the above example, the icon image will be exposed as /assets/application version/happy/components/happy.jpg (the application version number is incorporated into the URL). The "happy" portion is a virtual folder that maps to the librarie's root package (as folder org/example/happylib on the Java classpath).
...