what is the main difference between client SDK and plain Java client libraries?
Hi Everyone ,
May be the question sounds like odd , but i am not understanding clearly what is the different between client sdk and plain java client lib and their use cases ? In which scenario we opt for client SDK and whats the best scenario of using client java libs? any limitations are there ?
Thanking you..
Jyothsna.
Accepted answer
The SDK is packaged to be functioning as a target platform for the Eclipse Plugin Development Environment, including source code. The Plain Java Client Libraries are packaged as stand alone Java jars without source code.
The SCK has a server part, the Plain Java Client Libraries are client and common only.
See: https://rsjazz.wordpress.com/2013/03/14/what-apis-are-available-for-rtc-and-what-can-you-extend/
I always use the SDK. My development workspaces are all set up as in the RTC Extensions workshop. This gives me always the SDK source code visibility. All my projects are created as Plugin Projects which is key for the PDE to provide the SDK code visibility. Client applications have the Plain Java Client Libraries configured as user library to allow to run and debug them. A good example is the work item command line, that is developed using the SDK, but has the plain java client libraries in the build path and also requires the Plain Java Client libraries to be in the classpath when running it.
You use the plain java client libraries if you want to ship common and client API with your automation.