Data Palette not showing Managed Beans for Dynamic Web Project, JSF 2.1

Question

Hello.
I have a problem in OEPE (oepe-juno-distro-win32.zip), where the Data tab in Palette shows no Managed Beans,
even if I created them in the ManagedBeans in faces-config.xml using the Faces Config Editor.
I have created a Dynamic Web Project with these Facets:
Dynamic Web Module 3.0
Java 1.7 (JDK 1.7_21)
Java Annotation Processing Support 5.0
JavaScript 1.0
JavaServer Faces 2.1
JSTL 1.2
Oracle WebLogic Web App Extensions 12.1.1
I am using Oracle WebLogic Server 12c 12.1.1 zip distribution for hosting the application.
For example, I have a UserBean Managed Bean of Session scope, that has 3 String fields
and the respective getters and setters.
I create a "test.jspx" file, and from the Palette -> Tags tab -> JSF HTML I drag a Form into
the new file so I can connect it to UserBean and generate a form to enter its details.
I select the "Generate a form tag and content from data" and in the Choose Bean dialog
there is none of my Beans.
What could be the problem?
Thanks in advance.
Edited by: 997841 on Apr 30, 2013 6:09 PM
I forgot to mention the Oracle WebLogic Web App Extensions version 12.1.1 and that also
for JSF 2.1 the "sub-directory" Faces Configuration below the project in Project Explorer is not
existent, as in projects created with earlier versions of JSF.

Answer 1

Yes, they are both listed under the WebLogic System Libraries.
This is the content of .classpath file when using WebLogic System Library:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
     <classpathentry kind="src" path="src"/>
     <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/Oracle WebLogic Server 12c (12.1.1) JRE">
          <attributes>
               <attribute name="owner.project.facets" value="java"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="src" path=".apt_src">
          <attributes>
               <attribute name="optional" value="true"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="con" path="oracle.eclipse.tools.weblogic.lib.system">
          <attributes>
               <attribute name="owner.project.facets" value="jst.web"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>
     <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.module.container"/>
     <classpathentry kind="con" path="oracle.eclipse.tools.weblogic.lib.shared/jstl/exact/1.2"/>
     <classpathentry kind="output" path="build/classes"/>
</classpath>
And this is the content when using User Library with Mojarra:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
     <classpathentry kind="src" path="src"/>
     <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/Oracle WebLogic Server 12c (12.1.1) JRE">
          <attributes>
               <attribute name="owner.project.facets" value="java"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="src" path=".apt_src">
          <attributes>
               <attribute name="optional" value="true"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="con" path="oracle.eclipse.tools.weblogic.lib.system">
          <attributes>
               <attribute name="owner.project.facets" value="jst.web"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>
     <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.module.container"/>
     <classpathentry kind="con" path="oracle.eclipse.tools.weblogic.lib.shared/jstl/exact/1.2"/>
     <classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/JSF 2.1 (Mojarra 2.1.6-FCS)">
          <attributes>
               <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
               <attribute name="owner.project.facets" value="jst.jsf"/>
          </attributes>
     </classpathentry>
     <classpathentry kind="output" path="build/classes"/>
</classpath>