Return-Path: 
 <users-return-9691-apmail-cxf-users-archive=cxf.apache.org@cxf.apache.org>
Delivered-To: apmail-cxf-users-archive@www.apache.org
Received: (qmail 77307 invoked from network); 29 Jul 2008 14:49:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 29 Jul 2008 14:49:44 -0000
Received: (qmail 5180 invoked by uid 500); 29 Jul 2008 14:49:41 -0000
Delivered-To: apmail-cxf-users-archive@cxf.apache.org
Received: (qmail 5141 invoked by uid 500); 29 Jul 2008 14:49:41 -0000
Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@cxf.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@cxf.apache.org>
List-Post: <mailto:users@cxf.apache.org>
List-Id: <users.cxf.apache.org>
Reply-To: users@cxf.apache.org
Delivered-To: mailing list users@cxf.apache.org
Received: (qmail 5130 invoked by uid 99); 29 Jul 2008 14:49:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jul 2008 07:49:41 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [213.162.65.2] (HELO mail2.t-mobile.at) (213.162.65.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jul 2008 14:48:43 +0000
Received: from mailint1.t-mobile.at ([172.26.77.6])
	by mail2.t-mobile.at (mail2.t-mobile.at [172.26.76.66])
	(MDaemon PRO v9.6.4)
	with ESMTP id md50015049070.msg
	for <users@cxf.apache.org>; Tue, 29 Jul 2008 16:49:11 +0200
X-Spam-Processed: mail2.t-mobile.at, Tue, 29 Jul 2008 16:49:11 +0200
	(not processed: message from trusted or authenticated source)
X-MDRemoteIP: 172.26.77.6
X-Return-Path: jan.minaroviech@external.t-mobile.at
X-Envelope-From: jan.minaroviech@external.t-mobile.at
X-MDaemon-Deliver-To: users@cxf.apache.org
Received: from wien31.t-mobile.at ([195.5.66.31])
	by mailint1.t-mobile.at (mailint1.t-mobile.at [10.248.129.16])
	(MDaemon PRO v9.6.4)
	with ESMTP id md50018609573.msg
	for <users@cxf.apache.org>; Tue, 29 Jul 2008 16:49:04 +0200
X-Spam-Processed: mailint1.t-mobile.at, Tue, 29 Jul 2008 16:49:04 +0200
	(not processed: spam filter heuristic analysis disabled)
In-Reply-To: 
 <2B674CE447106D46A53D0FDDC7DF8B1C025B8F24@PTXSMSXM01.emea.ime.reuters.com>
To: users@cxf.apache.org
Cc: Maxime Orain <Maxime.Orain@thomsonreuters.com>,
	users@cxf.apache.org
Subject: Antwort: RE: Antwort: RE: Antwort: RE: Antwort: Pb with configuration
 with
 CXF    and various    Spring [Virus checked]
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
From: jan.minaroviech@external.t-mobile.at
Message-ID: 
 <OFF8917A36.A0652B2E-ONC1257495.005130CA-C1257495.0051656A@t-mobile.at>
X-Priority: 3 (Normal)
Date: Tue, 29 Jul 2008 16:49:03 +0200
X-MIMETrack: Serialize by Router on Wien31/T-Mobile/AT(Release 6.5.5|November
 30, 2005) at
 29.07.2008 16:49:02,
	Serialize complete at 29.07.2008 16:49:02
Content-Type: multipart/alternative;
 boundary="=_alternative 00516568C1257495_="
X-MDAV-Processed: mailint1.t-mobile.at, Tue, 29 Jul 2008 16:49:05 +0200
X-MDAV-Processed: mail2.t-mobile.at, Tue, 29 Jul 2008 16:49:12 +0200
X-Virus-Checked: Checked by ClamAV on apache.org

--=_alternative 00516568C1257495_=
Content-Type: text/plain; charset="US-ASCII"

remove all commons-logging jars from your EARS/WARs .
Let your application use one shipped with jboss

Note:
see 
deploy\jbossweb-tomcat55.sar\META-INF\jboss-service.xml 
      <!-- Get the flag indicating if the normal Java2 parent first class
           loading model should be used over the servlet 2.3 web container 
first
           model.
      -->
      <attribute name="Java2ClassLoadingCompliance">false</attribute> <!-- 
    false -->
      <!-- A flag indicating if the JBoss Loader should be used. This 
loader
           uses a unified class loader as the class loader rather than the 
tomcat
           specific class loader.
           The default is false to ensure that wars have isolated class 
loading
           for duplicate jars and jsp files.
      -->
      <attribute name="UseJBossWebLoader">false</attribute>

and especially this one (if such package is found, it'll raise an error 
according to my experience)

      <!-- The list of package names that should not be loaded without
         delegating to the parent class loader before trying the web app
         class loader. The packages listed here are those tha are used by
         the web container implementation and cannot be overriden.
         This only applies when UseJBossWebLoader=false.
      -->
      <attribute 
name="FilteredPackages">javax.servlet,org.apache.commons.logging</attribute>





Maxime Orain <Maxime.Orain@thomsonreuters.com> 
07/29/2008 16:46
Bitte antworten an
users@cxf.apache.org


An
Maxime Orain <Maxime.Orain@thomsonreuters.com>, users@cxf.apache.org
Kopie

Thema
RE: Antwort: RE: Antwort: RE: Antwort: Pb with configuration with CXF and 
various    Spring [Virus checked]






I found the problem!!!

It's in my jboss-services.xml

My deploy directory doesn't end with and / that s all!

Now I ve got problem with:
16:39:41,438 ERROR [BaseModelMBean] Exception invoking method init
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Invalid class
loader hierarchy.  You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed. (Caused
by org.apache.commons.logging.LogConfigurationException: Invalid class
loader hierarchy.  You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused
by org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Invalid class
loader hierarchy.  You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed. (Caused
by org.apache.commons.logging.LogConfigurationException: Invalid class
loader hierarchy.  You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed.))

-----Original Message-----
From: Maxime Orain 
Sent: 29 July 2008 16:29
To: 'users@cxf.apache.org'
Subject: RE: Antwort: RE: Antwort: RE: Antwort: Pb with configuration
with CXF and various Spring [Virus checked]

I use the Jboss 4.0.5 GA.

I only put jboss-web.xml in the CXF War
And I put jboss-app.xml in my 2 EARs (Those ears contains wars but I
didn t put jboss-web.xml file into wars)


I have in my deploy directory:

Deploy/
      CXF.war
                 | *Spring*.jar
                 | WEB-INF/jboss-xml.xml

                 MyEAR1.ear
                 | *.jar
                 | spring-2.5.1.jar
                 | META-INF/jboss-app.xml

                 MyEAR2.ear
                 | *.jar
                 | MyWar.war
                 | --> *.jar
                 | --> spring-2.5.1.jar
                 | META-INF/jboss-app.xml


-----Original Message-----
From: jan.minaroviech@external.t-mobile.at
[mailto:jan.minaroviech@external.t-mobile.at] 
Sent: 29 July 2008 16:17
To: users@cxf.apache.org
Cc: users@cxf.apache.org
Subject: Antwort: RE: Antwort: RE: Antwort: Pb with configuration with
CXF and various Spring [Virus checked]

Hi,

what did you do exactly? Or how does your deployment look like (only 
artifacts with spring libraries are interesting atm)?
Note: As i said you shouldn't add jboss-web.xml into WARs which are 
packaged inside EAR.

but anyway, it's only warning .. is your spring+cxf deployed now?

btw. which jboss version are you using ?

best regards
jano




Maxime Orain <Maxime.Orain@thomsonreuters.com> 
07/29/2008 16:10
Bitte antworten an
users@cxf.apache.org


An
users@cxf.apache.org
Kopie

Thema
RE: Antwort: RE: Antwort: Pb with configuration with CXF and various 
Spring [Virus checked]






It s not OK :( I have this message now:

16:01:21,420 INFO  [EARDeployer] Init J2EE application:
file:/jboss/deploy/reportService.ear
16:01:21,424 WARN  [DeploymentInfo] Only the root deployment can set the
loader repository, ignoring
config=LoaderRepositoryConfig(repositoryName:
com.report:loader=REPORT_SERVICE, repositoryClassName:
org.jboss.mx.loading.HeirarchicalLoaderRepository3,
configParserClassName: null, repositoryConfig: null)

Do you know what I need to change to avoid this?

Thanks!

-----Original Message-----
From: Maxime Orain 
Sent: 29 July 2008 15:57
To: users@cxf.apache.org
Subject: RE: Antwort: RE: Antwort: Pb with configuration with CXF and
various Spring [Virus checked]

No just to the CXF war.

I now understand that you re try to say to me since 2 mails! Thanks!

-----Original Message-----
From: jan.minaroviech@external.t-mobile.at
[mailto:jan.minaroviech@external.t-mobile.at] 
Sent: 29 July 2008 15:47
To: users@cxf.apache.org
Subject: Antwort: RE: Antwort: Pb with configuration with CXF and
various Spring [Virus checked]

but, have you added it to each WAR/EAR you have deployed (especially to 
these with spring)?
otherwise others will be in "default-common" repository which will be a 
parent repository to your custom one




Maxime Orain <Maxime.Orain@thomsonreuters.com> 
07/29/2008 15:45
Bitte antworten an
users@cxf.apache.org


An
users@cxf.apache.org
Kopie

Thema
RE: Antwort: Pb with configuration with CXF and various Spring
[Virus 
checked]






Yes I read don't worry but even with the configuration (jboss-web.xml) I
have the same problem. :(

-----Original Message-----
From: jan.minaroviech@external.t-mobile.at
[mailto:jan.minaroviech@external.t-mobile.at] 
Sent: 29 July 2008 15:38
To: users@cxf.apache.org
Subject: Antwort: Pb with configuration with CXF and various Spring
[Virus checked]

did you read reply i sent you?

i told you how to force jboss 4.x to use separete classloaders.

Read something about jboss classloading
http://wiki.jboss.org/wiki/ClassLoadingConfiguration
http://wiki.jboss.org/wiki/JBossClassLoadingUseCases

if you will not use separate classloaders, or you will use classloader 
which uses repository which could contain resources from different
spring 
version, you will run into troubles.


Another issue you will experience if you are sharing classloaders will
be 
e.g. that during bean factory initialization it'll load also
configuration 
from another ear and do initialization of it's beans .. 
or another issue you can have (depends on configuration) is if you have 
the classes in different version in different EARs, always will be used 
once loaded first (it's possible to configure if class from your EAR 
should be loaded first or first it should check if loader repository 
contains already loaded definition - note that this is different from 
loading resources, because when loading resources, it'll return you list

of resources - which will always contain all possible (from all ears) if

you don't have separate classloaders).

jano





Maxime Orain <Maxime.Orain@thomsonreuters.com> 
07/29/2008 15:28
Bitte antworten an
users@cxf.apache.org


An
users@cxf.apache.org
Kopie

Thema
Pb with configuration with CXF and various Spring  [Virus checked]






I found my classloader pb ? It s more a config pb? 
It?s vicious

CXF uses WAR:
-------------
spring-core-2.0.8.jar
spring-beans-2.0.8.jar
spring-context-2.0.8.jar
spring-web-2.0.8.jar


At init Spring loads the namespace handlers:
-------------------------------------------- 
org.springframework.beans.factory.xml.UtilNamespaceHandler
org.springframework.aop.config.AopNamespaceHandler
org.springframework.scripting.config.LangNamespaceHandler
org.springframework.transaction.config.TxNamespaceHandler
org.springframework.ejb.config.JeeNamespaceHandler
org.springframework.beans.factory.xml.SimplePropertyNamespaceHandler


If CXF is alone in the application server:
------------------------------------------
14:44:49,980 DEBUG [DefaultNamespaceHandlerResolver] Ignoring namespace 
handler [org.springframework.scripting.config.LangNamespaceHandler]: 
handler class not found
java.lang.ClassNotFoundException: 
org.springframework.scripting.config.LangNamespaceHandler
        at 
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader
.java:1355)

        It?s a warning : normal.

But If I have another EAR/WAR which uses other spring versions (In my 
---------------------------------------------------------------------
example one ear contains spring-2.5.1.jar) I?ve got this error:
----------------------------------------------------------------

java.lang.IllegalArgumentException: Class 
[org.springframework.scripting.config.LangNamespaceHandler] does not 
implement the NamespaceHandler interface"


                                 There it s an error. It searches the 
class org.springframework.scripting.config.LangNamespaceHandler in the 
classloader and this one is defined in the spring-2.5.1.jar but like
it?s 
a different version this one cause an error!

If someone knows how to configure CXF or Spring to avoid this it would
be 
very appreciated!

Thanks in advance

Max.

















--=_alternative 00516568C1257495_=--