To the point of the Bootstrap API being used for configuration and deployment, Emanuel and I discussed a bunch in #jboss-dev: "#jboss-dev@Freenode" wrote : emuckenhuber: Still here? | ALR: yes | emuckenhuber: I remember why I didn't give Embedded its own API | Because I'd essentially be either duplicating the AS Bootstrap or leaking it. | emuckenhuber: End user needs to start/stop/config | ALR: with config you mean the ServerConfig thingy ? | emuckenhuber: Yep. | ALR: yes, but this is currently based on system properties and should be mostly handled by the domain model in future - so i'm not sure how much of configuration part we can reuse for AS6 | emuckenhuber: Ideally very little. | emuckenhuber: IMHO the sysprop approach is a way of circumventing a proper API | emuckenhuber: Another thing we can consider: Plug through with the current model as we have it, and revisit config for AS6. | emuckenhuber: Where we provide a hook into the unified domain model. | emuckenhuber: And bootstrap>PS becomes integrated. | Then we can draw a line. Bootstrap starts/stops a server. Configutation is some runtime model which is exposed by a real "Server". The Server *has* a bootstrap, *has* a PS domain config, *has* deployment hooks.... | And we piece together a full view via composition | ALR: we can also do that later if you prefer | ALR: it's just that i noticed that this will change in future | ALR, emuckenhuber: composition is important | emuckenhuber: I think so. Because we can still move forward with what we have in the current model. In the future I'll def want to make PS a first-class citizen here. | But a lot of those hooks aren't yet available. | And major version changes ie 5 to 6, I like to use as an opportunity to break down walls and build the cleanest thing we can rather than support components across major versions. | ALR: yes that was at least the plan, i just can tell that profileservice nor bootstrap will depend on each other so far | emuckenhuber: Cool, I'll make some notes of the discussion on the post So the conclusion there is that the Embedded API will remain an extension of the bootstrap and we'll revisit at 6. The approach there may be: Embedded Server delegates start/stop to Bootstrap, Deployment to TMPDPL, and configuration to PS. All composed together and behind locked SPIs. S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261299#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...