geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Configuration start order
Date Wed, 30 Nov 2005 09:31:04 GMT

On Nov 29, 2005, at 7:52 PM, Jeff Genender wrote:

> I think it should go in the j2ee-server plan.  IMHO the security 
> should be available for all web apps, whether its used or not.  I 
> think it will be a PITA if every web app requires that import.

I strenuously object to foisting security onto every configuration 
whether or not it is wanted.  A more appropriate solution is to make 
the security builder into a real gbean and let it add to the parentId 
if it is called.  Please don't push us back into the miasma of a single 

I also hope you will correct the configId before you commit.

david jencks

> Dain Sundstrom wrote:
>> That was the problem.  I added the following to 
>> webconsole-jetty-plan.xml and webconsole-tomcat-plan.xml:
>>     <import>
>>       <uri>org/apache/geronimo/Security</uri>
>>     </import>
>> and the problem went away.  Is this something we want in the console 
>> plans or in the j2ee-server plan?
>> -dain
>> On Nov 29, 2005, at 7:29 PM, Dain Sundstrom wrote:
>>> I have been hacking on the configuration code, and I think I have 
>>> stumbled into an unrelated bug.
>>> The problem I'm having is caused by the 
>>> org/apache/geronimo/Console/Jetty configuration starting before the 
>>> org/apache/geronimo/Security configuration.  Which mean when the 
>>> console starts and attempts to initialize JACC is gets 
>>> "java.lang.ClassNotFoundException: Property 
>>> not set" 
>>> because the provider system property is set in the security 
>>> configuration.
>>> Should I make the security configuration a parent of the j2ee-server?
>>> -dain

View raw message