Skip to main content
Tridion

Return to Question

Tweeted twitter.com/#!/StackTridion/status/545690012847976449
added 15 characters in body
Source Link
Para Jaco
Para Jaco
  • 685
  • 3
  • 8

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about:

  1. using Spring WebApplicationInitializera(from servlet 3.0) ServletContainerInitializer to load thoseonly register the XPM filters only when some env-property is set/true
  2. Subclassing the XPM filters and only apply orig logic if some prop set/true

Other ideas?

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about:

  1. using Spring WebApplicationInitializer to load those XPM filters only when some env-property is set/true
  2. Subclassing the XPM filters and only apply orig logic if some prop set/true

Other ideas?

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about:

  1. using a(from servlet 3.0) ServletContainerInitializer to only register the XPM filters when some env-property is set/true
  2. Subclassing the XPM filters and only apply orig logic if some prop set/true

Other ideas?

added 65 characters in body
Source Link
Para Jaco
Para Jaco
  • 685
  • 3
  • 8

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about using WebApplicationInitializer of Spring to load those XPM filters only when some env-property is set/true, but maybe there is other/better ways:

  1. using Spring WebApplicationInitializer to load those XPM filters only when some env-property is set/true
  2. Subclassing the XPM filters and only apply orig logic if some prop set/true

Other ideas?

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about using WebApplicationInitializer of Spring to load those XPM filters only when some env-property is set/true, but maybe there is other/better ways?

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about:

  1. using Spring WebApplicationInitializer to load those XPM filters only when some env-property is set/true
  2. Subclassing the XPM filters and only apply orig logic if some prop set/true

Other ideas?

Source Link
Para Jaco
Para Jaco
  • 685
  • 3
  • 8

Is there some server-side setting to disable experience manager?

We want to generate and deploy one WAR package for our website, using Experience Manager only on the production/staging environment. So we package all the necessary jars, have the XPM filters configured in web.xml and the correct cd_XXX_conf.xml on the classpath. Is there some central way to disable the XPM filters from kicking in so we can disable XPM on all other envs? I was thinking about using WebApplicationInitializer of Spring to load those XPM filters only when some env-property is set/true, but maybe there is other/better ways?