Hi Joseph, Am 23.10.2008 um 23:32 schrieb Joseph Gangestad:
> I am using 0.8.x. I took the code from trunk, here. It was the only > place I could find the RPC code. OK, thanks for the info. > As I've been working on it further, I discovered that by running the > attempt at the RPC in IE 6 I do get exceptions from Tomcat output to > the console (I will confess I am a Windows user and have been > interacting with Tomcat through Eclipse 3.3, which could be its own > can of worms, although other non-qooxdoo servlets that I've > implemented through Eclipse have worked fine). I must say I don't really trust the Tomcat-Eclipse integration. It can fail in weird ways and adds yet another layer of uncertainty when trying to diagnose problems. IMHO it would be best if you could test your application in Tomcat standalone. > At first I believe I may have not had Tomcat looking at all of the > necessary jar files (a novice mistake; I was getting some class-not- > found exceptions for MethodUtils). So I took the two commons-XXX.jar > files from the SVN trunk and added them to Tomcat's classpath. It would be better to just place them in the WEB-INF/lib directory of your webapp, but making them available to the whole Tomcat should also work. > I also replaced Tomcat's default servlet-api.jar with the one on SVN > (in trunk/lib). Please don't do that! The servlet API JAR is only there to make building the rpc implementation easier. At runtime, stay with the servlet-api.jar that Tomcat provides. > Now Tomcat is throwing an unillustrative > javax.servlet.ServletException, which is originating at > org > .apache > .catalina > .core > .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: > 313). But there are no qooxdoo-related exceptions in the stack > trace. I certainly don't want to waste anyone's time on account of > my own inexperience on the server-side and implementation, but was > hoping that there might be some easy tipoff that someone more > experienced dealing with server-client interactions might catch. Please always send the _full_ stacktrace, no matter how uninformative and unwieldy it may seem to you. Otherwise, there's no way to tell what's going on. Tomcat exceptions always include the internalDoFilter line, so that isn't enough information. From what you describe, it clearly looks like a server-side problem, but I need more details to help you. Regards, Andreas ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
