obtaining context path in matcher

[Ross Woolf <rw...@cut.net>]

I have written a matcher that requires some config data that I supply in an external xml file.  At the moment I have the path to the config file hard coded into my matcher.

I would like to obtain the root path to James so that I can remove my hard coded path and obtain the path to James programmatically.  I tried implementing the interface Contextualizable but my matcher still did not obtain any context info, so I don't think that interface applies to matchers.

Can anyone tell me how I can pragmatically, obtain the root path of James?

Thanks

RE: obtaining context path in matcher

["Noel J. Bergman" <no...@devtech.com>]

> I have written a matcher that requires some config data
> that I supply in an external xml file.  At the moment I
> have the path to the config file hard coded into my matcher.

You could pass it as part of the condition string.

> I tried implementing the interface Contextualizable but my
> matcher still did not obtain any context info

Not going to happen.  :-)  We *are* talking about revising the Mailet API,
and adding improved configuration is something I'd like to see.

In the meantime, if you don't mind your code being Avalon dependent, see the
matchers and mailets for the CommandListserv, which "cheats" and allows more
advanced configuration options.

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org