Thanks, Remember back in windows C++ time with dll hell. Now we got a new language, and also introducing a new dependency hell :-)
Working one a large middleware system I now all about jar dependency hell and versions. The main problem we saw its the huge number of configurations files for library(componets) jars, they are just everywhere. A library should not require an own configuration file, it sould be possible to configure a component through system properties or a static singleton. Every component should not trust other componets, ie: be sure that the correct version are used, correct parameters are beeing passed. >From how I understand .Net they have a much better solution on this with versions and linking. Hopefully the JSR 277 (Java Module System) will guide us out of dependency hell. Since the java plugin server and the clean java api will save me a lot of time in an upcomming project I have some more questions. Hopefully I get some answers :-) Can you specify a log level for one plugin? Ie: you want DEBUG level for plugin YY, but ERROR for pluigin ZZ? (I count on that your using log4j for logging :-) Can you load C plugins from the java plugin server? Easier to maintain one distinct plugin server. Does the java plugins get loaded when the pluginserver starts, or when its first get accessed? -- Jarl On 7/26/07, Papolu, Appajee <[EMAIL PROTECTED]> wrote: > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
