This content has been marked as final.
Show 9 replies
-
1. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
meetoblivion Dec 8, 2009 3:24 AM (in response to hirowla.ian.rowlands.three.com.au)did you upgrade to a newer weld? They should be equivalent, as weld is injecting the bean into the JSF's scopes.
-
2. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
hirowla.ian.rowlands.three.com.au Dec 8, 2009 4:09 AM (in response to hirowla.ian.rowlands.three.com.au)No, same Weld as what came with 6.0.0 M1.
-
3. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
matt.drees Dec 8, 2009 4:53 AM (in response to hirowla.ian.rowlands.three.com.au)Did you add a beans.xml file to /WEB-INF?
-
4. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
hirowla.ian.rowlands.three.com.au Dec 8, 2009 5:31 AM (in response to hirowla.ian.rowlands.three.com.au)No I didn't - is that required?
-
5. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
hirowla.ian.rowlands.three.com.au Dec 8, 2009 5:42 AM (in response to hirowla.ian.rowlands.three.com.au)I added a beans.xml file into WEB-INF, now I get an error on application startup:
12:37:38,143 ERROR [AbstractKernelController] Error installing to Create: name=vfsfile:/C:/AAA_Working/Workspaces/OptinPrototype51/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Server/deploy/Optin.ear/_WeldBootstrapBean state=Configured
java.lang.NoClassDefFoundError: javax/inject/Provider
I get this in the log too (for reference): [Weld/Version] WELD-000900 1.0 (0)
Any ideas?
Thanks,
Ian -
6. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
nickarls Dec 8, 2009 6:14 AM (in response to hirowla.ian.rowlands.three.com.au)Due to a packaging error in M1 (first days), remove the .tmp extension of the javax.inject.jar.tmp file in common/lib and client/lib
-
7. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
hirowla.ian.rowlands.three.com.au Dec 8, 2009 6:20 AM (in response to hirowla.ian.rowlands.three.com.au)I had noticed that error in the client/lib file (when I wondered why Eclipse wasn't autocompleting when I wanted the @Named tag), but didn't know it happened in common/lib. That fixes it, thanks for that.
Ian
-
8. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
nickarls Dec 8, 2009 7:32 AM (in response to hirowla.ian.rowlands.three.com.au)Yep, that was the same way I noticed it...
-
9. Re: Equivalence of @Named and @ManagedBean with JBoss 6.0.0 M1
cbredesen Dec 12, 2009 10:12 PM (in response to hirowla.ian.rowlands.three.com.au)Banged my head on a very similar issue until I realized the Weld deployer is not in the 'web' profile. 'default' works like a charm!