Ruel kept telling that the third party version issue has been fixed.

When in doubt with third party library errors, nuke the third party folder and do a clean build.

---

From: jboss-development-bounces@lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Kabir Khan
Sent: Thursday, September 21, 2006 12:50 PM
To: 'JBoss.org development list'
Subject: RE: [JBoss-dev] DocumentException "missing" in Branch_4_0

A clean checkout works for me

---

From: jboss-development-bounces@lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark
Sent: 21 September 2006 18:44
To: JBoss.org development list
Subject: Re: [JBoss-dev] DocumentException "missing" in Branch_4_0

That is what I am using:
[starksm@succubus build]$ grep common build-thirdparty.xml
      <componentref name="jboss/common" version="snapshot-Branch_1_0"/>

I removed all contents from thirdparty. Is there a new jboss-common.jar in the repository or was there an update of an existing one?

Dimitris Andreadis wrote:

I've already handled this, you need to update your thirdparty libs
(common, snapshot-Branch_1_0)
 
 

-----Original Message-----
From: jboss-development-bounces@lists.jboss.org 
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf 
Of Scott M Stark
Sent: Thursday, September 21, 2006 8:31 PM
To: JBoss.org development list
Subject: Re: [JBoss-dev] DocumentException "missing" in Branch_4_0
 
The problem is that there are dom4j dependencies in 
jboss-common.jar (org.jboss.util.state.xml.StateMachineParser 
for one), and these will need to be removed to avoid leaking 
this dependency into the bootstrap classpath.
 
Kabir Khan wrote:
 

When starting up jboss in Branch_4_0 I get a load of these errors
 
2006-09-21 17:27:17,406 WARN  [org.jboss.system.ServiceController] 
Problem starting service 
jboss.web.deployment:id=-1758252921,war=invoker.war
java.lang.NoClassDefFoundError: org/dom4j/DocumentException
  at
 
 

org.jboss.security.jacc.JBossPolicyConfigurationFactory.<init>(JBossPo
 

licyCo
nfigurationFactory.java:57)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
  at
 
 

sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructo
 

rAcces
sorImpl.java:39)
  at
 
 

sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCo
 

nstruc
torAccessorImpl.java:27)
  at 
 

java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 

  at java.lang.Class.newInstance0(Class.java:308)
  at java.lang.Class.newInstance(Class.java:261)
  at
 
 

javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationF
 

actory
(PolicyConfigurationFactory.java:91)
  at
 
 

org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:351)
 

  at org.jboss.web.WebModule.startModule(WebModule.java:83)
  at org.jboss.web.WebModule.startService(WebModule.java:61)
  at
 
 

org.jboss.system.ServiceMBeanSupport.jbossInternalStart(Servic
eMBeanSupport.
 

java:289)
  at
 
 

org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBe
 

anSupp
ort.java:245)
  at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
  at
 
 

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
 

orImpl
.java:25)
 
But server/all/lib/dom4j.jar contains 
 

org.dom4j.DocumentException. Any 
 

ideas?