Académique Documents
Professionnel Documents
Culture Documents
Ans: Ans: The DSP tag library tags support runtime expressions, such as
ATG framework has provides his own tag libraries like DSP/DSPEL/CORE.
Q-Transactions Modes in ATG
Ans:
Mode
Description
Required
RequiresNe
w
Indicates that all activity within the demarcated area must occur in its own
separate transaction. If no transaction is in place in the area, a transaction is
created at the beginning of the demarcated area and ended at the end of the
demarcated area. If a transaction is in place when the demarcated area is
entered, that transaction is suspended, and a new transaction is begun; at
the end of the demarcated area, the new transaction is ended, and the
original transaction is resumed.
NotSupport
ed
Supports
Mandatory
Never
Q-Transaction Demarcation
Ans: Enclosing of transactional behavior is called transaction demarcation.
Transaction demarcation always wraps a sequence of actions, such as a
single request, a single method, or a section of code within a method. The
demarcation initializes some transactional behavior before the demarcated
area begins, then ends that transactional behavior when the demarcated area
ends. The application server uses these demarcations to determine the
appropriate calls to theTransactionManager object.
Q- Order States
State Name
Description
APPROVED
The approval process for the order is complete, and the order has b
approved.
FAILED
FAILED_APPROVAL
The approval process for the order is complete, and the order has b
rejected.
INCOMPLETE
NO_PENDING_ACTION
The order has been fulfilled, and processing of the order is complete
shipping groups in the order are in a NO_PENDING_ACTION or REMO
state, and order payment has been settled.
PENDING_APPROVAL
PENDING_CUSTOMER_A
CTION
PENDING_CUSTOMER_R
ETURN
This is an unused state. It is placed in the list of states for the conve
those who might want to implement this state.
PENDING_MERCHANT_A
CTION
PENDING_REMOVE
A request was made to remove the order. The order is placed in this
until all shipping groups in the order are set to a PENDING_REMOVE
PROCESSING
QUOTED
This is an unused state. It is placed in the list of states for the conve
those who might want to implement this state.
REMOVED
SUBMITTED
The order has completed the purchase process and has been submi
Fulfillment.
TEMPLATE
and populate the drop-down list, which is associated with the catalogRefIds
property of the CartModifierFormHandler. Additionally, the user can specify in
a textbox a quantity of the selected SKU to add to the cart, which is
associated with the quantity property of the CartModifierFormHandler.
When the user clicks the Add To Cart submit button, the form is processed,
the properties of CartModifierFormHandler are set, and the
handleAddItemToOrder method ofCartModifierFormHandler is invoked. The
handleAddItemToOrder method adds the quantity (specified in
CartModifierFormHandler.quantity) of the selected SKU (specified in
CartModifierFormHandler.catalogRefIds and identified by repository ID) to the
current Order and then reprices the Order.
Item caches hold the values of repository items, indexed by repository IDs.
Item caching can be explicitly enabled for each item descriptor.
Query caches hold the repository IDs of items that match given queries.
When a query returns repository items whose item descriptor enables query
caching, the result set is cached as follows:
InsertableServlet
Servlets that implement the InsertableServlet interface have an
insertAfterServlet property that enables the servlet to insert itself in a specific
spot in the pipeline. The key advantage of this mechanismis that it does not
require modifying any existing servlets in the pipeline compared to
Pipelineable Servlet.
Example: if we want to insert a servlet i.e. Servlet1a, between two servlets
i.e. Servlet1 & Servlet2 in the pipeline.
If Servlet1a implements Pipelineable Servlet, you can reroute the pipeline by
changing the value of theServlet1.nextServlet property pointing to Servlet1a
rather than Servlet2, and set Servlet1a.nextServlet to point to Servlet2.
But if Servlet1a implements InsertableServlet, all you have to do is set
Servlet1a.insertAfterServlet to point to Servlet1, and Servlet1a will
automatically be spliced into the pipeline right after Servlet1 and before
Servlet2.
Servlet1a is able to do this because it effectively sets its own nextServlet
property to the value of Servlet1s nextServlet property and rewrites
Servlet1s nextServlet property to point to Servlet1.
Steps to Create InsertableServlet
Following steps involve creating & adding an InsertableServlet to the servlet
pipeline.
1. Write a servlet e.g. MyServlet, extending InsertableServletImpl.
Ans: When a JSP page is requested, the DAF servlet pipeline runs through the
set of servlet shown below.
The application server follows the following path for processing the request.
1.When a user performs an action that prompts a response, the application
server creates an instance of the HttpServletRequest and
HttpServletResponse.
2.Based on the directories and file extension of the requestURI, the
application server uses servlet and filter mappings defined in web.xml to
determine the next resource to call.
3.By default, PageFilter is mapped to handle JSP requests. When the
application server invokes PageFilter, it checks the request and response for a
reference to a Dynamo request and response pair.
4.The pair does not exist; PageFilter will start the DAF servlet pipeline by
calling DynamoHandler ,the first servlet in the pipeline.
5.The DAF servlet pipeline will process through a series of servlets that
modify the request andresponse by extracting path information and providing
session, user, and security information.
6.The last servlet in the pipeline is TailPipelineServlet. It is responsible for
callingFilterChain.doFilter(), which invokes the next filter defined in web.xml.