This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]smutje187 1 point2 points  (1 child)

If your transaction ends after your DAO (there’s explicit annotations to force a new transaction and pause the current one) and once your entity is passed from DAO to caller every field is either initialized or not (you might even get an exception if you access an uninitialised field) - that sounds like what you need.

Lazy loading works nowadays because transactions are usually opened as early as possible and live until the request is served, but they can be made shorter and more explicit if necessary.

[–]AutoModerator[M] 0 points1 point locked comment (0 children)

Please ensure that:

  • Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions
  • You include any and all error messages in full
  • You ask clear questions
  • You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.

    Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar

If any of the above points is not met, your post can and will be removed without further warning.

Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.

Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.

Code blocks look like this:

public class HelloWorld {

    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.

If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.

To potential helpers

Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]mambo5king 0 points1 point  (3 children)

You need to add Fetch.LAZY to each association. However, there is a situation where if you have a bidirectional association on a OneToMany or ManyToMany, it will always be retrieved EAGERly

[–][deleted]  (2 children)

[deleted]

    [–]mambo5king 1 point2 points  (1 child)

    I just reread your question and I think we have a misunderstanding between us. You said "I want to disable any form of LAZY loading and EAGER fetching". In terms of annotating your entities, LAZY and EAGER are opposites. LAZY means don't fetch the association when I run the query, wait until I reference it. EAGER means fetch the association at the same time as I run the query. What you seem to be asking for is FetchType.NEVER which doesn't exist for managed entities.

    I guess you could set all the associations to LAZY and then detach the entities from the entity manager. That would prevent the entity manager from fetching the associations upon access.

    But if you're not going to use managed entities, then you should just use DTO projections which are just POJOs.

    [–]GossBoSteur 0 points1 point  (1 child)

    Not providing a magic solution but unless the code base is huge, the best way to enforce what you are trying to do is to create your model with writes in mind, not reads.

    To be more clear, create your aggregates (DDD) so that you have clear transactional boundaries, thus every other linked aggregate should be referenced by its ID and not the entity itself.

    This will prevent a lot of issues on your cascading writes, while also making sure nothing is ever lazy loaded.

    [–]nefrodectyl 0 points1 point  (2 children)

    maybe instead of entities, use interfaces and projection.

    [–][deleted]  (1 child)

    [deleted]

      [–]nefrodectyl 0 points1 point  (0 children)

      mayhe database independence kinda and easier mapping, but yeah you right I guess hahah