Develop Reference

Project won't launch on Google Cloud Tools for Eclipse

I've been trying to switch from the Google Eclipse Plugin to Cloud Tools for Eclipse, but I can't get a working launch configuration.
When I try to launch the project, the progress shows
Preparing launch delegate...: Launching delegate...
until it is finally aborted with
Server App Engine Standard at localhost (2) was unable to start within
240 seconds. If the server requires more time, try increasing the
timeout in the server editor.
It's a maven project with Java on App Engine.
I have created a hello world maven project which launches fine.
When I examine the org.eclipse.wst.server.core/tmpX folder of the hello world project, I see various files and directories such as index.jsp, META-INF and WEB-INF, with WEB-INF/lib containing the maven dependency jars.
The same folder for my project contains only WEB-INF/classes which contains a wierd collection of files, including another WEB-INF with an empty lib
I'm running "Google Cloud Platform for Eclipse 4.5 and later 1.2.0.201706082053" on Oxygen Release (4.7.0), although the issues has always existed since I first tried to migrate end of 2016
Any suggestions?

tomcat unable to start within 240 seconds, go to server view Double click on your server, you can see Right corner of the server property Window max Time out option, change it to more the 240 second. and also check your configuration.

JDeveloper Cannot run application due to error deploying to IntegratedWebLogicServer

I have a simple Fusion Web Application program that I could run my simple application on the weblogic server before, but now when I try to run the JSF page I get these errors:
Deployment cancelled.
---- Deployment incomplete ----.
Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
#### Cannot run application MyFirstApplication due to error deploying to IntegratedWebLogicServer.
How can I fix this problem?

The following worked for me:
Close Jdeveloper application.
Delete systemXX.x.x.x.x directory.
Restart Jdeveloper and integrated weblogic server.
I also faced the same issue but after deleting system directory, my server started successfully.

the steps of running an application on weblogic server (or any other java server) consists of the following 4 steps:
Compilation and building
Starting the server
Deploying the fusion web application
Running the application
Errors could happen in any of the steps, and would cause obstacles to move to the next steps.
Your problem seems to be in the deployment phase, so the next step which is the running of the application is stopped from being executed.
It is worth to mention that your savior is the logs.
So you need to look into the deployment logs where it would clearly show the fault and the exception from not being deployed.

I resolved it.
Please Follow These Steps :
Right Click On The Model ;
Project Properties...
Select In Left Page; "JAVA EE Application"
Insert In Java Web Application Name: XXXApplication-XXXModel-webapp (XXX is Name Of Project )
Insert Into Java EE Webcontent Root : XXXApplication-XXXModel-context-root

I'm on JDeveloper 11g Release 2.
The following worked for me:
At the application menu bar - click on Run option.
Click on Start Server Instance - IntegratedWebLogicServer (in my case)
Wait for Server to fully start.
Locate Projects box/section/tree structure, locate your project name. Right Click.
Select Deploy, (create a deployment profile if required), to open the deployment wizard.
In the deployment wizard, select Deploy to Application Server, click Next.
In my case, I saw the IntegratedWebLogicServer instance in the following list, I selected it, and continue/finish with the deployment.
I strongly believe this is related to permissions.
I was able to run and deploy my applications to the default Web Logic server until I had more restrictions in my Windows machine - for example I was no longer a local administrator.
Hope this helps.

Why won't basic spring 4 sample run with Eclipse kepler?

I am using the sample project code here that i've downloaded from the following:
http://javahash.com/spring-4-mvc-hello-world-tutorial-full-example/
Direct link here:
http://javahash.com/wp-content/uploads/2014/02/Spring4MVCHelloWorld.zip
I have Eclipse Kepler SR2 (J2EE), Tomcat 7 64-bit, Java 7.
The project does not appear to be a web project, so I add "Dynamic Web Module" version 3.0 and "Java" (version 1.7) to it. I right click, maven install, which appears to run fine. When I try to actually deploy it on tomcat, it does not give any errors in the console, but when the browser window pops up it shows a 404
http://localhost:8080/Spring4MVCHelloWorld/
HTTP Status 404 - /Spring4MVCHelloWorld/
--------------------------------------------------------------------------------
type Status report
message /Spring4MVCHelloWorld/
description The requested resource is not available.
--------------------------------------------------------------------------------
Apache Tomcat/6.0.39
That said, how do I get this "basic" example running in eclipse? Anyone able to get this working successfully? It feels like it should be more trivial than the 5 hours I've spent on trying to get this sample code working to no avail.
UPDATE:
Still continues to fail despite using Tomcat 7.0 server.
Download the sample, extract contents to workspace directory.
"Import Existing Project" in Eclipse
Since there is no "Run On Server" option, I right click on the imported project directory and hit "Properties".
I go to "Project Facets" and check 2 things: "Dynamic Web Module" (3.0) and "Java" (1.7) and hit apply then "Ok".
I right click on the project Spring4MVCHelloWorld and click "Maven"->"Update Project". Then I click "Run On Server".
There are no errors in the console, but the web browser that pops up in eclipse shows a HTTP STATUS 404.
I tried going to:
http://localhost:8080/Spring4MVCHelloWord/hello
and the same:
HTTP Status 404 - /Spring4MVCHelloWorld/hello
shows up, but the tomcat shows up as:
Apache Tomcat/7.0.53
Note that this is the 64-bit version. What steps am I missing? How do I get around this silent failing?

Apart from what Dimitri stated, your log seems to indicate that you are using
Apache Tomcat/6.0.39
That version of Tomcat does not support ServletContainerInitializer which your Spring web application depends on for configuration. Upgrade to a Tomcat version 7+.
It seems like the Maven update doesn't work for you (or for me).
First, go into Properties -> Deployment Assembly. You need to get rid of Web Content if it's there and add src/main/webapp (which is a maven convention). You also need to add the Maven Dependencies as shown below.
Finally, and this might not be necessary, delete the web.xml provided to you and re-create it by selecting and right clicking Deployment Descriptor in the Project Explorer and clicking Generate Deployment Descriptor Stub.
Also, make sure your Java Build Path in the Properties has a Java 7+ version of the JRE.

As far as I can see your controller only maps to /hello, which means your URL should be:
http://localhost:8080/Spring4MVCHelloWorld/hello
Another thing that might be interesting to you is that if your having problems with certain project facets (like Dynamic Web Module) not being recognized, you can usually fix them by righ clicking your project, opening the Maven menu and choosing Update Project.

Deploying spring web apps using Spring Tool Suite

I'm new to Java web framework, I googled to find that spring is one of the most popular framework. I tried to install tools and searched a tutorial to run spring framework on my mac.
step 1 - Tomcat installation
Following this site, I could install Tomcat on my mac. I'm using :8080 port for Tomcat.
step 2 - spring tool suite installation
From this site, I could install Spring Tool Suite.
step 3 - making an example following tutorial
I found a tutorial on using Spring Tool Suite. Following the procedure, I could build manolitomvc app.
step 4.1 - deployment <-- issue 1
Finally, I'd like to access the web app at http://localhost:8080/manolitomvc.
I clicked the green arrow to see the error message.
step 4.2 - deployment <-- issue 2
I opened overview page, and I guessed that I could set server location and deploy path to make spring web app available.
However, I have no idea how to set the server location (Tomcat server location that I installed in step1).
I tried to copy the manolitomvc directory into Tomcat main document directory(/Library/Tomcat/webapps), but it doesn't work.
How can I deploy the web app so that I can access the spring web app at http://localhost:8080/manolitomvc?
Could you recommend any other practical tutorial that I can follow to setup and use spring framework?

Thanks to Ralph's help, I could make Tomcat server working Spring Tool Suite.
Step1. Stop the tomcat server
cd /Library/Tomcat/bin and execute sudo sh shutdown.sh.
Step2. Create server
From Servers, New > Other ...
Select server/Server
Select Apache/Tomcat
Select web application
Step3. Execution and test
Execute the server
You can access the app through localhost:8080/manolitomvc.

Try not to use "VMware TC" try to start with a "normal" Tomcat.
Open the Context Menu in the "Servers" tab: New/Server
Select Apache/Tomcat v? -> Next
Select The Tomcat Intallation Directory, or click on "Download and Install.."

How can I deploy web app on Tomcat from running app

I would like to develop updater app. Lets say I've got:
- Running Tomcat
- Running Updater App on the Tomcat
- Running old version of the app on the same Tomcat
I would like to
- Stop old app
- Undeploy old app
- Deploy new version of app (lets assume that I've got new app war file somewere in Updater app resourcess.
Is it possible to do such remote deployment on Tomcat from another app at all?

To deploy a project to your Tomcat Server from another app you need to:
Add a library into your project “catalina-ant.jar” from the folder: {TOMCAT_PATH}\lib
And in your project to deploy a war file you need to only do:
org.apache.catalina.ant.DeployTask task = new org.apache.catalina.ant.DeployTask();
task.setUrl("http://localhost:8084/manager");
task.setUsername("managerLogin");
task.setPassword("managerPassword");
task.setPath("/UrlToYourDeploadingProject");
task.setWar(new File("c:/Project.war").getAbsolutePath());
task.execute();
Thanks to this solution I'm able to develop project that can update automatically my apps.

Yes. There's a set of tools (well, a .jar) released with Tomcat that's usually used by ant but that can be used by anyone willing to call the code. There are tasks for starting and stopping applications, deploying, undeploying, listing applications and so forth; essentially it's an API that wraps the functionality of the manager servlet.
One moment while I try to dig up the name or a link for you...
Here's Apache's information on this stuff: http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Executing Manager Commands With Ant
... and here's a user, elsewhere, describing in detail how he uses these tasks: http://raibledesigns.com/wiki/Wiki.jsp?page=TomcatAntTasks
You may object that you're not ant. That's true, but there's nothing magic about ant, it's just calling code inside the jar. That code can be called from anywhere else that follows the API.
Here's a tutorial on writing ant tasks: http://ant.apache.org/manual/tutorial-writing-tasks.html
Not quite the same, but it should give you an idea of how the API works.
I see no reason why you shouldn't be able to call this API from within a servlet if you want to.
Alternatively, you could run the manager servlet in your Tomcat and simply access the manager application like a Web service: Use your browser or WireShark to snoop on the traffic between your browser and Tomcat when you deploy an app, and then duplicate that to remote control manager. Me, I think using the tools jar is simpler.

If you use a "project lifecycle" tool, this undeploy/deploy can be automatized in the development cycle.
Saying that, I think about Maven2 and his "maven-deploy" plugin :
mvn compile : java compilation
mvn package : creation of the war file (for a webbapp project)
mvn deploy : stop, undeploy the old application, deploy and start the new version !
After, you can couple this automatization with a continous integration server (like Hudson).