The solution is the same for all optional code.
These should be plugins rather than integrated directly into
the core infrastructure.
On Wed, 2006-06-28 at 04:35 -0500, Heiko Braun wrote:
The latest XB version introduced a dependency towards JAF and Java Mail.
Currently these jars reside under
development list
Subject: Re: [JBoss-dev] JBossXB dependencies
The solution is the same for all optional code.
These should be plugins rather than integrated directly into
the core infrastructure.
On Wed, 2006-06-28 at 04:35 -0500, Heiko Braun wrote:
The latest XB version introduced a dependency
Heiko, you can assign this one to me.
Adrian Brock wrote:
The solution is the same for all optional code.
These should be plugins rather than integrated directly into
the core infrastructure.
On Wed, 2006-06-28 at 04:35 -0500, Heiko Braun wrote:
The latest XB version introduced a
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Thursday, June 29, 2006 1:40 PM
To: JBoss.org development list
Subject: Re: [JBoss-dev] JBossXB dependencies
The solution is the same for all optional code.
These should
The latest XB version introduced a dependency towards JAF and Java Mail.
Currently these jars reside under JBOSS/server/config/lib and are
not visible to the XB classloader. Moving them to JBOSS/lib doesn't
work, because the bootstrap process uses a hard coded set of libraries.
The current
