Good catch - I will see if I can get it fixed for you.

On Wed, 27 Nov 2002 18:54, Vjeran Marcinko wrote:
> Hi again.
> I found root of my problems, and I'm pretty sure it's a bug in fortress'
> DefaultContainerManager... This manager uses
> 'org.apache.excalibur.source.impl.SourceResolverImpl' to locate
> system.xconf file. This component doesn't get proper lifecycling, since its
> parameterize() method isn't called before resolveURI() method. That's why
> variable 'm_urlSourceClass' isn't set, which is necessary if one doesn't
> use custom 'resource' protocol, but some usual URL (like file:// ..) ...
>
> -Vjeran
>
> ----- Original Message -----
> From: "Vjeran Marcinko" <[EMAIL PROTECTED]>
> To: "Avalon framework users" <[EMAIL PROTECTED]>
> Sent: Tuesday, November 26, 2002 9:43 PM
> Subject: Fortress and system.xconf source ...
>
> > Hi folks.
> > I have a problem with Fortress and system.xconf source path.
> > In examples I find ...
> > ContextBuilder cb = new ContextBuilder();
> > .....
> > cb.setContainerConfiguration("resource://com/mycomp/myapp/system.xconf");
> >
> > And it works correctly. Now I bundled my server app in .jar file for
> > deployment, and I want this system.xconf to be out of that jar. Meaning
> > that I want to load this system.xconf not like classpath resource
> > anymore, but as ordinary file out of bundle. I tried with let's say :
> > cb.setContainerConfiguration(file://C:/system.xconf);
> > And it doesn't work ! I tried every possible way of selecting this win
> > path ( \\ instead / for instance), and it doesn't work ...I guess that I
> > don't understand well how this org.apache.excalibur.source.* package
> > works, since I think it relies on that ...

-- 
Cheers,

Peter Donald
*-----------------------------------------------------*
| Never argue with an idiot, they'll drag you down to |
| their level, and beat you with experience           |
*-----------------------------------------------------* 


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

Reply via email to