Problem in using the f:attribute tag in JSF

when I am trying to loop the JSF using the JSTL tag <c:foreach> I am getting the value as "Error:form_id0" .cold any one help me please

Now with Unified EL - JSTL and JSF tags are supposed to work on one page.
If you want to use Unified EL you need
1) A container that is built on Servlet 2.5 / JSP 2.1 , and example of such a container is Tomcat 6.x
2) Probably need to upgrade to JSTL 1.2 , and JSF 1.2
3) If you're upgrading the container to Servlet 2.5 then web.xml should conform to Servlet 2.5 version.
4) Use correct taglib URIs for JSTL 1.2 and JSF 1.2
Read here: Summary of new features in JSP 2.1
http://java.sun.com/developer/technicalArticles/J2EE/jsp_21/index.html
JSP 2.1 Technology and JSF 1.2 Technology
http://java.sun.com/developer/community/chat/JavaLive/2004/jl1207.html
http://java.sun.com/products/jsp/index.jsp
Message was edited by:
appy77

Similar Messages

Using the binding attribute within Tomahawk's t:dataList tag

I am trying to create a .jsp page with a dynamic list of tables. Each table on the page has a dynamic number of columns. I read an excellent blog ([The BalusC Code - Using datatables|http://balusc.blogspot.com/2006/06/using-datatables.html#PopulateDynamicDatatable]) that taught me how to create dynamic tables using the binding attribute. I can now get the tables with dynamic columns working.
What I would like to do next is nest the dynamic tables within a Tomahawk t:dataList tag:
<t:dataList value="#{utilitiesTableSegBean.attributeTables}" var="attributeTable">
    <h:outputText value="#{attributeTable.title}"/>
    <h:panelGroup binding="#{attributeTable.dynamicTableGroup}/>
</t:dataList>
{code}
When I run my app I get this error:
javax.servlet.ServletException: javax.servlet.jsp.JspException: org.apache.jasper.el.JspPropertyNotFoundException: /s/UtilitiesTableSeg.jsp(57,56) '#{attributeTable.dynamicTableGroup}' Target Unreachable, identifier 'attributeTable' resolved to null
Why do I get this error?
If I remove the h:panelGroup tag then the h:outputText tag works just fine. Why does 'attributeTable' resolve to null for the binding attribute of h:panelGroup, yet works for the value attribute of h:outputText?
So then I thought that I might be able to make it work with an index into a bean property that returned the list of table objects. So I tried to modify my panel group tag to:
{code}<h:panelGroup binding="#{utilitiesTableSegBean.attributeTables[0].dynamicTableGroup}"/>{code}
I was just doing a quick initial test and expected to see the first table repeated over and over because I had hard coded the value of '0' as the index. But I was wrong. It listed through all of the tables correctly. Why? This makes no sense to me!
So I changed my jsp again so that it looked like this:
{code}
<t:dataList rowIndexVar="tableIndex" value="#{utilitiesTableSegBean.attributeTables}" var="attributeTable">
    <h:outputText value="#{attributeTable.title}"/>
    <h:panelGroup binding="#{utilitiesTableSegBean.attributeTables[tableIndex].dynamicTableGroup}"/>
</t:dataList>
{code}
This is how I expected to code it so that the tables would all be shown correctly. And it gives this error:
org.apache.jasper.JasperException: An exception occurred processing JSP page /s/UtilitiesTableSeg.jsp at line 57
(Line 57 is the line with the h:panelGroup tag.)
Root cause: javax.servlet.ServletException: javax.servlet.jsp.JspException: java.lang.IllegalArgumentException: null
I would really like to get the original version working, but any feedback and/or suggestions would be greatly appreciated. I have spent a lot of time trying to figure this out and I just don't know where else to look.
Thank you very much!
Dave

Yes, sorry about that - I started off trying to prove a potential solution.
Aim:
A user logs onto a weblogic application and is authenticated against OID. The application is making SOAP service calls to a proxy endpoint monitored by another vendors software which authenticates the user against the ldap and checks their roles to see if the user can call the service.
Solution so far:
The initial application gets the username from the JAAS principal, but the password is not supplied. I can easily supply the SHA password digest to it (but putting a cleartext password in the header will probably not be given the go-ahead). This would enable the application to make the SOAP call with a username and digest.
The software protecting the services can be configured in a variety of ways to authenticate the user to the ldap. One involves using the wsse username token in the header (cleartext password or digest).
This authentication is failing and I don't yet have the diagnostic tools available to see which stage is in error. I was trying to prove that you could actually authenticate with an SHA password digest by doing a bind.
Regards

How to get cm:search to use the max attribute when creating the SQL query?

When we use the max attribute in the cm:search tag, it does not seem to honor the max attribute when creating the SQL query. However, the result returned from the tag is limited to the number specified by the max attribute. Then the tag seems to work as intended, but the performance will be sub optimal when the SQL query returns unnecessary rows to the application.
We use the cm:search tag to list the latest news (ordered by date), and with the current implementation we have to expect a decrease in performance over time as more news is published. But we can’t live with that. We need to do the constraint in the SQL query, not in the application.
The sortBy attribute of cm:search is translated to “order by” in the SQL query, as expected.
Is it possible to get cm:search to generate the SQL query with an addition of “where rownum <= maxRows”?

Hi Erik,
The behavior of a repository in regards to the search tag's max results parameter is dependent on the underlying repository's implementation. That said, the OOTB repository in WLP does augment the generated SQL to limit the number of rows returned from the database. This is done in the parsing logic. This behavior may differ with other repository implementations.
-Ryan

The name attribute on the img element is obsolete. Use the id attribute instead.

When I valadate my page I get an error "The name attribute on the img element is obsolete. Use the id attribute instead." In DW CS5.5 I cannot seem to enter an ID without DW also adding the ID as a name attribute too. Aside from manually going in and removing the name attribute from the code.

It won't hurt to leave the name attribute in your <img> tag. In fact, it may be necessary if you are going to add an image rollover behavior, since DW's javascript relies on that name attribute's value to correctly identify the desired image on the page.

Error occurred in deployment step 'Add Solution': A feature with ID '' has already been installed in this farm. Use the force attribute to explicitly re-install the feature.

Hi I am getting the error
Error occurred in deployment step 'Add Solution': A feature with ID 10495515-2482-41fd-98eb-3c87f739f54b has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
when trying to deploy web parts
question 1 - how do i use the force attribute when deploying from visual studio
question 2 - am i deplying it to the right place, if i deply it to the
url:port that points to my central admin tool it deploys but i cant seem to see it in any of my webs in my site collection, if i deploy it to the
url:port that points to my site collection I get this error.
im new to all this by the way :)
thanks in advance

If you are deploying from Visual Studio then please follow this post:
http://sharepointfordeveloper.blogspot.com/2014/03/solved-visual-studio-issue-error.html
Open the visual Studio and navigate to the feature XML file and add the bellow attribute.
AlwaysForceInstall="TRUE"
The <FeatureName>.Template.Xml output would be some think link this.
<?xml
version="1.0"
encoding="utf-8"
?><Feature
xmlns="http://schemas.microsoft.com/sharepoint/"
AlwaysForceInstall="TRUE"></Feature>

Feature with ID 15/.. has already been installed. Use the force attribute to explicitly re-install the feature

Hi everyone,
I really become desperate with this one. I know, it's mentioned hundred times in the web, and it really works when you use a force deployment, but my simple question is: Why?
To explain my issue: We have several SharePoint 2010 solutions which we want to deploy to SharePoint 2013 with Visual Studio 2012 running on Windows Server 2012. Site solutions work. But farm solutions just don't. I get the error (you
guessed it): A feature with ID 15/... has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
And it does really work with the force attribute, but why on earth do you have to use the force flag? Something has to be different, and if there is an already installed feature with this ID, then why can Visual Studio not uninstall or
deactivate it by itself first? This error never occurred with SharePoint 2010 and VS2012, although features are already installed.
Thanks a lot for your effort.
Best regards,
Patrick

Hi Check this
1.Double click on the feature.... ( or right click and choose properties)
2.then in the properties window make
3. ALWAYS FORCE INSTALL = false... (this should be false)
Manoj Gangwar | Sharepoint MCPD | Sharepoint MCTS |

I am having problem with using the Basic brush definition

I am having problem with using the Basic brush definition. When I try to click on it will not allow me to use it and will automatically use the 5 pt. oval brush definition. The only way I can use the basic brush is after I have already drawn something and then I have to click on the stroke and then press basic. This is incredibly annoying and if anyone could help I would greatly appreciate it. (I have Adobe CS6)

for whatever reason, the basic 'brush' you see in the brushes palette effectively means removing any brush from a path. to draw with the brush tool you need a brush defined. in your case the last one selected being the 5 pt oval one.

Ipad 3 charger problem im using the original charger and it say is not apropiet for device.this problem star today. :/

ipad 3 charger problem im using the original charger and it say is not apropiet for device.this problem star today. :/

Take it to an Apple Store for evaluation and possible replacement.
Make a Genius Bar Reservation
http://www.apple.com/retail/geniusbar/
 Cheers, Tom

I have problems when using the camera on my iPhone 4S (the same for my daughter with a iPhone4) A veil around the blurred photo, a development impossible and completely unable to read the bar code or QR code. What to do?

I have problems when using the camera on my iPhone 4S (the same for my daughter with a iPhone4)
A veil around the blurred photo, a development impossible and completely unable to read the bar code or QR code. What to do?

Sounds kind of stupid, but check to make sure that your iphone case cover is not blocking the edge of the camera lens. I had a silicone case on my 3S and when it got older, it started tot slip and the edges of my pictures were blurred.

We encountered a problem during use the Configtool access JAVA engine.

We encountered a problem during use the Configtool access JAVA engine.
Our environment of system as below:
HardWard: IBM i570
OS: IBM as/400 V5E3
DB: DB2/400
Application system:SAP XI 3.0
The problem we encountered as below:
Our company used XI 3.0 SR1 for exchange data between SAP R/3 and no-sap system.For now,we wanna create a backup system(for
offline recovery),so we backup the XI product system throught entiry system save in AS/400(we stopped the XI system before
save process start).And following,we restored from the tape that we save from XI product system to the new backup system(they
are whole different paratition),but the problem is coming.Describe as following item:
1. The application seem to can be started but the java node always restart circularly(We have 4 java node now),I think
because of different of hardware configure(between XI product and Backup system) and lack of hardware resource.(XI prduction
have 5 CPUs and 22G Mem,Backup system have 2 CPUs and 16G MEM ).Therefore we wanna decrease the number of java nodes for
start application in backup system(throught configtool).
2. We wanna use configtool to decrease the java nodes for start backup system.But we encountered a problem during running the
configtool ,the information of prompt dialog as following:
Error occurred while working with Configuration (Scanning).
Msg:Error while connecting to DB.
We also see the system.log that below the directory of usr\sap\PXI\DVEBMGS00\j2ee\configtool,and found some error as
following text:
#1.5#C0000A0008A8000000000000017A906E000423BFFC7246E0#1165207387826#/System/Configuration/Logging##com.sap.tc.logging.APILogg
er.LogController[addLog()]#######Thread[main,5,main]##0#0#Info##Java#TC_LOGGING_CONFIGURATION_NEW_ITEMS
[C0000A305666000000000002018FB1F70003D67C779ECE88]##The () has been added to the !#3#Log#.
system.log#/System#
#1.5#C0000A0008A8000000000001017A906E000423BFFC73A670#1165207388006#/System/Server##com.sap.engine.core.configuration#######T
hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store
Z:
sapmnt
PXI
global
security
lib
tools
iaik_jce_export.jar#
#1.5#C0000A0008A8000000000002017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T
hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store
Z:
sapmnt
PXI
global
security
lib
tools
iaik_jsse.jar#
#1.5#C0000A0008A8000000000003017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T
hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store
Z:
sapmnt
PXI
global
security
lib
tools
iaik_smime.jar#
#1.5#C0000A0008A8000000000004017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T
hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store
Z:
sapmnt
PXI
global
security
lib
tools
iaik_ssl.jar#
#1.5#C0000A0008A8000000000005017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T
hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store
Z:
sapmnt
PXI
global
security
lib
tools
w3c_http.jar#
#1.5#C0000A0008A8000000000006017A906E000423BFFC9C25A0#1165207390660#/System/Configuration/Logging##com.sap.tc.logging.APILogg
er.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[main,5,main]
##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the
has been changed from to )!#5#resource bundle
name#LogController#com.sap.security.core.server.secstorefs.SecStoreFS#<null>#com.sap.security.core.server.secstorefs.SecStore
FSResources#
#1.5#C0000A0008A8000000000007017A906E000423BFFC9C4CB0#1165207390670#/System/Configuration/Logging##com.sap.tc.logging.APILogg
er.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[main,5,main]
##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the
has been changed from to )!#5#resource bundle
name#LogController#/System/Security/SecStoreFS#<null>#com.sap.security.core.server.secstorefs.SecStoreFSResources#
#1.5#C0000A0008A8000000000008017A906E000423BFFCAC7D38#1165207391731#/System/Server##com.sap.engine.core.configuration#######T
hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###OpenSQLDataSource successfully created with secure
store.#
#1.5#C0000A0008A8000000000009017A906E000423BFFCDA3070#1165207394726#/System/Configuration/Logging##com.sap.tc.logging.APILogg
er.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[main,5,main]
##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the
has been changed from to )!#5#resource bundle
name#LogController#/System/Database/sql/jdbc#<null>#com.sap.sql.log.OpenSQLResourceBundle#
#1.5#C0000A0008A800000000000A017A906E000423BFFCDB41E0#1165207394796#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnect
ionFactory#######Thread[main,5,main]
##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error
occurred on connection : code={0,number,integer}, state="", message="".#5#-99999#08001#The application requester
cannot establish the connection. (XIPRD)#jdbc:as400://XIPRD/SAPPXIDB;transaction isolation=read uncommitted;data
truncation=true;date format=jis;time format=jis;sort=hex;hold input locators=true;hold statements=true;cursor
hold=false#<null>#
The "SQL error occurred on connection" happened during start run configtool.
We don't know how to solve this problem.
Thanks

I am unable to start my configtool.bat to administer JVM memory settings for my J2EE.
Wait......
Thanks

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

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>

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

When using the placholder attribute in an input field with a dark background, why can't the blinking caret be white on focus?

Chrome and Safari both do this, making it clear to the user that they're in the field and ready to type. Currently the caret will take the color property but only once the user has started typing. This seems like it would be a worthwhile feature to bake into the next build of FF.

I have a separate java class that gets my data and returns a Result object. Do you mean java.sql.ResultSet?
In my main servlet I do the following:
request.setAttribute("supporttracker",
supporttracker.findsupporttracker(monthYear));
and then in my JSP I can iterate through the Result
like the following with no problems:
<c:forEach var="supporttracker" begin="0"
items="${supporttracker.rows}" varStatus="counter">
My problem is that I can only iterate through this
once in the page whereas I have no problem doing
multiple forEach loops through other types of
lists/collections such as an ArrayList. Right, because a ResultSet is a database cursor and doesn't act the same way that an ArrayList does. It's more like an InputStream - once you read it, you close it. If you want to re-read it, you have to re-initialize it again.
Iterators behave that way, too. Once you walk through them, you have to re-initialize them.
I've looked
on the web and in a couple of books, I first thought
it may be scope or some attribute in forEach that I
was missing but I'm stumped. It seems like it's
because the pointer to the result set is at the end
of the result set when trying the second iteration,
but I thought by using the begin="0" would put the
pointer at the first row again, on my second
iteration I'm getting no rows/data outputed.
Please help and thanks in advance!The better thing to do is for your method to return a List of objects, one per row, that represent what the ResultSet returns. Have that method iterate through the ResultSet, loading the rows into the List, and close it before you leave in a finally block. A database cursor is a scarce resource, so it's a good idea to close it as soon as you can.
%

Embedding inline HTML data in XML using the mx:XML tag with < and >

What is best practice for embedding HTML within the
<mx:XML> tag? Programmatically, I can implement this
successfully:
[Bindable]
public var xmlDP:XML = <component data="<" />;
However, I get the following error if I try to store the same
data inline in an mx:XML tag, as such:
<mx:XML id="xmlDP">
<component data="<" />
</mx:XML>
Error #1095: XML parser failure: Unterminated attribute.
If I change the MXML tag as follows, it works fine:
<mx:XML id="xmlDP">
<component data="&lt;" />
</mx:XML>
Unfortunately, I also can not source the mx:XML tag to an XML
file which uses < or > codes, as it yields the same
results. This leads me to believe that the <mx:XML> tag does
not support the special character codes for < and >, but why?
Incidentally, this code also gives a 1095 error:
<mx:XML id="xmlDP">
<component data="<" />
</mx:XML>
This is causing an issue with my source data as it is not
hand typed into Flex, and standard XML supports the < and
> codes. I have tried a full HTML string, as shown below,
but this also generates the error:
<mx:XML id="xmlDP">
<component data="<b>Test</b>"
/>
</mx:XML>
Many thanks for any input you may have!

I’m generating the XML source file with
Microsoft’s XML Notepad 2007. It will encode invalid special
characters automatically. My understanding is that this is the
proper way to handle the less than symbol in a XML string, that is
to say using the < code.
With respect to the escape and un-escape methods, I am able
to successfully implement these in AS, but not in MXML. This makes
sense considering they are AS methods, but I was hoping to be able
to do something like:
<mx:XML id="xmlDP">
<component data="escape('<');" />
</mx:XML>
This gives the following compilation error:
The value of attribute "data" must not contain the '<'
character.
As does using the escape character as such:
<mx:XML id="xmlDP">
<component data="\<" />
</mx:XML>
Below is an example of what the escape character may be used
for in AS:
var myString:String = "\"";
trace(myString);
// result: "
Likewise, I can escape the < character as such:
var myString:String = escape("<");
trace(myString);
// result: %3C
<mx:XML id="xmlDP">
<component data="%3C" />
</mx:XML>
trace(un-escape(xmlDP.@data));
// result: <
As you can see, using %3C and unescaping in AS will yield the
correct result; however, this is not a practical method of
representing the data in MXML as I would have to write an AS method
to un-escape the XML string anyway, so I might as well just store
the data in AS to begin with. I was hoping for a way to source an
mx:XML object, without having to load it into ActionScript
manually. Here’s an example of the functionality I would
expect:
<mx:XML id="xmlDP">
<component data=">" />
</mx:XML>
trace(xmlDP.@data);
// result: >
Only this does not work for the less than symbol. I’m
assuming at this point that this is a bug in the Flex compiler.
Thanks again for your help troubleshooting this one!

Using the capture details tag

Hi... i have a capture details form on my product details page, where customers can write a personal message to go with their purchase(flowers).
On the shopping cart layout the tag_capturedetails displays the message, but also the product attributes, - which is not required. Is there a way to "filter" the tag so it only displays the message that the customer has entered? Thanks in advance

Thanks, .... tag_capturedetails is on the product details page, user fills this in and the message is appended to the Product description field. Unforunately in the shopping cart, in the productname field, it displays this message as an attribute of the product so is not really usable in its default state.
Also in the shopping cart , if you insert the tag_productdescription on the shopping cart layout so you can view the actual message, but what displays is also : product name and the product attributes attributes, so again - Very confusing and unusable.
I have a workaround which hopefully helps anyone with asimilar situation. I have products with no attributes. The capture details form is attached on the detail view page for a user to fill in his own message. At the shopping cart, I have used custiom1 to display the Product Name, so no attributes(ie the message) are displayed. At the bottom of the cart is the Personal Message, tag_-productdescription which is the tag that displays the message, and sadly also the attributes of the product. As the product has no attributes, the field only displays the message.
It seems to work for my flowers site. Bit odd this cant be done a bit more easily - makes it hard for similar sites, flowers, gifts, etc.
I could put a message field in the checkout registration, but this seems to lose the buying momentum of the purchaser at the time of viewing the product. Has anyone had this issue and how do you work around it?

Problems in using the driver coming with application in Crystal Report

Post Author: StrongWare
CA Forum: Data Connectivity and SQL
Hi! All,
I used the ADORecordSet to fetch data from tables, and pass it to ther report at runtime using AddADOCommand.
I got the ActiveConnection and ActiveCommand from ADORecordSet and passed them as parameters of AddADOCommand, it seems the AddADOCommand opens an addional connection, which can be told from the ODBC trace, instead of using the ActiveConnection I passed in.
Is that true?
It causes the big problem for me, since the ActiveConnection I passed in was opened using our OEM DataDirect driver and I assumed the AddAdoCommand uses it directly, but it is not the case!! The AddADOCommand just uses the connection information from ActiveConnection and opens an additional one. Since the connection string contains the driver name, so this connection is also opened via our OEM DataDirect Driver. But the Crystal Report tries to unlock it using its own license/password {qecr.lic,brahmabrahmabrahmabrahma} to unlock our OEM driver, which of course raises the license warning from DataDirect Driver 5.2!! After a certain grace period, any sql operations under the cover of AddADOCommand fail and thus causing the failure of AddADOCommand.
Now what is the solution?
1. how to avoid open an additional connection? or any other API I should call to avoid this?
2. How Crystal Report works with the driver coming with the application, and this driver needs to be unlocked before being used.
Thanks
Strong

I don't have the any driver's source code (such as ividcpwr.dll source code), how can I modify the specific driver through labwindows.
Follow your advice I use I/O trace to get trace as follows:
1 IviDCPwr_InitWithOptions ("ke2303", VI_FALSE, VI_TRUE, "", 0x0C913064) VI_SUCCESS 14:45:10.675
2 IviDCPwr_ConfigureVoltageLevel (ke2303, "CHANNEL1", 3.8) VI_SUCCESS 14:45:11.405
3 IviDCPwr_ConfigureCurrentLimit (ke2303, "CHANNEL1", 0, 3) VI_SUCCESS 14:45:12.104
4 IviDCPwr_ConfigureOutputEnabled (ke2303, "CHANNEL1", VI_TRUE) VI_SUCCESS 14:45:12.824
5 IviDCPwr_Measure (ke2303, "CHANNEL1", 1, 0) VI_ERROR_TMO 14:45:16.207
6 IviDCPwr_GetError (ke2303, -1073807339, 0, "") 0x00000037 14:45:32.991
7 IviDCPwr_GetError (ke2303, -1073807339, 55, "Primary Error: ..................") VI_SUCCESS 14:45:32.991
8 IviDCPwr_close (ke2303) VI_SUCCESS 14:45:33.847
I cannot see any GPIB command in the trace but some IviDCPwr functions.
Besides, if I know any bug (eg. some wrong GPIB command) in ividcpwr.dll, how can I modify it before I get it's source code.
Pls teach me anytime in your conveneince.
thanks!

Problem in using the f:attribute tag in JSF

Similar Messages

Maybe you are looking for