Regarding Value and Binding properties of af:inputTextBox

Hi All,
I am using JDeveloper 11.1.1.6.0. I want to set the value for af:inputTextBox from the backing bean.
I observed there are two properties for this component, 'Value' and 'binding'.
So, I thought of using 'Value' property. For this I created a property in my backing bean.
Number textBoxValue; //Setter and getter methods for this ( I want to display numbers ans persist the same thats whay i have given as Number)
and in one of my methods I had given,
textBoxValue = new Number(12);
I am able to display the value in the UI
Here goes my queries, please clarify these.
1) What is the need of these two properties?
2) How can set value using the 'Binding' Property.
3) Can I set value to the input using both properties?
4) If 2nd point is correct then what will happen, if I set two different values to the textbox using these two components.
Thanks & Regards,
Ravi.

1) Binding is uses as an EL reference that will store the component instance on a bean. This can be used to give programmatic access to a component from a backing bean, or to move creation of the component to a backing bean.
Value represents the value of the component. If the EL binding for the "value" points to a bean property with a getter but no setter, and this is an editable component, the component will be rendered in read-only mode.
So they are different.
2) You don't
3) You don't
4) as 2) in not correct this is not relevant
If you want to set the value of a ui component from inside a bean you have different possible solutions. Lets assume you have a binding for The component to bean. In case of a input text the bean property would be of type RichInputText. Lets the property name be myIPT. Then you set the value as myIPT.setValue("YOUR VALUE"); (if the component shows text).
If you have bound the value property of the component to a bean attribute (using EL) you only need the change the bean attribute.
If the value is bound to a value binding (e.g. one that was generated by dragging a VO onto the page and dropping it as form), you get the the value binding by
// GET A METHOD FROM PAGEDEF AND EXECUTE IT
// get the binding container
BindingContainer bindings = BindingContext.getCurrent().getCurrentBindingsEntry();
// get an ADF attributevalue from the ADF page definitions
AttributeBinding attr = (AttributeBinding)bindings.getControlBinding("NAME_OF_THE_ATTRIBUT");
attr.setInputValue("test");Timo

Similar Messages

Difference between value and binding ?

hello
I am afraid I am not clear on difference between value and binding of a component?
I will appreciate if you supply an explanation.
kind regards

Binding? Aren't you talking about JSF? That term doesn't occur in JSP world.

Value and binding attributes?

In a number of UIComponents there is a value and a binding attribute. What is the difference between these attributes and when should one be used vs. the other?

The "binding" attribute is used to bind the tag to a related instance of a component on a backing managed bean.
For example, if you had created an instance of HtmlPanelGrid (called "grid") on a backing bean and had a getter/setter method for that component (getGrid/setGrid), you would use "binding={managedBean.grid}" to tie the <h:panelGrid> tag to the backing instance of component.
The "value" tag is used to assign a value to the component. This may be a String for some components (i.e. outputText) or a List (i.e. dataTable)
The simplest example would be:
<h:outputText value="Hello world!"/>
The preceding tag would render text of "Hello World!"
However... if you were to use binding for that... in your managed bean:
private HtmlOutputText text = new HtmlOutputText();
text.setValue("Hello world!");
public void setText(HtmlOutputText t) {
this.text = t;
public HtmlOutputText getText() {
return text;
Then on the JSP:
<h:outputText binding="#{managedBean.text}"/>
Regards.

Value or binding, best practice.

I was using a lot of value attribute before. Played with Sun Creator lately and realized that it is using binding very heavily.
What's the best practice to use value and binding?
To use binding, it's more like Java Swing. You can access the UI Component inside the page bean. To use value, the user input is converted to the right type by the framework, which is very convenient.
thanks.

Note that you can use both at the same time.
I think that if you're comfortable with the concept of coding a "model" for your data - instead of just, say, writing JDBC calls - then the best practice is to use "value", and use "binding" only where you need to specifically access the component for component-ish things. This'll keep your model cleanly isolated from your view, generally considered a good thing.
But if you've got a strong personal preference for just talking to APIs like JDBC directly, and don't want the extra abstraction of a model layer, then by all means use "binding". Sun's JS Creator is targetted at that sort of developer.
Hope this helps.
-- Adam Winer (EG member)

Binding properties of a root node and using fx:include.

I posted a downloadable example of this here:
https://dl.dropboxusercontent.com/u/8788282/binding-test.zip
I've noticed some understandable, but less than perfect behaviour with the way FXML initialization is done when using fx:include. I find it's difficult to bind properties that belong to the root node of the included view without shooting yourself in the proverbial foot. Here is an example of what I mean:
sample.Main
package sample;
import javafx.application.Application;
import javafx.fxml.FXMLLoader;
import javafx.scene.Parent;
import javafx.scene.Scene;
import javafx.stage.Stage;
public class Main extends Application {
    @Override
    public void start(Stage primaryStage) throws Exception {
        Parent root = FXMLLoader.load(getClass().getResource("MainView.fxml"));
        primaryStage.setTitle("Hello World");
        primaryStage.setScene(new Scene(root, 300, 275));
        primaryStage.show();
    public static void main(String[] args) {
        launch(args);
sample.MainController
package sample;
import javafx.fxml.FXML;
public class MainController {
    @FXML
    void initialize() {
        System.out.println("MainController initialized.");
sample.MainView (FXML)
<?xml version="1.0" encoding="UTF-8"?>
<?import javafx.scene.control.Label?>
<?import javafx.scene.layout.*?>
<AnchorPane prefHeight="200.0" prefWidth="200.0"
            xmlns:fx="http://javafx.com/fxml/1"
            xmlns="http://javafx.com/javafx/2.2"
            fx:controller="sample.MainController">
    <children>
        <VBox prefHeight="200.0" prefWidth="200.0" AnchorPane.bottomAnchor="0.0"
              AnchorPane.leftAnchor="0.0" AnchorPane.rightAnchor="0.0"
              AnchorPane.topAnchor="0.0">
            <children>
                <Label text="Main"/>
                <StackPane prefHeight="150.0" prefWidth="200.0"/>
                <fx:include fx:id="sub" source="SubView.fxml" visible="false"/>
            </children>
        </VBox>
    </children>
</AnchorPane>
sample.SubController
package sample;
import javafx.beans.binding.Bindings;
import javafx.fxml.FXML;
import javafx.scene.control.Label;
import javafx.scene.layout.AnchorPane;
public class SubController {
    @FXML
    private AnchorPane anchorPane;
    @FXML
    private Label label;
    @FXML
    void initialize() {
        label.visibleProperty().bind(Bindings.createBooleanBinding(() -> true));
        /* When used as part of an fx:include, this controller's initialize()
         * block is called and the below binding is performed. After that, any
         * property values set via the containing view (MainView) are applied.
         * In this example, the MainView attempts to set the visible property
         * of this included view (fx:id="sub"). Since the visible property of
         * the root node (anchorPane) has already been bound, the error
         * "A bound value cannot be set." is given.
        anchorPane.visibleProperty().bind(Bindings.createBooleanBinding(() -> true));
        System.out.println("SubController initialized.");
sample.SubView (FXML)
<?xml version="1.0" encoding="UTF-8"?>
<?import javafx.scene.control.Label?>
<?import javafx.scene.layout.*?>
<AnchorPane id="AnchorPane" fx:id="anchorPane" maxHeight="-Infinity"
            maxWidth="-Infinity" minHeight="-Infinity" minWidth="-Infinity"
            prefHeight="400.0" prefWidth="600.0"
            xmlns:fx="http://javafx.com/fxml/1"
            xmlns="http://javafx.com/javafx/2.2"
            fx:controller="sample.SubController">
    <children>
        <VBox prefHeight="400.0" prefWidth="600.0" AnchorPane.bottomAnchor="0.0"
              AnchorPane.leftAnchor="0.0" AnchorPane.rightAnchor="0.0"
              AnchorPane.topAnchor="0.0">
            <children>
                <Label fx:id="label" text="sub view"/>
            </children>
        </VBox>
    </children>
</AnchorPane>
The comments in the initialize method of SubController explain what's happening. I found it a bit confusing until I figured out what was going on. Should FXMLLoader be checking to see if a property is already bound before trying to set it, at least for nodes declared via fx:include?

Hi Gaurave,
We need to show the report like this to some users, thats what the requirement is. Using the Posted nodes option does not help.
Thanks.

Pass values to bind variales and execute VO query

Hi All,
I have a requirement to add validation to an appraisal page via OAF.
As a part of testing I need to check, if the values in the query of VO is displayed in the page.
VO - QuestAnsValuesVO
EO - QuestAnswerValueEO, QuestFieldEO
The VO query is
SELECT * FROM (SELECT QuestAnswerValueEO.QUEST_ANSWER_VAL_ID, QuestAnswerValueEO.QUESTIONNAIRE_ANSWER_ID, QuestAnswerValueEO.FIELD_ID, QuestAnswerValueEO.OBJECT_VERSION_NUMBER, QuestAnswerValueEO.VALUE, QuestFieldEO.FIELD_ID AS QUEST_FIELD_ID, QuestFieldEO.NAME, QuestFieldEO.TYPE, QuestFieldEO.HTML_TEXT, rank() over (partition by QuestFieldEO.NAME order by QuestFieldEO.FIELD_ID) AS RANK, QuestAnswerValueEO.QUESTIONNAIRE_ANSWER_ID AS QUESTIONNAIRE_ANSWER_ID1 FROM HR_QUEST_ANSWER_VALUES QuestAnswerValueEO, HR_QUEST_FIELDS QuestFieldEO WHERE QuestFieldEO.QUESTIONNAIRE_TEMPLATE_ID(+) = :1 and QuestAnswerValueEO.QUESTIONNAIRE_ANSWER_ID(+) = :2 AND QuestFieldEO.FIELD_ID = QuestAnswerValueEO.FIELD_ID (+)) QRSLT ORDER BY QUEST_FIELD_ID
I am trying to execute this query in the extended controller class so that i can get the values printed on the page. I am getting SQL exception saying - not all variables are bound.
How do i pass values to bind variables :1 and :2 and execute this query?
Please help.
Thanks
Geetha

Geetha,
Instead of :1 and :2 use a named bind variable as part of your VO and then set either a default value or set its value during runtime. See this example on how to create bind variable:
http://formattc.wordpress.com/2010/04/02/custom-java-bind-variable-in-a-where-clause-of-an-adf-view-object/
Once created, you can set its value during runtime either in ApplicationModuleImpl or in ViewObjectImpl class
e.g.,
         ViewObjectImpl view = this.getEmpView();
        VariableValueManager vm = view.ensureVariableManager();
        vm.setVariableValue("empNo", value);
        view.executeQuery();regards,
~Krithika

Question regarding selectOneMenu and PROCESS_VALIDATIONS(3) phase

Hi im a bit lost regarding selectOneMenu and how validation phase all works together.
The thing is that i have a simple selectOneMenu
<h:form id="SearchForm">
     <h:panelGrid columns="3" border="0">
          <h:outputLabel id="caseTypeText" value="#{msg.searchCaseCaseType}" for="caseType" />
          <h:selectOneMenu id="caseType" value="#{searchCaseBean.caseType}" style="width: 200px;" binding="#{searchCaseBean.caseTypeSelect}">
               <f:selectItem itemValue="" itemLabel="#{msg.CommonTextAll}" />
               <f:selectItems value="#{searchCaseBean.caseTypes}" />
          </h:selectOneMenu>
          <h:message for="caseType" styleClass="errorMessage" />
          <h:panelGroup />
          <h:panelGroup />
          <h:commandButton action="#{searchCaseBean.actionSearch}" value="#{msg.buttonSearch}" />
     </h:panelGrid>
</h:form>Now when i hit submit button i can see that the bean method searchCaseBean.caseTypes (used in the <f:selectItems> tag) is executed in the PROCESS_VALIDATIONS(3) phase. How come? I dont whant this method to be executed in phase 3, only in phase 6.
If i add the this in the method if (FacesContext.getCurrentInstance().getRenderResponse())
public List<SelectItem> getStepStatuses(){
     List<CaseStep> caseSteps = new ArrayList<CaseStep>();
     if (FacesContext.getCurrentInstance().getRenderResponse()) {
          caseSteps = getCaseService().getCaseStep(value);
     List<SelectItem> selectItems = new ArrayList<SelectItem>(caseSteps.size());
     for(int i=0; i < caseSteps.size(); i++){
          CaseStep step = caseSteps.get(i);
          String stepStatus = step.getStatus() + "_" + step.getSubStatus();
          selectItems.add(new SelectItem(stepStatus, step.getShortName()));
     return selectItems;
} Now i get a validation error (javax.faces.component.UISelectOne.INVALID) for the select field and only phase1, phase2, phase 3 and phase 6 is executed.
Im lost?

I see. Many thanxs BalusC. Im using your blog very often, and its very helpfull for me.
I changed now to use the constructor load method instead. But know im getting problem of calling my service layer (Spring service bean). Its seems they havent been init when jsf bean is calling its constructor.
Can i init the spring service bean from the faces-config file?
JSF Bean
    public SearchCaseBean() {
          super();
                //caseService need to be init
          if(getCaseService() == null){
               setCaseService((CaseService)getWebApplicationContextBean("caseService"));
          fillCaseTypeSelectItems();
          fillCaseStatusSelectItems();
.....faces-config
<managed-bean>
          <managed-bean-name>searchCaseBean</managed-bean-name>
          <managed-bean-class>portal.web.SearchCaseBean</managed-bean-class>
          <managed-bean-scope>request</managed-bean-scope>
          <managed-property>
               <property-name>caseService</property-name>
               <value>#{caseService}</value>
          </managed-property>
     </managed-bean>

How to set buildID.xml and custom.properties in SDK

Hello,
I just completed a new build deployment of SAP ME5.2, because after I deployed the new version, I don't think I have set a
correct version number.Can you someone give me a sample how to set the buildID.xml and custom.properties? I am a new on the SAP ME5.2
The Base version is ME_Base_5.2.5.16.5_netweaver-71_Update.zip and
MEClient_Base_5.2.5.16.5_netweaver-71_Update.zip. the HB customzation
version is ME_xxxxxx_2.0.0.0.x_netweaver-71.
Within the sap note 1484551, you mentioned we need change the
SDKInstallDir/build/buildID.xml file, here is the context of the file:
buildID.xml -
<?xml version="1.0" encoding="UTF-8"?>
<buildID xmlns:xs="http://www.w3.org/2001/XMLSchema">
<customer>XXXXXX</customer>
<revision>1.0.0.0</revision>
<build>1</build>
</buildID>
buildID.xml -
1. how can we change the revision and build?
There is another file BuildToolDir/build/script/custom.properties, here
is the file context:
custom.properties----
This file contains build properties used to configure the build
system.
The name of the software vendor implementing the customizations.
vendor.name=xxxxxxxxx
Vendor build identifier. This value is used to uniquely identify
customizations built by a particular vendor for a particular customer
and base
application version.
This is also used in path locations and in naming certain build
artifacts, like the custom EJB module and the utility classes archive.
vendor.id=xxxxxxxxx
The installation of the J2EE engine installed in the development
environment.
ex. C:/usr/sap/CE1\J00
j2ee.instance.dir=J2EEInstanceDir
The web context path used to access the main web application. This
is used by the build to set the
context-root value in application.xml after an update has been
imported.
web.context.path=
The web context path used to access the production XML interface web
application. This is used by the build to set the
context-root value in application.xml after an update has been
imported.
xml.context.path=
The web context path to access resources from the web extension
application, like images and work instruction HTML files.
web-ext.context.path=web-ext
The target database vendor. Valid values are 'oracle' or 'sqlserver'.db.vendor=ORACLE
The JDBC driver configured for the application server.
db.drivername=VMJDBC
JDBC connection propertes for the WIP (Work In Process) database.
This is the primary application database.
db.wip.driverclassname=
db.wip.driver.url=
db.wip.host=
db.wip.port=
db.wip.sid=
db.wip.user=
db.wip.password=
JDBC connection propertes for the ODS (Open Data Store) database.
This is the offline reporting and archiving database.
db.ods.driverclassname=
db.ods.driver.url=
db.ods.host=
db.ods.port=
db.ods.sid=
db.ods.user=
db.ods.password=
Flag indicating whether to add DPMO NC codes to NC idat files when a
new update is imported. This value is initially
set by the installer according the the user selection.
dpmo.nc.codes=
The default locale used by the production system. The default locale
is the locale used to display locale
specific text and messages when the requested locale is not
available. This property does not need to
be set if the default locale is english.
default.locale=en
Used when running the build from Eclipse to locate the java compiler
used by the WebLogic EJB compiler.
jdk.home=C:/Program Files/Java/jdk1.5.0_20
Compiler debug mode. If set to 'true', debug symbols will be
compiled into the byte code.
compile.debug=true
Keystore alias
security.alias=xxxxx
Keystore password
security.storepass=ChangeIt
Key password
security.keypass=ChangeIt
Keystore type (jks=default,jceks,pkcs12)
security.storetype=jks
Optional source control build identifier that is to be displayed with
standard version information.
scs.build.ID=
Optional extended version information to be displayed with standard
version information.
ext.info=
custom.properties----
2. How can we change this here?
Regards,
Leon Lu
Edited by: Leon Lu on Aug 4, 2011 11:14 AM
Edited by: Leon Lu on Aug 4, 2011 11:21 AM

Hi,
I created one request with logo in the header an page in the footer etc. and called StyleSheet. After you can import this formats by each request.
You can do this in compound layout.
Regards,
Stefan

How to delete the existing list values before binding

Hi,
I'm new for flex..
i like to know how to delete(clear) the existing list data values before binding the new values..
I'm using the list for binding data dynamically by using http services.if i send the another call mean's the exiting item should be flushed and coming data item's would be binded into the same list...
Thank's in advance....
Regard's
mani

Hello
On your ResultEvent method you can add something like this:
private function onResultEvent(event:ResultEvent) : void
yourBindableList = null;
yourBindableList = event.result as ArrayCollection();
In this code i send to my BindableList a null value before i setter to list the result of my HTTPService, making a cast to ArrayCollection.
Regards

Ssrs parameter default value not showing ,when available values is binded to query dataset

I have developed a report using sql server data tools for vsiual studio2012 ,i have defined few parameters ,on one of the parameter when available values is binded to a dataset query, the report default value is not showing in report preview .
Many Thanks
Chandra

Hi Chandra,
According to your description, you have set the default value for a parameter, but it's not displayed when initially running the report. Right?
In this scenario, since you have set the available values bind to query, so your default values should be within these available values. If these default values are not within the available values, the default values will be not displayed. So please check
the default values.
Reference:
Add, Change, or Delete Default Values for a Report Parameter (Report Builder and SSRS)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

How to prevent editing a SharePoint site column value from document properties view of a downloaded document?

Hi,
We have created a SharePoint site column with below settings
1. ShowInEditForm - False
2. ShowInNewForm - False
3. ShowInDisplayForm - True
With the above definition, the site column showing only in view properties form not in New and Edit forms. This column is added to a document library and updating this column value will be managed by event receiver code when a document is uploaded.
Till this point, everything is working OK.
But the issue is when we download and open a document from the above document library, under document properties the above column (with value) is visible along with other document default properties and this column value is editable. With this issue,
user is able to set a new value and overwrite the existing value by re-uploading the document.
Could you please let me know how to handle this issue so that user should not be allowed to edit except viewing the value/property (read only)?
Thanks in advance.
Regards
Ramesh

You can set "ShowInFileDlg" property of field to "FALSE". Using this you will not see that field in document properties list

OracleConnectionCacheImpl setter values for instance properties

Hi!
I'm using OracleConnectionCacheImpl to cache my connections to the Oracle 8i (8.1.7.4)
The JDBC driver that I'm using is 9.2.x
I've read through the SQLJ/JDBC documentation and learned that it is possible to use certain properties for controlling the behaviour of connection cache.
Only thing is that the documentation does not specify whether the values for the properties should be milliseconds, seconds, minutes or something else. The long type of the parameter value would indicate milliseconds but according my minimal testing at least some of the values propably are not milliseconds. Help is greatly appreciated. Below is the list of the properties I'm interested in:
// Controls how often cache thread check whether a physical connection has become available
/*ods.setThreadWakeUpInterval(threadWakeUpInterval);
// How long the logical connection can be used before forced back to the cache pool and all
// resources are freed.
ods.setCacheTimeToLiveTimeout(cacheTimeToLiveTimeout);
// How long the physical connection can be unused before it is closed and all the resources are freed.
ods.setCacheInactivityTimeout(cacheInactivityTimeout);
// How long the connection request will be waiting before EOJ_FIXED_WAIT_TIMEOUT is thrown.
ods.setCacheFixedWaitTimeout(cacheFixedWaitTimeout);
// How long the cache waits before polling for an available connection
ods.setCacheFixedWaitIdleTime(cacheFixedWaitIdleTime); */
Best Regards:
Aapo Romu

Hello Radhakrishna D S,
The note you provided did not fit our problem. The bootstrap.maxheapsize in the instance.properties file is already 128MB. Thanks anyway!

Concatenating context value and non-context value

Hi,
I have a context binding to one of the input field(lets say field-X) and also I have another dropdown list UI element(lets say field-Y) which is not bound to any context. When a user enters values in field-X and selects a item from field-Y hits the save button, I need to concat "Field-X - Field-Y" and assign this concatenated value to field-X context. So in a road-map (next screen) when I retrieve field-X context value it should have concatenated value of dropdown UI element as well.
Where do I do this concat (I mean which method e.g. WDModify) and how do I do it?
Thanks
Praveen.

Hi Praveen,
What do you mean by field-Y is not bound to any context?? I am sure you would have atleast bound the selectedKey property of the dropdown list with some attribute of the context.
For concatinating the fileds you have to write the code on the onAction function of Save button which is taking you to the next screen of the road map. On the onActionSave() you have to get the values of the currently selected input field and the dropdown value. Then you have to concatenate the values and set it in some attribute from where you can pick it in the next screen.
Please use this code in onActionSave() method:
// Get the value of the currently entered value of the input field from the attribute which is bound to the input field. I am assuming the name of the attribute as InputFiledValue
String inpValue = wdContext.currentContextElement().getInputFiledValue();
// Get the value of the currently selected value of the drop down field from the attribute which is bound to the drop down field. I am assuming the name of the attribute as DropDownValue
String dropDpwnValue = wdContext.currentContextElement().getDropDownValue();
// Concatenate with "-" in between
String concatenatedValue = inpValue+ " - " + dropDpwnValue;
// Set the concatenated value to a temporary attribute. This will be accessed in next view of road map.
wdContext.currentContextElement().setConcatenatedValue(concatenatedValue);
// OR if you want to save in same inputfield Attribute then also you can do that.
// use the similar code as above. see this:
// wdContext.currentContextElement().setInputFiledValue(concatenatedValue);
Here I am assuming that the attribute which have bound to the inputfield and dropdown field are directly under the context node. If not then you have to get the values from a specific node. Do it like this:
// Get the value of the currently entered value of the input field from the attribute which is bound to the input field.
String inpValue = wdContext.current<NODE_NAME>Element().getInputFiledValue();
// Get the value of the currently selected value of the drop down field from the attribute which is bound to the drop down field.
String dropDpwnValue = wdContext.current<NODE_NAME>Element().getDropDownValue();
In the next view you can get this concatenated value and can use whereever you want. Use following code:
// To get the value of the concatenated string.
String value = wdContext.currentContextElement().getConcatenatedValue();
I hope this solves the issue. Please revert back in case you need any furtehr help on this.
Thanks and Regards,
Pravesh

Execute BAPI for different input values and dispaly data in a table

Hi all,
I have a specific problem about executing BAPI multiple times for different input values and didplay result in a table.
I am using the code similar to the following logic.
Bapi_Mydata_Input in = new Bapi_Mydata_Input();
wdContext.nodeBapi_Mydata_Input().bind(in);
String in = wdContext.currentperdataElement.getnumber();
in.setDestination_From(10)
wdThis.wdGetMydataComponentController().executeBapi_Mydata_Input();
in.setDestination_From(20)
wdThis.wdGetMydataComponentController().executeBapi_Mydata_Input();
in.setDestination_From(30)
wdThis.wdGetMydataComponentController().executeBapi_Mydata_Input();
And I want to display the data in a single table. I want the result in a table for Bapi execution based on input parameters passed 10,20 30.
But I am getting the table data only for the input parameter 30.I mean its actually display the data in table only for the last input parameter.
So May I ask you all if you know the solution for this problem.PLease advise me with some tips .or sample code is very much appreciated.I promise to award points to the right answer/nice advises.
Regards
Maruti
Thank you in advance.

Maruti,
It seems that WDCopyService replaces content of node, rather then adds to content.
Try this:
Bapi_Persdata_Getdetailedlist_Input frelan_in = new Bapi_Persdata_Getdetailedlist_Input();
wdContext.nodeBapi_Persdata_Getdetailedlist_Input().bind(frelan_in);
final Collection personalData = new ArrayList();
String fr1 = wdContext.currentE_Lfa1Element().getZzpernr1();
frelan_in.setEmployeenumber(fr1);
wdThis.wdGetFreLanReEngCompController().executeBapi_Persdata_Getdetailedlist_Input();
WDCopyService.copyElements(wdContext.nodePersonaldata(), wdContext.nodeNewPersonaldata());
for (int i = 0, c = wdContext.nodePersonaldata().size(); i < c; i++)
personalData.add( wdContext.nodePersonaldata().getElementAt(i).model() );
String fr2=wdContext.currentE_Lfa1Element().getZzpernr2();
frelan_in.setEmployeenumber(fr2);
wdThis.wdGetFreLanReEngCompController().executeBapi_Persdata_Getdetailedlist_Input();
WDCopyService.copyElements(wdContext.nodePersonaldata(), wdContext.nodeNewPersonaldata());
for (int i = 0, c = wdContext.nodePersonaldata().size(); i < c; i++)
personalData.add( wdContext.nodePersonaldata().getElementAt(i).model() );
wdContext.nodeNewPersonalData().bind( personalData );
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

Bgm.ser and jaxb.properties not created

Is there a particular reason to why the bgm.ser and jaxb.properties files are not created when a schema only consists of a simpletype and I run the binding compiler???
The two files seem to be created when I include a 'dummy' complextype in the schema. Is a complextype needed in order for the files to be created?
Cheers.
Anders
<simpleType name="Values">
    <restriction base="string">
        <enumeration value="ValueOne"/>
        <enumeration value="ValueTwo"/>
        <enumeration value="ValueThree"/>
        <enumeration value="ValueFour"/>
    </restriction>
</simpleType>

I've had the same exact problem! I had the property file in my JAR file properly, but the JAXBContext.newInstance( "package.name" ) call was failing - while at the same time I could load the property file via the ClassLoader just fine, by hand.
I played around with source for the jaxb beta a bit and I think I found the problem. I recompiled the JAR file after changing the "fileSep" variable in the "searchforcontextPath" method from "file.separatorChar" to "/".
This seemed to fix the problem. Well, the problem of it not finding the properties file that is... now I've got some kinda non-marshalable exception (but I haven't even spent 3 minutes on that problem yet, as opposed to the hours wasted on this bug).
I'm not sure if this bug only cropped up when running under a Windows env or not (my test was running under JBoss on XP... though I was building/compiling under Linux).
Anyway... to fix this just change that variable.. it's on line 228 (i think... i might have added some debug lines of my own in the code) of the javax/xml/bind/ContextFinder.java file. Then just re-jar it over the old JAR -- oh yeah, you'll need a few Message.property files from the jaxb-api.jar file for the new jar file to work (so make sure you unjar the old file 1st or back it up or whatnot).

Regarding Value and Binding properties of af:inputTextBox

Similar Messages

Maybe you are looking for