This is the pattern in Tapestry: there's an API that you can use, and then we layer annotation support on top of that to do the work of calling into the API for you. Generally, if you look at the annotation, you'll see hyperlinks to the APIs that are ultimately invoked.
This is true for the @Import annotation: http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Import.html It clearly identifies the methods of JavaScriptSupport it invokes. You have to dig a little deeper to find out how to @Inject an asset: http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Path.html On Sat, May 7, 2011 at 6:36 AM, Christian Köberl <tapestry.christian.koeb...@gmail.com> wrote: >>> I can't use annotations, since the assets are different for production >>> mode. >>> >> So @Import doesn't work for me! > > You could either use Symbols to change the location of CSS or inject > JavaScriptSupport (or RenderSupport before Tapestry 5.2) and add the > stylesheet programmatically. > > -- > Chris > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
