Hi

1) using winzip I removed the commons folder in the file gwt-dev-windows.jar
file

2) Then I added the following jar files on the classpath in intellij idea.
           - commons-collections-3.1.jar
           -  commons-configuration-1.4.jar
           -  commons-logging-1.1.jar
          - gwt-servlet.jar
    and also spring 2.5.5.jar :-)

Now I can start up gwt 1.6Rc1 and it can read the application xml , and I
can rpc call a spring bean.

Hope you can use this.


/Flemming


On Sun, Mar 22, 2009 at 10:14 AM, Flemming Boller <flemming.bol...@gmail.com
> wrote:

> Hi
>
> It seems that the jarfile gwt-dev-windows.jar includes a lot of apache
> commons libraries.
> which conflicts with jar files added in web-inf/lib that also uses the
> above commons libraries.
>
>
> /Flemming
>
>
> On Thu, Mar 19, 2009 at 9:08 PM, Flemming Boller <
> flemming.bol...@gmail.com> wrote:
>
>> I can also confirm the above experience. "loader constraint violation"
>>
>> /Flemming
>>
>>
>> On Thu, Mar 19, 2009 at 6:56 PM, magbyr <mag...@gmail.com> wrote:
>>
>>>
>>> I tried creating a completely blank / new 1.6RC project. When I put
>>> spring.jar and a blank applicationContext.xml the project stops
>>> working.
>>> Tried both with the spring context-listener and the spring servlet.
>>>
>>> [WARN] failed springServlet
>>> java.lang.LinkageError: loader constraint violation: loader (instance
>>> of com/google/gwt/dev/shell/jetty/JettyLauncher$WebAppContextWithReload
>>> $WebAppClassLoaderExtension) previously initiated loading for a
>>> different type with name "org/apache/commons/logging/Log"
>>>        at java.lang.ClassLoader.defineClass1(Native Method)
>>>        at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
>>>        at
>>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:
>>> 124)
>>>        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>>>        at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
>>>        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>>>        at java.security.AccessController.doPrivileged(Native Method)
>>>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>>>        at com.google.gwt.dev.shell.jetty.JettyLauncher
>>> $WebAppContextWithReload$WebAppClassLoaderExtension.findClass
>>> (JettyLauncher.java:303)
>>>        at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass
>>> (WebAppClassLoader.java:366)
>>>        at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass
>>> (WebAppClassLoader.java:337)
>>>        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>>>        at
>>> org.springframework.core.CollectionFactory.createConcurrentMapIfPossible
>>> (CollectionFactory.java:195)
>>>        at org.springframework.web.context.ContextLoader.<clinit>
>>> (ContextLoader.java:153)
>>>        at
>>> org.springframework.web.context.ContextLoaderServlet.createContextLoader
>>> (ContextLoaderServlet.java:89)
>>>        at org.springframework.web.context.ContextLoaderServlet.init
>>> (ContextLoaderServlet.java:80)
>>>        at javax.servlet.GenericServlet.init(GenericServlet.java:212)
>>>        at org.mortbay.jetty.servlet.ServletHolder.initServlet
>>> (ServletHolder.java:433)
>>>        at
>>> org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:
>>> 256)
>>>        at org.mortbay.component.AbstractLifeCycle.start
>>> (AbstractLifeCycle.java:39)
>>>        at org.mortbay.jetty.servlet.ServletHandler.initialize
>>> (ServletHandler.java:616)
>>>        at
>>> org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
>>>        at org.mortbay.jetty.webapp.WebAppContext.startContext
>>> (WebAppContext.java:1220)
>>>        at org.mortbay.jetty.handler.ContextHandler.doStart
>>> (ContextHandler.java:513)
>>>        at
>>> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
>>> 448)
>>>        at com.google.gwt.dev.shell.jetty.JettyLauncher
>>> $WebAppContextWithReload.doStart(JettyLauncher.java:397)
>>>        at org.mortbay.component.AbstractLifeCycle.start
>>> (AbstractLifeCycle.java:39)
>>>        at org.mortbay.jetty.handler.HandlerWrapper.doStart
>>> (HandlerWrapper.java:130)
>>>        at org.mortbay.jetty.handler.RequestLogHandler.doStart
>>> (RequestLogHandler.java:115)
>>>        at org.mortbay.component.AbstractLifeCycle.start
>>> (AbstractLifeCycle.java:39)
>>>        at org.mortbay.jetty.handler.HandlerWrapper.doStart
>>> (HandlerWrapper.java:130)
>>>        at org.mortbay.jetty.Server.doStart(Server.java:222)
>>>        at org.mortbay.component.AbstractLifeCycle.start
>>> (AbstractLifeCycle.java:39)
>>>        at com.google.gwt.dev.shell.jetty.JettyLauncher.start
>>> (JettyLauncher.java:449)
>>>        at
>>> com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:367)
>>>        at
>>> com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:590)
>>>        at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:397)
>>>        at com.google.gwt.dev.HostedMode.main(HostedMode.java:232)
>>>
>>>
>>>
>>> On 19 Mar, 15:28, magbyr <mag...@gmail.com> wrote:
>>> > I'm having a problem with 1.6RC / Jetty and Spring 2.5. Same project
>>> > worked well on 1.5.3, but not on 1.6RC.
>>> >
>>> > Fails on jsp and default servlet from Jetty:
>>> > javax.servlet.UnavailableException: Servlet class
>>> > org.apache.jasper.servlet.JspServlet is not a javax.servlet.Servlet
>>> > javax.servlet.UnavailableException: Servlet class
>>> > org.mortbay.jetty.servlet.DefaultServlet is not a
>>> > javax.servlet.Servlet
>>> >
>>> > Seems like some kind of classloader issue.
>>> >
>>> > Anybody running 1.6RC with Spring successfully?
>>> >>>
>>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to