Ales Justin [http://community.jboss.org/people/alesj] created the discussion "Re: Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/563878#563878 -------------------------------------------------------------- -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563878#563878] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] created the discussion "Re: Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/563972#563972 -------------------------------------------------------------- Indeed. In that case, an alternative is adding the libs at the exact moment setLibArchivesProvider is invoked. We could initialize the DefaultClasspath inside that method, that would need another name now, or we could initialize it staticaly again. Either way, this matter of initializing it statically or inside create is personal. I just think that it would be nice to get rid of the synchronized block and to get rid of the "if defaultClasspath is null", given that everytime ClasspathFactory is invoked, we will end up needing DefaultClasspath anyway. I think that the proper way is to initialize the parent container , i.e, DefaultClasspath, prior to initializing all the rest, including its contents, i.e., Archive/ArchiveInfo structure. Isn't it done this way with default domain initialization vs class loader initializations? The Archive/ArchiveInfo structure is written in a way that assumes that the container (Classpath) to which an Archive will be added is already created or, if not, will be created transparently, mirroring the ClassLoader structure. This saves whoever is the Archive client the trouble of having to worry about Classpaths. Transparently as well, the ArchiveInfo/Archive/Classpath structure reaccomodates itself to mirror BDAs created and BDAs not created.I wrote it this way because I was following the natural order of deployment, and I wanted to keep the deployers as simple as possible. So, in order to create BDAs for the libs, the best way IMO is to initialize DefaultClasspath without any contents,  and rename LibraryDiscoveryService.getLibraries method to discoverServices, loadServices, or something like that. You won't need any return value for that method because, at the moment it creates ArchiveInfo, the corresponding Classpath structure is initialized, and the structure is updated when you create an Archive out of it and extract the BDAs. Meaning that DefaultClasspath will automaticaly add the created Archives to itself. BTW DefaultClasspath does not ref itself, as the classpaths mirror the domain structure. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563972#563972] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]