Preferred classes are used for the proxy's currently, the jsk-dl.jar in
our current build is included in proxy codebase annotations, this is to
ensure that com.sun.* namespace implementation classes are loaded by the
proxy ClassLoader.
In the modular build, we have a dependency relationship wh
On 2/15/2011 4:29 PM, Gregg Wonderly wrote:
On 2/13/2011 6:13 PM, Calum Shaw-Mackay wrote:
What about using a standard html param that indicates the java version?
Would this allow those that support this different version to be transparent
for those services that support it, whilst allowing ensu
On 2/13/2011 6:13 PM, Calum Shaw-Mackay wrote:
What about using a standard html param that indicates the java version?
Would this allow those that support this different version to be transparent
for those services that support it, whilst allowing ensuring non-breaking
compatibility with those se
On 2/12/2011 7:10 AM, Niclas Hedhman wrote:
On Sat, Feb 12, 2011 at 8:41 PM, Mike McGrady
wrote:
Isn't OSGi now distributed? See Fuse 4.0.
OSGi has a specification for remote services and how to express
capabilities vs requirements, but the actual transport as such is left
out, and it hooks
Since there can be three different class loaders in play (1), 1) the service's,
2) the UIDescriptor's and 3) the clients classpath, we have to account for this
in the end. Many times the ServiceItem.service object and the UIDescriptor(s)
share the same codebase so there will only be two class
River-trunk-QA-solaris is reconfigured.
River-trunk-QA-windows is reconfigured.
River-trunk-QA-ubuntu is reconfigured.
Gr. Sim
