Coldfusion deploy into Google app with Eclipse - eclipse

I've download eclipse-jee-galileo-win32.zip and following instruction of this post, http://blog.kukiel.net/2009/09/coldfusion-on-google-app-engine-with.html
After that, I encounter following errors once I've deleted war file and replace openbd's war files into my project.
alt text http://img411.imageshack.us/img411/3479/52229590.png
Please let me know if you have such problem just like me.

Make sure that you are running the latest SDKs (Google Web Toolkit and Google App Engine). I had this same issue until I switched to the latest versions when I first started out as well.
You can see which ones you are using for a particular app by opening up its properties and looking under Google. The latest versions are 1.3.5 (App Engine) and 2.0.4 (Web Toolkit). If you are on older versions look for updates, new features to install the latest.

Related

Deploy new version to google app engine not work

I m a new user in the google cloud platform,
I followed the jhipster tutorial to deploy the jhipster web application to Google App Engine.
(https://www.jhipster.tech/gcp/)
I can deploy the original version of jhipser to GCP app engine, but when I deploy again it was not updated to the new version even my local was updated.
Does anyone know how to deploy new version to Google app engine??
I don't know much about jhipster, but if it is a classical java web application on app engine, as stated in the link you provided, you just need to re-deploy again:
./mvnw package appengine:deploy -DskipTests -Pgae,prod-gae
if you want to deploy as a new version, you should check what is the version parameter provided. You can find that in app.yaml, application-web.xml or pom.xml file depending on how the application is built.
If who built the application decided to automatically increment the version each deploy, you should have already everything set, but in App Engine > Version page in GCP you should migrate the traffic to your latest version.

Why is my Google Cloud Platform for Eclipse resulting in Error Not Found?

I upgraded Eclipse and moved to Google Cloud Platform for Eclipse for my existing Standard App Engine project. I also moved to Java 8.
Now, when I deploy my app, the size shown in the console is only 7.1mb vs. 220mb prior to the upgrade. And when I try to go to the app after deployment I get an Error: Not Found message.
Is there something in the setup for my new configuration that would be causing this?
Your question is indeed somewhat broad; you'll need to provide all necessary detail. A correspondingly general information page might help here, though, namely Eclipse "How-to Guides".
Have you adapted and re-written your app for Java 8? If so, in which way? Have you edited your app.yaml configuration file accordingly?
Cloud Tools for Eclipse writes out the app-to-be-deployed to a directory in your workspace called <workspace>/.metadata/.plugins/com.google.cloud.tools.eclipse.appengine.deploy/tmp/<timestamp>/staging-work/exploded-war, where <timestamp> is the time of the last two deploys. Look at the exploded-war directory and see what files are missing. You may then get a better sense of what needs to be remediated.

Ionic + IBM MobileFirst

I've found a few post on this topic but have not been able to find the best solution.
Attempted to integrate Ionic into IBM MobileFirst (Worklight).
At the moment - I have built a normal Ionic project and moved the WWW folder in the 'common' folder. Also added in the initOptions, main.js and messages.js.
MobileFirst has an awful build process - I hate having to deploy to a mobilefirst development server + preview app for any code changes. I am hoping to get some type of auto reload working within mobileFirst, or at least develop with ionic normally and hav ea job to bring my changes into my worklight project... something that is better than me current situation.
Does anyone have a sample project that actually auto-builds or picks up code changes automatically?
Any and all help is greatly appreciated.
Not sure what do you mean by "auto-reloading"; if you make any changes to the web resources to your project inside the Studio plug-in (in Eclipse) and reload the preview in the browser, it will show the changes.
You are not required to Run As > Run on MobileFirst Development Server for each change. As long as you work on the resources in your workspace, the "auto-reloading" as you call it, should work (make sure you are using the latest available MobileFirst Studio version from the Eclipse Marketplace).
There is also a rudimentary Starter Application that is based on Ionic.
You can download it from here.
There are also several results on the subject matter when searching in Google.
The need to rebuild in order to see changes in your Web components (CSS, JavaScript, HTML) did used to be an annoyance in early versions of what was then Worklight and is now MobileFirst. I forget when the need for a rebuild was removed but certainly in Worklight 6.2 and beyond you now simply need to refresh in your browser.
UPDATE: If using MobileFirst 6.3 you need to ensure that you are on a
suitable patch level. I find that simple refresh does not work in
6.3.0.00-20150106-1717, but if I update (Help->Check for Updates) to 6.3.0.00-20150214-1702 then edit/save/refresh works as
expected.
My personal practice is always to have Mobile Web environment in my project and then choose that from the Console. This loads the application in the browser-based Mobile Simulator that you can tailor to fit your target form-factor. This has a "Go/Refresh" button that immediately reflects your edits.
Alternatively, some folks these days do not use Studio, instead they use the Command Line Interfacer. Possibly this may be more to your taste. You can download it here.
there is a solution with using staff like ionic-cli serve command + symbolic links that will replace common folder.
check here an example https://www.dropbox.com/s/4pvaulo6yo47kb9/lab_7.2.mp4?dl=0
(you just can disable sound, cause i've recorded it in russian) 7-15 minutes of this video
Other option is to organize live-preview yourself using IDE features and/or nodejs
This will work as long as you are working on front-end (mostly non-worklight api) part.
You need to include this lines in the index.html
<!-- ionic bundle & css -->
<link href="www/ionic/css/ionic.css" rel="stylesheet">
<script src="www/ionic/js/ionic.bundle.js"></script>

How to deploy web application onto Google App Engine

This may be a vague question but I have been unable to find any help/tutorials specific to my situation and am stuck.
I have built a website using Eclipse (Dynamic Web Project.) I then deployed this application using Tomcat and can see it by going to localhost, however, I am struggling on how to actually deploy it to the cloud.
I am trying to use Google App Engine but am open to other (free) alternatives for deploying my web application.
With Google App Engine, I registered for an account, made a new project, connected it to my github repository and confirmed the correct code is listed.
However, when navigating to project_id.appspot.com (mine is http://mapp-development.appspot.com) I get a 404 error.
I have attempted various deployments and even made an entirely new Google Web Application Project in Eclipse for testing which worked but weirdly deployed to http://1-dot-mapp-develop.appspot.com/ and is the test files which I do not know how to correctly modify.
Is there any way to upload/deploy my existing web application to Google App Engine (as a .war or otherwise)?
I am new to web development and apologize for any unclear specifications. Any help would be greatly appreciated!
Edit: I have also tried (in Eclipse) right clicking the project and choosing "Deploy to App Engine" under Google however it states "mapp-website is not an App Engine project".
Edit2: I had a stupid mistake, I confused my Project ID (mapp-development) and app id (mapp-develop). I am able to successfully make a new Google web project and deploy it to mapp-develop.appspot.com
Sorry for the trouble!
Here are three ways to deploy:
Make an App Engine project in Eclipse
Deploy via Git
Deploy via GitHub
It seems like you tried #1 with a project named 1-dot-mapp-develop. If you select deploy from Eclipse, a dialog box will pop up with a link to "App Engine Project Settings" where you can change the project name (to mapp-development and version).

EclipseRT/Virgo not appearing in Eclipse Server Adapter list

I'm trying to get up and running with Virgo, and I'm following along with what appears to be an excellent tutorial, but I'm at section 7.2 and I just can't figure out why EclipseRT / Virgo doesn't appear in my list of options.
So far I've been using SpringSource Tool Suite (STS) as the guide recommended and have installed all the Spring dm Server Tools and Developer Resources bundles.
Has anyone else run into this issue or have a solution to getting the EclipseRT/Virgo server adapter?
Virgo 2.1.0.RELEASE and STS 2.5.0.RELEASE are both now out. The problems you had with the docs should be resolved. The documentation has also been updated to show the latest information as well.
Be aware that the STS 2.6.0 upgrade removes this server adapter! Refer to the STS JIRA entry STS-1690 for details on this removal. You can simply go to the Dashboard > Extensions tab and select "dm Server Support Extension" to put it back.
Hey, have a look at this eclipse forum for virgo
Seems like you have to get used to playing with the update sites until you find the right one. I imagine that by the time anyone reads this the url will probably have morphed every so slightly yet again. Sigh. Comes of playing with tech while they're still actively releasing.
In case someone is searching for more recant information, one need to install DM Server Tooling from http://dist.springsource.com/release/DMS-TOOLS/update to get Virgo in the server add dialog.
I've been just playing around with Virgo 2.1.1 and Eclipse STS 2.7.1.
Indeed there is no Virgo server adapter, but you can install it from this update site:
http://download.eclipse.org/virgo/milestone/IDE
For the latest version of STS (3.1.0), I tried many ways suggested, and find only the Eclipse Virgo/Tooling wiki works.
(http://wiki.eclipse.org/Virgo/Tooling#Install_Eclipse)
It adds the EclipseRT/Virgo adapter in STS 3.1.0.