Our Blog

Let us find tech solutions together

May 14

I gave a talk last night at the Orange County Java User’s Group (OCJUG) on Google App Engine development with the Java platform. This was the same one we gave at the Scandinavian Developer Conference in March. The whole talk stemmed from a good friend Eugene Ciurana being unable to attend, so I adapted his slides and did the talk.

One of the aspects I added was a demo showing how to deploy a Apache Wicket based web application to the dev server and then ultimately up to Google App Engine’s servers. In addition, the demo rather than show off the easy-to-use Eclipse plugin opts for using the App Engine SDK along with Maven to build. And we also use simpleds for persistence in the demo just to show an alternative to the JDO / JPA offerings that Google provides on top of Datastore.

With that, here is a snippet of the Maven pom.xml to grab all the required dependencies:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
<dependency>
    <groupId>org.extrema-sistemas</groupId>
    <artifactId>simpleds</artifactId>
    <version>0.9</version>
</dependency>

<dependency>
    <groupId>com.google.appengine</groupId>
    <artifactId>appengine-api-1.0-sdk</artifactId>
    <version>1.3.1</version>
</dependency>

<dependency>
    <groupId>asm</groupId>
    <artifactId>asm</artifactId>
    <version>3.1</version>
</dependency>

<dependency>
    <groupId>org.apache.geronimo.specs</groupId>
    <artifactId>geronimo-jta_1.1_spec</artifactId>
    <version>1.1.1</version>
</dependency>

<dependency>
    <groupId>javax.jdo</groupId>
    <artifactId>jdo2-api</artifactId>
    <version>2.3-eb</version>
</dependency>

<dependency>
    <groupId>org.apache.geronimo.specs</groupId>
    <artifactId>geronimo-jpa_3.0_spec</artifactId>
    <version>1.1.1</version>
</dependency>

<dependency>
    <groupId>org.datanucleus</groupId>
    <artifactId>datanucleus-jpa</artifactId>
    <version>1.1.5</version>
</dependency>

<dependency>
    <groupId>org.datanucleus</groupId>
    <artifactId>datanucleus-enhancer</artifactId>
    <version>1.1.4</version>
</dependency>

<dependency>
    <groupId>org.datanucleus</groupId>
    <artifactId>datanucleus-core</artifactId>
    <version>1.1.5</version>
</dependency>

<dependency>
    <groupId>com.google.appengine.orm</groupId>
    <artifactId>datanucleus-appengine</artifactId>
    <version>1.0.5</version>
</dependency>

Your mileage certainly may vary on versions, but as of this writing, slamming that into your pom.xml should get you cracking with simpleds for Google App Engine.

And in case you’re interested, here’s the presentation from last night and March’s talk at Scandev.

 - Google App Engine for Java

Enjoy!

Read more
May 04

In mid march I attended SDC2010 in Göteborg, Sweden. The event was very well attended with nearly 700 people and was filled with a wealth of great speakers. Some of the sessions I enjoyed were Matthew McCullough, Steven “Doc” List, Tim Berglund, and of course Kent Beck … too many to count. There definitely seemed to be an “agile” bend with a lot of the content … those folks sure do like to talk a lot :).

I presented on beginning Apache Wicket development, and here’s the presentation:

 -  <a href=”Rapid Application Development with Apache Wicket

Enjoy!

Read more
Mar 16

I’m currently in Europe speaking at Scandevconf.SE. And apparently some spammers have copied legitimate emails that I’ve sent to mailing lists with a signature line containing company phone numbers, and used this as seed content to pass through the usually pretty good spam filters.

Ordinarily this wouldn’t be against the norm for spammer sewer sludge, but since there are contact numbers in there, I’ve gotten several nasty text message and voicemails which are definitely filled with vile. And I don’t really blame them.

So if you get an email, and it’s obviously spam, and it has copies of our signature line on it, IT WASN’T US. We would never send emails that weren’t opt-in quality, and we’d like to string them up as much as you.

Read more