ModelReference vs DataBinding

When I try to use the components provided by SUN jsf ri, I always have a question: Can I use modelReference here and what the modelReference means to this component ? look at following components:
UISelectItem, UISelectItems, UIForm, UICommand, UIGraphics,
is modelReference really meaningful to them ?
From the other hand, if think about the ton of attributes of HTML element, I would like to ask : is one modelReference enough to represent the nature of a HTML component ? I was very confused.
In MS .NET's web control, it provides a DataBinding feature, which allow you to binding each Bindable attribute to data model, I think this is more meaningful than a single modelReference.
Are you guys agreed?

Yes, I completely agree. As a matter of facts, a lot of terms used in JSF are confusing for UI designers. Now that JSF is close to completion, I believe that the spec team will look at the terms used and replace them by more meaningful and user-friendly ones.

Similar Messages

Databind method call returns null in WebCenter Content Filter

Hi,
I have inherited some code that has an issue and I'm new to WebCenter Content and the Filters that can be added. We have a FileNameFilter class that starts off with the code
public class CWEFileNameFilter implements FilterImplementor {
    public CWEFileNameFilter() {
        super();
    public int doFilter(Workspace workspace, DataBinder dataBinder,
                        ExecutionContext executionContext) throws DataException {
        String service = dataBinder.getLocal("IdcService");
However, service sometimes comes back null and then the filter throws a NPE.
My questions are:
1) Can anyone explain what dataBinder.getLocal("IdcService"); is doing and why it could come back as null
2) Can anyone provide any links to documentation that explains Filters and a bit more about the DataBinder object as the JavaDoc isn't much help.
Thanks
Marc

Hi Marc,
Below code will give service name for which filter is implemented from LocalData
String service = dataBinder.getLocal("IdcService");
for example below
http://localhost:16200/cs/idcplg?IdcService=DOC_INFO_BY_NAME&dDocName=1111111&IsJava
This will print entire response data including localdata and results which are created as part of service execution. Below is snippet
<?hda version="11.1.1.8.0PSU-2015-04-01 00:14:53Z-r126309" jcharset="UTF8" encoding="utf-8"?>
@Properties LocalData
DocUrl=https://localhost:16200/cs/weblayout/groups/secure/documents/test/mhdk/mjg1/1111111.pdf
IdcService=DOC_INFO_BY_NAME
so String service = dataBinder.getLocal("IdcService"); will be service ="DOC_INFO_BY_NAME".
Below blog will give some idea about filter but best place to learn or start is "The Definitive Guide to Stellent Content Server Development" by Brian Huff
http://www.redstonecontentsolutions.com/technical-blog/ucm-service-handlers-and-javafilters
Also i would recommend reading "WebCenter Content Services Reference Guide"
http://docs.oracle.com/cd/E23943_01/doc.1111/e11011/toc.htm
Regards,
Amol Gavali.

Access the modelReference value

If I add a modelReference to a command_button like in the following code:
<h:command_button id="b" label="Click" commandName="Click" modelReference="UserBean.name">
</h:command_button>and if I catch the request at the ApplicationHanlder like this:
if (formEvent.getCommandName().equals("Click")) {
      UIComponent c = formEvent.getComponent();
      String model = c.getModelReference();
      treeId = ... //and so on
...So my question. Is it possible to get the "real" value of the modelReference. I mean if call the methode .getModelReference() I get the string "UserBean.name"! But I want to get the value!!!
Any Suggestions??

I thought, modelReference was replaced by valueRef (and maybe actionRef)
am i wrong?
if i am, when do i have to use which of the 3 attributes ?

Error Null Databinding context encountered -WSDL to Java webservice convert

HI,
I have been trying to generate service and client from WSDL using Jdeveloper11 and im unable to progress on this particular WSDL, i was succesfull in creating the client and service for a sample Apache WSDL using the Jdeveloper. If anyone can point out the issue in this WSDL or is there a bug in Jdeveloper when handling complex type? i attach the WSDL that i used, now note that the WSDL calls for another WSDL import witin it, if i comment out the import and its bindings im able to proceed,
WSDL-1

<wsdl:operation name="getAlarmsByKeys">
<wsdl:input name="getAlarmsByKeysRequest" message="fmWS-v1-0:getAlarmsByKeysRequest" />
<wsdl:output name="getAlarmsByKeysResponse" message="fmWS-v1-0:getAlarmsByKeysResponse" />
<wsdl:fault name="getAlarmsByKeysException" message="fmWS-v1-0:getAlarmsByKeysException" />
</wsdl:operation>
<wsdl:operation name="getAlarmsByTemplate">
<wsdl:input name="getAlarmsByTemplateRequest" message="fmWS-v1-0:getAlarmsByTemplateRequest" />
<wsdl:output name="getAlarmsByTemplateResponse" message="fmWS-v1-0:getAlarmsByTemplateResponse" />
<wsdl:fault name="getAlarmsByTemplateException" message="fmWS-v1-0:getAlarmsByTemplateException" />
</wsdl:operation>
<wsdl:operation name="queryAlarms">
<wsdl:input name="queryAlarmsRequest" message="fmWS-v1-0:queryAlarmsRequest" />
<wsdl:output name="queryAlarmsResponse" message="fmWS-v1-0:queryAlarmsResponse" />
<wsdl:fault name="queryAlarmsException" message="fmWS-v1-0:queryAlarmsException" />
</wsdl:operation>

<wsdl:operation name="getAlarmSpecificInfoTypes">
<wsdl:input
name="getAlarmSpecificInfoTypesRequest"
message="fmWS-v1-0:getAlarmSpecificInfoTypesRequest" />
<wsdl:output
name="getAlarmSpecificInfoTypesResponse"
message="fmWS-v1-0:getAlarmSpecificInfoTypesResponse" />
<wsdl:fault
name="getAlarmSpecificInfoTypesException"
message="fmWS-v1-0:getAlarmSpecificInfoTypesException" />
</wsdl:operation>
<wsdl:operation name="getVersion">
<wsdl:input
name="getVersionRequest"
message="fmWS-v1-0:getVersionRequest" />
<wsdl:output
name="getVersionResponse"
message="fmWS-v1-0:getVersionResponse" />
<wsdl:fault
name="getVersionException"
message="fmWS-v1-0:getVersionException" />
</wsdl:operation>
<wsdl:operation name="createAlarms">
<wsdl:input
name="createAlarmsRequest"
message="fmWS-v1-0:createAlarmsRequest" />
<wsdl:output
name="createAlarmsResponse"
message="fmWS-v1-0:createAlarmsResponse" />
<wsdl:fault
name="createAlarmsException"
message="fmWS-v1-0:createAlarmsException" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="JVTAlarmCreationSessionSoapBinding"
type="fmWS-v1-0:JVTAlarmCreationSessionWSPort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />

<wsdl:operation name="getAlarmsByKeys">
<soap:operation soapAction="getAlarmsByKeys" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name="getAlarmsByKeysException">
<soap:fault name="getAlarmsByKeysException" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getAlarmsByTemplate">
<soap:operation soapAction="getAlarmsByTemplate" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name="getAlarmsByTemplateException">
<soap:fault name="getAlarmsByTemplateException" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="queryAlarms">
<soap:operation soapAction="queryAlarms" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name="queryAlarmsException">
<soap:fault name="queryAlarmsException" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getAlarmSpecificInfoTypes">
<soap:operation soapAction="getAlarmSpecificInfoTypes" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name ="getAlarmSpecificInfoTypesException">
<soap:fault name ="getAlarmSpecificInfoTypesException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getVersion">
<soap:operation soapAction="getVersion" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name ="getVersionException">
<soap:fault name ="getVersionException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="createAlarms">
<soap:operation soapAction="createAlarms" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name ="createAlarmsException">
<soap:fault name ="createAlarmsException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>








<wsdl:service name="JVTAlarmCreationSessionWebService">
<wsdl:port name="JVTAlarmCreationSessionWSPort"
binding="fmWS-v1-0:JVTAlarmCreationSessionSoapBinding">
<soap:address location="http://localhost/JVTAlarmCreationSessionWebService/JVTAlarmCreationSession" />
</wsdl:port>

</wsdl:service>
</wsdl:definitions>
WSDL-2 imported in the above WSDL
<?xml version="1.0" encoding="utf-8"?>

<wsdl:definitions name="WS-BaseNotification"
targetNamespace="http://docs.oasis-open.org/wsn/bw-2"
xmlns:wsntw="http://docs.oasis-open.org/wsn/bw-2"
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsrf-rw="http://docs.oasis-open.org/wsrf/rw-2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

<wsdl:import
namespace="http://docs.oasis-open.org/wsrf/rw-2"
location="rw-2.wsdl"/>

<wsdl:types>
<xsd:schema elementFormDefault="qualified">
<xsd:import
namespace="http://docs.oasis-open.org/wsn/b-2"
schemaLocation="b-2.xsd"/>
</xsd:schema>
</wsdl:types>

<wsdl:message name="Notify">
<wsdl:part name="Notify" element="wsnt:Notify"/>
</wsdl:message>

<wsdl:message name="SubscribeRequest" >
<wsdl:part name="SubscribeRequest"
element="wsnt:Subscribe"/>
</wsdl:message>
<wsdl:message name="SubscribeResponse">
<wsdl:part name="SubscribeResponse"
element="wsnt:SubscribeResponse"/>
</wsdl:message>
<wsdl:message name="SubscribeCreationFailedFault">
<wsdl:part name="SubscribeCreationFailedFault"
element="wsnt:SubscribeCreationFailedFault" />
</wsdl:message>
<wsdl:message name="TopicExpressionDialectUnknownFault">
<wsdl:part name="TopicExpressionDialectUnknownFault"
element="wsnt:TopicExpressionDialectUnknownFault" />
</wsdl:message>
<wsdl:message name="InvalidFilterFault">
<wsdl:part name="InvalidFilterFault"
element="wsnt:InvalidFilterFault" />
</wsdl:message>
<wsdl:message name="InvalidProducerPropertiesExpressionFault">
<wsdl:part name="InvalidProducerPropertiesExpressionFault"
element="wsnt:InvalidProducerPropertiesExpressionFault" />
</wsdl:message>
<wsdl:message name="InvalidMessageContentExpressionFault">
<wsdl:part name="InvalidMessageContentExpressionFault"
element="wsnt:InvalidMessageContentExpressionFault" />
</wsdl:message>
<wsdl:message name="UnrecognizedPolicyRequestFault">
<wsdl:part name="UnrecognizedPolicyRequestFault"
element="wsnt:UnrecognizedPolicyRequestFault" />
</wsdl:message>
<wsdl:message name="UnsupportedPolicyRequestFault">
<wsdl:part name="UnsupportedPolicyRequestFault"
element="wsnt:UnsupportedPolicyRequestFault" />
</wsdl:message>
<wsdl:message name="NotifyMessageNotSupportedFault">
<wsdl:part name="NotifyMessageNotSupportedFault"
element="wsnt:NotifyMessageNotSupportedFault" />
</wsdl:message>
<wsdl:message name="UnacceptableInitialTerminationTimeFault">
<wsdl:part name="UnacceptableInitialTerminationTimeFault"
element="wsnt:UnacceptableInitialTerminationTimeFault"/>
</wsdl:message>

<wsdl:message name="GetCurrentMessageRequest">
<wsdl:part name="GetCurrentMessageRequest"
element="wsnt:GetCurrentMessage"/>
</wsdl:message>
<wsdl:message name="GetCurrentMessageResponse">
<wsdl:part name="GetCurrentMessageResponse"
element="wsnt:GetCurrentMessageResponse"/>
</wsdl:message>
<wsdl:message name="InvalidTopicExpressionFault">
<wsdl:part name="InvalidTopicExpressionFault"
element="wsnt:InvalidTopicExpressionFault" />
</wsdl:message>
<wsdl:message name="TopicNotSupportedFault">
<wsdl:part name="TopicNotSupportedFault"
element="wsnt:TopicNotSupportedFault" />
</wsdl:message>
<wsdl:message name="MultipleTopicsSpecifiedFault">
<wsdl:part name="MultipleTopicsSpecifiedFault"
element="wsnt:MultipleTopicsSpecifiedFault" />
</wsdl:message>
<wsdl:message name="NoCurrentMessageOnTopicFault">
<wsdl:part name="NoCurrentMessageOnTopicFault"
element="wsnt:NoCurrentMessageOnTopicFault" />
</wsdl:message>

<wsdl:message name="GetMessagesRequest">
<wsdl:part name="GetMessagesRequest"
element="wsnt:GetMessages"/>
</wsdl:message>
<wsdl:message name="GetMessagesResponse">
<wsdl:part name="GetMessagesResponse"
element="wsnt:GetMessagesResponse"/>
</wsdl:message>
<wsdl:message name="UnableToGetMessagesFault">
<wsdl:part name="UnableToGetMessagesFault"
element="wsnt:UnableToGetMessagesFault"/>
</wsdl:message>

<wsdl:message name="DestroyPullPointRequest">
<wsdl:part name="DestroyPullPointRequest"
element="wsnt:DestroyPullPoint"/>
</wsdl:message>
<wsdl:message name="DestroyPullPointResponse">
<wsdl:part name="DestroyPullPointResponse"
element="wsnt:DestroyPullPointResponse"/>
</wsdl:message>
<wsdl:message name="UnableToDestroyPullPointFault">
<wsdl:part name="UnableToDestroyPullPointFault"
element="wsnt:UnableToDestroyPullPointFault"/>
</wsdl:message>

<wsdl:message name="CreatePullPointRequest">
<wsdl:part name="CreatePullPointRequest"
element="wsnt:CreatePullPoint"/>
</wsdl:message>
<wsdl:message name="CreatePullPointResponse">
<wsdl:part name="CreatePullPointResponse"
element="wsnt:CreatePullPointResponse"/>
</wsdl:message>
<wsdl:message name="UnableToCreatePullPointFault">
<wsdl:part name="UnableToCreatePullPointFault"
element="wsnt:UnableToCreatePullPointFault"/>
</wsdl:message>

<wsdl:message name="RenewRequest">
<wsdl:part name="RenewRequest"
element="wsnt:Renew"/>
</wsdl:message>
<wsdl:message name="RenewResponse">
<wsdl:part name="RenewResponse"
element="wsnt:RenewResponse"/>
</wsdl:message>
<wsdl:message name="UnacceptableTerminationTimeFault">
<wsdl:part name="UnacceptableTerminationTimeFault"
element="wsnt:UnacceptableTerminationTimeFault" />
</wsdl:message>

<wsdl:message name="UnsubscribeRequest">
<wsdl:part name="UnsubscribeRequest"
element="wsnt:Unsubscribe"/>
</wsdl:message>
<wsdl:message name="UnsubscribeResponse">
<wsdl:part name="UnsubscribeResponse"
element="wsnt:UnsubscribeResponse"/>
</wsdl:message>
<wsdl:message name="UnableToDestroySubscriptionFault">
<wsdl:part name="UnableToDestroySubscriptionFault"
element="wsnt:UnableToDestroySubscriptionFault" />
</wsdl:message>

<wsdl:message name="PauseSubscriptionRequest">
<wsdl:part name="PauseSubscriptionRequest"
element="wsnt:PauseSubscription"/>
</wsdl:message>
<wsdl:message name="PauseSubscriptionResponse">
<wsdl:part name="PauseSubscriptionResponse"
element="wsnt:PauseSubscriptionResponse"/>
</wsdl:message>
<wsdl:message name="PauseFailedFault">
<wsdl:part name="PauseFailedFault"
element="wsnt:PauseFailedFault" />
</wsdl:message>

<wsdl:message name="ResumeSubscriptionRequest">
<wsdl:part name="ResumeSubscriptionRequest"
element="wsnt:ResumeSubscription"/>
</wsdl:message>
<wsdl:message name="ResumeSubscriptionResponse">
<wsdl:part name="ResumeSubscriptionResponse"
element="wsnt:ResumeSubscriptionResponse"/>
</wsdl:message>
<wsdl:message name="ResumeFailedFault">
<wsdl:part name="ResumeFailedFault"
element="wsnt:ResumeFailedFault" />
</wsdl:message>


<wsdl:portType name="NotificationConsumer">
<wsdl:operation name="Notify">
<wsdl:input message="wsntw:Notify" />
</wsdl:operation>
</wsdl:portType>

<wsdl:portType name="NotificationProducer">
<wsdl:operation name="Subscribe">
<wsdl:input message="wsntw:SubscribeRequest" />
<wsdl:output message="wsntw:SubscribeResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="InvalidFilterFault"
message="wsntw:InvalidFilterFault"/>
<wsdl:fault name="TopicExpressionDialectUnknownFault"
message="wsntw:TopicExpressionDialectUnknownFault"/>
<wsdl:fault name="InvalidTopicExpressionFault"
message="wsntw:InvalidTopicExpressionFault" />
<wsdl:fault name="TopicNotSupportedFault"
message="wsntw:TopicNotSupportedFault" />
<wsdl:fault name="InvalidProducerPropertiesExpressionFault"
message="wsntw:InvalidProducerPropertiesExpressionFault"/>
<wsdl:fault name="InvalidMessageContentExpressionFault"
message="wsntw:InvalidMessageContentExpressionFault"/>
<wsdl:fault name="UnacceptableInitialTerminationTimeFault"
message="wsntw:UnacceptableInitialTerminationTimeFault"/>
<wsdl:fault name="UnrecognizedPolicyRequestFault"
message="wsntw:UnrecognizedPolicyRequestFault"/>
<wsdl:fault name="UnsupportedPolicyRequestFault"
message="wsntw:UnsupportedPolicyRequestFault"/>
<wsdl:fault name="NotifyMessageNotSupportedFault"
message="wsntw:NotifyMessageNotSupportedFault"/>
<wsdl:fault name="SubscribeCreationFailedFault"
message="wsntw:SubscribeCreationFailedFault"/>
</wsdl:operation>
<wsdl:operation name="GetCurrentMessage">
<wsdl:input message="wsntw:GetCurrentMessageRequest"/>
<wsdl:output message="wsntw:GetCurrentMessageResponse"/>
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="TopicExpressionDialectUnknownFault"
message="wsntw:TopicExpressionDialectUnknownFault"/>
<wsdl:fault name="InvalidTopicExpressionFault"
message="wsntw:InvalidTopicExpressionFault" />
<wsdl:fault name="TopicNotSupportedFault"
message="wsntw:TopicNotSupportedFault" />
<wsdl:fault name="NoCurrentMessageOnTopicFault"
message="wsntw:NoCurrentMessageOnTopicFault" />
<wsdl:fault name="MultipleTopicsSpecifiedFault"
message="wsntw:MultipleTopicsSpecifiedFault" />
</wsdl:operation>
</wsdl:portType>

<wsdl:portType name="PullPoint">
<wsdl:operation name="GetMessages">
<wsdl:input name="GetMessagesRequest"
message="wsntw:GetMessagesRequest" />
<wsdl:output name="GetMessagesResponse"
message="wsntw:GetMessagesResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnableToGetMessagesFault"
message="wsntw:UnableToGetMessagesFault" />
</wsdl:operation>
<wsdl:operation name="DestroyPullPoint">
<wsdl:input name="DestroyPullPointRequest"
message="wsntw:DestroyPullPointRequest" />
<wsdl:output name="DestroyPullPointResponse"
message="wsntw:DestroyPullPointResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault"/>
<wsdl:fault name="UnableToDestroyPullPointFault"
message="wsntw:UnableToDestroyPullPointFault" />
</wsdl:operation>
<wsdl:operation name="Notify">
<wsdl:input message="wsntw:Notify"/>
</wsdl:operation>
</wsdl:portType>

<wsdl:portType name="CreatePullPoint">
<wsdl:operation name="CreatePullPoint">
<wsdl:input name="CreatePullPointRequest"
message="wsntw:CreatePullPointRequest" />
<wsdl:output name="CreatePullPointResponse"
message="wsntw:CreatePullPointResponse" />
<wsdl:fault name="UnableToCreatePullPointFault"
message="wsntw:UnableToCreatePullPointFault" />
</wsdl:operation>
</wsdl:portType>

<wsdl:portType name="SubscriptionManager">
<wsdl:operation name="Renew">
<wsdl:input name="RenewRequest"
message="wsntw:RenewRequest" />
<wsdl:output name="RenewResponse"
message="wsntw:RenewResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnacceptableTerminationTimeFault"
message=
"wsntw:UnacceptableTerminationTimeFault" />
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<wsdl:input name="UnsubscribeRequest"
message="wsntw:UnsubscribeRequest" />
<wsdl:output name="UnsubscribeResponse"
message="wsntw:UnsubscribeResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnableToDestroySubscriptionFault"
message=
"wsntw:UnableToDestroySubscriptionFault" />
</wsdl:operation>
</wsdl:portType>

<wsdl:portType name="PausableSubscriptionManager">

<wsdl:operation name="Renew">
<wsdl:input name="RenewRequest"
message="wsntw:RenewRequest" />
<wsdl:output name="RenewResponse"
message="wsntw:RenewResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnacceptableTerminationTimeFault"
message=
"wsntw:UnacceptableTerminationTimeFault" />
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<wsdl:input name="UnsubscribeRequest"
message="wsntw:UnsubscribeRequest" />
<wsdl:output name="UnsubscribeResponse"
message="wsntw:UnsubscribeResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnableToDestroySubscriptionFault"
message=
"wsntw:UnableToDestroySubscriptionFault" />
</wsdl:operation>

<wsdl:operation name="PauseSubscription">
<wsdl:input message="wsntw:PauseSubscriptionRequest"/>
<wsdl:output message="wsntw:PauseSubscriptionResponse"/>
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="PauseFailedFault"
message="wsntw:PauseFailedFault" />
</wsdl:operation>
<wsdl:operation name="ResumeSubscription">
<wsdl:input message="wsntw:ResumeSubscriptionRequest"/>
<wsdl:output message="wsntw:ResumeSubscriptionResponse"/>
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="ResumeFailedFault"
message="wsntw:ResumeFailedFault" />
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
And the error i get is [fatal error] null databinding context encountered when creating service.
Steps i followed:
1. Created a new project in Jdev
2. Right clicked on project to expand Business Tier - Web Services nodes. Selected the Java web Service from WSDL.
3. Selected WSDL to convert
---Says it is Fetching WSDL
---then says building model
--and pops error : [fatal error] null databinding context encountered.
Any suggestions? I'm unable to get this issue fixed for a long time.

Hey guys,
I couldnt get this fixed in jdeveloper, i finally gave up on using Jdeveloper for Web service creation.
I went back to my eclipse3.2.2 and used the Eclipse WTP 1.5.4 and guess what, it had no issues generating the service and client for my WSDL.
I am not sure Jdeveloper can compete with Eclipse functionality and ease.

UiXML: dataBinding problem with decimal validator

I'm trying to use the decimal validator inside a uit template and dataBind the minValue, maxValue, maxScale and maxPrecision attributes to the ui:rootAttr dataObject like so:
<textInput ...>
<onSubmitValidater>
<decimal
data:minValue="minValue@ui:rootAttr"
data:maxValue="maxValue@ui:rootAttr"
data:maxPrecision="maxPrecision@ui:rootAttr"
data:maxScale="maxScale@ui:rootAttr"/>
</onSubmitValidater>
</textInput>
However that doesn't seem to work the validation never executes.
But when I don't use dataBinding it works fine.
Example:
<textInput ...>
<onSubmitValidater>
<decimal
minValue="0"
maxValue="10"
maxPrecision="2"
maxScale="3"/>
</onSubmitValidater>
</textInput>
Could it be that there is some bug with the decimal validator? I'm using the dateValidator in just the same way and it works fine.
Guido

We'll at least warn you of the problem starting in 9.0.5.
Getting full databinding support in there may not happen
by then.
But there is a workaround today: databind the
onSubmitValidater attribute:
<textInput data:onSubmitValidater="decimal@someBean"/>
... to point to code that directly creates the
DecimalValidater.
public ClientValidater getDecimal()
DecimalValidater validater = new DecimalValidater();
validater.setMinValue(1.0);
// etc...
return validater;

Problem with complex dataBinding within concat

Im trying to create a link with a databound onClick attribute like so:
<link ....>
<boundAttribute name="onClick">
<concat>
<fixed text="submitForm('result',0,{'event':'action','action':'"/>
<dataObject select="defaultAction" source="fti:search"/>
<dataObject select="##','index':'%index%'});return false;" source="resultRow@fti:search"/>
</concat>
</boundAttribute>
</link>
fti:search is a dataObject that returns another dataObject for the selectString resultRow. The resultRow dataObject should then be called with the selectString ="##','index':'%index%'});return false;
However the resultRow dataObject is never called with that selecString.
I also tried writing:
<fixed data:text="##','index':'%index%'});return false;@resultRow@fti:search"/>
but with the same result.
I'm using this syntax for many other controls, but for the text attribute of a <fixed> element it doesn't seem to work.
So how can I do a complex dataBinding within a <concat> element?
Thanks,
Guido

Hi Guido
I think you need this
<dataObject select="##,'index':'%index%});return false;" data:source="resultRow@fti:search"/>Cheers
Ian

Databinding problem - tutorial

Hello,
I have just began to work with the SAP .NET connector.
I am trying to do the tutorial : "Write an ASP.NET Client Application with SAP.NET Connector".
The user writes a name in a textbox. Then the programm calls the Bapi RFC_CUSTOMER_GET and it returns the list of customers who have the name written in the textbox.
However the databinding is not working well between the textbox and the corresponding parameter in the method RFC_CUSTOMER_GET. The programm doesn't use the value in the textbox to find the customers. Instead, it always choses the default value in the SAPProxy11.
Once the list of customers is found, the value of the textbox changes automatically and is set to the default value of the SAPProxy.
I guess this is due to the databinding which only works in one direction. The textbox cannot set the value in the BAPI. But the value in the BAPI sets the value in the textbox.
To avoid the missing databinding, I have found the following solution :
there is a method Button_Click which calls the BAPI; at the beginning of this method, I write to following code to force the value of the parameter of the customer name
sapproxy11.CustName=this.TextBox1.Text;
However, this is not the right solution.
Have you ever had that problem ?
Any suggestions ?
Thank you.
Marie

Hi,
It's true, in a ASP.NET the databinding only works in one way (by design) - from source to UI, and not the other way around (this will apparently change in ASP 2.0)... so your solution is in-fact the right one.
If you want to enjoy the 2-way binding, use winforms
Regards,
Ofer

Use combination context param, EL of databinding in a EL.

Hi. I have a image tag(ADF Faces.General Controls). I add into source attribute at common of property palette a EL #{resource['images:bakery.jpg']} with bakery.jpg is a image locate directy in images directory. Now, I want to change images directory by a context param that i added and bakery.jpg by a EL of databinding, as #{bindings.Name.inputValue}. Purpose is to change dynamically image displayed. How to do that? Thanks.

Hi,
using Google to search for : EL JSF context parameter brings up
http://stackoverflow.com/questions/6523193/jsf-2-how-can-i-get-a-context-param-value-from-web-xml-using-jsf-el
For the image name, if it is in an ADF attribute you use
#{bindings.attributeName.inputValue}
So concatenating it
#{initparam El as in link above}/#{bindings.attributeName.inputValue}
or, to read it from HTTP and not through the faces servlet
/#{initparam El as in link above}/#{bindings.attributeName.inputValue}
Frank

COMMIT problem in TopLink, Struts, JSP and ADF Databinding sample

In the sample Developing a J2EE Application using TopLink, Struts, JSP and ADF Databinding,
I followed all the steps to build a department browse page and a edit page.
But when I get to Step number 23 in "Create a JSP to Edit Departments" I have a problem with the commit.
Only after I make a change in the form and click the sumbit button, the commit and rollback buttons become active. And After I click the commit button the data gets commited to the database but the page inofmation changes to the very first department record, not the current one.
How do I make those buttons active with out the extra click on the submit?
After I click the commit button, how do I keep the current data on the screen?
Thanks for you help.

Shay,
Thanks for the reply.
For #1, I was able to do the following and get away with not having to press submit first. I just removed the bindings for disable. I hope that does not cause any problems?
<input type="submit" name="event_Commit" value="Commit" />
<input type="submit" name="event_Rollback" value="Rollback" />
For #2, How I add an action on an HTML button? My UIModel.xml for the edit department page currently has two actions on it. Commit and RollBack. Is it linked through the "name" attribute of the input tag?

Flex databinding and webservices

Hi everyone,
At the beginning, i asked this on the Flex forum but they redirected me here, hoping i could find an answer.
I have a JBoss server, getting some data for my Flex/AIR client. The client is requesting the data using SOAP webservices.
The trouble is that it's getting really complex to handle the data so i basically want to use the databinding feature, or some pattern to make it easier.
The goal isn't only displaying, but also editing the data so that it's automatically sent to the JBoss server (and eventually auto-refreshing on other clients).
That's why i really want to use some kind of databinding, which totally fits: the displayed value is totally synchronized with the dataprovider variable. I would like to use that with external data (through webservice in the best case), hoping you know a way/pattern/feature to make it work.
Thank you very much.
Original post : http://forums.adobe.com/thread/801243

Ask on the BlazeDS and/or LiveCycle forums.

2 way databinding between DataGrid and DropDownList

I am not getting anywhere with what I thought is the most simplest basic thing in the world.
I have a ArrayCollection "employees" which is used to fill a DataGrid. The department is listed as an Integer value. I would like to display however the name of the department, which is in a second ArrayCollection "departmentsArray". So the itemRenderer (which is not yet implemented in this code) needs to match the "idn" value with the "departmentid" value and then display the name of the department. However, when the user clicks on the DropDownLists and selects a new department, the departmentid value in the employee array needs to get updated too.
I am assuming that this can be done with 2 way databinding, but I am not getting this to work and would greatly appreciate if someone could show me how the code would have to look for this.
Michael
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                  xmlns:s="library://ns.adobe.com/flex/spark"
                  xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
     <fx:Declarations>
          
     </fx:Declarations>
     <fx:Script>
          <![CDATA[
               import mx.collections.ArrayCollection;
               [Bindable]
               private var employees:ArrayCollection = new ArrayCollection([
                    {idn:1, firstname:'Lisa', lastname:'Tran', departmentid:1},
                    {idn:2, firstname:'Michael', lastname:'Orchard', departmentid:2},
                    {idn:3, firstname:'Wolfgang', lastname:'Prettyer', departmentid:2},
                    {idn:4, firstname:'Julia', lastname:'Stancau', departmentid:3},
               [Bindable]
               private var departmentsArray:ArrayCollection = new ArrayCollection([
                    {idn:1, department:'Video'},
                    {idn:2, department:'Web'},
                    {idn:3, department:'Print'},
          ]]>
     </fx:Script>
     <s:DataGrid x="57" y="90" width="410" requestedRowCount="4" dataProvider="{employees}">
          <s:columns>
               <s:ArrayList>
                    <s:GridColumn dataField="idn" headerText="ID"></s:GridColumn>
                    <s:GridColumn dataField="firstname" headerText="Vorname"></s:GridColumn>
                    <s:GridColumn dataField="lastname" headerText="Nachname"></s:GridColumn>
                    <s:GridColumn dataField="departmentid" headerText="Department"></s:GridColumn>
               </s:ArrayList>
          </s:columns>
     </s:DataGrid>
</s:Application>

Thanks for the info.
I've only seen info about Snow Leopard syncing (and it doesn't really specify 2 way) to Exchange (which is not LDAP)
Addressbookserver (www.addressbookserver.com) is also not LDAP.
I really need this to work (2 way sync) with an LDAP server.
Thanks.

ModelReference value used as a key with output_text

I think that it would be good to enable the use of the modelReference value as a key with output_text, through an additional attribute.
Example : instead of corresponding to the actual description of a product, the modelReference value would be the key to the locale-sensitive description.
Wouldn't it be necessary to support this scenario ?
Thanks in advance.

This can be done through the renderer. If you have a convention for naming resource keys, the renderer can recognize the value is a key and look it up in a resource ...

Good practice for async databinding, regarding entity-framework.

I have some issue to find a good pattern to keep my UI responsive using asynch databinding and entity framework which is not thread-safe. It would be a shame if the UI came to totaly freeze with no feedback for a connection lost.
So, entity framework is not thread-safe. Which mean I won't be able to rely on lazy loading here and involve than if I do async databinding to a collection of object, each object will have to load their navigations properties with their own context to display
data. Ok, I can handle this. But what if I need more than displaying data and I want to modify a navigation property ?
I need when I set the navigation property in my viewmodel to attach an entity from the same context than the parent entity is from. So here I have one context for multiple thread. What do I do ? =(
Does anyone have some experience in it and can help me to clear this mess from my mind ? =D
All the sample I can find about async databinding don't go any further than make a Thread.Sleep before returning a string, it's not realy helpfull.

There are reasons people post simple explanations.
One of those is because they post blog entries when they're learning something rather than when they are expert in it. The blog post is part of their learning process.
I sometimes share context.
What I do is put the context in Application.Current.Resources and then go get it from there when I need to re-use that particular one.
xxxDomainContext DBContext = new xxxDomainContext();
Application.Current.Resources.Add("DBContext", DBContext);
and using that:
context = (xxxxDomainContext)Application.Current.Resources["DBContext"];
You can alternatively share collections in a similar way. Depends on how many related tables you have, but reading a whole tree of static data is sometimes a good idea rather than just one table at a time.
One technique I use is to cache slowly changing data on the client and then go get changes since the last run off the server. For a fair few applications, yesterdays data is good enough for most data sets. It's just the odd one or two which you really
need up to date numbers or whatever.
You can see a collection shared in this sample ( but the sharing is for different reasons ) :
https://gallery.technet.microsoft.com/Dynamic-XAML-Composed-View-e087f3c1
Please don't forget to upvote posts which you like and mark those which answer your question.
My latest Technet article - Dynamic XAML

Uanble to see all the contexts in jsp NetUI DataBinding

I am unable to see all the contexts in the JSP file.
I am doing the following
In the controller I have following methods
@jpf:forward name="success" path="myJSP.jsp"
action1()
//populate formBean
return new Forward("success", formBean);}
action2(FormBean bean)
In the JSP I have the following form
<netui:form action="action2">
In the JSP when I try to user NetUI DataBinding, I dont see actionForm or pageFlow context in the dropdowns to select from. I only see application, bundle, globalApp, request, session, pageContext and url scopes.
Is there something in controller that will remove the contexts??

Solved. It was a privlege problem about weblogic database. After I have deleted all the records on the p13n tables I could get the content.

Datalist databinding in flash builder

Ok, so I have everything setup in Catalyst and imported into Flash Builder ok.
But, how do I get data from my AS code to bind to the datalist?
I am getting my data from web services - something I'm fine and experienced at doing. But, how do I databind to these components created in Catalyst?
Any help greatly appreciated!

Hi,
It's OK, I worked it out - just need to use normal databinding as in any other Flash Builder/Flex project.
I just got confused with the layout of the MXML and the way Catalyst throws everything together.
Lee's tutorial video here really helped explain it all:
http://www.gotoandlearn.com/play.php?id=111
Hope you too find it useful
I've now got it working with my usual PureMVC codebase. Works a treat! A fully 'designed' Air RIA connecting to a web service etc within a few hours. Nice.
Dave.

ModelReference vs DataBinding

Similar Messages

Maybe you are looking for