Community
Participate
Working Groups
>Problem: we wish to use mostly annotations for JSF 2.0 like @ManagedBean The issue is that we are no longer able to use the Eclipse 3.6 Helios JSF wizard that comes with the faces-config.xml file. >of secondary note - is the fact that the wizard adds a second config instead of replacing the commented original - I agree with this behavior as we should not be removing commented code when regenerating the faces-config.xml <managed-bean> <managed-bean-name>collatzBean</managed-bean-name> <managed-bean-class>org.eclipse.persistence.example.distributed.collatz.presentation.CollatzManager</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> <!-- manage the managed-bean via annotations --> <!-- managed-bean> <managed-bean-name>collatzBean<managed-bean-name> <managed-bean-class>org.eclipse.persistence.example.distributed.collatz.presentation.CollatzManager</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean--> Environment 32-bit Helios 3.6 on WebLogic 10.3.4.0 using the default "glassfish" JSF 2.0 implementation that ships with WebLogic. Feb 22, 2011 4:06:03 PM com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Mojarra 2.0.4 (FCS b05) for context '/collatz' >I use the following annotations to mark a POJO as a managed/backing bean for JSF 2.0 instead @ManagedBean(name="collatzBean") @SessionScoped public class CollatzManager { @EJB(name="ejb/CollatzFacade") private CollatzFacadeLocal collatzFacade; ... >WebLogic warns about an existing managed-bean configuration without failing It either replaces the annotated bean config with the XML defined one - need to verify which order
Created attachment 189542 [details] https://fisheye2.atlassian.com/changelog/eclipselink?cs=9011
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
