For starters, I think these might be suitable candidates for the move to webapps:
src: /cas-server-core/src/main/java/org/jasig/cas/web/DelegateController.java /cas-server-core/src/main/java/org/jasig/cas/web/bind/CredentialsBinder.ja va /cas-server-core/src/main/java/org/jasig/cas/web/flow/AbstractNonInteracti veCredentialsAction.java /cas-server-core/src/main/java/org/jasig/cas/web/flow/AuthenticationViaFor mAction.java /cas-server-core/src/main/java/org/jasig/cas/web/init/SafeContextLoaderLis tener.java /cas-server-core/src/main/java/org/jasig/cas/web/init/SafeDispatcherServle t.java /cas-server-core/src/main/java/org/jasig/cas/web/support/AbstractSingleSig nOutEnabledArgumentExtractor.java /cas-server-core/src/main/java/org/jasig/cas/web/support/ArgumentExtractor .java /cas-server-core/src/main/java/org/jasig/cas/web/support/CasArgumentExtrac tor.java /cas-server-core/src/main/java/org/jasig/cas/web/support/WebUtils.java /cas-server-core/src/main/java/org/jasig/cas/web/view/AbstractCasView.java test /cas-server-core/src/test/java/org/jasig/cas/web/flow/AuthenticationViaFor mActionTests.java /cas-server-core/src/test/java/org/jasig/cas/web/init/SafeContextLoaderLis tenerTests.java /cas-server-core/src/test/java/org/jasig/cas/web/init/SafeDispatcherServle tTests.java Spring webmvc and a few other related deps may also be up for a removal. -Misagh > -----Original Message----- > From: Marvin Addison [mailto:marvin.addi...@gmail.com] > Sent: Tuesday, February 19, 2013 7:45 AM > To: cas-dev@lists.jasig.org > Subject: Re: [cas-dev] Moving web components from core to webapp > > > I like the idea and I don't want to pretend I already did the work, > but I've moved a lot of classes from core to the server and management > webapps when I extracted the services management from the CAS server. > > I was thinking of this point. The existing split-brain state of Web > components, some in core, some in webapp, is troublesome. I'm > wholeheartedly in favor of putting them exclusively in one module or > another. It's a headache for us and likely other deployers having them > split fairly arbitrarily between two modules at present. > > Unless we can make an argument for another kind of webapp that needs > Web components that is _not_ an overlay, then I would argue it's safe > to complete the migration of classes in the org.jasig.cas.web package > (and possibly others) into cas-server-webapp. I'd like to see a > complete listing of "Web" components that would be affected by this > move. The package I mentioned seems obvious, but it may be more nuanced > than that. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@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
