Old thread, but I just ran into this recently as well so thought I'd 
share.

Turns out the /WEB-INF/flex/generated directory in the Flex install 
area was not writable by the tomcat user.  Making that directory 
writable by tomcat got rid of the log messages.


--- In [email protected], Antoine Malpel <[EMAIL PROTECTED]> wrote:
>
> Hi there,
> 
> I use Flex 1.5 /Tomcat 5.5 and I noticed that in my 
> {appRoot}/WEB-INF/flex/log/flex{x}.log there is thse messages :
> 
> 03/07 15:37:15 INFO Cached Component Loader: component Contact 
cannot be 
> cached.
> 03/07 15:37:15 INFO Cached Component Loader: component BasDePage 
cannot 
> be cached.
> 03/07 15:37:15 INFO Cached Component Loader: component CustomLycra 
> cannot be cached.
> 03/07 15:37:15 INFO Cached Component Loader: component 
thumbnailProduct 
> cannot be cached.
> etc....
> ....
> 
> these components refers to all my mxml and as files I use in my 
> Application ...
> 
> Does this mean my 'application' is compiled every time a client 
connect 
> to my App ?
> How can I resolve this, and can't find any information about that 
in 
> macromedia's doc ...
> (please Adobe continue support for Flex 1.5 as Flash 9 player is 
not 
> well diffused now)
> 
> I've check the configuration files and except the fact I use 
production 
> mode to false (as I may set new versions sometimes without wanting 
to 
> restart my tomcat server)
> but everything else seems ok in my flex-config.xml
> 
> for example :
> 
>     <cache>
>         <!-- cache compiled custom components as swo files -->
>         <cache-swos>true</cache-swos>
> 
>         <!-- content cache for dynamically generated SWF, SWD, and 
HTML -->
>         <content-size>500</content-size>
> 
>         <!-- source cache for dynamically generated MXML (from 
JSP) -->
>         <mxml-size>500</mxml-size>
> 
>         <!-- force a check for validation of page freshness every 
XX 
> seconds -->
>         <http-maximum-age>1</http-maximum-age>
> 
>         <!-- check for changes to dependent files on disk every XX 
> seconds -->
>         <!-- when production-mode is true, the file watcher runs 
once at 
> startup -->
>         <file-watcher-interval>1</file-watcher-interval>
>     </cache>
> 
> thanks if someone could clear my mind about this issue
> 
> Antoine Malpel
>


Reply via email to