[JBoss-dev] Re: Library dependencies/updates for jboss-4.0.5.GA

[Adrian Brock]

org.dom4j.Element element = ...
XMBean mbean = new XMBean(object, element, version);
server.registerMBean(mbean);

Won't work if it is org.jboss.dom4j.Element

On Tue, 2006-09-19 at 07:16 -0700, Scott M Stark wrote:
> What api are you talking about being broken? The dom4j uses will be 
> supported by deploying dom4j in the server lib. Neither the deployment 
> or console module uses need to be changed because these are not in the 
> server bootstrap classpath. Its a fair question as to whether jarjar is 
> worthwhile vs converting the few uses to use the bundled jdk apis.
> 
> Adrian Brock wrote:
> > The only reason JBossMX uses dom4j is for the XMBean.
> >
> > If you switch to the jarjared version then this api
> > is broken for existing users.
> >
> > If you are going to change the api to remove the dependency, 
> > I'd rather see it changed to org.w3c.dom.*
> >
> > On Tue, 2006-09-19 at 08:43 -0500, Dimitris Andreadis wrote:
> >   
> >>  With a quick search I've found org.dom4j usage in the
> >>
> >> A) jmx module (DescriptorSupport, JBossXMBean10, XMLMetadata, XMBean)
> >> B) deployment module (DeploymentMetadata, DeploymentManagerImpl)
> >> C) console module (XMLToHTMLTreeBuilder)
> >>
> >> D) build (VersionRelease) - not realy an issue
> >>
> >> Should I switch all to use org.jboss.dom4j and bundle with
> >> jboss-jmx.jar?
> >>
> >> Or
> >>
> >> Switch the jmx module, bundle with jboss-jmx.jar and, include the
> >> original dom4j.jar in server/lib for the others (including end-user code
> >> that depends on dom4j).
> >>
> >> But then, our jarjar'ed version would have to be in a different place in
> >> the repository (can't have 2 versions of the same thing), like
> >> repository.jboss.com/jboss/dom4j/1.6.1.jarjar
> >>
> >>     
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx