> That's why some classes shared by both webapps are in the core Lending further credence to the cas-server-web-support .jar-producing module idea, allowing moving those shared classes out of core while still allowing them to be shared unduplicated between the webapps?
On Wed, Feb 20, 2013 at 3:16 AM, jleleu <lel...@gmail.com> wrote: > Hi, > > It seems desirable to put all classes in the same module. But you must not > forget that there are now two webapps : the CAS server itself and the > services management webapp. That's why some classes shared by both webapps > are in the core : SafeContextLoaderListener.java for example. > > I tried to extract as many as possible classes from the core to the > webapps. I remembered having some surprising issues with modules using this > or that class. > > That said, there are certainly remaining classes to move. > > Best regards, > Jérôme > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > ape...@unicon.net > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
