I don't have one atm, will try to produce one... On Wed, Jan 13, 2010 at 9:28 PM, Chris Ramsdale <[email protected]>wrote:
> @Mike (either one), do you have a small test project that reproduces these > issues? If so, would you mind sending it to me? > > Thanks, > Chris > > On Tue, Jan 5, 2010 at 2:12 PM, MikeN <[email protected]> wrote: > >> Hi, >> >> I think I've found two issues in the new deRPC code, but I would like >> some confirmation before spamming the issuetracker. I'm using the GWT >> 2.0 release codebase, on various platforms. >> >> The first issue is in RpcServlet. By default the code can't find the >> *.gwt.rpc files (in production mode) if the webapp is not deployed at >> the root of the server. When determining the path to the ModuleBase, >> in getRequestModuleBasePath(), the code simply gets a client-side >> header and strips the host and port part (isn't this a security issue >> anyway?). Problem is, webapps/servlets don't have to be deployed to >> the root of the server. When deployed at an other path, for instance / >> webapps/myWebapp/, the client will send this in de ModuleBase header, >> but it shouldn't be included in the getServletContext >> ().getResourceAsStream(resourcePath) call as the resourcePath. I >> 'fixed' this by overriding findClientOracleDate(), but that shouldn't >> be necessary... >> >> The next issue took me somewhat longer to debug. When using a custom >> object, containing a bool, and sending that to the client and then >> back to the server, deserialization at the serverside fails with a >> ClassCastException (can't cast from Double to Boolean) (only in >> production mode). This is because the bool gets send over as a double >> (I see D1 in the request, instead of Z1). I'm not quite sure where the >> problem is, probably somewhere in >> CommandClientSerializationStreamWriter. I fixed it by using a Boolean >> instead of a bool in my object. >> >> Has anyone seen these bugs before, or is anyone able to reproduce >> them? >> >> Regards, >> >> --Mike >> >> -- >> 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]<google-web-toolkit%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> >> >> >> > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- Mike Noordermeer [email protected]--
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.
