On 3/24/03 01:52 PM David Ekholm <[EMAIL PROTECTED]> wrote: > ... > > Put the service in a web module that you hook into more than one > application. Bind the two applications to two different URLs and then > access the service. If you get the same date string when accessing the > two services, then you have the same problem as we have (i.e. the static > variable is shared across applications)
Thanks, lets see what I can find. > Interresting note. Thank you for telling. Seems that EJB (and/or Orions > implementation of it) isn't well suited for what we are doing - running > several instances of the same application with different branding in the > web layer on the same machine. [OffTopic] We did it in two different projects, a 4 tiered application which supports branding and much more, including shared and exclusive data. One of the projects (which is already dead since the company we were working for went bankrupt) was running almost 120 different look and feels on top of one application instance. The key design strategies: Decouple logic and presentation. Make your stateful service layer client aware and use stateless services as much as possible. Allow customizable look & feels, there is a lot possible using css. We did not have the portlet api at that stage, but we pretty much used something equal to that.
