[cosmo-dev] Re: Help with mvn package build failures

[Alan Lord]

Brian Moseley wrote:
> On Dec 10, 2007 3:49 AM, Alan Lord <alanslists at gmail.com> wrote:
> 
>> Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cosmoConfigPath' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Name cosmo is not bound in this Context
>> Caused by: javax.naming.NameNotFoundException: Name cosmo is not bound in this Context
> 
> this is the key info. the cosmo webapp expects three J2EE resources to
> be provided by the servlet container: the filesystem path to the
> cosmo.properties file, a JDBC DataSource for the Cosmo database, and a
> JavaMail Session for email notifications. it's croaking because it
> can't find these.

I kind of started to realise it was something a bit more when I looked 
into the server bundle tarball - there are quite a few jar files in the 
tomcat common/classes and lib heirarchy which I do not have, so I guess 
there's a bit to do to sort it all out...

> see snarf/src/main/config/server.xml for the Tomcat configuration that
> we use for snarf (the pre-configured Tomcat that is only officially
> supported deployment). you're actually breaking new ground by
> deploying the war into a container other than snarf, so there are a
> few hiccups to be expected. just be patient and we'll help you through
> it ;) we've been meaning to add some docs to the wiki for deploying
> the webapp into other containers, so maybe this is the excuse we need.
> any chance you could lend a hand?

I'd be more than happy to. I run a small consulting company 
(http://www.theopenlearningcentre.com) here in the UK which is focussed 
almost exclusively on Open Source so this is good stuff for me. If I can 
help you and get my head around tomcat/J2EE a bit more we'll both gain! 
I build Linux systems from scratch and know my way around pretty well. 
Get your thoughts together and let's work out a plan.

I guess what I'd envisage is some sort of config file one could edit 
before feeding to Maven (or is it Ant?) that would identify where 
everything needs to go and look for the missing pieces.

I'm going to be away for a day or two now but I'll be back around from 
Wednesday pm onwards.

> also of interest: somebody recently contributed a context.xml that
> we'll be integrating into the webapp to replace the snarf server.xml
> configuration. I'm hoping to get that committed in the next few days.

O.K. I'll be back in a couple of days.

Cheers

Al

-- 
The way out is open!
http://www.theopensourcerer.com