This content has been marked as final.
Show 2 replies
-
1. Re: overriding Seam components
rshan.bob.shanahan.alascorp.com Dec 15, 2008 12:05 AM (in response to rshan.bob.shanahan.alascorp.com)I changed the install value to true
@Install(value = true, precedence = APPLICATION)
and now I see a log message stating that 2 components were found with the same name and same precedence, which causes Seam startup to fail.
The Seam ContextLoader config actually looks like this:
@Scope(ScopeType.APPLICATION) @BypassInterceptors @Startup(depends="org.jboss.seam.ioc.spring.springELResolver") @Name("org.jboss.seam.ioc.spring.contextLoader") @Install(value = false, precedence = BUILT_IN) public class ContextLoader
Is this a bug?
-
2. Re: overriding Seam components
rshan.bob.shanahan.alascorp.com Dec 18, 2008 12:08 AM (in response to rshan.bob.shanahan.alascorp.com)I verified that the BUILT-IN ContextLoader's precedence was actually 20 (APPLICATION), even though its source file has the following annotations:
@Scope(ScopeType.APPLICATION) @BypassInterceptors @Startup(depends="org.jboss.seam.ioc.spring.springELResolver") @Name("org.jboss.seam.ioc.spring.contextLoader") @Install(value = false, precedence = BUILT_IN) public class ContextLoader
Hence the startup failure. Changing my component's precedence to DEPLOYMENT (30) allowed it to override the BUILT-IN.
This seems to be a bug, unless there is some other configuration I'm overlooking.