Regarding the mechanism of QueryBean

[PassXml]

Regarding the mechanism of QueryBean: QueryBean is generated at compile time, and then the _xxx() method is injected into the class. In practice, using xxx.eq(abc) is equivalent to _xxx().eq(abc). Is this
understanding correct?

We are currently using PF4J as the plugin execution framework. When I perform business queries in a sub-plugin, it throws an NPE — the xxx field in the QueryBean becomes null.

However, the same QueryBean works fine in the main process.

[rbygrave]

Is this understanding correct?

Yes. It is "simulating properties". It is doing that because we want to have a visual difference between "properties" and expressions like gt(), lt(), startsWith() etc which are all methods.

PF4J as the plugin execution framework.

Yeah, I don't know anything about PF4J - but I'd suggest that code isn't getting enhanced hence the NPE.

[PassXml]

Is this understanding correct?

Yes. It is "simulating properties". It is doing that because we want to have a visual difference between "properties" and expressions like gt(), lt(), startsWith() etc which are all methods.

PF4J as the plugin execution framework.

Yeah, I don't know anything about PF4J - but I'd suggest that code isn't getting enhanced hence the NPE.

Yes, I also suspect it hasn’t been enhanced, but in my plugin’s business module I’m using compileOnly (the query bean
project), so the classes should be using the host’s classes. They should have been enhanced. My understanding is that
once the compilation is done, the classes should remain permanently enhanced.

So I debugged for a long time and still couldn’t figure it out. I can successfully invoke _xxx() directly via
reflection.