http://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/
So it looks like our site and/or example is kind of bare bone and empty at the moment. So I think my demo site and Java service will be a good start. Right now they are separate J2EE applications using client side Javascript to call the Java DeviceMap service. Looking forward to getting it online on our dev server. I will keep everyone posted. ________________________________ From: Bertrand Delacretaz <[email protected]> To: [email protected] Sent: Tuesday, May 7, 2013 10:13 AM Subject: Re: DeviceMap Java API Hi, On Tue, May 7, 2013 at 3:52 PM, Reza <[email protected]> wrote: > -The oddr package is empty... Yeah, I forgot to remove that folder after moving the java classes to the org.apache.devicemap package - fixed in http://svn.apache.org/r1479913 > ...The example here makes use of oddr: > https://github.com/OpenDDRdotORG/OpenDDR-Java. > So this needs to be rectified and/or the example needs to be updated.... That's an OpenDDR example, we should have our own under http://incubator.apache.org/devicemap/ (which can be edited from https://cms.apache.org/devicemap/ and/or http://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/ ) > > -We have a maven project for the DeviceMap resources > (https://svn.apache.org/repos/asf/incubator/devicemap/trunk/openddr/data/) but > the Java API cannot load resources from a jar source. I havent looked deeply > at the code, but this is fixable. If this > functionality exists today, please guide me in the right direction.... It doesn't exist, you're correct - currently the tests under openddr/java use the maven-dependency-plugin to unpack the dependencies under target/devicemap, but you're right that loading data directly from a jar would be more convenient. > > -Make the project "zero configuration", or close to it. I would like to > simply add 2 dependencies to my POM > and then add 5-10 lines of code and be done. I think this is possible. The > dependencies would be DeviceMap > data (resources) and the DeviceMap Java API. We could even make a version of > the data called LATEST > which would always pull our latest DDR. This way you get the latest devices > on every compile (if you choose).... Sounds good to me. > -Streamline the Java API... I guess that depends how close we want to be to the w3c DDR spec - for my use cases I'd be happy with a simplistic interface like public Map<String, String> getDeviceProperties(String userAgent); which we can certainly support in parallel with the w3c DDR APIs. -Bertrand
