I am working on a mixed situation where i am using Servlets & Struts2.
I am calling a HTTPServlet and where i am processing on data.
Then I need to make a call to struts API to insert data in DB.
In that i am using HTTPSession also.
So I am calling
ServletActionContext.getRequest()
To get HttpRequest and then session in that struts action class.
Struts Action class is getting called by Servlet.
But
ServletActionContext.getRequest()
always returns NULL.
Is it because that it is not getting called by web.
First, ServletActionContext and ActionContext both use a ThreadLocal to store per-request objects (such as the request and response). This is handled by Struts2. If you attempt to call those from a Servlet, they'll return null, since the request was routed to your servlet, not to Struts2 (and thus Struts2 did not create an action context for the request).
With that said, Struts2 is a higher level abstraction over the Servlet API. The fact that you are invoking a Struts2 action from within a servlet sounds really wrong.
If you need to perform some common process in both a servlet and an action, then create a separate class to handle the process (i.e., inserting data in a database) and then call that class from both your servlet and your action.
If that isn't what you're trying to do, then please provide more details, along with an example of your servlet and action code.
Related
I'm way new to Spring.
I am looking to verify the following understanding of SpringMVC lifecycle-- to put things into places in the overall view:
The entire process is request-driven.
There is a Front Controller pattern and the Front Controller in Spring MVC is DispatcherServlet.
Upon every incoming request from the user, Spring manages the
entire life cycle as described in here.
In the overall view, DispatcherServlet dispatches the request to a controller for a service at the back-end.
Once this is done, it hands it in to the View component of MVC for its view to be prepared in response to the user.
In more detail,
DispatcherServlet uses Handlers to decide "which controller" to serve that request.
The controllers are/should be "light-weighted"-- should be decoupled from
the service processes at back end as a good design practice-- they hold references to the service(s) and invoke the right one(s).
Their "mission" is to control the service process(es) for building the model and handing
it back to the dispatcher for the next step.
The View component in itself has 2 parts: first the ViewResolver picks the right type of look for View to put the model into the final format for the user.
From the developer's angle-- the DispatcherServlet is a behind-the-scenes thing.
All i do is to define, and configure it, if necessary, in web.xml.
As the developer, I instantiate an ApplicationContext (there are many ApplicationContext types-- i pick one depending on what i need, typically the
WebApplicationContext(?) ). AplicationContext is the factory that creates all the servlets/beans including
the DispatcherServlet, using their descriptions in the .xml files. The DispatcherServlet then runs behind the scenes and manages the
entire process-- goes&gets the controllers, using the annotations or the their .xml descriptions,
views, handlers, validators etc.
I am wondering whether this description is holds-- valid&complete, and whether there are big missing pieces in it.
Thanks in advance.
Let's go into detail step by step
DispatcherServlet uses Handlers to decide "which controller" to serve
that request
The DispatcherServlet maintains an ordered List of HandlerMapping beans (which it loaded from the WebApplicationContext). A HandlerMapping is
Interface to be implemented by objects that define a mapping between
requests and handler objects.
When the DispatcherServlet receives a request, it iterates over this list until it finds a matching handler object for the request in question. For simplicity, let's consider only RequestMappingHandlerMapping.
A bean of this type stores a mapping of #RequestMapping annotated methods (the actual Method object retrieved with reflection) stored as a HandlerMethod instances and wrapped in RequestMappingInfo objects that hold mapping data for matching the request, ie. URL, headers, and request parameters.
The DispatcherServlet retrieves the best matching HandlerMethod from these and any corresponding HandlerInterceptor instances which you may have registered. It retrieves these as a HandlerExecutionChain object. It will first apply any pre-handling by HandlerInterceptors. It will then try to invoke your HandlerMethod. This will typically (but not always) be a #RequestMapping annotated method inside a #Controller annotated class. This produces what Spring calls a dispatch result. The DispatcherServlet then applies post-handling by the HandlerInterceptors. It finally processes the dispatch result depending on what it is. You can see the supported return types for an idea of what that can be.
The controllers are/should be "light-weighted"-- should be decoupled
from the service processes at back end as a good design practice--
they hold references to the service(s) and invoke the right one(s).
Their "mission" is to control the service process(es) for building the
model and handing it back to the dispatcher for the next step.
In an MVC application, the controller controls operations by making changes to the model. You can do this directly in your controller or you can decouple it by implementing and providing service and business classes for that purpose. The controller depends on these, but not the other way around. Check out multilayered architectures.
The controller then builds the model (Model) which the DispatcherServlet possibly makes available to the view. I say possibly because the controller can produce a response directly without any view (think jsp) involved.
The View component in itself has 2 parts: first the ViewResolver picks
the right type of look for View to put the model into the final format
for the user.
In the typical case where the Controller handler method would return a Model, View, ModelAndView, String (and some others) object, then a ViewResolver would handle finding the correct View. The DispatcherServlet then tries to render that view by first merging the model as you said. This usually means taking all Model attributes and putting them into the HttpServletRequest attributes. The rendering step can involve rendering a jsp, generating XML, or anything at all really.
From the developer's angle-- the DispatcherServlet is a
behind-the-scenes thing. All i do is to define, and configure it, if
necessary, in web.xml. As the developer, I instantiate an
ApplicationContext (there are many ApplicationContext types-- i pick
one depending on what i need, typically the WebApplicationContext(?)
).
You don't actually need to instantiate it. The DispatcherServlet will do that itself (or use the ContextLoaderListener's) when the Servlet container calls init() on it. It will generate its own WebApplicationContext. What you can do is decide which subclass of WebApplicationContext to use. This is an important choice if you want to load your context from XML or from a Java configuration. You can do this by providing an <init-param>.
AplicationContext is the factory that creates all the servlets/beans
including the DispatcherServlet, using their descriptions in the .xml
files. The DispatcherServlet then runs behind the scenes and manages
the entire process-- goes&gets the controllers, using the annotations
or the their .xml descriptions, views, handlers, validators etc.
The ApplicationContext is also known as the Inversion of Control Container. It does not include the DispatcherServlet. The DispatcherServlet is managed by the Servlet container and not by Spring. However, it does primarily take its configuration from Spring's ApplicationContext (WebApplicationContext). It registers a number of special beans it finds in the context. You can declare these yourself or let Spring do it for you with this little bit of XML
<mvc:annotation-driven>
This will (mostly) take care of doing what you describe, ie. registering handlers, validators, views, etc.
I am wondering whether this description is holds-- valid&complete, and
whether there are big missing pieces in it.
Don't forget that a Spring MVC web application is a Servlet web application. The lifecycle of the application is therefore tied to the Servlet container.
There is no good answer to your question. "Sure" is as close as I can get.
You can configure spring using xml files or annotations or a combination of both.
You don't need to write servlets with Spring MVC, but you can if you want. Mostly you can (maybe should) create controller classes (either by extending a Spring controller class or marking a class with the #Controller annotation).
The "mission" of the controller is to perform necessary processing of requests. They do not just "control service processes"
There is no "hand it back" to the dispatcher.
The DispatchServlet must be configured in the web.xml file,
this is never optional.
You can (maybe should) have a layer between your controller classes and any web services that you will call from the controller classes.
You can have multiple applicationContexts or use a single applicationContext.
As often as not,
the View is a JSP file.
The Controller should add DTOs (data transfer objects) that are used by the view to display non-static information.
EDIT: I removed the mention of VO objects, I (like many, it seems) incorrectly conflated DTO and VO patterns.
There is no "behind the scenes".
The DispatcherServlet receives a request and passes it to the appropriate controller for processing.
Read section 17 of the Spring Framework Reference
When we create Servlet object on JSP page or in Java class, How it works internally ? How it will effect on performance ?
you should not call the servlet explicitly by the new keyword as we normally do.In the case of servlet, servlet container is responsible for instantiating the servlet.
For each servlet defined in the deployment descriptor of the Web application, the servlet container locates and loads a class of the type of the servlet. This can happen when the servlet engine itself is started, or later when a client request is actually delegated to the servlet.
There is only a single instance which answers all requests concurrently. This saves memory and allows a Servlet to easily manage persistent data.
When one create Servlet object on JSP page or in Java class,
You cannot expect to work it as a Servlet.
For More in details answer, Refer BalusC's answer here.
We can create an object of our servlet class. But because servlet operation depends on the servlet context, request, response, etc provided by the web container, there is nothing to be gained by creating one outside the container environment.
In one sentence - By doing so, we cannot expect to work as a servlet.
When I invoke a controller, it's possible that the view response calls other controllers. Is there a way to determine, in MVC, all of the views and/or controllers were called in a single response?
Thanks.
I don't think that the framework exposes this directly, but you could hook into the OnActionExecuted method and log each action that gets invoked along with a unique request identifier. You could hook into Application_BeginRequest in global.asax.cs to generate a GUID to use as the unique id for that request (stored in the Session, but overwritten for each new request). If you use a base controller and derive all your controllers from it, you could put the logging in the base controllers OnActionExecuted method to keep it DRY.
Alternatively, you could look at creating a custom ActionInvoker and put the logging there.
This is where I would start anyway, though, there might be a better way.
NOTE: This will only tie together actions that are invoked server-side for the request. Any AJAX requests kicked off client-side when client receives the rendered view will show up as different requests. If you need to include those as well, your unique id generation code should probably only run on non-AJAX requests, leaving the existing id alone in the session otherwise. Typically AJAX requests have an HTTP_X_Requested_With header to distinguish them.
How do Struts2 actions compare to Servlets? Can an action act as a servlet?
A Struts (Struts1/Struts classic) action was more tied to a servlet. In Struts2, things are quite different. A Struts2 action is just a POJO (plain Java class), totally decoupled from the Servlet API. This decoupling eases testing.
In the typical workflow of a Struts2 webapp, an action will be instantiated for each request and will be associated with a Servlet (it can implement the ServletAware interface if it needs to be aware of this association; normally this is not necessary nor advisable).
An important conceptual difference with Servlets (and with Struts actions) is that Struts2 actions are not reused for different requests, and hence are thread safe: say, it can happen that three http requests (simultaneous or not) are served by one servlet instance; but inthat case we will still have three different Struts2 action instances, one for each request.
Struts is an abstraction layer on top of the vanilla java servlet stuff. Actions themselves are defined by the programmer and are invoked by struts frameworks when a URL is hit (you configure what url maps to which action). So they don't really "compare" to a servlet, they are an abstraction around the functionality the servlet provides. One typical thing you do with an action is output a jsp, which is equivalent to a servlet. so what happens is
a) request comes in, gets mapped to action
b) action loads some data
c) action renders a jsp, passing loaded data to the jsp.
An action can output directly to the request/response, if that is what you want, but in most cases is probably not good practice.
Struts2 is a MVC framework implementation based on Java EE technology.
I am using pieces of the Spring MVC framework; in particular, I am making use of the #Controller, #RequestMapping and #ResponseBody annotations, in conjunction with a webstatsHttpMessageConverter hooked up to an OXM jaxb2 marshaller bean. My controller methods use the #RequestParam annotations to parse some GET parameters, query a service that uses a JPA EntityManager behind the scenes, and returns a JAXB object that is converted to its XML representation by the HttpMessageConverter.
I pared this scenario down to a very simple test case to try and determine the location of an execution delay that I have noticed; Example controller method:
#RequestMapping("/my_service__method_endpoint")
#ResponseBody
public Jaxb2CompiledClass getSomeData(#RequestParam String param1,
#RequestParam Date start, #RequestParam Date end) {
log.debug("Entering getSomeData");
Thread.sleep(5000);
log.debug("Finished waiting, leaving getSomeData);
return new Jaxb2CompiledClass();
}
This scenario works fine, and returns the appropriate data in the appropriate format. However, while load testing this configuration, I've run into a problem - each of my controller methods annotated with #RequestMapping will not run concurrently; if I spawn multiple HTTP requests to the service endpoint, each method call will finish before the next HTTP request is processed. In my actual code, I am using service objects to pull results via JPA and transform those results into an object of the appropriate Jaxb2 class. My understanding is that this controller should be able to run these methods concurrently, one for each HTTP request invoking the /my_service__method_endpoint. Is there some fundamental concept I am missing out on here? The log output from the code above shows that each call to getSomeData is waiting for the previous invocation to complete running before kicking off. This is obviously highly undesirable in a high-volume environment.
Skaffman's response is correct - everything is working fine concurrently, but because I was too lazy to use a real load testing tool, my browser was throttling the requests before they were sent.