Based on samples found in the net, I developped a GWT webapp....that works fine (so far) when it is started in superdevmode from eclipse (through Jetty).
A browser can access my webpage from local/remote computer (bindaddress=0.0.0.0).
Issues appear when trying to deploy it with TomCat. Indeed, the webpage is accessible, but at some point, there is a redirection to port 9786. I guess this is a normal situation since it is built in superdevmode? If I set the development mode in Eclipse to Classic mode, it doesn't even work in Eclipse.
I thought having a web server listening on port 9786 is not a proper implementation. So, I am trying to get rid of this port (probably a matter of dev mode).
What should I do?
Related
I am trying to simulate user input (keyboard) using Robot library from java.awt, and it is working on my development enviroment, but when deploying to Tomcat (installed as a service on a different machine), it wont work at all. My OS is Windows.
Is there any configuration that I am missing? I already tried "let tomcat interact with the desktop" option, changing users to run the service, changing java used by tomcat (from jre/ to jdk/jre/..), but still I can't make it work.
Also, if it is not possible, is there another way to achieve this?
I finally solved this, not in the best way I guess.
I stopped Tomcat Service, and then started it from CMD as the current user.
Steps to open tomcat from cmd:
Open cmd.exe
Path-to-tomcat\bib\tomcat7.exe
And then opened my browser, went to the application, tried the proccess and the robot worked correctly!
I know this is not the best way as it can led to security issues, but I couldn't make it work using it as a Service because the different user sessiones (Session 0).
I'm having a strange problem. I have a Java application which I want to run using Java web start. This Java application is signed by a trusted authority (digicert) certificate. When I deploy my application to my local glass fish 4.1 server and run the Java I get the dialogue "do you want to trust ....). So far so good. When I deploy the exact same app to a glass fish server hosted on a remote machine (Amazon instance) and attempt to run the Java web start app, I get. "This application is blocked" message, as if the Java app is not signed. What is the cause of this behavior? My remote server uses ssl connections, but even when I specify http in the jnlp I get the same problem (my server listens to both http and https). This has been driving me crazy for three days now. Please help.
There are other hoops to jump through. You need a permissions applet
tag, and the main jar has to have a matching permissions line, and
a codebase line compatible with the site being loaded from.
All the jars have to be listed in the jnlp.
I have created a website running on eclipse and tomcat. What is the way to make this website running online for real?? I have developed it, adding filters and sessions and using a database. I want to allow people to use this website. What I have to do?
You need to publically expose your computer and the port you set up.
If your application runs locally, it must be able to be hit by the outside world.
Make sure the tomcat config is setup correctly and ensure port forwarding on your router or modem is setup. Your public IP (available if you google whats my ip) and the port is all your users would need.
I have a server running on app-engine. I am working on version 2 of my server, which serves as the backend for a mobile app. How do I a dev and a staging server so that I can test before replacing the production server? Does anyone know of a tutorial somewhere that addresses exactly this issue? It would be nice if I could set things up the way Google Play sets up android publication: I can publish to Alpha; then move the apk to Beta; and then to production. I will take what I can get at this point, but that structure would be nice.
You can use versions for this purpose. This way you can talk to myApp.appspot.com for a "production" version, to beta.myApp.appspot.com for a beta version, etc.
EDIT:
All versions run in different instances, but they all talk to the same datastore. It is a good option to test changes that do not break your data model - i.e. a beta version does not make changes in the datastore that break the production version.
If you want to test it in a local environment before pushing it to app engine. I would recommend have a separate box/server and deploy your code there and run the application on that server. Run application as web application in debug mode so you can see errors or problems that occurs. Connect your phone via Wi-Fi to your LAN and make sure the port you are using such as 8080 is open in your hub/firewall.
This way your server's services can send data and receive data without actually deploying on app engine.
This link might be useful:
https://developers.google.com/appengine/docs/java/tools/devserver
I implement using http://www.streamhead.com/google-appengine-staging-server/. It's better than versioning. But thanks everyone for helping.
I've been using XAMP and it's features for some php sites and it's working fine. I'm now needing to use it for JSP development for a project we're about to start working on.
So far it's functioning on my local machine in that I downloaded the sample war file from Tomcat and it deploys fine and is visible when using localhost:8080/sample.
The problem is that I can't seem to access it from a browser using the domain name. I tried www.mydomain.com/sample but receive a 404 error.
The same when using my local IP address instead.
I've searched online for a while now and have come across a few sources that hint at integrating apache with tomcat but nothing concrete enough to try and get a working solution.
I've also tried (and miserably failed) to watch the video that is referenced in a few other questions.
Any help is hugely appreciated,
Thanks.
that's because tomcat works on port 8080 unlike apache - when you run php sites they are just behind the apache which is visible on port 80 (which the default one in browsers), you can go through "http://mydomain.com:8080/sample" and it would work the same as through localhost
you can also change tomcat's settings and change it's connector's port from 8080 to 80, and then it would work as you expected