True. And it gives the rest of us a new gwt-foo.jar to bother with and still leaves open the possibility for people to mistakenly deploy gwt-foo.jar.
On Tue, Nov 4, 2008 at 11:12 AM, Jason Essington <[EMAIL PROTECTED]> wrote: > > It would allow people to mistakenly deploy the gwt-user.jar rather > than the correct lib (gwt-servlet.jar) in their web applications. > > -jason > > > On Nov 3, 2008, at 5:51 PM, Isaac Truett wrote: > >> >> What would that accomplish? >> >> >> On Mon, Nov 3, 2008 at 7:47 PM, Joshua Partogi >> <[EMAIL PROTECTED]> wrote: >>> >>> I think I understand where this questions leads us. He's asking why >>> doesn't GWT distribution just put the servlet API in a separate jar >>> instead of bundling it inside gwt-user.jar :-) >>> >>> On Nov 4, 8:37 am, Jason Essington <[EMAIL PROTECTED]> wrote: >>>> you shouldn't be deploying gwt-user.jar, but rather gwt- >>>> servlet.jar ... it omits all of the stuff required for development, >>>> but undesirable in deployment. >>>> >>>> -jason >>>> On Nov 3, 2008, at 9:43 AM, Harsha wrote: >>>> >>>> >>>> >>>>> When we deploy the webapplication with gwt-user.jar to JBoss, we >>>>> are >>>>> getting offended error. Is there any reason, why servlet api's are >>>>> included with in the jar file? >>>> >>> >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
