Which of the following two outcomes are achieved by the following snippet of code?
<dsp:importbean bean= “/Project/ShippingConf”/>
A.
Imports shipping Confinto page Context so you can exclude the full path and use the
ShippingConf as short hand
B.
Imports Shipping Confinto page Context so you can exclude the full path and use the shipConf
as short hand
C.
Makes the Shipping Conf available to the EL through the name ShippingConf
D.
Imports the ShippingConf to the page and is required to or reference it on the page
E.
Allows access to the DSP element through JavaScript or AJAX library
Explanation:
dsp:importbean
Imports a servlet bean or JavaBean component into a JSP.
<dsp:importbean bean=”Nucleus-path” [var=”attr-name” [scope=”scope-spec”] ]
dsp:importbean can import a servlet bean or a JavaBean component into a JSP. After a
component is imported, references to it can omit its full Nucleus path. You can also use
dsp:importbean to map the imported component to a scoped attribute that is EL-accessible.
dsp:importbean tags are typically placed at the top of the JSP, in order to facilitate references to
them.
Attributes
* bean
Set to the fully-qualified Nucleus path and name of the servlet bean to import.
* var
Names an EL variable that enables access to other page tags. When you use var, you can set its
scope attribute to page, request, session, or application. The default scope is page.
If var is omitted, the shorthand name for the component is used.
* scope
By default, the named variable is set to page scope, which makes it accessible to any EL-enabled
resources on the same page. The scope attribute lets you define a larger scope for variable, by
setting it to request, session, or application.
ATG Page Developer’s Guide