select * from A a where a.id in (select b.id from B b order by b.id)Hm. I don't see anything missing... Ok, let's remove the order clause, as it is not really needed:
select * from A a where a.id in (select b.id from B b)And, voilà! No ORA-00907. And it seems that I am not the only one having these troubles, see the blog entry by oraclequirks.
Kickstart for creating Java web project with the gradle buildtool.
The well known gradle init task is an easy way to create a Java project:
[520]% gradle init --type java-library
However, there is no support for initializing a web application. Alternatively, you may use the cool gradle-templates of townsfolk: https://github.com/townsfolk/gradle-templates.
How this may be done, is described below.
Create a master build.gradle script. This may be done anywhere. However, I use the project parent directory where all my projects are found:
buildscript {
repositories {
maven {
url 'http://dl.bintray.com/cjstehno/public'
}
}
dependencies {
classpath 'gradle-templates:gradle-templates:1.4.1'
}
}
apply plugin:'templates'
List the tasks:
> gradle tasks [...] Template tasks -------------- createGradlePlugin - Creates a new Gradle Plugin project in a new directory named after your project. createGroovyClass - Creates a new Groovy class in the current project. createGroovyProject - Creates a new Gradle Groovy project in a new directory named after your project. createJavaClass - Creates a new Java class in the current project. createJavaProject - Creates a new Gradle Java project in a new directory named after your project. createScalaClass - Creates a new Scala class in the current project. createScalaObject - Creates a new Scala object in the current project. createScalaProject - Creates a new Gradle Scala project in a new directory named after your project. createWebappProject - Creates a new Gradle Webapp project in a new directory named after your project. exportAllTemplates - Exports all the default template files into the current directory. exportGroovyTemplates - Exports the default groovy template files into the current directory. exportJavaTemplates - Exports the default java template files into the current directory. exportPluginTemplates - Exports the default plugin template files into the current directory. exportScalaTemplates - Exports the default scala template files into the current directory. exportWebappTemplates - Exports the default webapp template files into the current directory. initGradlePlugin - Initializes a new Gradle Plugin project in the current directory. initGroovyProject - Initializes a new Gradle Groovy project in the current directory. initJavaProject - Initializes a new Gradle Java project in the current directory. initScalaProject - Initializes a new Gradle Scala project in the current directory. initWebappProject - Initializes a new Gradle Webapp project in the current directory. [...]
As you can see, there are many different templates you may use. For our purpose, the createWebappProject task seems to be interesting.
Use the createWebappProject task for creating a new fresh web project. Invoke the task and answer some questions:
> gradle createWebappProject :createWebappProject templates> Project Name: (WAITING FOR INPUT BELOW) > Building 0% > :createWebappProjecttestweb templates> Project Parent Directory: [/Development/java/projects/projects-test] (WAITING FOR INPUT BELOW) > Building 0% > :createWebappProject templates> Use Jetty Plugin? (Y|n) [n] (WAITING FOR INPUT BELOW) > Building 0% > :createWebappProjectY templates> Group: [testweb] (WAITING FOR INPUT BELOW) > Building 0% > :createWebappProject templates> Version: [0.1] (WAITING FOR INPUT BELOW) > Building 0% > :createWebappProject BUILD SUCCESSFUL Total time: 25.877 secs
Check the generated files and directories:
> cd testweb/ > find . . ./build.gradle ./gradle.properties ./LICENSE.txt ./src ./src/main ./src/main/java ./src/main/resources ./src/main/webapp ./src/main/webapp/WEB-INF ./src/main/webapp/WEB-INF/web.xml ./src/test ./src/test/java ./src/test/resources
List the tasks:
> gradle tasks Build tasks ----------- [...] war - Generates a war archive with all the compiled classes, the web-app content and the libraries. [...] Web application tasks --------------------- jettyRun - Uses your files as and where they are and deploys them to Jetty. jettyRunWar - Assembles the webapp into a war and deploys it to Jetty. jettyStop - Stops Jetty. [...]
Create the landing page:
> echo "Hello" > src/main/webapp/index.html
And finally, run the web application in Jetty:
> gradle jettyRun Starting a new Gradle Daemon for this build (subsequent builds will be faster). :compileJava UP-TO-DATE :processResources UP-TO-DATE :classes UP-TO-DATE > Building 75% > :jettyRun > Running at http://localhost:8080/testweb
Open your browser http://localhost:8080/testweb/ and you should see the welcome message.
private static final Logger logger = LoggerFactory.getLogger(XXX.class); by hand to your Java classes is tiring.
private static final Logger LOG
= LoggerFactory.getLogger(${enclosing_type}.class);
${:import(org.slf4j.Logger,org.slf4j.LoggerFactory)}
Note, that there are two import statements, one for the Logger and another for the LoggerFactory class.
~/Google\ Drive/:cd ~/Google\ Drive/ mkdir projects cd projects mkdir my_project.git cd my_project.git git init --bareIn the test project workspace, a project is added to the repository as follows:
cd my_project git init git add * git commit -m "My initial commit message" git remote add origin ~/Google\ Drive/projects/my_project.git git push -u origin masterNow I can clone the project:
git clone ~/Google\ Drive/projects/my_project.git cd my_project
boot2docker up
var express = require('express');
var DEFAULT_PORT = 8080;
var PORT = process.env.PORT || DEFAULT_PORT;
var app = express();
app.get('/', function (req, res) {
res.send('Hello World\n');
});
app.listen(PORT)
console.log('Running on http://localhost:' + PORT);
Create the Docker package.json file:
{
"name": "docker-centos-hello-world",
"private": true,
"version": "0.0.1",
"description": "Node.js Hello World app on CentOS using docker",
"author": "Daniel Gasienica",
"dependencies": {
"express": "3.2.4"
}
}
Create the Dockerfile:
FROM centos:6.4 RUN rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm RUN yum install -y npm ADD . /src RUN cd /src; npm install EXPOSE 8080 CMD ["node", "/src/index.js"]The layout of your directory should be as follows:
> ls Dockerfile index.js package.jsonBuilding the image:
docker build -t peter/centos-node-hello .Verify if the image exists:
docker imagesThis should print:
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE peter/centos-node-hello latest 6c55823e6868 4 hours ago 672.2 MB
docker run -p 49160:8080 -d peter/centos-node-helloThe option
-p exposes the port 8080 to 49160. This is essential. Without that, the server is not visible to a client.docker psYou should see:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 578bd01b0407 peter/centos-node-hello:latest node /src/index.js 4 hours ago Up 2 hours 0.0.0.0:49160->8080/tcp jovial_feynmanInspect the image:
docker inspect 578bd01b0407You should see a JSON output showing all relevant information:
...
"PortBindings": {
"8080/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "49160"
}
]
}
...
If the -p was not given when starting the process, HostPort would have been null and the application would not have been visible to clients.
Test it:
curl localhost:49160Now you should see:
Hello World.Stop and start the process again:
docker stop 578bd01b0407
docker ps doesn't show the process any more. docker ps -a lists the process as Exited:
> docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 578bd01b0407 peter/centos-node-hello:latest node /src/index.js 12 minutes ago Exited (143) 9 seconds ago jovial_feynmanSo, start it again:
docker start 578bd01b0407Test if the process is running:
> docker -ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 578bd01b0407 peter/centos-node-hello:latest node /src/index.js 14 minutes ago Up 2 seconds 0.0.0.0:49160->8080/tcp jovial_feynmanCheck the logs:
> docker logs 578bd01b0407 Running on http://localhost:8080 Running on http://localhost:8080
> mkdir tmp > cd tmp > curl -f -o ./ld.tgz https://get.docker.io/builds/Darwin/x86_64/docker-latest.tgz > gunzip ld.tgz > tar xvf ld.tar > sudo cp usr/local/bin/docker /usr/local/binSpecify the docker deamon Host for the client:
export DOCKER_HOST=tcp://127.0.0.1:4243
> boot2docker init
2014/06/06 09:51:37 Downloading boot2docker ISO image...
2014/06/06 09:51:38 Latest release is v0.9.1
2014/06/06 09:52:01 Success: downloaded https://github.com/boot2docker/boot2docker/releases/download/v0.9.1/boot2docker.iso
to /Users/peterkeller/.boot2docker/boot2docker.iso
Generating public/private rsa key pair.
...
2014/06/06 09:53:03 Creating VM boot2docker-vm...
2014/06/06 09:53:04 Apply interim patch to VM boot2docker-vm (https://www.virtualbox.org/ticket/12748)
2014/06/06 09:53:04 Setting NIC #1 to use NAT network...
2014/06/06 09:53:04 Port forwarding [ssh] tcp://127.0.0.1:2022 --> :22
2014/06/06 09:53:04 Port forwarding [docker] tcp://127.0.0.1:4243 --> :4243
2014/06/06 09:53:04 Setting NIC #2 to use host-only network "vboxnet0"...
2014/06/06 09:53:04 Setting VM storage...
2014/06/06 09:53:10 Done. Type `boot2docker up` to start the VM.
Running the deamon:> boot2docker up 2014/06/06 09:55:23 Waiting for SSH server to start... 2014/06/06 09:55:47 Started. 2014/06/06 09:55:47 To connect the Docker client to the Docker daemon, please set: 2014/06/06 09:55:47 export DOCKER_HOST=tcp://localhost:4243Test:
> docker version Client version: 0.11.1 Client API version: 1.11 Go version (client): go1.2.1 Git commit (client): fb99f99 Server version: 0.11.1 Server API version: 1.11 Git commit (server): fb99f99 Go version (server): go1.2.1Setup forward network ports. According to the documentation, the boot2docker VM must be powered off for this to work:
> boot2docker stopRun following script (this takes a while):
for i in {49000..49900}; do
VBoxManage modifyvm "boot2docker-vm" --natpf1 "tcp-port$i,tcp,,$i,,$i";
VBoxManage modifyvm "boot2docker-vm" --natpf1 "udp-port$i,udp,,$i,,$i";
done
Starting docker VM again and login using ssh:> boot2docker up > boot2docker sshThen you should see:
wildfly-camel-installer-1.0.0.Alpha1.jar