-
1. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
jaikiran Jan 15, 2010 1:09 AM (in response to alrubinger)ALRubinger wrote:
The current API allows you to point to one entry "bootstrapUrl" which in turn references other relative URLs (which, in the MC case, are "urn:jboss:bean-deployer:2.0" descriptors).
....We should no longer accept "bootstrapHome" and "bootstrapUrl" parameters, but instead allow the user to pass in a Set of bootstraps
If i understand this right, instead of passing the URL/home of the file containing the relative URLs, the API would now expect a Set of URLs which point to the individual xmls which form the bootstrap? For example a set of URLs pointing to classloader.xml (which sets up classloading), vdf.xml (which sets up deployer framework).
-
2. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
alrubinger Jan 15, 2010 9:30 AM (in response to jaikiran)jaikiran wrote:
If i understand this right, instead of passing the URL/home of the file containing the relative URLs, the API would now expect a Set of URLs which point to the individual xmls which form the bootstrap? For example a set of URLs pointing to classloader.xml (which sets up classloading), vdf.xml (which sets up deployer framework).More like a Set of Bootstrap types, which can come in from a File, URL, ClassLoader resource, String, anything etc. At the end of the chain this just goes into a KernelDeployer, so anything that can be represented as a bunch of bytes with a name works.
S,
ALR
-
3. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
brian.stansberry Jan 15, 2010 11:47 AM (in response to alrubinger)You mention ordering being important (which it is) so should this be a List not a Set? -
4. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
alrubinger Jan 15, 2010 11:51 AM (in response to brian.stansberry)bstansberry@jboss.com wrote:
Yes, Carlo called me on it earlier. java.util.List.
I mention "Set" only in the context of "don't deploy the same component twice". The API won't support notion of equality for components defined in a bootstrap though, so that responsibility lies with the caller.
S,
ALR
-
5. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
alrubinger Jan 17, 2010 6:16 PM (in response to alrubinger)https://jira.jboss.org/jira/browse/JBBOOT-118
Do we want AS upgraded in time for M2? I don't see any pressing reason why this would be required now.
S,
ALR
-
6. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
alrubinger Jan 18, 2010 12:12 AM (in response to alrubinger)I have Reloaded now packaging fine-grained "Bootstrap Descriptor" XML bits, and exposing the contracted names via an interface "VdfBootstrapDescriptorNames". Consuming projects can assemble the runtime like:
// Create a server final MCServer mcServer = MCServerFactory.createServer(); // Add the required bootstrap descriptors final List<BootstrapDescriptor> descriptors = mcServer.getConfiguration().getBootstrapDescriptors(); descriptors.add(new ClassLoaderResourceBootstrapDescriptor(VdfBootstrapDescriptorNames.RESOURCE_NAME_VDF)); descriptors .add(new ClassLoaderResourceBootstrapDescriptor(VdfBootstrapDescriptorNames.RESOURCE_NAME_CLASSLOADING)); mcServer.start(); // VDF / MainDeployer will now be available
S,
ALR
-
7. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
brian.stansberry Jan 18, 2010 10:44 AM (in response to alrubinger)ALRubinger wrote:
No, unless 1) someone can provide a really really strong reason for it and 2) it can be done this week including fixing the bizarro testsuite regressions that pop up whenever anything gets changed.
-
8. Re: RELOADED-10: Consuming fine-grained bootstrap definitions
alrubinger Jan 21, 2010 4:27 PM (in response to alrubinger)Just a note that I've made things a bit more friendly:
final List<BootstrapDescriptor> descriptors = mcServer.getConfiguration().getBootstrapDescriptors(); descriptors.add(ReloadedDescriptors.getClassLoadingDescriptor()); descriptors.add(ReloadedDescriptors.getVdfDescriptor());
S,
ALR