I've committed new jboss-embedded projects:
http://anonsvn.jboss.org/repos/jbossas/projects/embedded/trunk/
This is defined by:
https://jira.jboss.org/jira/browse/EMB-17
Included in this initial setup is a prototype of JBoss Embedded AS distribution which packages up AS and a few Embedded-specific classes into a single JAR, and successfully starts the AS Bootstrap.
Some points:
* Tangential to this is refactoring of the bootstrap project as defined by JBBOOT-4, where the common server locations (JBOSS_HOME, deploy, lib, etc) must be represented by VFS instead of java.io.File. This is required to get a server contained within a JAR.
* Embedded should really have no common server locations - it's got all of its binaries on the classpath and should be able to boot straight from there.
* I had to introduce a NoOpClassLoadingFactory to ignore any roots defined by classloading elements within the AS bootstrap. Due to the repackaging, these roots are not (and shouldn't be) found in the form they're listed. This furthers the notion that Embedded runs within a host ClassLoader.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190807#4190807
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190807
"scott.stark(a)jboss.org" wrote : I cleaned up the deployment code in the test layer to properly cleanup the failed test as this was causing every other test to fail due to the previous incomplete deployment.
|
| We either need
| - a fix from messaging, not likely as the code is ready to go out the door
| - exclude this property
|
Okay thanks for cleaning up the deployment code, i thought i already did the the undeployment
so that it does not cause any further regressions - that was not the intention.
Well basically the problem with this attribute was after persisting and restarting AS, as the default attributes are also persisted.
Maybe we should have a way to exclude attributes or just persist the changed ones.
But i guess this depends on the MO<->xml marshalling/unmarshalling first.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190777#4190777
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190777
"scott.stark(a)jboss.org" wrote : Without a jboss-structure.xml excluding a jar from the meta-inf bucket, you can't. We can't both treat WEB-INF/lib as a source for deployment descriptors and know when not to do so without some user input.
|
I was thinking more about it yesterday
and you're absolutely right.
What eventually triggered my check, was when I was getting unexpected web-beans.xml -- > WBMD.
But it was only unexpected since I missed some detail. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190775#4190775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190775