If you missed the first article in the series that focussed on the greater flexibility of the new classpath paradigm, in which the classpath that BBjServices uses internally can be completely independent of the classpaths that you can configure and use in your BBj applications, read " Getting on the Right (Class)Path" here.
The new classloader model is just one piece of the solution to replace Web Start with BASIS's Desktop Apps solution, and it is mostly unseen by users. But good performance should never go unnoticed, so stay tuned for the next article in this series, "Desktop Apps, a Zero Deployment Strategy", to learn about improvements that users are sure to see with their applications!
|