It should work with 1.6, but I only test web stuff with tomcat7 these days, so I bumped it upto java7.
All the other comments are pretty trivial, so feel free to make the changes. Just please test any changes on an app server (preferably tomcat6/7) to make sure nothing breaks... very important. ________________________________ From: Werner Keil <[email protected]> To: "[email protected]" <[email protected]>; Reza <[email protected]> Sent: Thursday, July 24, 2014 11:17 AM Subject: Re: java webservice example Is it necessary e.g. for additional dependencies like Spring to use JDK 1.7? The actual POM's version is just 2 rather than 3 digits. not horrendous, but it would be great to have the DM projects in sync on that, similar using a parent POM here, either that of the parent project or the Apache master. The "console" project I already created a few days ago also uses Classifier, so at least these two with an identical set of dependencies should be treated as a group, otherwise there will be a "version hell" among different components Werner On Thu, Jul 24, 2014 at 4:55 PM, Reza <[email protected]> wrote: I checked in a java webservice example, it uses plain servlet: > >http://svn.apache.org/viewvc/incubator/devicemap/trunk/examples/servlet/ > > >Its running here: > >http://devicemap-vm.apache.org/dmap-servlet/ > > >direct call: > >http://devicemap-vm.apache.org/dmap-servlet/classify > > >Im going to do a Spring example too, probably over the weekend. It will pretty >much be the same, except it will use a Spring controller. Also, this example >uses the 1.1 version of the dmap java client. The toString() method of the >v1.1 Device object outputs valid json, so its easier to work with than having >to manually generate this json. > >I need to add an init.d script to tomcat, if the vm restarts, tomcat wont >start, this is probably why the service keeps on disappearing in the past. >
