Yeah I know ;) , in the future I'll make sure to keep better control of my jars.
Mikael On 09/12/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > On 12/9/05, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > > > >From: Mikael Andersson <[EMAIL PROTECTED]> > > > Hi, > > > I discovered the problem, I had not specified the ContextLoader > listener > > for Spring. > > > I thought that I didn't have to have that enabled! > > > > > > When adding the following to my web.xml everything works: > > > > > > contextConfigLocation > > > /WEB-INF/applicationContext*.xml > > > > > > > > > > > > org.springframework.web.context.ContextLoaderListener > > > > > > > > > > > > Does anyone know if the Spring stuff is required by Shale, or have I > > > introduced this dependency some way (I had the shale-spring.jar in the > > lib > > > folder). > > > > > > > The shale-spring.jar contains a faces-config.xml within the META-INF of > > the archive. > > JSF autoloads all of these resources if the archive is included in the > > classpath. > > In the case of the shale-spring.jar, the custom variable resolvers are > > loaded. > > > > It's strange that the exception didn't point to the > > DelegatingVariableResolver or > > WeApplicationContexVariableResolver. Good to know.... > > > > If you include shale-spring.jar in your application, then you *are* > declaring that you are depending on Spring :-). That being said, the > error > message should definitely point you directly at the root cause, instead of > leading you down a wild goose chase. I'll see what can be done about > that. > > > > Cheers, Mikael > > > > > > > Gary > > > > Craig > >
