Browse Prior Art Database

View page generation trace back mechanism

IP.com Disclosure Number: IPCOM000198633D
Publication Date: 2010-Aug-11
Document File: 2 page(s) / 55K

Publishing Venue

The IP.com Prior Art Database

Abstract

In typical MVC structure applications, a request will be handled firstly by a controller. and will be forward/redirect for serval time and finally find a view to render the result. Developer want to know the invocation chain to better identify where the error comes from. Currently, there's no good way for the developer to see such a chain. Most of the system does not have the invocation chain log system. For those that have the chain log. The developers have to dig the info out from a big central log file. It's not a easy job. This artical introduce a new way to log the innovation chain into the result MVC view page instead of a central file so that when developers find a error in view, they can check the invocation chain in the resulting page directly to find out what has been done underlying. As a result, they can better understand the system or better identify the cause of the error easliy.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 2

View page generation trace back mechanism

Title:View page generation trace back mechanism

Background:

In typical MVC structure applications, a request will be handled firstly by a controller. and will be forward

finally find a
view to render the result.
Those kind of forward

. When developers want to edit the logic or to debug the

defects of such a
system.

They usually want to know the invocation chain to better identify where the error comes from.

Existing solution:

1, The developers can't find useful information in the resulting view web pages. The developers have to find the invocation chain by

hand or by looking at the
complex source code logic.
2, there are some systems that can store all invocation chain to a central log file. But the user still need to map the resulting page to a

huge invocation
chain set in the central log file.

Both of them are not very easy and time consuming !

/redirect for serval time and

/redirect are all defined in config files or program logic

1

Page 2 of 2

My solution:

The MVC system based on web usually have the request and response object that passing to each web controller and handlers. The

controller and handles in MVC system conform to a specific interface. (To help better understand this, take httpServlet in java web MVC

world as an example.)

We can use AOP to create a intercepter for each contract point in the interface. In the intercepter, we can catch the invocation and store

the trace into a attribute of the request object. W...