On 03/02/2011, at 3:04 PM, Scott Battaglia wrote: > > > Whether to use Maven with YOUR application is your decision. We can't force > Maven or filtering on your applications that are clients of CAS. That said, > the Jasig CAS Client for Java supports the following: > > 1. Hardcoded values in web.xml > 2. JNDI lookup > 3. Spring Dependency Injection > > One of those should be able to support your needs. The last two separate the > configuration from the generated WAR. >
I'm not sure I follow. CAS uses Maven to build. I stated that we are modifying the CAS build to add filtering. Without filtering, you cannot reuse the same source on multiple environments. Adding build filtering allows this. I was specifically talking about the CAS server, not the client. The original poster was talking about both a local app and the CAS server itself. In both cases, Maven can be used to provide build time filtering and enable reuse of code on different servers. So I suggested that this be added to the CAS server by default, since it is useful functionality. cheers, Steve > > > > On 02/02/2011, at 10:31 PM, Kristian Rink wrote: > > > Folks; > > > > so far stumbling into running CAS in our environment, I am stuck with a > > scenario like this: I do have a Java web application (war package) > > including a web.xml having all the CAS related filters declared and > > configured so things work fine. However, right now I end up with > > configuration like this... > > > > [...] > > <filter> > > <filter-name>CAS_Authentication_Filter</filter-name> > > > > <filter-class>org.jasig.cas.client.authentication.AuthenticationFilter</filter-class> > > <init-param> > > <param-name>casServerLoginUrl</param-name> > > > > <param-value>http://localhost:8080/auth/login</param-value> > > </init-param> > > <init-param> > > <param-name>serverName</param-name> > > <param-value>http://localhost:8080/</param-value> > > </init-param> > > </filter> > > [...] > > > > ... which is not that nice. The CAS application, generally, is a .war > > file built using the maven overlay approach and supposed to run in the > > same servlet container the business application (so far) is running in, > > and, for testing purposes, I would like to have the CAS and business > > app run on my local machine (thus "localhost") and, for production > > environment, I want to be able to deploy the whole configuration > > (without changing web.xml) to the server. Trying something like > > > > [...] > > <filter> > > <filter-name>CAS_Authentication_Filter</filter-name> > > > > <filter-class>org.jasig.cas.client.authentication.AuthenticationFilter</filter-class> > > <init-param> > > <param-name>casServerLoginUrl</param-name> > > <param-value>/auth/login</param-value> > > </init-param> > > <init-param> > > <param-name>serverName</param-name> > > <param-value>/</param-value> > > </init-param> > > </filter> > > [...] > > > > however failed, and, looking at what happened, it didn't take me twice > > seeing why. However: Is there a good way of achieving what I would like > > to do (i.o.w. not hard-coding the serverName in web.xml), or should I > > use some kind of maven magic and profiles in order to deploy my > > application right? Comments? > > > > TIA and all the best, > > Kristian > > > > -- > > You are currently subscribed to [email protected] as: > > [email protected] > > To unsubscribe, change settings or access archives, see > > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
