OutputText : why both bind and value attribute and other gripes

Hi
gripe1
I have started using creator and I'm a bit confused as to why creator insists on the binding attribute being in place to link the outputText field to the default managed bean -
like most of us I want to set the value via a resource bundle. ( as shown blelow). If I delete the binding atttribute then outputText Field doesn't get displayed in the Visual Design tab. aaaaaaah!
<h:outputText binding="#{DemographicInformation.nameLabel}" id="nameLabel" value="#{bundle.userName_label}"/>
gripe2
When you declare a resource bundle; either through editing the source directly or dragging from the advanced palette you can't seem to be able place the contained "names" in this the individual outputText field values via value property->bind to object->select from property file. i.e you do don't see to be able to expand the f: loadBundle. This results in a lot of tedious typing
which I thought this tool was all about preventing!
Regards
Daniel

Re gripe 1:
Why do you want to remove the binding attribute? The binding attribute has nothing to do with the value - you can certainly display values from resource files without removing the binding attribute. One of the online tutorials (the Sign On example) shows a Creator project using bundle files.
Re gripe 2:
The designtime experience for using bundle files in the web app has been improved in the next version of Creator.
-- Tor
http://blogs.sun.com/tor

Similar Messages

Difference between using Binding and Value Attribute

what is the deference between using binding and value attribute, when I use binding attribute at the time of Value change listener is behaving like action listener,
Ex:
If I use value attribute, at the time of value change listener the component is not showing the result in the component but when I use Binding attribute it is happening automatically. So I want to know how the binding attribute is working.
I know, at the time of binding attribute the component is creating an instance at the bean side, So even also how it is following the life cycle of the JSF Frame work, and also Please suggest me weather which one is better to use either Binding or Value?

JNaveen wrote:
If I use value attribute, at the time of value change listener the component is not showing the result in the component but when I use Binding attribute it is happening automatically. So I want to know how the binding attribute is working.You need to learn about the JSF lifecycle. The ValueChangeEvent is invoked after conversion and validation in the 3rd phase, while the model values are updated in the 4th phase. In the valueChangeListener method you normally use ValueChangeEvent#getNewValue() to get the new value after the change.
I know, at the time of binding attribute the component is creating an instance at the bean side, So even also how it is following the life cycle of the JSF Frame work, and also Please suggest me weather which one is better to use either Binding or Value?Use the 'value' attribute to bind the value to the bean. Use the 'binding' attribute to bind the component to the bean. If you don't need to precreate the component or do other things than getting/setting its value, then there is no need for the 'binding' attribute.
Read on those links if you want to know something more about the JSF lifecycle:
[http://balusc.blogspot.com/2006/09/debug-jsf-lifecycle.html].
[http://jcp.org/aboutJava/communityprocess/final/jsr252/index.html] (pick 1st download).

Picklist -- display and value attribute

Is there a way to get and store both display and value attributes from the picklist? I would like to store the display attribute and the value attribute of the selected item from the picklist. It seems like it only returns one attribute. Thanks!

Get an instance of messagechoice...
there are two methods.
setListValueAttribute("ViewAttributeName");
setListDisplayAttribute("ViewAttributeName");
you can get both values...
Anoop

Difference between value attribute and value attribute under Node in contex

I have very basic question..it might be very simple but it is giving me a problem.
I have created one Node name "Input" and value attribute "Input1" under it.
I have just created one more value attribute named "in1" not under any Node.
I have created two input filed in the my view.One first I have mapped the value in properties
to variables "Input.Input1" and on another "in1".
When I deploy and run the application one Input box is coming as readonly and other is working fine .Will anybody tell me why it is so?

There is no major difference between value attribute and inside a node.
It is a separation of attributes. Usually all the attributes belongs to same purpose will create in one value node. Like, calling one BAPI - requestListBAPI - it contains all the bapi related value attributes.
For your question, one field is read only(Input.Input1), bcz that context is not created. see the context properties.....cardinality will be 0..n. Change the cardinality to 1...n (<b>or</b>) create that context element .
In your implementation create that value node like this in your init method.
wdContext.createInputElement();
It will solve your problem.
in1 - is a value attribute, which is mapped to your input element. It wont have any problem.
Regards,
Sri

Model attribute binding to value attribute.

Hi all,
I have problem that i have used a model in my view. First i will me executing that model. Then i need to use the ouput parameter of that model to assign it to the value attribute present in the same view. And make it to be visible in the field to which that value attribute is assigned. Please help me out.

Hi Selvakumar,
Is it that, Your value attribute , say 'var' (which is bound to the view field) is
the child of a value node(say this value node be 'MyNode')??
Then give
If only 1 record is needed for 'MyNode' set the cardinality of 'myNode' as 1..1 and then give
wdContext.currentMyNodeElement().setVar(wdContext.<outputModelNode()>.<currentOutputmModelNodeElement>.getOutResult());
Thanks
Smitha
Message was edited by:
Armin Reichert

Copying and pasting attributes and styles of text track

Simple question,
I have two text tracks and would like to copy and pasts the attributes and style tabs in "inspector" to another text track. How could I do this without having to manually set each individual track as I create it.
Thanks,

Did you check the opacity value in the paste attributes dialog?

h:selectOneMenu and "value" attribute

I have an issue with the <h:selectOneMenu> tag. On a page I've written, the select items are populated with a <f:selectItems> tag that is bound to a managed bean property with session scope which queries from a database table for the select items. The <h:selectOneMenu> value property - which determines the item that is selected - is bound to a property of a managed bean that has session scope.
There is a button on the screen that causes navigation to a new screen. On this screen, the user can add an entry to the database table from which the <f:selectItems> are populated. The event handler for the second screen adds a new item to the database table and sets the property on the managed bean to that determines which item is selected on the previous screen to this new value.
The problem I have is that the new item is added to the list, but it is not the selected item when the first screen is navigated back to. If I view the HTML code generated, none of the <option> tags contains the "SELECTED" property. Strangely, if I enter a new item that is less - alphabetically - than the existing items, it will be selected, but if I add an item that falls into the middle of the list or the end of the list alphabetically, it is not selected.
I don't know what to do here. Is there some requirement about sorting the collection that backs the <f:selecteditems> facet? This doesn't seem likely since I've tried various sorts to figure this out and nothing has worked. Is there a known bug setting the value property of <h:selectOneMenu>?
Any ideas?

When your setting the value for the <h:selectOneMenu> make sure its a string!
Here is a simple example
(.jsp page)
<h:selectOneMenu id="locationID" value="2">
   <f:selectItems value="#{LocationList.itemList}"/>
</h:selectOneMenu>
(HTML Code that gets generated from the .jsp page
<select id="edit:locationID" name="edit:locationID" size="1">
   <option value="1">Anoka</option>
   <option value="2" selected>MSO</option>
</select>

Difference between binding and value

Hi
I am new to JSF
Can you tell me what is the difference between binding and value attribute of a
JSF component ?
Many thanks.

Hi,
the binding is the component association to a managed bean (or backing bean). This allows you to manipulate the component in Java code stored in a managed bean.
The value is what the actual component value is.
Frank

Check table and value table -Example

Hi Experts
Please give me the step by step procedure to create the check table and value table, and how to work on it.
Thanks in advance.
Regards
Rajaram

Hi
Check Table is for Field level Validation whereas Value table is for Domain Level Validations.
Value Table proposes table for check table.
I think you are clear with this.
more elaborate.
Check Table
The Check Table is the table used by system to check if a data exist or not exist.
While creating a table if you want to be sure that a field can have some values
and these are in a certain table, you can give IT this table as CHECK TABLE.
Value Table
This is maintained at Domain Level.
When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator.
Here only allowed values is H or S.
When ever you use this Domain, the system will forces you to enter only these values.
This is a sort of master check . .
To be maintained as a customization object.
This mean that if you want to enter values to this table you have to create a development request & transport the same.
Differences:
1)check table will carry out the check for input values for the table field being entered in any application
and value table will provide values on F4 help for that table field.
2)The check table defines the foreign keys and is part of the table definition.
The value table is part of the domain definition.
check table is validation at field level.
value table is at domain level.
Value table is defined at the domain level and is used to provide F4 help for all the fields which refer to that domain.
Check table is defined against a field in SE11 if you want the values in that field to be checked against a list of valid values. For e.g. if you are using the field matnr in a table you could define MARA as the check table.
Also while defining a check table SAP proposes the value table as check table by default. Referring to the previous example if you tried to define a check table for the matnr field SAP would propose MARA as the check table.
1. what is the purpose / use ?
-- so that the user can select values
from some master table , for that field !!!!
2. This is done by
CHECK TABLE (foreign key concept)
(and not value table)
3. When we create a check table for a field,
then
some DEFAULT table is PROPOSED
4. that DEFAULT table is nothing
but PICKED up from the domain of that field,
and shown from the value of VALUE TABLE.
CHECK TABLE -it is a parent table.
for example..
i have two tables ZTAB1 and ZTAB2.
I have one common field in both the tables,i can make any ztable to be the check table .If i make Ztab1 to be the check table then when i have to make an entry in ztab2 i will check whether ztab1 is having that value or not..
its also field level checking..
Valuetable-It is nothing but default check table.
one parent can have n number of child tables.For example
For ztable we have zchild1 and zchild2 tables r there.
Its domain level checking..When zchild2 uses the same domain as used by zchild1 then the system automatically generates a popup saying a check table already exists would u want to maintain it.
go to domain and then press the value tab u can see the valuetable at the end...
Please refer the links below,
d/r b/n check and value table?
wjhat is the exct difference between check table and value table
what is the check table and value table
check table and value table
Re: wjhat is the exct difference between check table and value table
http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm

Condition types and value fields

hi Gurus,
Can anybody please explain me what is condidion type and value field and the purpose of these two in costing??
Regards,
S.Sumana

Dear Sumana,
Condition types and Value field conjuction is used in Profitability Analysis.
Condition type is an element in pricing procedure. For e.g price of the product consist of several things like base price, discount, tax, etc. so each compenent is called condition type.
Value fields are grouping of cost elements for e.g. you have created a cost element Sales revenue then all revenue cost elements which consist of revenue.
Condtion type Base Price is revenue which is mapped to value field Sales revenue. So as soon as the billing document is created value field is updated.
For more information on Profitability analysis please read the documentation provide in www.help.sap.com
Regards,
Chintan Joshi.

Value attribute not visible in runtime collection

Hi,
I have created some 2-3 value attributes (display only) in a standard model node for BTDOCFLOW (which also contains some display only fields). Put in the logic in their Getter methods and fields are getting displayed in UI with the values.
Now, my requirement is to display this table view (Assignment block) in default sorting based upon one value attribute and one model node attribute. But the problem here is, I am unable to find value node attribute at runtime in BTDOCFLOW collection at DO_PREPARE_OUTPUT. (Even display only standard context node attributes, which are not part of model node structure are not visible)
I have re-defined method GET_TABLE_LINE_SAMPLE with the value attributes, resulting in enhanced rv_sample line, but still the value attribute is not visible at runtime in the collection.
Can someone pl. tell me, how can I display my value attributes in collection along with model node attributes, so that I can do default sorting based upon one custom and one model node attribute.
Thanks,

Hi,
Whne you define value attributes within the model attribute then the node becomes mixed instead of either value node or model node.
So you need to access the mixed node and then should access model attributes and value attributes separately.
Get your collection into a normal entity then assign the entity to mixed node
DATA: lr_mixed TYPE REF TO cl_bsp_wd_mixed_node ,
            current TYPE REF TO if_bol_bo_property_access,
             lr_current TYPE REF TO cl_crm_bol_entity.
     current ?= me->typed_context->entity name->collection_wrapper->get_current( ).
      lr_mixed ?= current..
      lr_current ?= lr_mixed->if_bsp_wd_ext_property_access~get_model_node( ).
Best Regards,
Dharmakasi.

Facing problem with Value Attributes

Hi,
I have created a value attribute under the context node. This attribute is editable field. User can enter value for this attribute on WEBUI.
Now, my problem is in GET_METHOD.
In get method, normally we get the value using "COLLECTION_WRAPPER" or "ITERATOR". If the attribute is BOL attribute , then we can get the value from these . However my attribute is value attribute, and I am unable to get the value using COLLECTION_WRAPPER or ITERATOR. So, when the user enters any value it is coming into GET_METHOD, and displaying blank value on the screen.
Now my bottom line question is: if the attribute is value attribute, how can we get the value in GET method.
Note: I can't add it as BOL attribute, for my case it is not possible.
Thanks,
Sandeep

Hi,
if it is a pure value note then you could access this using this class instead of bol class:
lr_value_node TYPE REF TO cl_bsp_wd_value_node.
Kind regards
Manfred

OIM 11gR2 : recon matching multi-value attribute

Hi, OIM Gurus,
The basic recon matching rule works very well, but business want to matching against users multi-value attribute, for example, one of the multiple AD accounts of user.
Can anyone tell me how this can be done in OIM 11gR2 BP7.

Rajiv, you are right. I choose the "Reconciliation Create/Update/Delete Received" tasks as I could not make Kevin's suggestion work. Here is what I did and failed to trigger the custom adapter.
(1) I created a task called "Child Table UD_MYAuth row updated" and attach my custom-adapter to it.
(2) I found "Reconciliation Update Received" task is called whenever there is a change in multi value attributes and is called by "Target Recon", which update the multivalue in child table UD_MYAuth.
In this task I mentioned the child table (UD_MYAuth) and trigger type as 'update'. The idea was to trigger the exclusive child-table related task created in step-1 from this "recon update Rcvd" task.
(3) To test this setup, I changes the multi-valued data of a user in LDAP and ran the "Target Recon". I found that adapter code was not executed, that means "Child Table UDMYAuth row updated" task was not called.
Since I have mentioned the child table and trigger type in "Recon Update Rcvd" task, should not it trigger "child table xxx row updated" task ? I could not make it work.

Difference between the binding and the value attribute of an Oracle ADF com

Can somebody please tell me the difference between
the binding attribute and the value attribute of any oracle ADF component such as inputText and when would we use one over the other.
THanks,

Value represent the value that is going to be displayed by the item.
Binding indicate the backing bean object that represents the instance of the component.

For the Attribute Movement type(BWA) we use Value " 201" and not "101" why?

Hello Experts,
We are in SRM 7.0 classic scenario,
For the Attribute Movement type(BWA) we use Value " 201" and not "101" and provide the Source syst(backend R/3)
Can you all plz help me understand what is the difference if use value "101" for the Attribute Movement type(BWA)
Also,can you all plz help me understand if we shd use value "101" or "201" for the Attribute Movement type(BWA) and under what scenario.
Any pointers will be highly appreciated.
Thanks & Regards,
RKS

Hi,
Movment type " 201 maintained for the Classic scenario only.
It is necessary to maintain the attribute if the default material group for a given user (or) sit is set to a backend logical system. The EBP system knows that if the user is set for backend procurement ,that there might be a possibility for a reservation to be generated therefore it checks to see that a value for this attribute is maintained. The BWA value should be defined for the as 201 preceeded by the logical system and a backslash.
101 should not be used. This isfor the Good receipt.
In the extended classic scenario when you do the confirmations in SRM the movement type 101 will be created in the
backend system (R/3 or ECC6.0)
Regards
Ganesh Kumar .G

OutputText : why both bind and value attribute and other gripes

Similar Messages

Maybe you are looking for