Jarl Yes, while implementing stuff in Java and our impulse to use available libraries/infrastructure rather than creating our own -- had the unfortunate side effect of adding numerous JAR file dependencies (for example, to apache stuff, logging, rpc and so on). Given that we have not quite removed the native library dependencies -- in the end, the dependency list in fact is increased in 7.1 release.
Hopefully in a future release, not only we'll remove the native dependencies but also simplify the external jar dependencies (by building some kind of all-inclusive arapi jar file(s)). If any of you guys have ideas on jar dependency hell and simplifying it -- you're welcome to share those with us and recommend us pursue certain technique/idea/product(s) to simplify the AR API deployment bundle. Regards Appajee -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jarl Grøneng Sent: Wednesday, July 25, 2007 11:44 PM To: [email protected] Subject: Re: API libraries for Solaris on X86. Wow, this is just awesome! How many jars are needed to run a version 7.1 java program? I suspect tons of them :-) -- Jarl On 7/25/07, Papolu, Appajee <[EMAIL PROTECTED]> wrote: > Sure you can. > > In fact in the 7.1 Java API, we have implemented the necessary rpc version > mapping infrastructure as well, but it is validated for 7.0/7.0.1 only. What > that means is -- the client program runs the pure Java code in issuing AR > API's underlying RPC calls when interacting with servers of version 7.0 or > greater. However if the client is interacting with older servers (say 6.3 or > even older), then the Java API silently falls back to delegating the calls to > underlying JNI code, which in turn calls C API which has rich implementation > of RPC version mapping. All of this happens transparently to client program > any ways, so in essence, the Java API clients of 7.1 version can indeed talk > to same or older or newer versions of Server as were before. Only thing is > that for legacy server interactions, the Java API relies on its legacy > infrastructure (JNI/C API combo) in 7.1 release. In future, as indicated in > previous email note, this will change (i.e. improve RPC version mapping layer > within Java API) so that this native dependency is also eliminated. > > Hope this helps. > Appajee > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Jarl Grøneng > Sent: Wednesday, July 25, 2007 10:50 AM > To: [email protected] > Subject: Re: API libraries for Solaris on X86. > > Appajee, > > Can you connect from 7.1 java api to a 7.01 server? > > -- > Jarl > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
