meant to send this to the list too.
-Scott
---------- Forwarded message ----------
From: Scott Battaglia <[EMAIL PROTECTED]>
Date: Sep 4, 2007 12:16 PM
Subject: Re: AW: Maintaing local customizations via Maven2
To: "Smith, Matt" <[EMAIL PROTECTED]>
I think if we move in the UserDetailsService we should be okay as the
CasAuthoritiesPopulator references that. We just need to make sure people
don't change the name of the UserDetailsService when they replace it.
The point of the ViewResolver with a JAR file would be for you to keep all
of your changes external to the project and include the JAR as a dependency.
Then you would just need to tell CAS that you are using the uconn theme and
its located in this jar. This was just a preliminary thought I had and I
haven't thought it through yet.
I'll add JIRA issues for some of the other stuff though. And maybe some
other people will have some opinions.
-Scott
On 9/4/07, Smith, Matt <[EMAIL PROTECTED]> wrote:
>
> Scott-
>
> Moving the casAuthoritiesPopulator definition into
> deployerConfigContext.xml is a definite win. Moving the inMemoryDaoImpl
> userMap definition may help, but since it shouldn't be used in
> production (JdbcDaoImpl or an eventual JndiDaoImpl should be used IMHO),
> it may not be worth it.
>
> I'm not familiar in the slightest with Spring WebFlow, so how would a
> ViewResolver determine which view is the right view, if multiple views
> are available? "default" and "simple" may still be included, depending
> on how the Maven dependencies are handled. I think a
> "viewName" ("basename") and "defaultThemeName" in cas.properties would
> be great.
>
> Other opinions?
> -Matt
>
>
> On Tue, 2007-09-04 at 10:38 -0400, Scott Battaglia wrote:
> > Matt,
> >
> > Would be a good first step be to move the changes in 1 and 3 to
> > deployerConfigContext.xml (or at least #3, and we could move the
> > themename to the cas.properties file).
> >
> > We should also look into a ViewsResolver that can maybe read views
> > from a JAR file so people can merely include the JAR file with the JSP
> > pages and the properties files.
> >
> > -Scott
> >
> >
> >
> > On 8/27/07, Smith, Matt <[EMAIL PROTECTED]> wrote:
> >
> > ...
> > > A second step could be to identify commonly changed items
> > in the XML
> > > files and isolate those changes to one file so that merging
> > becomes
> > > easier.
> > ...
> >
> >
> > Not sure how common my changes are, but:
> >
> > 1) I change cas-servlet.xml to reflect my "ThemeName" and
> > "basename".
> > 2) I change deployerConfigContext.xml to reflect my
> > authenticationHandler.
> > 3) I change securityContext.xml to remove "battags" from
> > "ROLE_ADMIN",
> > and eventually will be replacing the inMemoryDaoImpl with
> > something
> > better.
> > 4) I include my view pages in views/jsp/uconn
> > 5) I include my themes in themes/uconn
> > 6) I modify the log4j.properties in WEB-INF/classes
> > 7) I add a uconn.properties and a uconn_views.properties to
> > WEB-INF/classes.
> >
> > If the XML changes in 1-3 could be centralized, it would help.
> >
> > I'll post something (to the Wiki if appropriate) about
> > managing these
> > customizations as a Maven project, once I actually hammer out
> > the
> > details.
> >
> > HTH,
> > -Matt
> >
> > --
> > Matt Smith
> > [EMAIL PROTECTED]
> > University Information Technology Services (UITS)
> > University of Connecticut
> > PGP Public Key: http://web.uconn.edu/dotmatt/matt.asc
> >
> > _______________________________________________
> > Yale CAS mailing list
> > [email protected]
> > http://tp.its.yale.edu/mailman/listinfo/cas
> >
> >
> >
> >
> >
> > --
> > -Scott Battaglia
> >
> > LinkedIn: http://www.linkedin.com/in/scottbattaglia
> --
> Matt Smith
> [EMAIL PROTECTED]
> University Information Technology Services (UITS)
> University of Connecticut
> PGP Public Key: http://web.uconn.edu/dotmatt/matt.asc
>
>
--
-Scott Battaglia
LinkedIn: http://www.linkedin.com/in/scottbattaglia
--
-Scott Battaglia
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
