Hi Thomas, You're right, it wasn't gwt-servlet, I found them in gwt-user and gwt-dev; I did it manually a long time ago and had to check back to see what I actually did there. Thanks for clearing that up!
During development, an OSGi-fied gwt-user bundle was added to the list of deployed bundles and was providing implementations of classes from the javax.servlet package. I refer to a fat jar whenever I find more than one package tree inside. It's not meant to have a derogatory connotation. Maybe 'fat' belongs in the space where really everything is just in one jar; and 'obese' should be a better match for the former case. At any rate, it's something we need to be careful with, especially in an OSGi context. Cheers, Dann On Monday, November 4, 2013 3:23:50 PM UTC+1, Thomas Broyer wrote: > > > > On Monday, November 4, 2013 9:00:13 AM UTC+1, Dann Martens wrote: >> >> Hi All, >> >> Better OSGi support would be great: right now we bundleize everything >> manually. The fat gwt-servlet jar pulls in a lot of 'stray' platform >> extension packages, e.g. javax.servlet which whould be provided by proper >> osgi-ified platform extension libraries. >> > > gwt-servlet is not "fat" (it's bloated with unneeded classes, but not a > "fat jar"), and certainly doesn't embed javax.servlet. gwt-user is, but you > don't deploy it, you only use it in your classpath at build-time (javac > then GWT compilation). > External dependencies are bundled in a gwt-servlet-deps "fat jar" in the > downloadable SDK, and simply declared in the POM when you pull gwt-servlet > from Central. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
