Hi, On Thu, Apr 28, 2011 at 9:50 PM, Alec Swan alecs...@gmail.com wrote: Thanks, Andrea. I was running in DEVELOPMENT mode and switching to DEPLOYMENT mode fixed the problem. I hope this gets documented somewhere. You are doing something wrong. MyApp#init() is called after
I've seen folks get a misconfigure like this when they make the call in the application's constructor instead of the init() method. On Friday, April 29, 2011, Martin Grigorov mgrigo...@apache.org wrote: Hi, On Thu, Apr 28, 2011 at 9:50 PM, Alec Swan alecs...@gmail.com wrote: Thanks, Andrea. I
Thanks, Andrea. I was running in DEVELOPMENT mode and switching to DEPLOYMENT mode fixed the problem. I hope this gets documented somewhere. Martin, are you saying that page rendering will not block waiting for the static resource to render while it will block on a component resource to render?
Hi Alec, are you sure you are testing your code in DEPLOYMENT mode and not in DEVELOPMENT mode? To answer your question about benefits of using shared resources, I can say that they make sense when you need to access a resource (like a picture) with an absolute path instead of a relative
Static resources are more suitable for the cases when you want to avoid page locking. E.g. when you need to deliver dynamic response and there is a chance that the processing will be slower or there will be more clients for the same resource. Using a normal component for this will suffer that only