rmcontrol | RM Control — A python app

The reason you're having this problem is because associations that your view requires should be initialized inside a transaction boundary to avoid the LazyInitializationException. Adding an option to load collections outside of a transaction is merely a bandaid and doesn't truly address the underlying design flaw of your code.

If your view requires that you load Profile and its associated collection of Advert entities, then your either your data access should should specifically toggle that behavior or the query specify that you need that collection initialized.

There are a number of ways you can trigger this collection to be loaded as part of a query.

• JPQL/HQL using a JOIN FETCH on the adverts collection.
• Specify a join fetch using the Criteria API
• Use @FetchProfile to toggle a specific fetch strategy by name.
• Use @NamedEntityGraph.