-
1. Re: Setting debug="false" in components.xml prevents initialization of @Startup bean during server startup
swd847 Feb 26, 2009 3:31 AM (in response to sheldons)Can you post your beans?
You should never have debug=true in production, it will lead to instability (ConcurrentModificationException) under load.
With regard to the pages rendering slowly did you remember to update your schema in the .page.xml files?
-
2. Re: Setting debug="false" in components.xml prevents initialization of @Startup bean during server startup
sheldons Feb 26, 2009 7:08 AM (in response to sheldons)Here is the code:
in components.xml:
<core:init debug="false" jndi-pattern="n2/#{ejbName}/local"/>
Startup bean:
@Startup @Scope(ScopeType.APPLICATION) @Name("com.myapplication.configuration") public class Configuration { @Out(scope=ScopeType.APPLICATION) private String imageWebRoot; // a bunch of other properties with getters and setters ... } @Startup(depends = {"com.myapplication.configuration"}) @Scope(ScopeType.APPLICATION) @Name("neighborhoodListCache") public class NeighborhoodListCacheBean implements NeighborhoodListCache { ... @Factory("neighborhoods") @Create public void loadNeighborhoods() { ... } }
None of the @Startup beans was executed during server startup. But they would be fine if I set <core:init debug="true".../>
-
3. Re: Setting debug="false" in components.xml prevents initialization of @Startup bean during server startup
sheldons Feb 26, 2009 7:15 AM (in response to sheldons)BTW, regarding *.page.xml, I did change all headers before testing the app (changed to use http://jboss.com/products/seam/pages-2.1.xsd).
-
4. Re: Setting debug="false" in components.xml prevents initialization of @Startup bean during server startup
sheldons Mar 5, 2009 8:24 PM (in response to sheldons)finally found the problem: jboss-seam-debug is missing under WEB-INF/lib. This is needed even when debug='false'
-
5. Re: Setting debug="false" in components.xml prevents initialization of @Startup bean during server startup
jkronegg Jun 15, 2009 4:29 PM (in response to sheldons)I had the same problem using Seam 2.1.2.GA for a project created using Eclipse's JbossTools 3.x (Seam Tools for Eclipse
3.0.1.GA-R200905070146-H18). The project is created using the wizardNew Seam Web Project
.- When using <core:init debug="true" jndi-pattern="@jndiPattern@"/>, Seam creates the component.
- When using <core:init debug="false" jndi-pattern="@jndiPattern@"/>, Seam does not create the component.
This occurs because Seam uses hot deployment into the /WEB-INF/dev directory and hot deployment seems to be disabled when using the debug=false mode.
The solution was to disallow output folder for source folders in the Eclipse project properties: Project -> Properties -> Java Build Path -> Source tab -> unckeck
Allow output folders for source folders
.This problem is not described explicitely in the Seam reference documentation. The section on hot deployment states to put debug=true. The section on exception handling states the actions to do but miss the hot deployment directory problem described above.
Worth a JIRA issue?