Is this going to include merging jboss.conf and jboss.jcml into one file (or
perhaps using a standard jboss.conf from a class resource for
boot-strapping) or will there still be two files?
--jason
On Wed, 9 May 2001, marc fleury wrote:
>
> |The setting of the security manager and server.policy file are
> |better done from
> |the command line as many security related events and debugging hooks are
> |done on startup of the vm. I don't think these should be set at all from
> |within the server. Setting the thread-local mode of the SecurityAssociation
> |could be moved to an mbean.
>
> either command line or xml file. whichever you feel is more "admin friendly"
> or both.
>
> I want to be done with the properties file asap.
>
> Let's simplify, the properties files is a big "ZIT" in our face and I want
> to squeeze it "splatch"
>
>
> aaaah feels good doesn't it?
>
> |If I comment out the call to DocumentBuilderFactory.newInstance() I am
> |still able to switch the xml parsers using the JAXP properties so
> |I don't see
> |that this call has any effect other than preloading the parser classes. The
> |xml parser settings could be moved to an MLet.
>
> ooookaay.... voodoo refactoring.... if I move this does it die? nope... ok
> then... :)
>
> we should configure the xml stuff in a mlet as well, although it should be
> one of the first ones (we do the mbean based on xml :)
>
> marc
>
> |
> |
> |
> |_______________________________________________
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
