WebWork's own TAG interface component library is not strong, but also practical, but when doing some universal systems, their components cannot fully meet the needs. In many universal systems, the interface tends to use batch generation, rather than manual drawing, in which the developers cannot determine which field information is set in the Action. At the same time, in the WebWork existing component library, it is necessary to manually set which data is taken from the Action class or the data collection. In general system development, the purpose of the component automatic value can be achieved by setting the naming rules of the interface component and the background properties field. In other words, in the development of the general system development, the background ACTION and the front interface intervene will achieve communication by interacting data packets, this packet has those attribute information to plan according to the specific page scene. Then, in the background, you can do only one an action class. This action only receives a datagram, then analyzes the information of the packet, and then transmits the business logic operation class to execute business logic. This action class can be a session bean, Can be other. So, to reach this, you have to rewrite a interceptor that packets the value to the packet by pressing the page, and then incompart the packet into the Action class. Since only one of the Action class, the page returned by the action is a system unified container page, and the container page will load other page components based on the content returned to the packet. At the same time, the purpose of expanding the webworktag library is to let the interface component automatically find the value of the packet to itself.
