Worklight application builder never finish execution in OS X - eclipse

I have created a test application (hello world and a button) using Eclipse and Worklight 6.2.
I have 3 environments: iphone, ipad and android.
My project also includes jQuery Mobile 1.4.4.
Everything is set up correctly (ADT, Xcode, Worklight).
When I right-click myApp -> Run As > Run on Worklight Development Server, I see on the right bottom of Eclipse "Worklight application builder running". The problem is that it never finishes...
What could be the cause? Any solutions?

Things to try:
Close Eclipse and kill the Java process via Applications > Activity Monitor
Close Eclipse and delete the your-workspace\worklightServerConfig folder
Then open Eclipse and try again to build the app.

Related

Can't Preview my mobilefirst application

I've created a project & application, and deployed successfully. But When I click Run As->Preview, it runs with no error and it is taking me to wordpad and pops up "Failed to load document".
If I run the project on server it again get deployed successfully but it is giving no output. How do I fix this?
Go over the Getting Started training materials in the MobileFirst Platform Developer Center: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started/
I am uncertain why you would even need XAMP here when you're using MobileFirst Platform. It is completely unneeded. Close it.
Open Eclipse Java EE Kepler/Luna and make sure that you have MobileFirst Platform Studio installed (you can obtained from the Eclipse Marketplace (help > marketplace)).
Then, click the mobilefirst button from the top toolbar and create a New MobileFirst project > application.
Right-click the generated application folder (your-project\apps\your-app) and select Run As > Run on MobileFirst Development Server).
Right-click the generated project folder and select Open MobileFirst Console
You should then see the console and by click "preview web resources" you will see the application's default template.
You can also verify the server is running by opening the Servers view in Eclipse and making sure to select the server and click the green 'play' button to start the server.
Also, try in the eclipse preferences to set the browser to an external one.

Debugging Eclipse plug-ins

This is my first attempt at creating an Eclipse plug-in. I've created one, along with a feature and update site. I set the target platform as my local Eclipse installation. When I run/debug the plugin from within the development environment everything works fine.
Now, my colleague installed the plug-in from the update site that I hosted. When he starts using any of the functionality exposed by my plugin he gets runtime exceptions.
He sees null pointer exceptions which didn't occur when I ran my plug-in project from my development environment.
I have a wizard that's part of my plug-in. When he close it he gets a "Unhandled event loop exception", and the wizard doesn't close. I didn't have this issue when I was running/debugging my plugin in my development environment.
Now I'm confused as to why the same plug-in is behaving differently in the production environment, as against the dev environment and when I was debugging it from my IDE. The target platform in both cases is the same Eclipse version. What could be the reasons?
And how do I debug the plug-in in a production environment? Is there a remote debugging capability for debugging the plug-ins on the production environment?
Any suggestions would be really useful!
To remote debug your plug-in, first add debug arguments to your target Eclipse .ini file
-vmargs
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
before launching it.
Then open another Eclipse instance with a workspace containing your plug-in project.
Open Run > Debug Configurations..., select Remote Java Application and create a new configuration.
As Project, browse and select your plug-in project.
Also fill in your connection properties (host of target Eclipse and port 1044).
Launching the newly created debug configuration allows you to debug your plug-in the same way you debug locally.
Now I'm confused as to why the same plug-in is behaving differently in
the production environment, as against the dev environment and when I
was debugging it from my IDE. The target platform in both cases is the
same eclipse version. What could be the reasons?
This is a classic: Eclipse plugins and RCP applications do indeed behave differently between PDT (the Eclipse IDE) and the exported product.
In your case, a NullPointerException thrown from the exported version but not from Eclipse is 9 times out of 10 an image or other resource files (properties, etc.) that is loaded by your code but is not listed in the build.properties of your plugin.
Anyway, you'll need to check the logs to retrieve the stacktrace and hunt down its cause. Such logs could be found in your friend's workspace under le .metadata/.log file
From your development workspace as it stands now, use the "Debug As -> Eclipse Application" menu item to startup a test workspace. When it starts up, you'll have two workspaces running: the original development workspace and the new test workspace. You can set breakpoints in your plugin code in the development workspace and run your plugin in the test workspace.
When your plugin execution in the test workspace gets to one of your breakpoints, execution will pause and you can use the Debug view in your development workspace to look at variables, set more breakpoints or anything else you want to do to debuf your plugin.
See the Apache Wiki for Developing with Eclipse.
Under Windows 10 with Tomcat running as a windows service I started:
tomcat8.5\bin\Tomcat8w.exe
& added in the Java tab as the first entry in Java Options to enable remote debugging:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n

After installing Blackberry Java plug-in in Eclipse cannot see the option for running the blackberry project

I have being developing application using android on Eclipse Helios(Windows XP).
Now i want to develop it for blackberry, and for that i found the following links
http://thinkingblackberry.com/?p=260
http://us.blackberry.com/developers/javaappdev/javaupdate.jsp
Now installation ran smoothly, i can see the blackberry installed in HELP -> ABOUT option in Eclipse. but when i started Eclipse i cannot see the option's for blackberry.
Have you tried the menu on the upper right border of eclipse?
Go to Window->Open Perspective->BlackBerry Application Development
There you have it.

How To Run JAR Application On NOKIA 6030?

I have a problem. I make an application in MIDP and then run it in wtk 2.2 it runs perfectly but when I use datacable and install the application using jad and jar on the mobile (NOKIA 6030); the application does not open. Can anyone help me on this?
Mobile Error = "invilied application delete this application?"
just open your project in Netbeans, right click on project & select properties. In left side select Second Option "PlatForm" and now in Right side change the version of MIDP Verion to 2.0 your problem will be solved. By Default NetBeans uses Midp-2.1 Version so this error is very common.

Stop running GWT application in development mode (in eclipse)

I'm developing a simple GWT application with eclipse. When I try to run it, it runs in development mode. How I can change its configuration and disable running in development mode?
From eclipse, choose the google tools icon from the toolbar, and then click the red toolbox to compile the code.
When it's compiled, run the project as normal. From this point, you can either run in development mode by including the gwt.codesvr=localhost:9997 argument on the url, or you can run in production mode by omitting the gwt.codesvr argument.
To be more concise: to run in production mode, just remove the gwt.codesvr argument from the url. If you get the error that your module "may need to be recompiled," go back to eclipse and choose the red toolbox icon to compile the code again.
I think you don't want to disable anything. Instead of running the application as a gwt application deploy the application in tomcat or some other servers. Then it will run as normal web application. Gwt application also a dynamic web project. Nothing extra in it.
From the question I am not able to identify whether you are using any build tool or not. Just incase if you are using maven build tool you have option to maven jetty plugin and execute the mvn jetty:run option.