On Fri, 20 Dec 2002 12:49, Adam Murdoch wrote:
> > partially intentional. The fact that <policy> can refer to things outside
> > the .sar file is purely a historical artefact. It should not be able to
> > but it can atm so we leave it as is.
>
> Ok. Is this worth adding to the docs as a suggestion?
yep.
> Let me just clarify:
>
> - When deploying from sar, <policy> and <classloader> should only refer to
> contents of sar (but due to backwards compat, <policy> has to be able to
> refer to anything).
> - When deploying from xml, <policy> and <classloader> can refer to
> anything.
yep.
> A fantastic idea. Sounds like heaps more fun than writing up
> environment.xml docs :)
:)
> Sure, but it's certainly not context-free to the user.
> It's a phoenix config file. Phoenix provides a fixed set
> of predefineds.
atm - not in the future.
> All the classloader stuff is in a single XML
> element with a handful of entries - the user doesn't need any more info
> than where the bad name is, and what the set of available predefineds are.
> Tell them that in the error message.
that was in the original design/implementation which we moved away from.
--
Cheers,
Peter Donald
-----------------------------------------------------
When a stupid man is doing something he's ashamed of,
he always declares that it is his duty.
George Bernard Shaw
-----------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
