About some questions about jsplet

Quote: If you are in the framework of the Action Centric, you can avoid two access points. View.do ?&templatename=a & objectname = / @ Demo & ObjectEvent = TEST

This approach is to process yourself instead of the framework. I have said, work is so much, just what is the division of the framework and what is the procedure. Saying jsplet is page and is not accurate. JSplet is a center-oriented, just specifying the view page that I want to use. View.jsp placed in front of just JSP implementation,

Quote: Action Centric is really troublesome, you must pass to the list of role lists and user lists. What is JSPLET for this question?

It is very simple to include two subpages list_both.jsp in access At the time by specifying the EventTarget parameter, the event can be routed to the appropriate object, and the contents of the object thisobj in response event constant, because the front desk VIEW display does not change. Note that role_list.jsp and roleManager, the UserManager object is developed independently.

Quote: This time, role_list.jsp and user_list.jsp have thisoBJ. And all the two Thisobj's Scope is SESESSION? Note that all object models require state hold mechanisms, so thisobj is indeed held in the session. In WebWork2, if you want to coordinate between multiple Actions, you must keep an object in the session, otherwise the stateless model is used, all status data is persisted in the database, and the pages per output each time and Action generates binding (a behavior), the decomposition process in the above example is not possible, because the status and behavior in the Action model cannot be abstracted together! When the page display logic is complicated, the page itself also has some temporary status. The MVC does not mean that all states are critical business data that requires persistence to the database. At each level, you may need to keep a state, and the MVC just says that some state variables are more important, and other levels can be driven. In addition, thisoBJ's Scope is SESSION is also inaccurate. First, it is noted that the JSplet has implemented the status and behavior abstraction through the objectization. Since then, the program has the control of this overall control, and there is a lifecycle control of the object in the jsplet, and the object's scope is custom, object The life cycle is the sub part of the session, not the entire session life cycle. Please note the scalability of this control strategy. We have the right to control the life cycle, and we can still use a stateless design, but it can be done when needed. There is no such option in the Action model like Webwork.

Quote: Semsis is excessive use is not good for thisobj just allowing the use of sessions, whether you can use the session to decide it, this is an enable technology, without Object support, the result is unable to use. Also, please read it carefully. Objectscope is a very fine resource usage control. In addition, don't mix design concepts and performance to talk. Design is reflected in the concept of concepts, which can achieve proper abstraction, and performance is the actual implementation process. In the case of support, technical means can be used to resolve performance issues, or degraded to lower hierarchies, this is a choice. In the case where the concept is unable to support, it is necessary to achieve a variety of ways of winding holes. Thisobj is important to concept, if needed, it can serialize the status to the Cookie or DotNet parameters, this is just a problem. Quote: JSPlet Action must be JSP? Of course, you can be any Java class, JSP Action is just an implementation of the IEventListener interface. In the initial version of JSplet, Action can only be written in the Java file. Separation can be written in JSP can also be written in Java.

Quote: Webwork's Action itself is a model object. This is a weak place in WebWork. The completely stateless design is because there is no suitable carrier. The JSPLET in JSPLET can be seen as a localization of session and is the decomposition of session. Many concepts in the jsplet can find the corresponding in the framework of webwork, just plus a lot of restrictions and becomes blurred.

Quote: No Model1 Easy (JSTL Javabean) No Struts "elegant" positioning blur. JSplet is an objective in a very refined manner. Again again, don't put JSPlet's positioning to those open source frames. The development time of JSplet is approximate to those open source frames. Take a closer look at the scalability in the design. All feature of the XWork can be implemented, and some of JSplet provides more than objectization.

It doesn't mean that you must use, all stateless design can be applied. JSplet is an event-driven design, at this point, more like Tapestry or JSF. ActioIn-based design is the real incompetent use of Session, which does not dare to apply session because it has no control for Session. And in jsplet's use control is natural: when you need an object, it exists when you need this state. It appears because it needs to exist. In the framework for an action, you still need to resolve status issues. It's just a framework that is unable to support it.

I think that most people developed by most people are the pile of Curd, so it is difficult to understand the necessity of state management in a complex application. After the object support, it constitutes the conceptual completeness of the entire framework.

It is very simple to include two subpages list_both.jsp in access At the time by specifying the EventTarget parameter, the event can be routed to the appropriate object, and the contents of the object thisobj in response event constant, because the front desk VIEW display does not change. Note that role_list.jsp and roleManager, the UserManager object is developed independently. Quote: This time, role_list.jsp and user_list.jsp have thisoBJ. And these two thisobj's scope are SESESSION?

Note that all object models require state hold mechanisms, so Thisobj is indeed held in the session. In WebWork2, if you want to coordinate between multiple Actions, you must keep an object in the session, otherwise the stateless model is used, all status data is persisted in the database, and the pages per output each time and Action generates binding (a behavior), the decomposition process in the above example is not possible, because the status and behavior in the Action model cannot be abstracted together! When the page display logic is complicated, the page itself also has some temporary status. The MVC does not mean that all states are critical business data that requires persistence to the database. At each level, you may need to keep a state, and the MVC just says that some state variables are more important, and other levels can be driven. In addition, thisoBJ's Scope is SESSION is also inaccurate. First, it is noted that the JSplet has implemented the status and behavior abstraction through the objectization. Since then, the program has the control of this overall control, and there is a lifecycle control of the object in the jsplet, and the object's scope is custom, object The life cycle is the sub part of the session, not the entire session life cycle. Please note the scalability of this control strategy. We have the right to control the life cycle, and we can still use a stateless design, but it can be done when needed. There is no such option in the Action model like Webwork.

Quote: Semsis is excessive use is not good for thisobj just allowing the use of sessions, whether you can use the session to decide it, this is an enable technology, without Object support, the result is unable to use. Also, please read it carefully. Objectscope is a very fine resource usage control. In addition, don't mix design concepts and performance to talk. Design is reflected in the concept of concepts, which can achieve proper abstraction, and performance is the actual implementation process. In the case of support, technical means can be used to resolve performance issues, or degraded to lower hierarchies, this is a choice. In the case where the concept is unable to support, it is necessary to achieve a variety of ways of winding holes. Thisobj is important to concept, if needed, it can serialize the status to the Cookie or DotNet parameters, this is just a problem.

Quote: JSPlet Action must be JSP? Of course, you can be any Java class, JSP Action is just an implementation of the IEventListener interface. In the initial version of JSplet, Action can only be written in the Java file. Separation can be written in JSP can also be written in Java.

Quote: Webwork's Action itself is a model object. This is a weak place in WebWork. The completely stateless design is because there is no suitable carrier. The JSPLET in JSPLET can be seen as a localization of session and is the decomposition of session. Many concepts in the jsplet can find the corresponding in the framework of webwork, just plus a lot of restrictions and becomes blurred. Quote: No Model1 Easy (JSTL Javabean) No Struts "elegant" positioning blur. JSplet is an objective in a very refined manner. Again again, don't put JSPlet's positioning to those open source frames. The development time of JSplet is approximate to those open source frames. Take a closer look at the scalability in the design. All feature of the XWork can be implemented, and some of JSplet provides more than objectization.

It doesn't mean that you must use, all stateless design can be applied. JSplet is an event-driven design, at this point, more like Tapestry or JSF. ActioIn-based design is the real incompetent use of Session, which does not dare to apply session because it has no control for Session. And in jsplet's use control is natural: when you need an object, it exists when you need this state. It appears because it needs to exist. In the framework for an action, you still need to resolve status issues. It's just a framework that is unable to support it.

I think that most people developed by most people are the pile of Curd, so it is difficult to understand the necessity of state management in a complex application. After the object support, it constitutes the conceptual completeness of the entire framework.