Future in Java

Thursday, November 9, 2017

dealing-with-non-fast-forward-errors
when we create a repository and then add a readme file to it then while pushing to it generates the error. I have not worked on its solution instead I created a new repository and did not add readme. then performed the following steps

goto to the root of the project folder ( check its properties by right clicking n it)
git init
git remote add origin https://github.com/javaiskool/springexamples.git
i got the error:
fatal: remote origin already exists.
i removed the error by using the following command
git remote rm origin
then
git remote add origin https://github.com/javaiskool/springexamples.git
git add .
git commit -a -m "initial commit"
git push -u origin --all
after that i created a readme.md file and described the example.
As the repository is public username and password were not asked

order has the details of customer,orderid,orderdate
orderline has the details about the order ie all the products that particular order contains ie same sone order can have multiple quantities of multiple products.
see the example

spring application can be found under debug menu in sts and hence it can be terminated here
if unable to create spring boot project inside STS 3.8.4 then goto start.spring.io
there Spring Initializer
click switch to full version
choose the required dependencies
download the zip
unzip it
open it in STS as new maven project
tutorial-spring-boot-application-development-using-sts.html

for consolidated billing we need to create the organization and the creator of the organization is the owner of the organization and can control the services of the other linked accounts.
for this the owner need to add account through the email or account id. if the invitee accepts the invitation then services of this account can be controlled by the organization owner.
details is as follows:
If you accept the invitation, the administrator of the organization can attach policy-based controls to your AWS account. The organization administrator can control which AWS services and APIs are allowed in this account for business reasons such as security or budgetary controls. These controls can include preventing this account from leaving the organization.