Hi,
Thanks for the quick response.
That's fair, and I did discover that this works. I was hoping for a more
global place to put the Resources.
The issue is that the apps are currently getting deployed using Warp and/or
ant. The Default Context is advantageous in this environment since any of
the new Contexts created on the fly inherit the Resources.
Is there a place to put these definitions so that a new application
deployed out of ant, for example, would be able to pick them up?
Am I missing an easy way to create the context with resources using ant?
-Christian
On Wed, 2 Jul 2003, Shapira, Yoav wrote:
> Subject: RE: loadOnStartup: Default Context Resources unavailable?
>
>
> Howdy,
>
> >Is there a better place to put the Resource/ResourceParams than in the
> >Default Context?
>
> In the <Context> element for your own context.
>
> Yoav Shapira
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
