Getting Flex Builder to use a Tomcat server on Eclipse - eclipse

I'm currently trying to get a Tomcat server I have running in Eclipse on http ://localhost:8080/ to be noticed through Flex Builder 4. I think it may have to do with the config.xml file in my Flex Builder project. It is currently set as the following (as well as some other stuff)
<config>
<server>
http://localhost:8080/myty/myy?p1=a1
</server>
<iroot>
c:</iroot>
<oroot>
c:</oroot>
I think it may be that I am using a Mac and there is no C drive on a Mac. However, I think it may also be the server location. I tried taking the part after 8080 out, but then I just get errors and nothing happens as opposed to the actual server page showing up.

You can use lcds or blazeds to push your application to an app server like tomcat. I haven't tried configuring my installation of tomcat to it. But I have worked with the tomcat installation that lcds provides. Works fine.
You can read up on configuring tomcat to lcds here http://help.adobe.com/en_US/livecycle/es/lcds_installation.html#tomcat
Let me know how it goes

Related

GWT 2.7 Super Dev Mode not working while testing on the same network

I recently began using GWT 2.7 in Eclipse Luna and I was running my projects seamlessly while testing them in localhost:8888, the thing is, when I tried to test them (any of them, even a new app with only the autogenerated content) with another device on the same local network using (pc running eclipse ip):8888 I get a message like this:
The page at (ip):8888 says: Couldn't load (app) from Super Dev Mode server at http://(ip):9876. Please make sure this server is ready. Do you want to try again?
This also happens when I try to access to the app in the pc running eclipse with (its own ip):8888.
I've checked these four similar questions, but they didn't have any really helpful answers, these are a few things I've tried or discovered already:
I enabled the 9876 port on the firewall
I've deleted the .nocache.js and .devmode.js so that they're generated again
I noticed that when this problem occurs it's because the browser can't get the (ip):9876/recompile-requester/(app) file
I tried deploying the app to GAE and it doesn't work there either, nothing that happens on the modules Java code runs (And for some reason, I get a "Uncaught java.lang.ClassCastException" message on the chrome console, but this only happens on the deployed version, it doesn't happen on localhost:8888 or in (local ip):8888)
But nothing has worked and the four questions I mentioned are pretty much the only things related to this I've found, so I really don't know what else to try.
As Thomas pointed out, the problem I had was that from GWT 2.6 onwards, if you want to test from other devices in the same network, you have to whitelist the addresses you'll be using in each *.gwt.xml file using a command line like this:
<set-configuration-property name="devModeUrlWhitelistRegexp" value="http://(localhost|127\.0\.0\.1|192\.168\.150\.(\d{1,3}))(:\d+)?/?.*" />
I also had to add a -bindAddress 0.0.0.0 attribute to the run config for it to work.

How do I run GWT on a linux server

Sorry for this simple question but I seem not to find any other way than to publish a GWT app to Google App Spot. I'm sure there must be a way to do this.
I've got the development environment working on my local machine but I'd like to publish the solution to my ubuntu server running nginx.
Edit: Just thought of something... maybe I can just deploy the js-code to the ubuntu server? As simple as that? ;)
No you cant just deploy the js-code and html files to an ubuntu server and put it for apache to serve, well... unless your code only outputs hello world that is. Probably your GWT app is calling/using some other Java code that needs to be deployed in tomcat or jboss, is it? If that is the case, ie your GWT is in a war, then yes, just deploy that .war file to any container on any linux box.
Try to copy your .war into a jboss deploy dir.
Deploying to app spot is similar, ie uploading your .war to google. Read more here http://code.google.com/webtoolkit/doc/1.6/DevGuideDeploying.html
Two options:
Run it in Eclipse
Run it with Ant

Debugging a GWT application in a remote environment

I have deployed my GWT application to its target environment (i.e. compiled and copied the war directory contents to the target device's /var/www) and some parts of it are not working. I understand that I can debug my local instance of the GWT app as if it were running in the target environment, by opening the deployed GWT App URL and adding gwt.codesvr URL parameter to it, like this:
http://deployment_host/gwtapp.html?gwt.codesvr=localhost:9997
I get
Plugin failed to connect to Development Mode server at localhost:9997
Follow the underlying troubleshooting instructions
My Chrome browser is running on the same machine as Eclipse, so localhost above should be ok. Just to make sure, I've added -bindAddress 0.0.0.0 in the Run/Debug configuration in Eclipse and tried with my external IP/hostname, with no change, except that the error message is updated accordingly. What am I doing wrong?
If I replace deployment_host with localhost above everything works fine, but it's of no use to me to debug locally. (There is some Proxy and ReverseProxy-ing going on in the local Apache, so I do not need the 8888 port when running locally, but this should be unrelated)
Questions Debugging GWT applications outside of dev mode? and Debug GWT application in a remote browser are related but do not help.
If you are using chrome, look in the address bar at the right for a grey GWT icon. In any other browser, you would see a popup message confirming that you want to debug, but in Chrome this apparently isn't possible.
Click the icon, and it will ask you to whitelist this site as allowed to run Java locally on your computer. After you whitelist it, it should run correctly.
Along the same lines as the answer above Ive just had some success restarting the extension helped (but restarting browser hadnt)
Just enable and disable it in :
chrome://chrome/extensions/
Good luck! It's the only thing wrong with GWT imho...

Tomcat in Eclipse remains starting/synchronized but is actually running

I'm having the following problem with Eclipse 3.7 and Tomcat 7.0.8: I've added my Tomcat with a deployment descriptor in my Eclipse. I've enabled "Use Tomcat installation" in the server settings and tried to start it. The Console in Eclipse says "Server started up in 70s", I can access my application, but the servers state remains "Starting/Synchronized". As a result sooner or later the configured timeout is triggered and I'm getting an error.
Why is Eclipse not recognizing that the server was started successfully?
I've also tried to reinstall Eclipse and Tomcat - no positive changes.
Also adding a clean, fresh downloaded Tomcat results in the same "error".
Any suggestions?
Richard
Try changing the HTTP port from the server configuration screen. For example if you previously had 8080, try changing it to 8090. This should automatically update the new port number to server.xml.
I started running into the same problem after I had been modifying the server port directly in server.xml. Changing the ports back to what they had been did not seem to solve the problem. It looked like the server pluging and actual configuration got somehow out of sync.

gwt response at run as web application

In my gwt application,i am using php code for back end process...i can get response from that php file when i deploy on iis server...
but i can't get response from that php file when i running from the eclipse...
(i.e)
can get response from this url "http://localhost/sample/index.php"
can't get response from this url "http://localhost:8888/sample/index.php" it returns my php code...
It's probably possible to run PHP on Jetty, too: See these instructions - not sure, if they still work with Jetty 6, and I really haven't tried it.
But I would recommend to simply run a separate PHP server (maybe deployed from a separate Eclipse project). See this GWT FAQ entry: How do I use my own server in hosted mode instead of GWT's built-in Jetty instance
You could use the gwt -noserver option
"The -noserver option instructs hosted mode to not start the embedded Jetty instance. In its place, you would run the J2EE container of your choice and simply use that in place of the embedded Jetty instance."
I don't know if this would solve your problem