[jboss-dev] [Fwd: [jboss-dev-forums] [Design of POJO Server] - Re: Getting rid of conf/jboss-service.xml]

[Dimitris Andreadis]

There was a problem with the minimal config not booting. To fix that:

1) I've removed the jndi service from the jboss-minimal.xml and copied the 
deploy/naming-jboss-beans.xml instead.

2) God rid of the conf/xmdesc/Naming* descriptors, as I think those are not used now, but 
re-instanted the Log4jService-xmbean.xml one

3) Used the same bootstrap.xml that we have in 'default' that brings in the bindinds.xml, 
too, due to the bindind service used by naming-jboss-beans.xml

4) Added minimal/lib/jboss-bindingservice.jar

The question is if we want to keep the binding service in the minimal config, or use a 
simplified version of the deploy/naming-jboss-beans.xml with a subset of the beans:

LookupPool
LocalNamingBean
RemoteNamingBean
JndiViewBean
NamingService

The more general question is if we want to alter the minimal config in some manner:

https://jira.jboss.org/jira/browse/JBAS-6103

Scott Stark wrote:
> This is all working and I have committed the changes. Note that I made a 
> https://svn.jboss.org/repos/jbossas/branches/JBAS-4814/ branch as 
> revision 79561 in case this needs to be rolled back for GA so the 
> changes can be moved into that branch. Now that its committed I'll do 
> some more testing on another box to make sure all of the changes are in.
> 
> Scott Stark wrote:
>> The smoke-tests are clean, but there are a few naming test failures I 
>> should fix as well to validate the naming-jboss-beans.xml changes 
>> before committing.
>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development