Ok... but isn't James telling the container which blocks to configure? Doesn't james exist somewhere in the stack trace? (I can't actually find that out because the stack trace is so long it gets truncated with "..... 23 more....."

Kenny

Stephen McConnell wrote:

The problem you are seeing is generated by the container you are using. I.e. it isn't a James issue.

Stephen.


Kenny Smith wrote:


Hi all,

I'm trying to get a new installation of 2.2-dev working and I'm running into this error:

org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component named "fetchmail" failed to pass through the Configuration stage. (Reason: org.apache.avalon.framework.configuration.ConfigurationException: Block named "fetchmail" implements Configurable, but has no corresponding in config.xml).

I've run into this error before when I removed my nntp block and james refused to start. I think it would be better if james simply ignored those missing blocks. If I don't want to use fetchmail or nntp, why do I need to have them in my config? In the 2.2 version I pulled from CVS, the default config has an entity reference to fetchmailConfig which should point to ../apps/james/conf/james-fetchmail.xml, but that file wasn't included with the distribution.

So, I can't comment it out and I don't know what it's supposed to look like, so I'm stuck. Can anyone help?

Thanks,
Kenny


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to