ClassCastException for com.querydsl.core.Tuple



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I am getting exception as



java.lang.ClassCastException: com.chat.dao.model.PGUserRoles cannot be cast to com.querydsl.core.Tuple


My code seems to be correct.



JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
List<Tuple> dataList = query
.from(pgUserRoles)
.where(isRoleName(userRolesDTO.getRoleName()),
isRoleType(userRolesDTO.getRoleType()),
isStatus(userRolesDTO.getStatus()),
isStatusNotEq()
)
.offset(offset)
.limit(limit)
.orderBy(orderByRoleIdDesc())
.fetch();
UserRolesDTO userData = null;
for (Tuple tuple : dataList)
userData = new UserRolesDTO();
userData.setRoleId(tuple.get(pgUserRoles.roleId));
userData.setRoleName(tuple.get(pgUserRoles.roleName));
userData.setRoleType(tuple.get(pgUserRoles.roleType));
userData.setStatus(tuple.get(pgUserRoles.status));
userRoleList.add(userData);



Exception is thrown at line with for



I don't understand why exception is been throw. Tuple is generic query result projection. And the example in there doc is similar to mine.
I'm using querydsl 4.2.1 version.










share|improve this question



















  • 1





    I think the fetch method is returning a List<PGUserRoles> rather than a List<Tuple>

    – Jeroen Steenbeeke
    Nov 15 '18 at 10:04











  • It looks like the List returned by List<Tuple> dataList = query does not return a list of Tuples but rather PGUserRoles. Beware that although you use the Type Tuple in the list, the actual list may be of a different type. See Type Erasue

    – tom1299
    Nov 15 '18 at 10:04












  • @JeroenSteenbeeke that's useless. It's like saying "I think there's an error" when user literally said it in his post

    – Sarief
    Nov 15 '18 at 10:12











  • @Jeroen Steenbeeke, you are right. It is returning List<PGUserRoles>. This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up.

    – RC2793
    Nov 15 '18 at 10:23











  • @Sarief pointing out an issue that normally only generates a warning at compile time but causes invalid casts at runtime is useless? The reason I added "I think" is because I do not know the specific API the question mentions, and the OP did not mention the generic type difference in his question.

    – Jeroen Steenbeeke
    Nov 16 '18 at 8:28

















1















I am getting exception as



java.lang.ClassCastException: com.chat.dao.model.PGUserRoles cannot be cast to com.querydsl.core.Tuple


My code seems to be correct.



JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
List<Tuple> dataList = query
.from(pgUserRoles)
.where(isRoleName(userRolesDTO.getRoleName()),
isRoleType(userRolesDTO.getRoleType()),
isStatus(userRolesDTO.getStatus()),
isStatusNotEq()
)
.offset(offset)
.limit(limit)
.orderBy(orderByRoleIdDesc())
.fetch();
UserRolesDTO userData = null;
for (Tuple tuple : dataList)
userData = new UserRolesDTO();
userData.setRoleId(tuple.get(pgUserRoles.roleId));
userData.setRoleName(tuple.get(pgUserRoles.roleName));
userData.setRoleType(tuple.get(pgUserRoles.roleType));
userData.setStatus(tuple.get(pgUserRoles.status));
userRoleList.add(userData);



Exception is thrown at line with for



I don't understand why exception is been throw. Tuple is generic query result projection. And the example in there doc is similar to mine.
I'm using querydsl 4.2.1 version.










share|improve this question



















  • 1





    I think the fetch method is returning a List<PGUserRoles> rather than a List<Tuple>

    – Jeroen Steenbeeke
    Nov 15 '18 at 10:04











  • It looks like the List returned by List<Tuple> dataList = query does not return a list of Tuples but rather PGUserRoles. Beware that although you use the Type Tuple in the list, the actual list may be of a different type. See Type Erasue

    – tom1299
    Nov 15 '18 at 10:04












  • @JeroenSteenbeeke that's useless. It's like saying "I think there's an error" when user literally said it in his post

    – Sarief
    Nov 15 '18 at 10:12











  • @Jeroen Steenbeeke, you are right. It is returning List<PGUserRoles>. This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up.

    – RC2793
    Nov 15 '18 at 10:23











  • @Sarief pointing out an issue that normally only generates a warning at compile time but causes invalid casts at runtime is useless? The reason I added "I think" is because I do not know the specific API the question mentions, and the OP did not mention the generic type difference in his question.

    – Jeroen Steenbeeke
    Nov 16 '18 at 8:28













1












1








1








I am getting exception as



java.lang.ClassCastException: com.chat.dao.model.PGUserRoles cannot be cast to com.querydsl.core.Tuple


My code seems to be correct.



JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
List<Tuple> dataList = query
.from(pgUserRoles)
.where(isRoleName(userRolesDTO.getRoleName()),
isRoleType(userRolesDTO.getRoleType()),
isStatus(userRolesDTO.getStatus()),
isStatusNotEq()
)
.offset(offset)
.limit(limit)
.orderBy(orderByRoleIdDesc())
.fetch();
UserRolesDTO userData = null;
for (Tuple tuple : dataList)
userData = new UserRolesDTO();
userData.setRoleId(tuple.get(pgUserRoles.roleId));
userData.setRoleName(tuple.get(pgUserRoles.roleName));
userData.setRoleType(tuple.get(pgUserRoles.roleType));
userData.setStatus(tuple.get(pgUserRoles.status));
userRoleList.add(userData);



Exception is thrown at line with for



I don't understand why exception is been throw. Tuple is generic query result projection. And the example in there doc is similar to mine.
I'm using querydsl 4.2.1 version.










share|improve this question
















I am getting exception as



java.lang.ClassCastException: com.chat.dao.model.PGUserRoles cannot be cast to com.querydsl.core.Tuple


My code seems to be correct.



JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
List<Tuple> dataList = query
.from(pgUserRoles)
.where(isRoleName(userRolesDTO.getRoleName()),
isRoleType(userRolesDTO.getRoleType()),
isStatus(userRolesDTO.getStatus()),
isStatusNotEq()
)
.offset(offset)
.limit(limit)
.orderBy(orderByRoleIdDesc())
.fetch();
UserRolesDTO userData = null;
for (Tuple tuple : dataList)
userData = new UserRolesDTO();
userData.setRoleId(tuple.get(pgUserRoles.roleId));
userData.setRoleName(tuple.get(pgUserRoles.roleName));
userData.setRoleType(tuple.get(pgUserRoles.roleType));
userData.setStatus(tuple.get(pgUserRoles.status));
userRoleList.add(userData);



Exception is thrown at line with for



I don't understand why exception is been throw. Tuple is generic query result projection. And the example in there doc is similar to mine.
I'm using querydsl 4.2.1 version.







java spring jpa spring-data-jpa querydsl






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 15 '18 at 13:02









Feedforward

2,15431527




2,15431527










asked Nov 15 '18 at 10:00









RC2793RC2793

233




233







  • 1





    I think the fetch method is returning a List<PGUserRoles> rather than a List<Tuple>

    – Jeroen Steenbeeke
    Nov 15 '18 at 10:04











  • It looks like the List returned by List<Tuple> dataList = query does not return a list of Tuples but rather PGUserRoles. Beware that although you use the Type Tuple in the list, the actual list may be of a different type. See Type Erasue

    – tom1299
    Nov 15 '18 at 10:04












  • @JeroenSteenbeeke that's useless. It's like saying "I think there's an error" when user literally said it in his post

    – Sarief
    Nov 15 '18 at 10:12











  • @Jeroen Steenbeeke, you are right. It is returning List<PGUserRoles>. This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up.

    – RC2793
    Nov 15 '18 at 10:23











  • @Sarief pointing out an issue that normally only generates a warning at compile time but causes invalid casts at runtime is useless? The reason I added "I think" is because I do not know the specific API the question mentions, and the OP did not mention the generic type difference in his question.

    – Jeroen Steenbeeke
    Nov 16 '18 at 8:28












  • 1





    I think the fetch method is returning a List<PGUserRoles> rather than a List<Tuple>

    – Jeroen Steenbeeke
    Nov 15 '18 at 10:04











  • It looks like the List returned by List<Tuple> dataList = query does not return a list of Tuples but rather PGUserRoles. Beware that although you use the Type Tuple in the list, the actual list may be of a different type. See Type Erasue

    – tom1299
    Nov 15 '18 at 10:04












  • @JeroenSteenbeeke that's useless. It's like saying "I think there's an error" when user literally said it in his post

    – Sarief
    Nov 15 '18 at 10:12











  • @Jeroen Steenbeeke, you are right. It is returning List<PGUserRoles>. This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up.

    – RC2793
    Nov 15 '18 at 10:23











  • @Sarief pointing out an issue that normally only generates a warning at compile time but causes invalid casts at runtime is useless? The reason I added "I think" is because I do not know the specific API the question mentions, and the OP did not mention the generic type difference in his question.

    – Jeroen Steenbeeke
    Nov 16 '18 at 8:28







1




1





I think the fetch method is returning a List<PGUserRoles> rather than a List<Tuple>

– Jeroen Steenbeeke
Nov 15 '18 at 10:04





I think the fetch method is returning a List<PGUserRoles> rather than a List<Tuple>

– Jeroen Steenbeeke
Nov 15 '18 at 10:04













It looks like the List returned by List<Tuple> dataList = query does not return a list of Tuples but rather PGUserRoles. Beware that although you use the Type Tuple in the list, the actual list may be of a different type. See Type Erasue

– tom1299
Nov 15 '18 at 10:04






It looks like the List returned by List<Tuple> dataList = query does not return a list of Tuples but rather PGUserRoles. Beware that although you use the Type Tuple in the list, the actual list may be of a different type. See Type Erasue

– tom1299
Nov 15 '18 at 10:04














@JeroenSteenbeeke that's useless. It's like saying "I think there's an error" when user literally said it in his post

– Sarief
Nov 15 '18 at 10:12





@JeroenSteenbeeke that's useless. It's like saying "I think there's an error" when user literally said it in his post

– Sarief
Nov 15 '18 at 10:12













@Jeroen Steenbeeke, you are right. It is returning List<PGUserRoles>. This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up.

– RC2793
Nov 15 '18 at 10:23





@Jeroen Steenbeeke, you are right. It is returning List<PGUserRoles>. This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up.

– RC2793
Nov 15 '18 at 10:23













@Sarief pointing out an issue that normally only generates a warning at compile time but causes invalid casts at runtime is useless? The reason I added "I think" is because I do not know the specific API the question mentions, and the OP did not mention the generic type difference in his question.

– Jeroen Steenbeeke
Nov 16 '18 at 8:28





@Sarief pointing out an issue that normally only generates a warning at compile time but causes invalid casts at runtime is useless? The reason I added "I think" is because I do not know the specific API the question mentions, and the OP did not mention the generic type difference in his question.

– Jeroen Steenbeeke
Nov 16 '18 at 8:28












2 Answers
2






active

oldest

votes


















0














query from generated class QPGUserRoles will return list of PGUserRoles, i.e. List



I have no idea what Tuple is, but it is allowed, apparently, because method return List but does not take actual parameter for list from the returned parameter but from supplied generated class. May be bad design or java limitation.



In all cases, you have to change your code. Your code is not correct, simply because it compiles :)



upd: Tuple is projection of Select statement. You don't use it - result is different ;)






share|improve this answer























  • This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

    – RC2793
    Nov 15 '18 at 10:26











  • In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

    – Sarief
    Nov 15 '18 at 10:31











  • @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

    – Sarief
    Nov 15 '18 at 10:31


















0














Ok so after modifying my code a little bit wrt v4. Its working now. Thank you all for your support.



JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
List<Tuple> dataList = query
.from(pgUserRoles)
.select(pgUserRoles.roleId,
pgUserRoles.roleName,
pgUserRoles.roleType,
pgUserRoles.status)
.where(isRoleName(userRolesDTO.getRoleName()),
isRoleType(userRolesDTO.getRoleType()),
isStatus(userRolesDTO.getStatus()),
isStatusNotEq()
)
.offset(offset)
.limit(limit)
.orderBy(orderByRoleIdDesc())
.fetch();





share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53316806%2fclasscastexception-for-com-querydsl-core-tuple%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    query from generated class QPGUserRoles will return list of PGUserRoles, i.e. List



    I have no idea what Tuple is, but it is allowed, apparently, because method return List but does not take actual parameter for list from the returned parameter but from supplied generated class. May be bad design or java limitation.



    In all cases, you have to change your code. Your code is not correct, simply because it compiles :)



    upd: Tuple is projection of Select statement. You don't use it - result is different ;)






    share|improve this answer























    • This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

      – RC2793
      Nov 15 '18 at 10:26











    • In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

      – Sarief
      Nov 15 '18 at 10:31











    • @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

      – Sarief
      Nov 15 '18 at 10:31















    0














    query from generated class QPGUserRoles will return list of PGUserRoles, i.e. List



    I have no idea what Tuple is, but it is allowed, apparently, because method return List but does not take actual parameter for list from the returned parameter but from supplied generated class. May be bad design or java limitation.



    In all cases, you have to change your code. Your code is not correct, simply because it compiles :)



    upd: Tuple is projection of Select statement. You don't use it - result is different ;)






    share|improve this answer























    • This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

      – RC2793
      Nov 15 '18 at 10:26











    • In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

      – Sarief
      Nov 15 '18 at 10:31











    • @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

      – Sarief
      Nov 15 '18 at 10:31













    0












    0








    0







    query from generated class QPGUserRoles will return list of PGUserRoles, i.e. List



    I have no idea what Tuple is, but it is allowed, apparently, because method return List but does not take actual parameter for list from the returned parameter but from supplied generated class. May be bad design or java limitation.



    In all cases, you have to change your code. Your code is not correct, simply because it compiles :)



    upd: Tuple is projection of Select statement. You don't use it - result is different ;)






    share|improve this answer













    query from generated class QPGUserRoles will return list of PGUserRoles, i.e. List



    I have no idea what Tuple is, but it is allowed, apparently, because method return List but does not take actual parameter for list from the returned parameter but from supplied generated class. May be bad design or java limitation.



    In all cases, you have to change your code. Your code is not correct, simply because it compiles :)



    upd: Tuple is projection of Select statement. You don't use it - result is different ;)







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 15 '18 at 10:09









    SariefSarief

    566519




    566519












    • This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

      – RC2793
      Nov 15 '18 at 10:26











    • In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

      – Sarief
      Nov 15 '18 at 10:31











    • @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

      – Sarief
      Nov 15 '18 at 10:31

















    • This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

      – RC2793
      Nov 15 '18 at 10:26











    • In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

      – Sarief
      Nov 15 '18 at 10:31











    • @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

      – Sarief
      Nov 15 '18 at 10:31
















    This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

    – RC2793
    Nov 15 '18 at 10:26





    This code used to work correctly in mysema.querydsl v3 but after upgrading to querydsl v4, things have messed up

    – RC2793
    Nov 15 '18 at 10:26













    In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

    – Sarief
    Nov 15 '18 at 10:31





    In that case, revert back and figure out where the problem is. This looks to me like a bug, but might be a change in interface. Regardless, the only thing i can say: try debugging AND reading patch notes. If it's an introduced bug = make a report

    – Sarief
    Nov 15 '18 at 10:31













    @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

    – Sarief
    Nov 15 '18 at 10:31





    @RC2793 if you do make a report, post a link as accepted answer here. You do need to debug in that case.

    – Sarief
    Nov 15 '18 at 10:31













    0














    Ok so after modifying my code a little bit wrt v4. Its working now. Thank you all for your support.



    JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
    QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
    List<Tuple> dataList = query
    .from(pgUserRoles)
    .select(pgUserRoles.roleId,
    pgUserRoles.roleName,
    pgUserRoles.roleType,
    pgUserRoles.status)
    .where(isRoleName(userRolesDTO.getRoleName()),
    isRoleType(userRolesDTO.getRoleType()),
    isStatus(userRolesDTO.getStatus()),
    isStatusNotEq()
    )
    .offset(offset)
    .limit(limit)
    .orderBy(orderByRoleIdDesc())
    .fetch();





    share|improve this answer





























      0














      Ok so after modifying my code a little bit wrt v4. Its working now. Thank you all for your support.



      JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
      QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
      List<Tuple> dataList = query
      .from(pgUserRoles)
      .select(pgUserRoles.roleId,
      pgUserRoles.roleName,
      pgUserRoles.roleType,
      pgUserRoles.status)
      .where(isRoleName(userRolesDTO.getRoleName()),
      isRoleType(userRolesDTO.getRoleType()),
      isStatus(userRolesDTO.getStatus()),
      isStatusNotEq()
      )
      .offset(offset)
      .limit(limit)
      .orderBy(orderByRoleIdDesc())
      .fetch();





      share|improve this answer



























        0












        0








        0







        Ok so after modifying my code a little bit wrt v4. Its working now. Thank you all for your support.



        JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
        QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
        List<Tuple> dataList = query
        .from(pgUserRoles)
        .select(pgUserRoles.roleId,
        pgUserRoles.roleName,
        pgUserRoles.roleType,
        pgUserRoles.status)
        .where(isRoleName(userRolesDTO.getRoleName()),
        isRoleType(userRolesDTO.getRoleType()),
        isStatus(userRolesDTO.getStatus()),
        isStatusNotEq()
        )
        .offset(offset)
        .limit(limit)
        .orderBy(orderByRoleIdDesc())
        .fetch();





        share|improve this answer















        Ok so after modifying my code a little bit wrt v4. Its working now. Thank you all for your support.



        JPAQuery<Tuple> query = new JPAQuery<Tuple>(entityManager);
        QPGUserRoles pgUserRoles = QPGUserRoles.pGUserRoles;
        List<Tuple> dataList = query
        .from(pgUserRoles)
        .select(pgUserRoles.roleId,
        pgUserRoles.roleName,
        pgUserRoles.roleType,
        pgUserRoles.status)
        .where(isRoleName(userRolesDTO.getRoleName()),
        isRoleType(userRolesDTO.getRoleType()),
        isStatus(userRolesDTO.getStatus()),
        isStatusNotEq()
        )
        .offset(offset)
        .limit(limit)
        .orderBy(orderByRoleIdDesc())
        .fetch();






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 15 '18 at 13:17

























        answered Nov 15 '18 at 11:59









        RC2793RC2793

        233




        233



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53316806%2fclasscastexception-for-com-querydsl-core-tuple%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

            Syphilis

            Darth Vader #20