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 @Impor
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
---
Sorry, just realized that addScriptLink() is deprecated, as is
addStylesheetLink(), in favor of:
JavaScriptSupport.importJavaScriptLibrary()
and
JavaScriptSupport.importStylesheet()
See
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/javascript/JavaScriptSuppor
I guess you could call addScriptLink() from your serupRender() method. See
http://tapestry.apache.org/javascript.html
Bob Harner
On May 7, 2011 4:35 AM, "stephanos2k" wrote:
This works. In ClasspathURLConverter replace this, which worked in JBoss 5...
URLConnection connection = url.openConnection();
Object virtualFile = connection.getContent();
Object zipEntryHandler = inv
Guys, thanks for the reply.
But in my post I said
> I can't use annotations, since the assets are different for production
> mode.
>
So @Import doesn't work for me!
PS: You may ask yourself why I use different assets: I use LESS for CSS and
have multiple .less files in development and one .c
Oops - don't modify ClasspathURLConverter as I did below.
The JBoss server log shows that Tapestry's services start but no
pages/components/mixins have been found, ie. there are no INFO messages from
ComponentClassResolver.
The solution will be to get ClasspathURLConverter working again.
On 0
