• SBT SDK vs ExtLib sbt packages?

    By Fero Kossuth 1 decade ago

    I am trying to figure out how to access Connections data with SSO (still no success) and found that Extlib introduced SBT packages prior to SBT SDK with name com.ibm.xsp.extlib.sbt, and SBT has its own packages: com.ibm.sbt. No big deal, but some demo databases use extlib implementation (Social Enabler), others SBT implementation (SBT Playground).

    What implementation should I use in my code?

    Will be Extlib converted to SBT? For example endpoints from mentioned APIs are incompatible if accesed by @Endpoint() function (for obvious reason).

     

    • Depends on your use case...

      By Philippe Riand 1 decade ago

       

      Good question.

      The work started with the extension lib, and then moved to the SDK which is not specific to Domino. The move required some code refactoring, thus the package names and some features changed. Now, because all the enhancements go to the SDK, we are in the process of consuming the SDK from the extlib, and removing the original classes in the extlib. I don't have an ETA yet, but I hope that this can be done in the next few weeks. When done, the old classes from the extlib will be removed.

      This leads to this answer: if you need some features that are specific to XPages (ex: the REST datasource), then you have to use the extlib, and then you have to adapt your code when the SDK will be merged into the extlib. Else, you should directly use the SDK.

      • Good to know

        By Fero Kossuth 1 decade ago

        Thanks. Any thoughts about what endpoint to stick to? ExtLib controls require its own implementations, SBT SDK ones do not work with ExtLib SBT related datasources (xe:connectionsData for example).

        • If you want to use XPages...

          By Philippe Riand 1 decade ago

          then you have to use the Xpages implementation, or wait a few weeks until we get that merged.