I've managed to reduce my dependencies to the following:
<dependencies>
<dependency>
<groupId>org.jasig.cas</groupId>
<artifactId>cas-server-webapp</artifactId>
<version>${cas.version}</version>
<type>war</type>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>c3p0</groupId>
<artifactId>c3p0</artifactId>
<version>0.9.1.2</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>${hibernate.core.version}</version>
</dependency>
At this point, I get the error from before. If I remove any of these
dependencies, I get different errors that indicate I am missing one of the
above.
On Fri, Aug 15, 2014 at 1:05 PM, Jeff Chapin <jeff.cha...@uni.edu> wrote:
> I'm all for paring it down if that will help. I may have misunderstood,
> but most of those made it in because they were required for the features we
> are using -- I may have been overzealous adding them in, though.
>
> I added the recommended dependency, and see no large change in behavior.
>
> I believe that I followed that document -- I applied the changes from
> the CAS 3.3.5 to CAS 3.4 section, and CAS 3.4.x to CAS 3.4.10 did not seem
> to apply.
>
> I have attached my deployerConfigContext.xml.
>
> Thanks for your help!
>
>
> On Fri, Aug 15, 2014 at 12:09 PM, Al Krinker <al.krin...@gmail.com> wrote:
>
>> There is a lot of stuff in that pom indeed... I almost want to try to
>> remove part of it to just get it to deploy properly and then add
>> dependencies one by one to see when it would break. Before we do that, can
>> you add commons-dbcp. You might play with version a little bit...
>>
>> <!-- For the connection pool to the db -->
>>
>> <dependency>
>> <groupId>commons-dbcp</groupId>
>> <artifactId>commons-dbcp</artifactId>
>> <version>1.4</version>
>> <scope>runtime</scope>
>> </dependency>
>>
>>
>> Also, have you followed this document:
>> https://wiki.jasig.org/display/CASUM/Upgrading. You would need to change
>> few things around in deploymentConfigContext, etc. Maybe you are using old
>> bean names. Could you also provide us with a copy of your
>> deployerConfigContext.xml?
>>
>>
>> On Fri, Aug 15, 2014 at 11:03 AM, Jeff Chapin <jeff.cha...@uni.edu>
>> wrote:
>>
>>> Sure thing. Since it's a bit long, I put it in a pastebin here:
>>> http://pastebin.com/KgYD79aN
>>>
>>> Thanks for looking!
>>>
>>>
>>> Jeff
>>>
>>>
>>> On Fri, Aug 15, 2014 at 9:55 AM, Al Krinker <al.krin...@gmail.com>
>>> wrote:
>>>
>>>> Seems like spring version/jar conflict. Could you post your pom.xml
>>>> file?
>>>>
>>>>
>>>> On Friday, August 15, 2014, Jeff Chapin <jeff.cha...@uni.edu> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> I am working on getting CAS 3.5.2 configured and compiled. We
>>>>> previously had a working 3.3.5 install, and I used the existing
>>>>> documentation as a starting point, and adapted it to address the changes
>>>>> between the two versions. I can successfully build with Maven, with no
>>>>> issues.
>>>>>
>>>>> When I deploy this to Tomcat, I am seeing the following error in the
>>>>> logs. It looks like I might have a version issue in the dependencies, but
>>>>> I
>>>>> am unclear how to get this resolved.
>>>>>
>>>>> 2014-08-06 13:26:57,987 ERROR
>>>>> [org.springframework.web.context.ContextLoader] - <Context initialization
>>>>> failed>
>>>>> org.springframework.beans.factory.BeanCreationException: Error
>>>>> creating bean with name 'servicesManager' defined in ServletContext
>>>>> resource [/WEB-INF/spring-configuration/applicationContext.xml]: Cannot
>>>>> resolve reference to bean 'serviceRegistryDao' while setting constructor
>>>>> argument; nested exception is
>>>>> org.springframework.beans.factory.BeanCreationException: Error creating
>>>>> bean with name 'serviceRegistryDao' defined in ServletContext resource
>>>>> [/WEB-INF/deployerConfigContext.xml]: Cannot resolve reference to bean
>>>>> 'entityManagerFactory' while setting bean property 'entityManagerFactory';
>>>>> nested exception is
>>>>> org.springframework.beans.factory.BeanCreationException: Error creating
>>>>> bean with name 'entityManagerFactory' defined in ServletContext resource
>>>>> [/WEB-INF/deployerConfigContext.xml]: Invocation of init method failed;
>>>>> nested exception is java.lang.IncompatibleClassChangeError: Implementing
>>>>> class
>>>>>
>>>>> Thanks for any help,
>>>>> Jeff
>>>>> --
>>>>>
>>>>> Jeff Chapin,
>>>>> Assistant Systems/Applications Administrator
>>>>> ITS-IS, University of Northern Iowa
>>>>> Phone: 319-273-3162 Email: jeff.cha...@uni.edu
>>>>>
>>>>> --
>>>>> You are currently subscribed to cas-user@lists.jasig.org as:
>>>>> al.krin...@gmail.com
>>>>> To unsubscribe, change settings or access archives, see
>>>>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>>>>
>>>>> --
>>>> You are currently subscribed to cas-user@lists.jasig.org as:
>>>> jeff.cha...@uni.edu
>>>>
>>>>
>>>> To unsubscribe, change settings or access archives, see
>>>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Jeff Chapin,
>>> Assistant Systems/Applications Administrator
>>> ITS-IS, University of Northern Iowa
>>> Phone: 319-273-3162 Email: jeff.cha...@uni.edu
>>>
>>> --
>>> You are currently subscribed to cas-user@lists.jasig.org as:
>>> al.krin...@gmail.com
>>> To unsubscribe, change settings or access archives, see
>>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>>
>>>
>> --
>> You are currently subscribed to cas-user@lists.jasig.org as:
>> jeff.cha...@uni.edu
>> To unsubscribe, change settings or access archives, see
>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>
>>
>
>
> --
>
> Jeff Chapin,
> Assistant Systems/Applications Administrator
> ITS-IS, University of Northern Iowa
> Phone: 319-273-3162 Email: jeff.cha...@uni.edu
>
>
--
Jeff Chapin,
Assistant Systems/Applications Administrator
ITS-IS, University of Northern Iowa
Phone: 319-273-3162 Email: jeff.cha...@uni.edu
--
You are currently subscribed to cas-user@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-user
