Woof! In the beginning, we looked at JAIN-SIP and saw that it was good.
So we embarked on a project to use it, and thus begat sipXpage. Then we hired the main developer of JAIN-SIP (Hi Ranga!) and saw that he was good, and asked him to build a bridge, and that begat sipXbridge (I don't think we spec'ed it in Cubits however). And later, sipXconfig started using JAIN-SIP, as it was good (alas, no begatting as sipXconfig already existed). But lo-and behold, all three projects were using different versions of JAIN-SIP, and there was duplication and confusion reined. But then, Marden spoke saying "Let's put all this into sipXcommons", and so he did, checking in a jar file with all the JAIN-SIP goodness, and there was much rejoicing. And later JAIN-SIP became a "Dependency" and begat an RPM that was named after it. And that RPM is available in the sipxecs-unstable yum repository, and it is good. And the great book Wiki calls out that developers should install this RPM least they be found wanting. But things are not always as they seem, and evil lurks in the code base at every turn, as one can still find a jain-sip jar file checked into the sipXcommons/lib directory, and it seems that THAT particular version of JAIN-SIP is what is used during development builds and installs...which isn't always the same as the RPM version that was in /usr/share/java/jain-sip, and so there is much confusion in the land, with developers dodging fire and brimstone trying to track down version issues between the two. So this very confused developer is trying to determine if the sipXcommons version of the jain-sip jar is indeed supposed to be there, and if so, is the great book Wiki incorrect (blaspheme!) and developers should NOT install the jain-sip RPM. Or instead are the config.propertes.in files of sipXpage and sipXbridge incorrect, and just have not yet been modified to pick up the RPM version that is expected to be installed? (I won't go into that heretical sipXconfig's way of finding jain-sip, mainly as it is incomprehensable to lay persons, being written in the original Aramaic of autoconf M4 that only the high priest understands). In the end I find that RPM installs use a different version of JAIN-SIP than that with which I develop, and this may explain why I cannot reproduce issues seen by sipXpage users in the field. Or Not. Oh wise and merciful keepers of JAIN-SIP, can you point the way to salvation for this confused and weary pilgrim? --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
