[ADF] Having Difficulties in Figuring Out Using the af:selectInputText Tag

Question

This is my first time using the ADF tags.
The <af:selectInputText> is an input component that can launch a dialog and automatically accept its return value.
My pop-up is a data table that provides "code" and "description". And the selection made will be return to the parent page and the "code" will be populated in the input field.
First, I tested if my data table can be constructed successfully. Yes, I am able to use the JSF <h:dataTable> tag to display without problem.
Second, I have adf-faces-api-10_1_3_0_4.jar and adf-faces-impl-10_1_3_0_4.jar in my WEB-INF/lib directory.
Third, my web.xml and faces-config.xml work well because I was able to render JSF tags.
Fourth, I have created the adf-faces-config.xml file with its contents directly copied from the ADF Configuration web site. The adf-faces-config.xml is placed together with the web.xml and faces-config.xml files.
Fifth, on top of my ***.jsp, I added
<%@ taglib uri="http://xmlns.oracle.com/adf/faces/EA10" prefix="af" %>
<%@ taglib uri="http://xmlns.oracle.com/adf/faces/EA10/html" prefix="afh" %>
However, the IDE says that <af:selectInputText ...> is an unknown tag.
Besides, for the value of the "action" attribute of the <af:selectInputText ...>, what is supposed to be filled for the "dialog:?????"
and the compiler starts complaining that the "value" attribute in my <h:dataTable ...> has no value! But, my <h:dataTable ....> worked well before I introduced ADF.
Here is my code in the ***.jsp:
     <f:view>
          <h:form>
                 <af:selectInputText label="Sex: " id="idInputText"
                   value="#{listOfValuesManagementBean.selectedGender}"
                popupTitle="Sex Types"
                    action="dialog:????????????" windowWidth="300" windowHeight="200">
                   <h:dataTable id="gender" value="#{listOfValuesManagementBean.genderTypes}" var="genderType">
                        <h:column>
                             <f:facet name="header">
                                  <h:outputText value="Code"/>
                             </f:facet>
                             <h:outputText value="#{genderType.code}"/>
                        </h:column>
                        <h:column>
                             <f:facet name="header">
                                  <h:outputText value="Description"/>
                             </f:facet>
                             <h:outputText value="#{genderType.description}"/>
                        </h:column>                   
                   </h:dataTable>
          </af:selectInputText>             
          </h:form>
     </f:view>

Answer 1

I use IBM Rational Application Developer (RAD v.7)
As you know that my JSF code had worked before I started introducing ADF tags.
Now, I have resoved all the complilation complaints in my ***.jsp where I have the ADF <af:selectInputText ...> tag and all tags inside the <af:selectInputText ...> tag.
But, I have the "Error 500: Cannot find FacesContext" in the browser when I run the ***.jsp.
I believe it is in my web.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
     <display-name>
     ADF_TEST</display-name>
     <context-param>
          <description>
          The location where state information is saved.
Valid values are 'server' (typically saved in HttpSession) and 'client' (typically
saved as a hidden field in the form.
Default is server.</description>
          <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
          <param-value>client</param-value>
     </context-param>
     <context-param>
          <param-name>javax.faces.CONFIG_FILES</param-name>
          <param-value>/WEB-INF/faces-config.xml</param-value>
     </context-param>
     <context-param>
          <description>
          The default suffix for extension-mapped resources that contain JSF components.
Default is '.jsp'.</description>
          <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
          <param-value>.jsp</param-value>
     </context-param>
     <context-param>
          <description>
          Number of Views to be stored in the session when Server-Side State Saving is being used.
Default is 15.</description>
          <param-name>com.sun.faces.NUMBER_OF_VIEWS_IN_SESSION</param-name>
          <param-value>15</param-value>
     </context-param>
     <context-param>
          <description>
          If set to true while server-side state saving is being used, a serialized representation
of the view is stored on the server. This allows for failover and sever clustering support.
Default is false. This parameter is not available in JSF 1.0.</description>
          <param-name>com.sun.faces.enableHighAvailability</param-name>
          <param-value>false</param-value>
     </context-param>
     <context-param>
          <description>
          If set to true while client-side state saving is being used, reduces the number of bytes
sent to the client by compressing the state before it is encoded and written as a hidden field.
Default is false. This parameter is not available in JSF 1.0.</description>
          <param-name>com.sun.faces.COMPRESS_STATE</param-name>
          <param-value>false</param-value>
     </context-param>
     <context-param>
          <description>
          Monitors Faces JSP files for modifications and synchronizes a running server with
the changes without restarting the server. If this parameter is set to false or
removed from the deployment descriptor, any changes made to Faces JSP files may
not be seen by the server until it is restarted. This parameter is usually set
to true while the Faces JSP files are being developed and debugged in order to
improve the performance of the development environment.</description>
          <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <description>
          Load JSF runtime when the application server starts up. If this parameter is set to false or removed,
JSF runtime will be loaded and initialized when the first JSF request is processed.
This may disable custom JSF extensions, such as factories defined in the project.</description>
          <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
          <description>
          If set to true disables use of MultipartFacesContext, allowing underlying implementations to be used.
MultipartFacesContext is required when the FileUpload component is used, and can be disabled otherwise.</description>
          <param-name>com.ibm.faces.DISABLE_JWL_MULTIPART_CONTEXT</param-name>
          <param-value>false</param-value>
     </context-param>
     <context-param>
          <description>
          Value, in milliseconds, to be used for Expires header for resources served by the JavaScript Resource Servlet.
Default is never (31536000000 milliseconds or 1 year).</description>
          <param-name>com.ibm.faces.RESOURCE_EXPIRE_MS</param-name>
          <param-value>31536000000</param-value>
     </context-param>
     <context-param>
          <description>
          Defines the strictness of the conversion when converting from a string to a date.
The higher the value, the more exactly the value must conform to the format.
If 0 (liberal), all 'literals' are ignored while parsing a value, mis-ordered components will be rearranged,
any missing component is supplied using the current datetime, misspellings and incomplete spellings are allowed
(to the extent that they can be evaluated), 'E' and other non-unique components are ignored.
If 1 (strict), all 'literals' are ignored while parsing a value, any missing component is supplied using the current
datetime, misspellings and incomplete spellings are allowed (to the extent that they can be evaluated),
'E' and other non-unique components are ignored. For example if the pattern is MMMM dd, yyyy a user can enter 'Feb/02/04'
and it will be parsed as February 02, 2004.
If 2 (very strict), an exact match is required except long month names can be 'shortened' to the minimum number of unique
characters and 'E' and other non-unique components are ignored. Literals must match exactly.
Default is 1.</description>
          <param-name>com.ibm.faces.DATETIME_ASSIST_STRICTNESS</param-name>
          <param-value>1</param-value>
     </context-param>
     <context-param>
          <description>
          Defines the strictness of the conversion when converting from a string to a number.
The higher the value, the more exactly the value must conform to the pattern.
For numbers, currently strictness levels of 0 and 1 are equivalent. If the strictness is 2,
if number is signed, the sign must be provided (otherwise it's assumed positive).
Default is 1.</description>
          <param-name>com.ibm.faces.NUMBER_ASSIST_STRICTNESS</param-name>
          <param-value>1</param-value>
     </context-param>
     <context-param>
          <description>
          Defines the path for resources such as JavaScript libraries and images.
The value can be either:
1. An empty string. Context path of the current application will be used.
2. A path string. Example: /project13. A number. Specifies the number of nodes to use from the context path starting from the left.
Example: With a value of 1 if the context path is /screen/faces/SSID110267549/RID1102676
the path will be evaluated as /screen
Default is an empty string.</description>
          <param-name>com.ibm.faces.USE_UNENCODED_CONTEXT_PATH</param-name>
          <param-value></param-value>
     </context-param>
     <context-param>
          <description>
          Sets a custom url-pattern for the JavaScript Resource servlet.
Should match servlet mapping setting for the JavaScript Resource servlet. If the default default mapping
value '/.ibmjsfres/*' is modified, this context-param should also be modified.
</description>
          <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_URL_PATTERN</param-name>
          <param-value>/.ibmjsfres/*</param-value>
     </context-param>
     <context-param>
          <description>
          If set to true, forces JavaScript Resource Servlet to cache all resources on the server.
This can be useful when client-side caching is turned off.</description>
          <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_CACHE</param-name>
          <param-value>false</param-value>
     </context-param>
     <context-param>
          <description>
          Sets a custom charset mapping properties file similar to converter.properties in WAS.</description>
          <param-name>com.ibm.faces.ENCODING_MAPPING</param-name>
          <param-value>converter.properties</param-value>
     </context-param>
     <context-param>
          <description>
          Number of Views to be stored in the session when Enhanced State Saving is being used.
Default is 15.</description>
          <param-name>com.ibm.faces.ENHANCED_SERVER_STATE_SAVING_SESSION_STORED_VIEWS</param-name>
          <param-value>15</param-value>
     </context-param>
     <context-param>
          <description>
          If set to true, the entire JavaScript library, containing code for all components, will be included
in the generated pages as one file. If set to false or removed, multiple smaller JavaScript files will be
included, depending on the components used on the page.Default is false.</description>
          <param-name>com.ibm.faces.USE_HXCLIENT_FULL</param-name>
          <param-value>false</param-value>
     </context-param>
     <listener>
          <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
     </listener>
     <servlet id="Servlet_1181745021880">
          <servlet-name>Faces Servlet</servlet-name>
          <servlet-class>
          javax.faces.webapp.FacesServlet</servlet-class>
          <load-on-startup> 1 </load-on-startup>
     </servlet>
     <servlet id="Servlet_1181745029380">
          <servlet-name>JavaScript Resource Servlet</servlet-name>
          <servlet-class>
          com.ibm.faces.webapp.JSResourceServlet</servlet-class>
          <load-on-startup>-1</load-on-startup>
     </servlet>
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>/faces/*</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>*.faces</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>JavaScript Resource Servlet</servlet-name>
          <url-pattern>/.ibmjsfres/*</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>index.html</welcome-file>
          <welcome-file>index.htm</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>default.html</welcome-file>
          <welcome-file>default.htm</welcome-file>
          <welcome-file>default.jsp</welcome-file>
     </welcome-file-list>
</web-app>and my ***.jsp looks like:
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://xmlns.oracle.com/adf/faces" prefix="af" %>
<%@ taglib uri="http://xmlns.oracle.com/adf/faces/html" prefix="afh" %>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Test the ADF selectInputText Tag</title>
</head>
<body>
     <f:view>
          <h:form>
                <af:selectInputText label="Sex: " id="idInputText"
                   value="#{listOfValuesManagementBean.selectedGender}"
                    action="dialog:chooseGender" windowWidth="300" windowHeight="200">
                   <af:table id="gender" value="#{inputListOfValuesManagementBean.genderTypes}" var="genderType">
                        <af:column>
                             <f:facet name="header">
                                  <af:outputText value="Code"/>
                             </f:facet>
                             <af:outputText value="#{genderType.code}"/>
                        </af:column>
                        <af:column>
                             <f:facet name="header">
                                  <af:outputText value="Description"/>
                             </f:facet>
                             <af:outputText value="#{genderType.description}"/>
                        </af:column>                   
                   </af:table>
               </af:selectInputText>
          </h:form>
     </f:view>
</body>
</html>Message was edited by:
user537770