There's a note in the build file -- due to WO bug don't use tomcat 8 unless you replace WOJavaServletAdapter or whatever its called. Use tomcat 7.
On Fri, Mar 6, 2015, 9:09 AM John Huss <[email protected]> wrote: > Here's what I can do now: > > https://www.dropbox.com/s/bfgmzkrz6cyw1xe/buid.xml?dl=1 > > https://www.dropbox.com/s/56cojqgulc7sezj/Application.java?dl=1 > > > On Thu, Mar 5, 2015 at 2:49 PM Paul Hoadley <[email protected]> wrote: > >> Hi John, >> >> On 6 Mar 2015, at 2:01 am, John Huss <[email protected]> wrote: >> >> Are you doing any of this in practice? How do you handle session >> persistence? >> >> Yes, I have a very high traffic WO app deployed this way -- but it is >> purely web services and javascript, no components. It used EOF originally, >> but now uses Cayenne instead. >> >> I have another app which is a more traditional one with many pages >> deployed this way as well, but it is not really in use yet. It has passed >> testing and works well. >> >> I'm not doing session persistence. My web service/javascript app doesn't >> use sessions; the other app does. The elastic load balancer supports >> sticky sessions, so sessions are routed to the same instance. This isn't >> ideal for many reasons but it is the same thing you get with a traditional >> deployment, so it's not a point for or against anything. >> >> >> It's interesting to know that ELB-based sticky sessions works for WO. >> Without session persistence, though, isn't auto-scaling going to be a bit >> rough? If my session is stuck to an instance that auto-scaling is about to >> kill, my session is going to disappear, isn't it? Do you handle (or intend >> to handle) that in some way? Also, are the EC2 instances you're talking >> about here each running a single servlet app instance, or do you have some >> other setup for this? >> >> It's easy to get started with a WAR deployment - the only thing you have >> to do that isn't built-in is to put your web service resources in the >> WEB-INF/static folder and set the base url for them. The standard >> build.xml file should be changed to do this automatically, but no one >> maintains wolips anymore. >> >> >> Can you commit the change anyway? Interested parties (like me) could >> then just grab that file. >> >> Thanks for discussing what you're doing here, very interesting. >> >> >> -- >> Paul Hoadley >> http://logicsquad.net/ >> >> >>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
