What features does the Client Java Content DB Development Kit library offer over the regular Java bindings?
The client Java Content DB Development Kit library (cdb-devkit-client.jar) that supplements the standard Content DB Java Web Service bindings/stubs (content-ws-client.jar) was introduced to allow client code to run either in-process or remotely without having to make significant (or any) code changes. To achieve this, Oracle provides proxy classes that: • hide from developers the DAV server dependency for content upload/download // Java Example Code (using client Java Content DB Development Kit): FileManager fileM = … // source content stream InputStream is = … Item docDef = fileM.createDocumentDefinition( new NamedValue[] { ClientUtils.newNamedValue(Attributes.NAME, “test.doc”), // A client using standard auto-generated Web Service bindings CANNOT // utilize Options.CONTENTSTREAM in a createDocument[Definition]/updateDocument // call. Instead, they must make a PUT call to the Content DB DAV // Server using a HTTP client and use the JSESSIONID (session state) as // the Web Services
Related Questions
- I want to write a JavaBean for use as a pluggable component for the Forms Java Client. What version of the Java Development Kit (JDK) should I use?
- What features does the Client Java Content DB Development Kit library offer over the regular Java bindings?
- What features does the C# .NET Development Kit offer over auto-generated C# bindings?
