Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <20030711191926.84764.qmail@web41004.mail.yahoo.com>
Date: Fri, 11 Jul 2003 12:19:26 -0700 (PDT)
From: Steven Cummings <stevenc79@yahoo.com>
Subject: [2.1m3] [Authentication-fw] AuthenticationManager not found
To: users@cocoon.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hello,

I've upgraded to milestone 3 and when I try to access my web application I'm
getting an error that a component could not be found (with key
"org.apache.cocoon.webapps.authentication.AuthenticationManager"). Surely
enough, it is not in cocoon.xconf. But then, it wasn't there previously either,
so how was it that one was automatically instantiated in 2.1m2. The
configuration was just an empty "authentication-manager" element (both tags, no
content). Is there a problem or do I now have to configure one on my own. 

I found
org.apache.cocoon.webapps.authentication.components.DefaultAuthenticationManager,
but I don't know what type of configuration it expects. I would hope that it's
just a default container for generic authenticated users so I can just continue
using the fw as before. But by just using it as a component-instance in
cocoon.xconf with the
org.apache.cocoon.webapps.authentication.AuthenticationManager role I get a
NullPointerException, so obviously it wants some kind of configuration.

Is anybody else using the auth-fw in 2.1m3 that knows about whether or not
there's a problem, I'm making a mistake, or there's an actual change? TIA.

/S

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org