A2040-922 試験問題を無料オンラインアクセス

Brandon wants to extend Dojo's dijit.Dialog box to add some extra functionality. How would Brandon declare the new Dojo class?

• A.dojo.declare("brandons.Dialog", dijit.Dialog, { // added functionality });
• B.dijit.declare("brandons.Dialog", dijit.Dialog, { // added functionality });
• C.dojo.declare("brandons.Dialog", "dijit.Dialog", { // added functionality });
• D.dijit.declare("brandons.Dialog", "dijit.Dialog", { // added functionality });

Aaron has created an XPages application that has a couple of XPages to surface the same data to two different application roles in two completely different user interfaces. Each role can manipulate parts of the data, but in both cases, the data must adhere to the same business logic and rules. What would be the best way for Aaron to implement the same business logic in each XPage?

• A.Create a common Server-Side JavaScript Library for the XPages to share that the user interface can use to execute the business logic
• B.Create a common Client-Side JavaScript Library for the XPages to share that the user interface can use to execute the business logic
• C.Use a series of Custom Controls to hold the business logic and share them amongst the XPages
• D.The user interface and the business logic in an XPage can not easily be separated and must be maintained in each XPage

John wishes to add a managed bean to his application. In order to do this he must do which of the following:

• A.Create a file called xpages-config.xml within his application and define the managed bean within the file using the appropriate syntax.
• B.Create a JavaBean class and add the Java class as a page resource to the XPage where the managed bean is to be used.
• C.Open the pre-existing xpages-config.xml file located at WebContent\WEB-INF\xpagesconfig.xml and add the appropriate markup to the file.
• D.Open the pre-existing faces-config.xml file located at WebContent\WEB-INF\faces-config.xml and add the appropriate markup to the file.

John has a managed bean which is defined as follows: The bean has a property called 'miles' which allows a distance in miles to be entered and converted to kilometers. John wishes to have a user enter a value via an edit box and use the managed bean to convert the value from miles to kilometers. What should the value of the edit box's value attribute be in order to utilize the managed bean?

• A.<xp:inputText id="inputText1" value="distanceConverter.miles"></xp:inputText>
• B.<xp:inputText id="inputText1" value="#{view.distanceConverter.miles}"></xp:inputText>
• C.<xp:inputText id="inputText1" value="#{bean.MyBean.setMiles()}"></xp:inputText>
• D.<xp:inputText id="inputText1" value="#{distanceConverter.miles}"></xp:inputText>

Jeremy wants all of the dijit.Dialog boxes in his application to call a client side JavaScript function called "validateForm" whenever they are hidden. What is the best solution?

• A.Create a custom Dojo control and use that instead of the standard dijit.Dialog in the application
  using the following code:
  /**
  *Custom Dojo Control
  */
  dojo.provide('com.myco.widget.Dialog');
  dojo.require('dijit.Dialog');
  (function(){
  dojo.declare("com.myco.widget.Dialog", dijit.Dialog, {
  onHide: validateForm
  })
  }());
  /**
  *Initialization code
  */
  var dialog = new com.myco.widget.Dialog();
• B.Create a custom Dojo control and use that instead of the standard dijit.Dialog in the application
  using the following code:
  /**
  *Custom Dojo Control
  */
  dojo.provide('com.myco.widget.Dialog');
  dojo.require('dijit.Dialog');
  (function(){
  dojo.declare("com.myco.widget.Dialog", dijit.Dialog, {
  onHide: validateForm
  })
  }());
  /**
  *Initialization code
  */
  var dialog = new com.myco.widget.Dialog();
• C.Whenever he initializes a new dijit.Dialog, add an onHide event like so:
  var dialog = new dijit.Dialog({
  onHide: validateForm
  }
  );
• D.Create a custom Dojo control and use that instead of the standard dijit.Dialog in the application
  using the following code:
  /**
  *Custom Dojo Control
  */
  dojo.provide('com.myco.widget.Dialog');
  dojo.require('dijit.Dialog');
  (function(){
  dojo.declare("com.myco.widget.Dialog", dijit.Dialog, {
  onHide: validateForm
  })
  }());
  /**
  *Initialization code
  */
  var dialog = new dijit.Dialog();
• E.Create a custom Dojo control and use that instead of the standard dijit.Dialog in the application
  using the following code:
  /**
  *Custom Dojo Control
  */
  dojo.provide('com.myco.widget.Dialog');
  dojo.require('dijit.Dialog');
  (function(){
  dojo.declare("com.myco.widget.Dialog", dijit.Dialog, {
  onHide: validateForm
  })
  }());
  /**
  *Initialization code
  */
  var dialog = new com.myco.widget.Dialog();
• F.In the "Close" or "Cancel" button of each dialog add a call to validateForm in the onClick event.
• G.Create a custom Dojo control and use that instead of the standard dijit.Dialog in the application
  using the following code:
  /**
  *Custom Dojo Control
  */
  dojo.provide('com.myco.widget.Dialog');
  dojo.require('dijit.Dialog');
  (function(){
  dojo.declare("com.myco.widget.Dialog", dijit.Dialog, {
  onHide: validateForm
  })
  }());
  /**
  *Initialization code
  */
  var dialog = new com.myco.widget.Dialog();