JBoss Web Stand-alone

[wolfc]

In similar vain to JBoss Web Profile we're going to create a JBoss Web Stand-alone.

Whereas Web Profile is a top-down approach, we'll create Web Stand-alone as a bottom-up, by taking the latest Bootstrap and define a dedicated web bootstrap on top of it.
The big difference will then be that it'll not the Profile Service will not be running and thus not be managing a web profile.

The code stemming from this effort should be a stand-alone integration implementation of Tomcat and VDF usable in AS, Embedded and other runtimes based on Bootstrap.

First we need to uniquely name this component and find a place in subversion (/ Jira).
I don't think it should be under http://anonsvn.jboss.org/repos/jbossweb, because that would exceed the mandate of that repo.
It should also not be put under Reloaded, because it's going to be the actual integration implementation and not a definition.
I would rather see it as a new project in the jbossas repo, which only leaves the name question.

Second I want the build structure in the same way as MC (one version for all components). Although the versioning scheme of EJB3 (version per component) has the advantage of more maturity of the components, it's a hassle to keep track of.

[emuckenhuber]

Hmm, so you want to use bootstrap to start JBossWeb and boot VDF on top of JBossWeb?

[wolfc]

No, I want Bootstrap to boot up the JBossWeb deployers. Maybe we'll boot up the VDF with the exclusion of the Profile Service, but first we go for raw speed.

[wolfc]

I'll name the project 'spider' and I'll start by putting down the build structure.

[wolfc]

The build structure for deployers is up. Although the unit test doesn't pass yet, it does deploy a virtual war.

I scratched the original idea of going completely from the ground up, because the current integration code which resides in AS is pretty large and contains lots of features. So I now consume these artifacts in spider and build up a standalone bootstrap. It still uses bootstrap-impl-mc which leads to some wicked integration issues (with JMXKernel), so I'll switch to bootstrap-impl-as instead.

The next step will be to fork the existing code into Spider. After that the untangling of AS dependencies must happen which probably also entails the removal of service bean usage.

[sebastian.otaegui]

Can you post the link to the repo?

[wolfc]

Spider can be found here: http://anonsvn.jboss.org/repos/jbossas/projects/spider/trunk/.