Marcel Ruff schrieb: > Thanks for all your input :-) > >> Hello, >> >> Here is what you should do: >> 1) Install a tomcat server on the same machine you are developping >> your web application >> 2) Install the eclipse tomcat plugin >> (http://www.eclipsetotale.com/tomcatPlugin.html) >> >> > Ok, thanks for this, it works very nice: > Now i can debug my servlet, change the servlet code and it is auto > compiled by eclipse > and auto loaded by tomcat: The change is immediately available - great! > The smart thing is i could make symbolic links to my different svn > projects and so > access the servlets without changing my directory structure (thanks to > Unix). > >> 3) Work with the qooxdoo 'source', not with the 'build'. >> You dont need to re-compile qooxdoo everytime you are doing changes !! >> The 'source' version of your application is a javascript script that >> will load all the classes involved in your project. >> This mean that you need to re-compile qooxdoo (make source) everytime >> you add a new class : and that's all ! >> >> > This i can't figure out: > > If i load the qooxdoo project in firefox like (directly from harddisk): > > file:///home/watchee/watcheeweb/src/main/track.jsp > > then the javascript inside can't access the servlet with > > http://localhost:8080/watchee/ajax > > it gets a > > "Permission denied to call method XMLHttpRequest.open" > > -> The browser does not allow to change from file:// to http://. > > If i load the qooxdoo project like: > http://localhost:8080/watchee/track.jsp > everything runs fine (as the javascript also uses http://localhost:8080...). > >
Here you have been hit by the browser's "same origin policy", which doesn't permit XMLHTTPRequests to servers from a different domain. In your case you have even a different protocol (http vs. file). what we do is doing a symlink of the source version into the deployed webapp. You may have to copy the qooxdoo SDK into the web server as well for the loader script to find the qooxdoo classes. Best Fabian > But now i need to redeploy the qooxdoo war on > each change on Application.js :-( > > Here i need some smarter approach ... > >> * Compared to the build version, your in-developpement application >> will load a little bit slower: that's because instead of getting one >> big file containing all the classes (with data compression) -- the >> 'build' --, your web browser will load each classes as individual >> files --the 'source' -- (it means that when using 300 classes, you >> will load 300 small javascript files instead of one big javascript >> file) : but, you can change sources and check up the results by >> reloading your web page. >> >> > I do a 'make build' which creates the compressed track.js > and throw it into tomcats webapp - no this is loaded fast. > And now i make a clever symbolic link from webapps/Application.js to my > svn directory where i edit the file - but: > It didn't work here as the comressed track.js already contains the > Application.js > code and i end up having it twice - which irritates qooxdoo. > > We would nee to have a > "make semibuild" > which includes everything but not the Application.js which i edit all > the time. > > Thanks > Marcel > > -- Fabian Jakobs JavaScript Framework Developer 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Andreas Gauger, Matthias Greve, Robert Hoffmann, Norbert Lang, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
