I am following hello world application of Amazon Web Services Simple Workflow Service. According to description #Activities annotation should have been able to generate two classes GreeterActivitiesClient and GreeterActivitiesClientImpl. But these classes has not been generated.
I have Enable annotation processing in project properties. I am using Eclipse Mars with Jdk 1.8. I have also installed AWS toolkit for eclipse, aspectj.
Can someone see where the problem is?
Some versions of Eclipse, (notably Mars and Neon), may fail to fetch the latest artifacts due to a bug in old versions of the Oomph plugin. To work around this issue:
Make sure that you’re using https://aws.amazon.com/eclipse/site.xml as the AWS Toolkit for Eclipse update site.
Delete the ~/.eclipse/org.eclipse.oomph.p2/cache/ directory to remove cached content.
Install the latest version of Oomph (Eclipse Installer).
Reference: Set up the Toolkit
Related
What's the difference between these
Eclipse with the Spring IDE plugin
Spring Tool Suite (STS) alone
I ask because STS says it's built on top of Eclipse, and I wonder what differences it has over simply using a plugin that adds similar functionality to "vanilla" Eclipse.
It's true, STS is built on top of Eclipse. The difference is only related to another products support from the STS installation, like Roo, Pivotal tc Server, Cloud Foundry and getting started guides, but you could also include this features in your Eclipse installation.
So STS gives a complete solution around Spring features and simplifies the developer environment install, that's the key difference.
As Martin Lippert explains in the forums:
"So you can end-up having the same features in STS and your existing
Eclipse installation after installing the STS features into it."
You could find more details on the Spring forums.
Details on features: STS features and Spring IDE plugin features.
Spring Tool suite has ready to go features specially designed to spring supported projects and cloud environment. And Eclipse is more generic where we've to add the plugins and extensions for our platform setup.
There is already an article about this in DZone Spring IDE and the Spring Tool Suite - Using Spring in Eclipse.
While the Spring IDE project provides a set of plugins for the Eclipse
IDE, the Spring Tool Suite comes as a ready-to-use distribution of the
latest Eclipse releases with the Spring IDE components pre-installed.
This includes the tc Server integration for Eclipse (another IDE
extension that is provided by Pivotal as an open-source project) and
various other additions to Eclipse that turn the pure Eclipse IDE into
a ready-to-use, best-of-breed environment for enterprise Spring
application development.
I am starting to develop WebApp using Spring Framework. For that I know I have to use Spring Tool Suite. I went to the Eclipse site for downloads but I am having trouble knowing wich of the four types of downloads suggested in the page below should I choose, sicnce none of them seem to have Spring in its features ?
http://spring.io/tools/eclipse
Any help ?
Just for your consideration I wrote the following tutorials about STS
Installing Spring Tool Suite
Configuring Apache Maven
Getting Started: IDE & Projects
Configuring The Java Working Set
Structuring The Workspace
Complete and more detailed tutorials, available here: Spring Tutorial
Spring Tool Suite is a different download. It can be found here: http://spring.io/tools/sts .
Unless you are using Java EE which btw stands for Enterprise Edition,
I'd recommend just going with
Eclipse Luna -> Eclipse IDE for Java Developers
In addition to the full distribution downloads on http://spring.io/tools/sts (they are ready-to-use Eclipse distributions with pre-installed Spring tooling) you can also use an Eclipse installation and go to the Eclipse Marketplace to install the Spring tooling into your Eclipse instance.
I'm running Eclipse Juno 4.2 (upgraded from Indigo 3.7), with the Spring Tool Suite tools installed. A while ago I had installed Spring Roo 1.2.2.RELEASE, and configured the Roo plugin to point to the 1.2.2.RELEASE runtime.
I would now like to upgrade to Spring 1.2.4.RELEASE, but cannot find the runtime anywhere. I've looked on the Spring site, but cannot seem to find a download link to it anywhere.
So a few questions:
1) Is the runtime still required as a separate download and do I still need to configure Eclipse to point to it separately?
2) Where can I download the runtime from?
3) Why do I need the separate runtime? Why is STS/Eclipse not smart enough to use the Roo artifact that is included in my maven project?
I still don't why I need the separate runtime to configure Eclipse, however, I did finally find a download link for the latest ROO packages: http://docs.spring.io/downloads/nightly/release-download.php?project=ROO
I am looking for a bit of Liferay/Glassfish assistance here.
I am currently using a Liferay 6.0.6 portal running on Glassfish 3.0.1 and developing in Eclipse 3.7 (Indigo). I have downloaded the Liferay IDE for Eclipse as well.
The trouble I am having is in actually developing in Eclipse against a Glassfish server. I cannot create an actual Liferay project in Eclipse because the wizard requires me to specify a Liferay-Tomcat runtime environment.
Now I realize that this is the only server that is supported for the Liferay IDE as it is clearly documented in multiple places on the Liferay website and various forums around the web. However, I seem to recall one site (which, of course, I didn't bookmark :/ ) that gave instructions on a workaround for using Glassfish within the Liferay IDE. I believe it had something to do with creating the initial project as a Tomcat project, then going behind the scenes and changing some configuration files' Tomcat references to point to my Glassfish server.
I have set up my Liferay SDK environment correctly, including the build.username.properties file. I have this file pointing to my Glassfish server.
#
# Specify the paths to an unzipped Glassfish bundle.
#
project.dir=C:\\DEV\\myworkspace
app.server.type=glassfish
app.server.dir=${project.dir}\\..\\bundles\\liferay-portal-6.0.6\\glassfish-3.0.1
app.server.deploy.dir=${app.server.dir}\\autodeploy
app.server.lib.global.dir=${app.server.dir}\\domains\\domain1\\lib
app.server.portal.dir=${app.server.dir}\\domains\\domain1\\applications\\liferay-portal
However, everytime I try to do a deploy through Eclipse...
...this build.username.properties file gets overwritten with Tomcat settings from the runtime environment.
app.server.type = tomcat
app.server.dir = C:\\DEV\\bundles\\liferay-tomcat-6.0.6\\tomcat-6.0.29
app.server.deploy.dir = C:\\DEV\\bundles\\liferay-tomcat-6.0.6\\tomcat-6.0.29\\webapps
app.server.lib.global.dir = C:\\DEV\\bundles\\liferay-tomcat-6.0.6\\tomcat-6.0.29\\lib\\ext
app.server.portal.dir = C:\\DEV\\bundles\\liferay-tomcat-6.0.6\\tomcat-6.0.29\\webapps\\ROOT
Is there somewhere else that I need to make a change in order to get Eclipse to recognize my Glassfish server?
Any help or tips would be greatly appreciated.
It is not currently possible to use a Liferay+Glassfish bundle directly as a runtime or server adapter in Eclipse with the Liferay IDE plugins. As you pointed out the only runtime and server adapters for Liferay IDE are the tomcat bundles. However, you can still use Liferay IDE to develop with Glassfish by using the following receipe with version 6.0.6 and current version of Liferay IDE.
Download Liferay+tomcat bundle
Configure it as a Liferay runtime
Create the project pointing to Liferay runtime
Go to Window > Preferences > Liferay > Installed SDKs, switch "update build.properties" option to Never
Launch Glashfish externally using startup script
Modify the build.properties in your SDK to point to Glasshfish as runtime
For deployment use the SDK deploy action just as you showed and it should be deployed to glassfish.
This should work for now. In the future, we will be adding support for Glassfish server to our Server Manager plugin that can be using with Liferay IDE and Liferay 6.1 for remote deployment and development, so it will work just like a local tomcat instance except it will be remote Liferay running on glassfish or jboss, or whatever you like. But right now the Server manager plugin in 6.1 beta4 only supports Tomcat6/7 and Jboss7. We hope to add Glassfish very soon.
I have an existing, fully functional Spring web application based on Spring 2.5.6 - developed using SpringSource Tool Suite 2.1.0.SR1.
Because I'd like to use REST I decided to upgrade to Spring 3.0.0.M4. After editing the dependencies in pom.xml and changing my code to reflect the API changes in Spring 3.0 I tried to publish my web app to a local server (SpringSource tc - a Tomcat derivate).
The result is an almost empty web app folder and therefore a non-functional app. The app's folder only contains WEB-INF/lib with all libraries required by the Maven dependencies.
After realising that something's broken, I created a new Spring MVC project (based on the default 2.5.6) and published it to the same server. No problems. I tried to adapt my project's files (.settings/*, .project, .classpath, .springBeans), but this didn't change anything.
I'm pretty lost right now. My guess is that STS doesn't handle 3.0 apps correctly. Any suggestions?
PS: I don't want to revert to 2.5 if it's not absolutely necessary. I don't need STS and tc so I don't have a problem using other tools, but it worked fine so far.
I run into this all the time using Eclipse Galileo and m2eclipse 0.9.8 and Tomcat with WTP. I think it is m2eclipse that is the culprit. The problem seems worse after switching from Ganymede. The work around is to run mvn to create the war and then copy the war contents from "target" to WTP's "wtpwebapps" directory. You can conveniently find this horribly long path by double clicking the server in the Servers view, and choosing "Open Launch Configuration" from there click on Arguments(?) tab I think and copy the catalina.home java property that is defined as an argument there.
The problem vanished with newer versions of STS. Additionally my development environment changed a bit since I posted this question, so I can't really tell what caused the problem.
For me, it looked like a weird hiccup inside STS.
Spring Tool Suite 2.1.0 claims partial support for Spring 3.0, though not for the REST features. According to the release, future releases will add full support. From the release statement:
Features
Support for milestones of Spring 3.0 including XML editing and validation, support for #Configuration and #Bean annotations
Future
Complete Spring 3.0 support including tools for developing RESTful web applications
Try deploying your app to embedded jetty. 'mvn jetty:run' with help you confirm if that there's nothing wrong with your build (that all the right manifests and deps are in place)