[jboss-dev] JBoss-AS-5.0.x-TestSuite-sun15

[Dimitris Andreadis]

That would be best because the two files are (and will get more and more) out-of-sync.

Scott M Stark wrote:
> Yes, would need to switch the config around again. We had talked about 
> breaking the bootstrap-beans.xml up to make it easier to change features 
> without updating the bootstrap file.
> 
> I'm just getting back online as I had to relocate due to power outage 
> after yet another storm.
> 
> Dimitris Andreadis wrote:
>> I switched the profileservice configuration in the testsuite, that 
>> uses bootstrap-repo-beans.xml to use the new VFS classloader and it 
>> now boots normally.
>>
>> That could mean however that we'll have problems switching back to the 
>> old unified classloader, if needed?
>>
>> Dimitris Andreadis wrote:
>>> In that latest run, the profile service config didn't start properly.
>>>
>>> I guess it's because of WarClassLoaderDeployer changes not synched 
>>> with the testsuite?
>>>
>>>
>>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/351/artifact/trunk/build/output/jboss-5.0.0.Beta4/server/profileservice/log/ 
>>>
>>>
>>> 2008-02-01 08:44:07,356 ERROR 
>>> [org.jboss.system.server.profileservice.ProfileServiceBootstrap] 
>>> Failed to load profile: Summary of incomplete deployments (SEE 
>>> PREVIOUS ERRORS FOR DETAILS):
>>>
>>> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required 
>>> State:Actual State}
>>>
>>> WarClassLoaderDeployer
>>>  -> ClassLoading{Configured:** NOT FOUND **}
>>>  -> ClassLoaderSystem{Configured:** NOT FOUND **}
>>>
>>>
>>> *** CONTEXTS IN ERROR: Name -> Error
>>>
>>> ClassLoaderSystem -> ** NOT FOUND **
>>>
>>> ClassLoading -> ** NOT FOUND **
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>