Thoughts on minor re-org of source tree
by David M. Lloyd
I'd like to propose that the source tree be reorganized as follows:
1. Create a new module called "subsystems" with its own parent POM.
2. Move all subsystems and their support modules into this directory.
This will make modules easier to find and also will let us apply policy
to subsystems, which may come in handy, and also lets us rebuild just
subsystems, which may also come in handy.
I bring it up on the list because of the potential conflicts introduced,
so people can sync up and be ready if we go ahead with it.
--
- DML
15 years
JBoss AS 7.0.0.Beta1 tagged...
by David M. Lloyd
I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for
Beta2 development. Later this week Jason will be setting the release
"code name" and uploading the binary artifacts to be made available for
downloading and taking care of all that business.
Big thanks to everyone who put in extra effort to get this tag done. I
expect that the official release announcement will be happening later
this week.
--
- DML
15 years
Distribution of testing modules
by David M. Lloyd
In our current modules distribution for AS7 we currently are distributing:
- JUnit
- HTMLUnit
- JSFUnit
- Arquillian SureFire
- the AS7 Arquillian subsystem
- ShrinkWrap
- Various glue and support modules for the above
- Probably more test-oriented stuff I missed in my glance-over
The question is:
1. Do we really want to be distributing these test frameworks?
2. If so, should we put them in their own area somehow?
3. Also if so, should be recommend, as a policy, how and when these
modules should be used by end users?
4. If not, how can we exclude them from the final build?
--
- DML
15 years
Account for OSGi bundles in DeploymentUnitProcessors
by Thomas Diesler
Folks,
an OSGi bundle deployment is fundamentally different from an EE
deployment and must be handled by the OSGi subsystem. DUPs that are not
targeted for OSGi bundle deployments must ignore these. Currently the
recommended approach to ignore an OSGi deployment in a DUP is
DeploymentUnit deploymentUnit = phaseContext.getDeploymentUnit();
if(deploymentUnit.hasAttachment(Attachments.OSGI_MANIFEST)) {
return;
}
If you work on some other type of marker attachment, make sure that this
marker is not attached for an OSGi deployment. For the above check to
work, the OSGi manifest processor must come early in the chain. I
changed the order of structure processors to
// STRUCTURE
public static final int STRUCTURE_MOUNT
= 0x0000;
public static final int STRUCTURE_MANIFEST
= 0x0100;
public static final int STRUCTURE_OSGI_MANIFEST
= 0x0200;
public static final int STRUCTURE_RAR
= 0x0300;
...
This relates to a bug related to WAB (Webapp Bundle) deployments
https://issues.jboss.org/browse/JBAS-8940
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years
Re: [jboss-as7-dev] [JBoss AS7 Development] - Beta1 MUST HAVE List
by Ales Justin
Hey,
not a bad idea, and I would gladly do it.
I'm already hacking on Modules for some other project, so I'm quite familiar with them.
I'll try to implement something for Beta1,
to ease user experience with the new modularized cl layer.
It will probably be similar to what I did for MC deps, a simple .war app,
and I'll check with HeikoB what can/should be done to integrate it with the new console.
-Ales
On Mar 12, 2011, at 4:35 PM, Scott Marlow wrote:
> Hi Ales,
>
> You weren't on IRC chat in the AS7 room but I volunteered you to do a visualization tool for AS7 classloaders. :-) I was kidding of course, about volunteering you but thought I would mention the idea, in case you like it. The awesome visualization tool that you did for MC dependencies made me think of you for this idea. I'm not sure if it is even possible or wanted. But, how do our users figure out, what is going on in classloader land, with regard to what classes/jars are accessible to each module or deployment (maybe both?).
>
> Maybe this is a possible google summer of code idea?
>
> ;-)
>
> Scott
15 years
proposed cli changes
by Alexey Loubyansky
Max, Emanuel and I discussed the usability aspects of the cli today. We
agreed on the following:
1) drop the '/' prefix for the commands;
2) instead of '~' signifying the root node use '/';
3) instead of ',' as a node separator in the address (node path) use
'/'. so the format of an operation will look like
[node-type=node-name (/node-type=node-name)*] : operation-name
['('param=value (,param=value)*')']
This (2 and 3) will make the path look more linux-like, so hopefully
more friendly for an admin.
4) in the same spirit, the tab-completion for operations will start with
'./', e.g. './subsystem=web/connector=http:read-resource'
5) for the command names, Max likes
cn (change node) - current /prefix or /to.
cwn (current working node) - again current /prefix or /to w/o arguments.
I'd even go for cd to change the node. The reason I didn't add it
originally was 'directory' doesn't belong here. But cd is kind of habit
for this kind of thing, so I could add it as an alias.
Any objections or suggestions?
Thanks,
Alexey
15 years
Missing Java EE API classes in Arq (via JMX)
by Carlo de Wolf
At a glance it looks like the wrong class loader is used to deserialize
the exception.
Carlo
-------------------------------------------------------------------------------
Test set: org.jboss.as.test.embedded.demos.ejb3.StatefulBeanTestCase
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.25 sec
<<< FAILURE!
testSFSB(org.jboss.as.test.embedded.demos.ejb3.StatefulBeanTestCase)
Time elapsed: 0.03 sec <<< ERROR!
java.lang.ClassNotFoundException: javax.ejb.EJBException from [Module
"org.jboss.arquillian.protocol.jmx:main" from local module loader
@5b6df84b (roots:
/home/carlo/work/jboss-as/testsuite/smoke/target/modules,/home/carlo/work/jboss-as/testsuite/smoke/../../build/target/jboss-7.0.0.Alpha2/modules)]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:603)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1574)
at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731)
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at
org.jboss.arquillian.protocol.jmx.Utils.deserialize(Utils.java:78)
at
org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:108)
at
org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:50)
at
org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:40)
at
org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63)
at
org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115)
at
org.jboss.arquillian.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:160)
at
org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:247)
at
org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:210)
at
org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:228)
at
org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:300)
at
org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:224)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at
org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:166)
at
org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:189)
at
org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:300)
at
org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:185)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:128)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:339)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1011)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.modules.Module.run(Module.java:261)
at org.jboss.modules.Main.main(Main.java:236)
15 years
