Write an isAuthor method? about acs-aem-commons

[davidjgonzalez]

I think just a isAuthor(..) method would be overkill since we have slingSettingsService.getRunModes().contains("author")

If it was part of a broader Util full of handy tolls for out-of-HTTPRequest context, then it would be a different story.

(If im in the context of a HTTP Request I (almost) always want to use WCMMode rather than runmodes.)

[justinedelson]

I could see this being useful if it was a static. That requires jumping through some hoops to get this value set in a static context. Probably an immediate component which sets the values on startup. Runmodes can't be changed at runtime, so this is OK to do once.

If so, I'd like to see

isAuthor()
isPublish()
isRunmode(String)

[kaushalmall]

@davidjgonzalez I thought WCMMode was never a good way to differentiate between being on author or publish. IIRC @justinedelson is a proponent of this.

@justinedelson are you talking about creating a OSGi component that sets the values on startup? I would love to do this, but, might (read will) need direction to get me started.

[davidjgonzalez]

@kaushalmall WCMModes don't differentiate between author and publish instances; but can differentiate between intended publish and author behaviors. Within HTTP Request scoped-behaviors (Components/Servlets/etc.) the idea of the author/publish runmode is (normally) just an abstraction around WCMMode types.

Creating hard in-code deps on Author or Publish make it more difficult to experience the behavior on Author as it would on Publish.

Runmodes typically play a role in changing backend behaviors (WF, Listeners, Jobs, etc.) that need to behave differently based on the tier.

Of course, as with anything there are exceptions.

IIRC @jayk is a proponent of WCMModes :P