Claude Moore wrote:Thanks so much for your kindly answers.
On question 1) I thought that WorkLight Server may not require WebSphere, and times ago I was told during an IBM's presentation of WorkLight that Worklight may be installed in WAS as if it were a Java EE application, but I've no experience in that
(and I may have misunderstood something in that presentation), so I asked you about it.
On question 2) Liberty profile as far as I know - and please correct me if I'm wrong - is "limited" to support web related Technologies (no EJB for example, which I'm a fan of); it would be nice to have a preview of a full Java EE stack.
Anyway, we're discussing about web development so that Liberty would be perfect to experiment techniques you describe in your book.
Thank you again
Roland Barcia wrote:Worklight can run on a server like Tomcat, however, by default, it comes with a Liberty Profile and can install on top of Traditional WAS ND. When running on WebSphere, we have additional integration for example, using WebSphere Security like LTPA and such. In addition, we can invoke Java Code running in WAS from JS. if Worklight is sitting on different servers from your WebSphere Business Logic, than it can make Web Service or REST calls to get data.
The Worklight product uses lots of third-party libs (JPA, Spring, etc, etc.) so there is very high risk to get classes conflicts, and we were unable to resolve it with WAS classloader settings (parent last).
Claude Moore wrote:
By the way, Mikalai: did / do you use worklight yourself ? Would you like to share with us any experiences with it ?