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
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.
>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
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
or
On 08/12/05, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>
> Well, I'm not sure what to make of this one. The RI doesn't throw and
> exception when a managed bean is not found, just returns a null object.
>
> // Retrieve an existing instance, or one created and configured by
> // the
Well, I'm not sure what to make of this one. The RI doesn't throw and
exception when a managed bean is not found, just returns a null object.
// Retrieve an existing instance, or one created and configured by
// the managed bean facility
ValueBinding vb =
cont
Gary VanMatre comcast.net> writes:
[snippet]
>
> Make sure that you don't have any expression like #{ managed-bean-name}
bound to
> a control. If you are using the " managed-bean-name" symbol, make sure
it's registered
> in the faces-config.xml.
>
> If you have a more specific exception,
>From: Mikael Andersson <[EMAIL PROTECTED]>
> Gary VanMatre comcast.net> writes:
>
> [snippet]
> > > >
> > > > When running this without a managed bean called 'test' in
> faces-config.xml, I
> > > > get the following error:
> > > > ERROR
> > >(org.apache.catalina.core.ContainerBase.[Catali
Gary VanMatre comcast.net> writes:
[snippet]
> > >
> > > When running this without a managed bean called 'test' in
faces-config.xml, I
> > > get the following error:
> > > ERROR
> >(org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/estoolweb].
> > > [Faces
> > > Servlet]) - Se
>From: Ryan Wynn <[EMAIL PROTECTED]>
> On 12/8/05, Mikael Andersson wrote:
> > Hi,
> > testing some clay templating ( base code from some very helpful posts in
> > this
> > forum),
> > and it seems like I must have a managed bean associated to every view.
> > Is this correct?
> >
> > When
Ryan Wynn gmail.com> writes:
> Mikael,
>
> I think you could get it down to 1 managed-bean by doing this
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> And declaring layoutBe
On 12/8/05, Mikael Andersson <[EMAIL PROTECTED]> wrote:
> Hi,
> testing some clay templating ( base code from some very helpful posts in this
> forum),
> and it seems like I must have a managed bean associated to every view.
> Is this correct?
>
> When running the code below without a managed bean
Hi,
testing some clay templating ( base code from some very helpful posts in this
forum),
and it seems like I must have a managed bean associated to every view.
Is this correct?
When running the code below without a managed bean I get an error, but if I
declare one for it it works fine.
The code
13 matches
Mail list logo
