-
1. Re: Seam Excel w async problem
www.supernovasoftware.com Mar 12, 2009 12:18 AM (in response to www.supernovasoftware.com)After looking through the Seam source I see that it tries to load from the classpath if the resource cannot be located in via the ServletContext.
So my first question was not necessary. I was just confused by the method signature of
public String render(final String viewId)
in
org.jboss.seam.ui.facelet.FaceletsRenderer
I assumed that is would only work with a viewId from the ServletContext.
I would still appreciate any advice on using a Factory or similar caching strategy to keep the value method from being called many times during rendering.
-
2. Re: Seam Excel w async problem
swd847 Mar 12, 2009 3:32 AM (in response to www.supernovasoftware.com)If you set up another method on the same bean to access this list annoted with @BypassInterceptors it should speed things up considerably
-
3. Re: Seam Excel w async problem
www.supernovasoftware.com Mar 12, 2009 6:47 PM (in response to www.supernovasoftware.com)How will this help?
The problem is not that interceptors are slowing this down.
The problem is that my db query is executed many times because I cannot put this variable in an appropriate scope using a factory method or alternative.What contexts are available to an async quartz job?
-
4. Re: Seam Excel w async problem
www.supernovasoftware.com Mar 13, 2009 1:29 AM (in response to www.supernovasoftware.com)Setting the value manually in the EVENT context solved the problem I was having.
Contexts.getEventContext().set("costExportList", costDAO.getSummaryList());
Is the factory method expected to work in this case because it does not for me?