How to unpack the cas war (5.3.x) with Jetty

[Kartik Mehta]

Hi,

I am using embedded Jetty with CAS 5.3.X and I start the cas war (created using overlay) using java -jar. The war s not unpacked to the temp directory. I have tried setting java.io.tmpdir to a suitable value, and have also tried configuring JettyEmbeddedServletContainerFactory by calling setTempDir on the WebAppContext extracted out of  JettyEmbeddedServletContainerFactory.

Does any one know how to make CAS unpack the war file to the temp directory with embedded Jetty ?

regards,

Kartik

[Misagh Moayyed]

Does any one know how to make CAS unpack the war file to the temp directory with embedded Jetty ?

That is not how "embedded" works. An "embedded" container is not a repackaged version of the server distribution stuffed into the CAS web application artifact.  You won't find a "real jetty" if you unpacked CAS. Embedded container only means that you are getting a server that is able to run the CAS webapp automatically without extra manual/download work, regardless of how and to what effect. 

If you want to actually use a real jetty instance, download it first, remove the embedded jetty from the CAS webapp build and deploy the now-made-vanialla/plain webapp there as you normally would with any other webapp. With embedded, you lose control at the expense of auto-configuration, automation and comfort. If you prefer manual work for deployments, embedded is not the right option for you.