New AS Module: "depchain"
by Andrew Lee Rubinger
https://jira.jboss.org/jira/browse/JBAS-7894
This week we've introduced a new module into AS, "depchain". As the
name infers, this is a single POM dependency which consumers of the
Application Server may use to import the full runtime ClassPath into
his/her Maven-based project.
The driving use case here is for users of the EmbeddedAS APIs; it's much
easier for them to write and execute tests using the full runtime
complement if they employ a ClassLoading structure where everything is
available via parent delegation up to the appCL. This means users are
free to link directly to the Kernel etc without worrying about what
other dependencies are required (and which are prohibited) at different
ClassLoading levels to avoid NoClassDefFoundError.
In AS proper/standalone we circumvent this issue with a very explicit
BOOT_LIBRARY set in Main, and a repackaged run.jar to boot. For most
users this constitutes a prohibitively difficult and involved setup.
The AS "build" module depends upon "depchain" to create the $JBOSS_HOME
assembly.
The Ant/Standalone corollary, a single JAR dependency, is pending:
https://jira.jboss.org/jira/browse/JBAS-7907
S,
ALR
--
Andrew Lee Rubinger
Sr. Software Engineer
JBoss by Red Hat
http://exitcondition.alrubinger.com
http://twitter.com/ALRubinger
14 years
key/value tx-db recommendations?
by Bill Burke
I'm looking for a small key/value pure Java transactional store that's
not GPL and thats distributed with LGPL based projects through maven or
whatever.
Anybody have any suggestions?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
14 years
Reminder Commit & Testing Policy
by Jason T. Greene
This is just a friendly reminder that all minor commits (changes
unlikely to affect others) need to be ran through smoke-tests before
committing.
Everything else needs to have a full testsuite run *before* committing.
This can be done by either running it locally on your box, or you can
commit to a private branch and create a temporary hudson job.
--
Jason T. Greene
JBoss, a division of Red Hat
14 years
Testsuite regression caused by JBossXB 2.0.2.BetaX
by John Bailey
I have been looking into some testsuite regressions related to the
JNDIBindingManager not correctly binding values, and I have traced the
issue back to recent updates (~last month) to the jbossxb JAR. When
running with one of the 2.0.2.BetaX versions (I tested X= 3|4|5|6), it
fails to correctly set the value on the JNDIBinding object. When
running in trace I can see the following messages that may point to an
issue:
2010-04-08 15:06:15,581 TRACE
[org.jboss.xb.binding.sunday.unmarshalling.XsdBinder] (RMI TCP
Connection(2)-192.168.1.102) Element
{urn:jboss:jndi-binding-service:1.0}value added to choice:
{urn:jboss:jndi-binding-service:1.0}value
2010-04-08 15:06:15,581 TRACE
[org.jboss.xb.binding.sunday.unmarshalling.XsdBinder] (RMI TCP
Connection(2)-192.168.1.102) element:
name={urn:jboss:jndi-binding-service:1.0}value, type=null,
repeatable=false, nillable=false, minOccurs=1, maxOccurs=1, owner type=null
2010-04-08 15:06:15,582 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102)
http://apache.org/xml/features/validation/dynamic set to: true
2010-04-08 15:06:15,582 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Created parser:
org.apache.xerces.jaxp.SAXParserImpl@51d9b4aa, isNamespaceAware: true,
isValidating: true, isXIncludeAware: true
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Enter startElement
http://www.w3.org/2001/XMLSchema:annotation
2010-04-08 15:06:15,583 TRACE [org.jboss.xb.binding.ObjectModelBuilder]
(RMI TCP Connection(2)-192.168.1.102) accepted
http://www.w3.org/2001/XMLSchema:xs:annotation
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Exit startElement
http://www.w3.org/2001/XMLSchema:annotation
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Enter startElement
http://www.w3.org/2001/XMLSchema:appinfo
2010-04-08 15:06:15,583 TRACE [org.jboss.xb.binding.ObjectModelBuilder]
(RMI TCP Connection(2)-192.168.1.102) accepted
http://www.w3.org/2001/XMLSchema:xs:appinfo
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Exit startElement
http://www.w3.org/2001/XMLSchema:appinfo
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Enter startElement
http://www.jboss.org/xml/ns/jbxb:skip
2010-04-08 15:06:15,583 TRACE [org.jboss.xb.binding.ObjectModelBuilder]
(RMI TCP Connection(2)-192.168.1.102) ignored
http://www.jboss.org/xml/ns/jbxb:jbxb:skip
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Exit startElement
http://www.jboss.org/xml/ns/jbxb:skip
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Enter endElement
http://www.jboss.org/xml/ns/jbxb:skip
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Exit endElement
http://www.jboss.org/xml/ns/jbxb:skip
2010-04-08 15:06:15,583 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Enter endElement
http://www.w3.org/2001/XMLSchema:appinfo
2010-04-08 15:06:15,584 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Exit endElement
http://www.w3.org/2001/XMLSchema:appinfo
2010-04-08 15:06:15,584 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Enter endElement
http://www.w3.org/2001/XMLSchema:annotation
2010-04-08 15:06:15,584 TRACE
[org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
Connection(2)-192.168.1.102) Exit endElement
http://www.w3.org/2001/XMLSchema:annotation
*2010-04-08 15:06:15,584 TRACE
[org.jboss.xb.binding.sunday.unmarshalling.XsdBinder] (RMI TCP
Connection(2)-192.168.1.102) element
name={urn:jboss:jndi-binding-service:1.0}value: will be skipped, it's
attributes, character content and children will be set on the parent*
I haven't had a chance to dig into what is happening, but I have
confirmed that falling the jbossxb version back to 2.0.1.GA eliminates
the issues.
Any ideas?
14 years
AS testsuite build broken
by Thomas Diesler
compile-annotated-classes-50:
[javac] Compiling 255 source files to
/home/tdiesler/svn/jbossas/trunk/testsuite/output/classes
BUILD FAILED
/home/tdiesler/svn/jbossas/trunk/testsuite/build.xml:718: Reference
org.jboss.aop:jboss-aop:jar:client not found.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
14 years
Maven Repository 2.0
by Paul Gier
Hi Everyone,
This is a reminder that the new Maven repository will be available April 12. We
will be disabling write access to the svn repository 20 UTC April 9. This means
that you will not be able to do any releases to the repository the weekend of
April 9.
I put together a small FAQ [1] with information about the new repository.
Please take a look if you have questions.
Also, if your project uses a groupId other than org.jboss, please take a look at
the JBoss groupId page [2] and make sure yours is included. Otherwise you will
not be able to deploy to the new repository.
[1]http://community.jboss.org/wiki/MavenRepository-FAQ
[2]http://community.jboss.org/wiki/MavenJBossGroupIds
14 years
M3 Regressions & Freeze
by Jason T. Greene
Hi Everyone,
The M3 release is currently blocking on various regressions
Currently we have 66 regressions in the testsuite:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test...
The problem areas appear to be security, naming, profile service,
messaging/mdb, ejb3, and web services.
Please take a look to see if any of them apply to your area. I will be
pinging various folks offline as well.
Thanks!
--
Jason T. Greene
JBoss, a division of Red Hat
14 years
AS trunk - WARN messages on shutdown
by Jaikiran Pai
I keep seeing these WARN messages on shutdown of the AS (and even on
undeploying applications):
16:26:16,671 WARN [ClassLoading] Exception unregistering module,
registry:
org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback@1762fc7,
cause: java.lang.IllegalStateException: Module
VFSDeploymentClassLoaderPolicyModule juddi-service.sar:0.0.0 is not
registered
16:26:16,672 WARN [ClassLoading] Exception unregistering module,
registry:
org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback@1762fc7,
cause: java.lang.IllegalStateException: Module
VFSDeploymentClassLoaderPolicyModule jsr88-service.xml:0.0.0 is not
registered
16:26:16,673 WARN [ClassLoading] Exception unregistering module,
registry:
org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback@1762fc7,
cause: java.lang.IllegalStateException: Module
VFSDeploymentClassLoaderPolicyModule jgroups-channelfactory.sar:0.0.0 is
not registered
I don't remember which change in AS trunk introduced these. Are those
messages expected? Does something needs to be fixed? If not, can they be
logged at a lower log level?
regards,
-Jaikiran
14 years
OSGi available in AS trunk
by Thomas Diesler
Folks,
as of today we have JBoss OSGi available as part of the default profile
in AS.
You can point your browser to http://localhost:8090/jboss-osgi after
startup.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
14 years
