I like this idea. The biggest question mark I had was introducing those dependencies, and this solves that issue.
By the way: Are you the same Sasha that implemented the "json-rpc-client" hosted on Google code? If so, I also have a patch for that client (using the same method as the patch I submitted yesterday). That is the client that we're using in production. We simply haven't moved to jabsorb yet.... Thanks! Brantley Sasha Ovsankin wrote: > Brantley and all -- > > Do you think the following approach will work for you? The idea is to > have the application register locallyResolved classes and avoid > introducing dependency into the package? > > See the enclosed patch. > > Thanks, > -- Sasha > > Brantley Hobbs wrote: >> Here's a patch to fix issue #48. Only one file is patched >> (o.j.cl.Client.java). >> >> The patch works by removing any outgoing arguments if they are one of >> the classes that should be locally resolved on the server >> (HttpSession, HttpServletRequest, HttpServletResponse and JSONRPCBridge). >> >> Brantley >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Jabsorb-dev mailing list >> [email protected] >> http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev > ------------------------------------------------------------------------ > > _______________________________________________ > Jabsorb-dev mailing list > [email protected] > http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev _______________________________________________ Jabsorb-dev mailing list [email protected] http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
