Building CAS

[Scott Battaglia]

We probably need to do a better job of documenting when something changes in
the deployerConfigContext.xml.  For the most part it doesn't change between
releases, but when Spring Security changes their package name, it does :-)

If you can think of a good spot, let me know.

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia


On Fri, Oct 10, 2008 at 12:22 PM, Matthew Jones <
matthew.jones at interactivedata.com> wrote:

> Hi David,
>
>  You're having the "CAS-that-I-built-deployment-problem" :-)  That's
>> why I still recommend you put the logging, the UI, the LDAP, etc.
>> aside.  Use your newly installed Maven 2.0.9 and build the CAS
>> download overall.  It automatically pulls the authenticator and builds
>> a CAS.war for you.  When that deploys, add the logging.  Do it again.
>> If you're successful, modify the UI for your CAS.war.  Deploy.  Test.
>>
>
> All those done and all work
> Next I modified the pom.xml file and it still works and the sping LDAP jars
> are pulled in and appear in the libs folder.
> Next, I edited deployerContextConfig.xml first just adding
> AuthenticatedLdapContextSource without enabling it as the authentication
> handler and then enabling it.
>
> On each occasion, I stopped Tomcat (after un-deploying) and cleared the log
> files so I could see that there were no errors. So I ended up producing the
> correctly configured & working .war file.
>
> When I was differencing my deployer config with one from one of my the
> previous installs, I finally saw the difference in the file (which I have
> just seen that Scott diagnosed, thanks Scott). I had obviously managed to
> pull a 3.2.1 config file into my 3.3 tree. (I think I know why that happened
> too, someone switched off my 3.3 test server!)
>
>  I'm purposely not trying to tell you what the error is.  I want you to
>> understand how to find the reason why your Spring bean won't
>> instantiate.  And, when your Spring bean doesn't instantiate, your
>> application that you built doesn't work.  I'll look over these files
>> and reply if I see something obvious.  I understand your pain there,
>> but if you start simple and add you'll be able to ask the list why
>> "this" configuration for this bean "classA" doesn't instantiate.
>>
>> Simplify your CAS.war and deploy that successfully.  You're building it.
>>
>
> I'm not sure I am that much the wiser but I got to deploy my war file loads
> of times and it does now work.
>
>
> Thanks
>
> --
> Matthew Jones
> Interactive Data Managed Solutions Ltd
> -----------------------------------------------------------------------
> Registered in England Company Number 3691868
> Registered Office: Fitzroy House, 13-17 Epworth Street, London, EC2A 4DL
> Tel: +44 (0)1242 694133 | Fax: +44 (0)1242 694109
> matthew.jones at interactivedata.com
> http://www.interactivedata-ms.com/694133
>
> This message (including any files transmitted with it) may contain
> confidential and/or proprietary information, is the property of Interactive
> Data Corporation and/or its subsidiaries, and is directed only to the
> addressee(s). If you are not the designated recipient or have reason to
> believe you received this message in error, please delete this message from
> your system and notify the sender immediately. An unintended recipient's
> disclosure, copying, distribution, or use of this message or any attachments
> is prohibited and may be unlawful.
> Interactive Data (Europe) Ltd Registered No. 949387 England Registered
> Office: Fitzroy House 13-17 Epworth Street. London. EC2A 4DL
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20081010/01b3e50a/attachment.html