Hey Matt, thank you, I just removed all the filters and at least the gwt call is working again! Now I will try to make a dicotomic search in order to find the one that is causing the problem (hope is just one). Bye
Vincenzo Caselli On Fri, Aug 8, 2008 at 4:05 PM, Matt Raible <[EMAIL PROTECTED]> wrote: > I would try commenting out filters in web.xml to see if that helps. > > Matt > > On Fri, Aug 8, 2008 at 7:44 AM, Vincenzo Caselli <[EMAIL PROTECTED]> wrote: > > Hi all, > > I finally managed to make GWT to co-exist into an Appfuse-JSF project. > > But I am facing a very strange problem when the GWT service returns an > > object with more than, about 64 characters! > > In GWT Hosted mode debugging (from inside the Appfuse project) all is > > working right, without the above limitation. > > After GWT compilation, still from inside the Appfuse project, all is > working > > again. > > But when I deploy to Tomcat, well, all ok if the returned object (a bean > > with two string attributes) has less than about 64 characters, while I > > receive an gwt InvocationException when the object contains more > characters. > > > > Note that, among the various tests, only when deployed to an external > Tomcat > > the Appfuse filters are applied. > > It seems as if some Appfuse settings is limiting the GWT response, maybe > > something dealing with javascript content, header of the response, don't > > know, but it must be something like this. > > > > Any ideas? > > > > Vincenzo Caselli > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
