mirror of https://github.com/apache/jclouds.git
43f357e1bd | ||
---|---|---|
.. | ||
src | ||
README.txt | ||
pom.xml |
README.txt
==== Licensed to jclouds, Inc. (jclouds) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. jclouds licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ==== This sample is a "port" of jclouds-demo-gae-tweetstore with the initial context setup and wiring carried out with Spring. It is intended to demonstrate how to integrate jclouds into your Spring application. It should not be regarded as a sample of how to write a web application using Spring, however! The original jclouds-demo-gae-tweetstore has been modified in as few places as possible; it has not been rewritten in the style of a Spring MVC application. A guide to generating Twitter consumer keys and access tokens is at http://tinyurl.com/2fhebgb This sample uses the Google App Engine for Java SDK located at http://code.google.com/p/googleappengine/downloads/list Please unzip the above file and modify your maven settings.xml like below before attempting to run 'mvn -Plive install' <profile> <id>appengine</id> <activation> <activeByDefault>true</activeByDefault> </activation> <properties> <appengine.sdk.root>/path/to/appengine-java-sdk-1.4.2</appengine.home> <appengine.applicationid>yourappid</appengine.applicationid> </properties> </profile> <profile> <id>keys</id> <activation> <activeByDefault>true</activeByDefault> </activation> <properties> <test.aws-s3.identity>YOUR_ACCESS_KEY_ID</test.aws-s3.identity> <test.aws-s3.credential>YOUR_SECRET_KEY</test.aws-s3.credential> <test.cloudfiles-us.identity>YOUR_USER</test.cloudfiles-us.identity> <test.cloudfiles-us.credential>YOUR_HEX_KEY</test.cloudfiles-us.credential> <test.azureblob.identity>YOUR_ACCOUNT</test.azureblob.identity> <test.azureblob.credential>YOUR_BASE64_ENCODED_KEY</test.azureblob.credential> <test.twitter.gae-tweetstore-spring.consumer.identity>YOUR_TWITTER_CONSUMER_KEY</test.twitter.gae-tweetstore-spring.consumer.identity> <test.twitter.gae-tweetstore-spring.consumer.credential>YOUR_TWITTER_CONSUMER_SECRET</test.twitter.gae-tweetstore-spring.consumer.credential> <test.twitter.gae-tweetstore-spring.access.identity>YOUR_TWITTER_ACCESSTOKEN</test.twitter.gae-tweetstore-spring.access.identity> <test.twitter.gae-tweetstore-spring.access.credential>YOUR_TWITTER_ACCESSTOKEN_SECRET</test.twitter.gae-tweetstore-spring.access.credential> </properties> </profile>