On Fri, Dec 17, 2021 at 10:48 AM Oliver Kaiser <oliver.kai...@eddyson.de> wrote:
> On 12/14/2021 10:40 PM, Dimitris Zenios wrote: > > Hi all it seems there is a raise condition when realizing lazy loaded > > services. > Indeed it is. > if you want to do the same try marking your "service A" as eager load. > I was going to suggest that, but Oliver was faster than me. :D Marking the other service with eager load would most probably solve the problem too. Unless one of these services isn't always actually called during the app's lifetime *and* it has a heavy resources usages, I don't see the downside of this solution except a little slower startup. > @Thiago: in case you are reading this; I may not check this mailing list every day but I do read everything here. :) > w.r.t. Java 17 (ASM update); do > you have a tool / mechanism to do that; or manually copy into "plastic" > + adjust package name? anything else that needs to be done? > No tool other than the IDE's refactor support. I check out the ASM latest release tag, refactor the packages so they align with the names used in Tapestry (Plastic, to be more precise), copy them to the Tapestry sources, and I just change the visibility of a single method there so it can be used by Plastic and there's also some other place I need to remove an enum's value so it doesn't use ASM experimental features, something that causes an error. > maybe i'll give that a try; no promises :-) > :) I did upgrade the Tapestry's embedded ASM version to the latest released one, 9.2, last week. Thanks for the offer! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
