Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #32263

Java Library/SDK Best Practice

Show all headers | View raw

I work on an open source eCommerce platform and we are creating a native Java object that is designed to be a convenience object that will work over our API and allow for eCommerce sessions, and the ability to push and pull data.

I am not a full-time Java developer, so I'm wondering what the best / most common way to package up that java object and offer a download of it.

Right now I was thinking that a code sample might looks something like this:

// Import the Slatwall Java SDK
import Slatwall.*;
 
// Instantiate the SlatwallScope, to use as an API wrapper
SlatwallScope slatwallScope = new SlatwallScope( 'http://www.mySlatwallInstance.com/?authToken='205c1fd430fb4588bf5a5b82a03fe1af' );
 
// Load a Product Entity Object
SlatwallProduct product = slatwallScope.getEntity('Product', '8c06bbba048f4ce9ba36e23d10d38f13');
 
// Output the results of the Product
out.writeObject( product );

Any examples of companies that do this well would be greatly appreciated.  We're not talking about a complex thing, it's just a wrapper for a RESTful api and a few other pieces.

Back to comp.lang.java.programmer | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Java Library/SDK Best Practice greg@gregmoser.com - 2015-08-05 11:31 -0700
  Re: Java Library/SDK Best Practice Arne Vajhøj <arne@vajhoej.dk> - 2015-08-06 21:26 -0400

csiph-web