Re: "Detached entity passed to persist"

Surprisingly, this (re-attaching a detached entity) is not a simple problem. First of all, you need to be very careful about holding onto entities in your session. It's too easy with JPA/Hibernate to accidentally keep the whole query resultset in memory when you think you are holding onto a single

"Detached entity passed to persist"

Hi team, I suspect you'll be able to answer this right off the top of your head, as this error occurs in response to what I imagine is a very routine code assignment: set a newly created user's company to be the same company as that of the user doing the creating. Code snippet from

Re: Authorisation in Tapestry Applications

Hi Kalle, Thank you for explaining what Tynamo Model has to offer. It certainly looks interesting, and promises to save much time in creating CRUD heavy apps in Tapestry. I'll give it a go on my next webapp. For now, I think I'll simply inspect the user's permissions in the onActivate() method

Re: Grid component customization

On Tue, Nov 28, 2017 at 6:33 AM, Erich Gormann wrote: > Dear all, > Hi! > I wanted to customize the GridColumns component, which is embedded inside > the Grid component, by trying different approaches. > > Finally I failed, because it was neither possible by a request

RE: Contribute requirejs.config.paths to ModuleManager

I tried to fight it too, but had to capitulate. After some debugging my @Contribute(JavaScriptStackSource.class) was not set: public class ModuleManagerImpl implements ModuleManager { private Resource resolveModuleNameToResource(String moduleName) { Resource resource =

Grid component customization

Dear all, I wanted to customize the GridColumns component, which is embedded inside the Grid component, by trying different approaches. Finally I failed, because it was neither possible by a request filter replacing the GridColumns component at runtime with my customized one, nor did it