Patrick Casey <[EMAIL PROTECTED]> wrote: Patrick,
at first I thought that caching assets might be a good idea. But as far as I cann see, they are already cached by the framework. I guess, I'll just call getAsset() whenever I need an asset while rendering. Thanks for your help! Dirk Dittert > You might be running into a sequencing problem e.g. the component is > being created prior to the assets, hence you're getting a null here. Why not > just get the asset during the render method of the component? Not sure > that'll work, but there's really no reason your logic has to be in the > constructor so I'd definitely try moving it to render. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
