Well, thats a bit of a fail on my part... I missed the web.xml file while I was 
copying some files in.

Either add the following to a web.xml inside the test webapp

<?xml version="1.0" encoding="UTF-8"?>
<web-app
                xmlns="http://java.sun.com/xml/ns/javaee";
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
                xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
                                                        
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
                version="3.0" metadata-complete="false">
        <context-param>
                <param-name>contextConfigLocation</param-name>
                
<param-value>classpath*:META-INF/spring/applicationContext.xml</param-value>
        </context-param>
        <listener>
                
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
        </listener>
</web-app>

or I have uploaded a fixed version which you can get here
https://www.dropbox.com/s/fn834edpw376f8z/classloadfixed-test-tomee%2B-1.6.1-SNAPSHOT.zip

Trevor Stevens
[email protected]


On Dec 23, 2013, at 1:47 AM, Romain Manni-Bucau <[email protected]> wrote:

> Hi
> 
> What to do to get classnotfound? it starts cleanly.
> 
> btw try keeping spring jars named spring-* instead of
> org.springframework.* (shouldn't change a lot of things for you but
> few things can be impacted)
> 
> Note: openejb.classloader.forced-load=org.springframework shouldn't
> change anything too
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
> 
> 
> 
> 2013/12/23 Trevor Stevens <[email protected]>:
>> In tinkering with the project I was able to reproduce the exception on the 
>> latest snapshot with very few changes. I have stripped out almost everything 
>> from the test webapp apart from basic spring config which will trigger the 
>> classloading issue.
>> 
>> Updates to vanilla 1.6.1-SNAPSHOT needed to reproduce issue
>> Add openejb.classloader.forced-load=org.springframework to system.properties
>> Add Spring jars to TomEE lib
>> Add test exploded war to webapps
>> 
>> I am adding a link here to my updated snapshot for now and I will work on 
>> getting a version working with the TomEE plugin sometime tomorrow.
>> 
>> https://www.dropbox.com/s/8d14h94m706j36u/classload-test-tomee%2B-1.6.1-SNAPSHOT.zip
>> 
>> Trevor Stevens
>> [email protected]
>> 
>> 
>> On Dec 21, 2013, at 4:10 PM, Romain Manni-Bucau <[email protected]> 
>> wrote:
>> 
>>> Does http://tomee.apache.org/tomee-maven-plugin.html help?
>>> Le 21 déc. 2013 21:41, "Trevor Stevens" <[email protected]> a écrit :
>>> 
>>>> Are there any examples of using the TomEE maven plugin I can take a look
>>>> at? I would gladly try and reproduce this for you guys I just don't have
>>>> any experience building with the maven plugin.
>>>> 
>>>> Thanks,
>>>> Trevor Stevens
>>>> [email protected]
>>>> 
>>>> 
>>>> On Dec 21, 2013, at 2:19 AM, Romain Manni-Bucau <[email protected]>
>>>> wrote:
>>>> 
>>>>> Hmm, cxf has some spring links, putting spring in the container AND the
>>>>> webapp can lead to some issues, would be great if you can reproduce it
>>>> with
>>>>> tomee maven plugin and share it to let us dig into it
>>>>> Le 20 déc. 2013 22:33, "Trevor Stevens" <[email protected]> a écrit :
>>>>> 
>>>>>> Plus. I am currently running the latest snapshot I could find
>>>> (20131220).
>>>>>> 
>>>>>> Trevor Stevens
>>>>>> [email protected]
>>>>>> 
>>>>>> 
>>>>>> On Dec 20, 2013, at 4:27 PM, Romain Manni-Bucau <[email protected]>
>>>>>> wrote:
>>>>>> 
>>>>>>> Hmm
>>>>>>> 
>>>>>>> Webprofile, plus or jaxrs version?
>>>>>>> Le 20 déc. 2013 21:58, "Trevor Stevens" <[email protected]> a écrit :
>>>>>>> 
>>>>>>>> I am getting them for Spring jars (Caused by:
>>>>>>>> java.lang.ClassNotFoundException:
>>>>>>>> org.springframework.aop.support.AopUtils). I do have Spring jars in my
>>>>>>>> TomEE lib for activemq xml configuration along with a different
>>>> version
>>>>>> of
>>>>>>>> Spring inside the war. I have
>>>>>>>> openejb.classloader.forced-load=org.springframework set in my
>>>>>>>> system.properties so I assume that it is loading from the war and not
>>>>>> from
>>>>>>>> TomEE lib which was my first thought.
>>>>>>>> 
>>>>>>>> Trevor Stevens
>>>>>>>> [email protected]
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Dec 20, 2013, at 3:51 PM, Romain Manni-Bucau <
>>>> [email protected]>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Hi
>>>>>>>>> 
>>>>>>>>> Which classes, few changes you shouldnt see
>>>>>>>>> Le 20 déc. 2013 20:10, "Trevor Stevens" <[email protected]> a écrit
>>>> :
>>>>>>>>> 
>>>>>>>>>> I am currently getting classloading issues on the latest TomEE
>>>>>> snapshot.
>>>>>>>>>> If I take a war successfully deployed to 1.6.0 and copy it to
>>>>>>>>>> 1.6.1-SNAPSHOT I get class not found exceptions for classes
>>>> contained
>>>>>>>>>> within the lib of the webapp. Have there been any changes since
>>>>>> release
>>>>>>>>>> which could cause this?
>>>>>>>>>> 
>>>>>>>>>> Trevor Stevens
>>>>>>>>>> [email protected]<mailto:[email protected]>
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>> 

Reply via email to