I would like to use this blog to record this card for two weeks of the bug ...
Or before the problem, through the Get method, background @controller back to the page and then pop the window. But I do not know why all the JS files and CSS files are reported 404 ...
(Previous blog record: http://www.cnblogs.com/wangshen31/p/8655044.html)
Then change the Get method to the Post method to solve!!! And then it's not in the first. Write to the back, more pop-up window, found at the end of the submit operation, found that do not know why layui.form monitoring submit always listen to two times submit action, obviously only click the button of the Submit event.
Commissioning for half a day, found not to say two times, as if the layer of the window too much and then a problem. So, decided to put the first pop-up window into the tab, so as to improve the full screen window of the situation.
However ... tab can only get the interface by getting the method ... And then back to the original question
At first, see Googlechorme, Error has shiro words, Baidu feel is Shiro static resources processing related. But looking at the code for a half-day, it seems that's not the reason.
Engaged for a long time, at last, with the help of the big guy, pointed out that the original is @controller intercept content and return the page name repeated and then caused the exception ...
@GetMapping ("Productbase/productbasemedicinalgone") public Modelandview Productbasemedicinalgone (@RequestParam map<string, object> Map) { returnnew Modelandview ("Productbase/productbasemedicinalgone"). AddObject ("map", map); // }
However, there is a doubt, many of the above code I are the two repeated, but the window is not the tab why this error?
The amount of ... Big Guy explained that may be tab or belong to this page, the Layer pop-up window belongs to a new page, although still a little puzzled, but the problem is solved, in short, after encountering similar problems, you can forget the controller to intercept the content and return the name of the view is repeated this aspect to consider!
About the controller returned the page JS file and CSS file 404 A formal solution to the problem