Inserting a MessageLovInput
To insert a messageLovInput component:
-
In the Design Structure Window of the desired file, locate the node in
which you wish to insert a messageLovInput component.
-
In the Component Palette, select Form Components
from the dropdown list, and then drag and drop the
messageLovInput component to the parent node of your choice.
The messageLovInput node is inserted and
highlighted under the expanded parent node.
-
In the Property Inspector, set the following attributes for the
messageLovInput component:
-
prompt - Enter the prompt text that displays before the
text field.
-
name - (Required) Enter a name for the component.
-
columns - Enter the number of columns to display in the
text field.
-
destination - Enter the URL to launch the page that will
populate the LOV window when the user clicks the LOV button.
-
rows -Enter the number of rows to display in the text
field. If the rows attribute is less than the maximumLength
attribute, the text willl scroll.
-
showWindow - Set to false if the value in the text field is
considered valid. No processing is performed. This attribute
should be data bound. In a partial page refresh, if showWindow is
true, the LOV window opens. If it is false, the text field is
re-rendered.
-
text - Enter the text value of the input field.
-
enterClientAction - Enter the clientAction to fire when the
user presses the Enter key. In the right column, click the
icon to open a dialog. In the Advanced tab, you
can enter an EL syntax data binding expression or use the Bind to
Data dialog to select a data source for this complex attribute.
-
formSubmitted - Select true to use form submission to
transmit the lovValidate event.
-
onLovInit - Enter the name of the JavaScript function to
call before opening the LOV window. Use the signature:
function initCallBack(params). The params
argument is a simple object of all the parameters that the destination URL
uses to open the LOV window. You can add, delete, or update any of
the parameters in this callback.
-
onLovValidate - Enter the name of the JavaScript function
to call immediately before sending the lovValidate event. Use the
signature: function initCallBack
(params). The params
argument is a simple object of all the parameters that the URL
uses to send the event. You can add, delete, or update any of the
parameters in this callback.
-
maximumLength - Enter the maximum number of characters per
line that can be entered in the text field. This value is
independent of the number of columns displayed.
-
onBlurValidater -Enter the client validater to fire on the
client when the text input field loses keyboard focus. In the
right column, click the
icon to display the dialog to edit the
onBlurValidater complex attribute.
-
onSubmitValidater - Enter the client validater to fire on
the client when the form containing the text input field is
submitted. In the right column, click the
icon to display the dialog to edit the
onSubmitValidater complex attribute.
-
partialRenderMode - Select multiple, none, or self to
specify the partial page rendering behavior. If set to multiple,
then set the partialTargets attribute, which automatically
includes the ID of the messageLovInput component.
-
partialTargets - Enter the IDs of the partial target nodes
to render when partialRenderMode is set to multiple.
-
primaryClientAction - Enter the clientAction to fire when
the text in the text input field changes. In the right column,
click the
icon to enter a ClientAction. See
Editing the PrimaryClientAction Attribute for details. Alternatively, use
the Advanced tab to enter an EL syntax
data binding expression or use the Bind to Data dialog to select a
data source for this complex attribute.
-
searchDesc - Enter the search description on the LOV button.
-
secret - Select true to hide the actual value of the text
from the user. Applies only to single line text fields only.
Default is false.
-
unvalidated - Set to true to inhibit the validation step.
Default is false.
-
validateBlanks - Set to true to fire the lovValidate event
even if the input field is blank or all whitespace. Default is
false.
-
wrap - Select the type of wrapping to be used in a
multi-row text field only. By default multi-row text does not wrap
at the edge of the column, but scrolls horizontally instead.
Available options are:
-
hard - Specifies that the value of the text
should include any carriage returns that are needed to wrap
the lines.
-
soft - Specifies that the text should wrap
visually but that the value of the text does not include
carriage returns.
Note: To use data binding, see
Data Binding a Component Attribute.
For information about message attributes, see
Setting the Message Attributes for a Message Form Component. For
information about other general attributes of message form components,
see Setting the General
Attributes for a Message Form Component.
Example (UIX XML)
Example: Copyright (c) Oracle Corporation 2002-2003. All Rights Reserved.
<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright (c) Oracle Corporation 2002-2003. All Rights Reserved. -->
<!-- lovInputTest.uix -->
<page xmlns="http://xmlns.oracle.com/uix/controller"
xmlns:ctrl="http://xmlns.oracle.com/uix/controller"
xmlns:ui="http://xmlns.oracle.com/uix/ui"
expressionLanguage="el">
<content>
<dataScope xmlns="http://xmlns.oracle.com/uix/ui">
<contents>
<document>
<contents>
<body>
<contents>
<form name="form1">
<contents>
<!-- importScript names="TableProxy()"/-->
<script>
<contents>
<!-- Define JavaScript functions to handle all the possible callbacks -->
function SelectCallBack(lovWin, field, event, mainWin)
{
// This function will be called after the select button has been clicked.
// - lovWin points to the not-yet-closed LOV dialog window.
// - field points to the lovInput field that triggered this
// LOV dialog.
// - event is the window close event
// - mainWin is the main window that opened the LOV
//
// Note: Because IE destroys the items on the window at close() time, but
// before the close callback, this callback gets called BEFORE the LOV Window
// is closed under IE. There should be no processing differences, but any
// confirmation dialogs will come up between the main window, and the still
// displayed LOV window. This can be very confusing.
// For this reason, this function is not setup. To test this function, you
// need to do two things:
// 1.) Add the following attribute to the lovInput element:
// onLovSelect="SelectCallBack"
// 2.) Load the TableProxy library by uncommenting the importScript above.
//
var selVal = '*NULL*';
if (lovWin)
{
if (lovWin.document)
{
var doc = lovWin.document;
if (doc.forms)
{
var forms = doc.forms;
if (forms && forms.length)
{
var form = doc.forms[0];
if (form)
{
var proxy = new TableProxy("lovTbl", form.name, lovWin);
var selRows = proxy.getSelectedRows();
for(var i=0; i < selRows.length; i++)
{
var rowid = proxy.getFormElement("rowid", selRows[i]);
selVal = rowid.value;
}
}
}
}
}
}
field.value = selVal;
return confirm("Click 'OK' to further process, 'Cancel' to use rowid.");
}
function _printCallbackParams(params, CBName)
{
// This function just raises a confirm dialog listing
// key:value pairs in the params object
var str = CBName + ' called with:'
for (var key in params)
{
str += "\nparameter: '" + key +
"', value '" + params[key] + "'";
}
return confirm(str);
}
function InitCallBack(params)
{
// If passed as the onLovInit attribute, this function is called
// after the LOV icon is clicked, but before the LOV dialog window
// is launched. This gives the developer a change to change the
// parameters that are going to the dialog window.
// The params object contains all the parameters which will end up
// on the URL.
// Add our own parameter. This will end up as a parameter on the
// LOV dialog window URL.
// (http://...?...&myParam=foo)
params["myParam"] = "foo";
return _printCallbackParams(params, 'InitCallback');
}
function ValidateCallBack(params)
{
// If passed as the onLovValidate attribute, this function is called
// before the lovValidate event is fired.
// This gives the developer a chance to add, subtract or change
// parameters that will be sent with the lovValidate event
return _printCallbackParams(params, 'pre-validate Callback');
}
</contents>
</script>
<stackLayout>
<contents>
<header>
<contents>
<flowLayout>
<contents>
<flowLayout>
<contents>
<styledText styleClass="OraPromptText"
text="First lovInput field: "/>
<messageLovInput name="lov1"
id="Lov1-target"
formSubmitted="true"
destination="listOfValues_Dialog.uix"
shortDesc="Click to select a predefined value"
partialRenderMode="multiple"
partialTargets="Lov1-dependent1
Lov1-dependent2
Lov1-dependent3"
showWindow="${uix.eventResult[
'Lov1-target'].showWindow}"
text="${ui:defaulting(uix.data.fieldData[
'Lov1-target'].fieldText,
uix.data.fieldData.defaultText)}"/>
</contents>
</flowLayout>
<spacer width="8"/>
<styledText styleClass="OraInstructionText"
text="summit elevation: "/>
<styledText styleClass="OraDataText"
id="Lov1-dependent1"
text="${uix.data.fieldData['Lov1-target'].row1.altitude}"/>
</contents>
</flowLayout>
<header>
<contents>
<stackLayout>
<contents>
<styledText styleClass="OraInstructionText"
text="These two fields return data from the
second selected row. This is a very simple
example, your application would actually
add rows to a table, update a dataset, or
do some other complex operation using all
the selected rows."/>
<flowLayout>
<contents>
<styledText styleClass="OraInstructionText"
text="Row 2, peak: "/>
<styledText id="Lov1-dependent2"
styleClass="OraDataText"
text="${uix.data.fieldData['Lov1-target'].row2.peak}"/>
<spacer width="15"/>
<styledText styleClass="OraInstructionText"
text="summit elevation: "/>
<styledText id="Lov1-dependent3"
styleClass="OraDataText"
text="${uix.data.fieldData['Lov1-target'].row2.altitude}"/>
</contents>
</flowLayout>
</contents>
</stackLayout>
</contents>
</header>
</contents>
</header>
</contents>
</stackLayout>
</contents>
</form>
</contents>
</body>
</contents>
</document>
</contents>
<provider>
<data name="fieldData">
<method class="oracle.cabo.servlet.demo.ListOfValuesDemoData"
method="getFieldSet"/>
</data>
...
</provider>
</dataScope>
</content>
<handlers>
<!-- The null event mapped to reset clears all on each initial visit -->
<event name="null reset">
<method class="oracle.cabo.servlet.demo.ListOfValuesDemoData"
method="doReset"/>
</event>
<event name="lovValidate">
<method class="oracle.cabo.servlet.demo.ListOfValuesDemoData"
method="handleLovValidateEvent"/>
</event>
<event name="lovUpdate">
<method class="oracle.cabo.servlet.demo.ListOfValuesDemoData"
method="handleLovUpdateEvent"/>
</event>
<event name="setSearchMode">
<method class="oracle.cabo.servlet.demo.ListOfValuesDemoData"
method="handleLovSearchModeEvent" />
</event>
</handlers>
</page>
See Inserting a ListOfValues
for thelistOfValues_Dialog.uix file.
Related topics
About MessageLovInput
About Message Form Components and Attributes
Inserting an End Named Child for a
Message Form Component
Inserting a ListOfValues
Working with Form Components
Copyright © 1997, 2004, Oracle.
All rights reserved.