> Since we add WB Bootstrap bean into top level deployment,
> that top level needs to see wb-core.jar (which is what wasn't
> happening with WBINT-16).
NB we have
https://jira.jboss.org/jira/browse/WBINT-17 which removes the
need for adding the jar into the deployment (it can just be a library
jar) which should mean that non-isolated CL will work (assuming we also
do
https://jira.jboss.org/jira/browse/WBINT-18).
The original idea was to add this dynamically depending on the version
of WB.
But since most of WB libs is already shared - part of wb.deployer folder
- I guess this is really no longer needed/useful.
Although I think we should re-visit this, once we do proper CL versioning,
so the users could actually run different versions on WB in single AS
instance.