Today with SPRINGBOOTJPA paged query, using the Entitymanager + query way to inquire
PrivateList<policy> Getqueryresult (StringBuilder basejpql, map<string, object>Paras, pageable pageable) { //Be sure to add the following policy.class, otherwise it will not automatically map the results of the query to the policy, resulting in a list<object[]>, resulting in a property that cannot be taken to the policy in the JSPQuery query = em.createquery ("Select P" +basejpql.tostring (), Policy.)class);//query query = Em.createnativequery ("Select ID, title, author, url, publishtime, Menucode, Urlcode, Createtime, CreateUser, UpdateTime "+basejpql.tostring (), policy.class);Setqueryparameter (Query,paras); Query.setfirstresult ((int) Pageable.getoffset ()); Query.setmaxresults (Pageable.getpagesize ()); returnquery.getresultlist (); }
At first, the second argument was not added to the CreateQuery method, resulting in the query's result set not being automatically mapped to the policy entity
When the front-end JSP takes the policy attribute, it will always error.
On the JSP for a long time, the final discovery is the problem, I hope we can less detours.
The JSP takes the property that list can traverse but cannot take to the object Springboot JPA