Hi Ed, It turns out that packaging our own version of org.apache.commons.beanutils.PropertyUtils (and other org.apache.commons classes) was needed in order to embed the Tomcat server in hosted mode. Since we're moving to Jetty in GWT 1.6, this should no longer be an issue moving forward.
Thanks for the heads up, -Sumit Chandel On Mon, Feb 2, 2009 at 2:28 AM, Ed <[email protected]> wrote: > > Hellu all, > > Why is GWT using his own version of the > org.apache.commons.beanutils.PropertyUtils class in the gwt-dev jar ? > (probably there are more of these classes). > > This can cause nasty conflicts, which I just had :( > For example: Dozer also uses this apache class but because the gwt-dev > jar was included (t's shouldn't which I changed now) and appeared > first on the classpath, Dozer used the PropertyUtils class in de gwt- > dev jar which caused out of memory errors :(... > > -- Ed > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
