Hi,

I figured that above validation were applied on quartz objects because they
were used as argument in one of the public method of a domain service.

public JobDetail createJobDetail(String name, String group, JobDataMap
jobDataMap) {

After making this method private it started working fine. Any more
clarification/detail on above behavior is much appreciated.

Cheers,
Jayesh

On Sun, Oct 8, 2017 at 2:21 PM, Jayesh Prajapati <[email protected]>
wrote:

> Hi,
>
> I am using v1.15.0 along with quartz addon. While starting below errors
> are reported.
>
> ################################################ ISIS METAMODEL
> VALIDATION ERRORS ##############################
> ##################################
>
> org.quartz.JobDataMap#clearDirtyFlag: has prefix clear, is probably
> intended as a supporting method for a property, collection or action.  If
> the method is intended to be an action, then rename and use
> @ActionLayout(named="...") or ignore completely using @Programmatic
> org.quartz.utils.DirtyFlagMap#clearDirtyFlag: has prefix clear, is
> probably intended as a supporting method for a property, collection or
> action.  If the method is intended to be an action, then rename and use
> @ActionLayout(named="...") or ignore completely using @Programmatic
> org.quartz.utils.StringKeyDirtyFlagMap#clearDirtyFlag: has prefix clear,
> is probably intended as a supporting method for a property, collection or
> action.  If the method is intended to be an action, then rename and use
> @ActionLayout(named="...") or ignore completely using @Programmatic
>
> Please inspect the above messages and correct your domain model.
>
> ################################################ ISIS METAMODEL
> VALIDATION ERRORS ##############################
> ##################################
>
>
> These classes are part of Quartz library and hence I cannot attach
> Programmatic annotation.
>
> Question is why metamodel validations are applied on classes under
> org.quartz package?
>
> Any way to skip this validation will help greatly. As of now this is
> blocking access to Wicket UI. As a workaround I am initializing quartz on
> click of an action/button.
>
> Thanks,
> Jayesh
>

Reply via email to