Difference between revisions of "1.0.4 Release Notes"
From GCube System
Manuele.simi (Talk | contribs) (→Changes Related to Services) |
Manuele.simi (Talk | contribs) |
||
Line 4: | Line 4: | ||
:* ''configuration'': The gCore container is now defaulted to start with a service thread pool sized to 100; | :* ''configuration'': The gCore container is now defaulted to start with a service thread pool sized to 100; | ||
− | :* '' | + | :* ''gHN profile'': |
+ | ::* the RuntimeEnvironment section of the gHN profile is updated each the GHN is started; | ||
+ | ::* the name of the domain is now formed by the two last tokens of the host name (if available) or the complete IP address | ||
====Changes Related to Services ==== | ====Changes Related to Services ==== |
Latest revision as of 16:17, 26 November 2010
gCore 1.0.4
introduces the following changes:
Changes Related to the gHN
- configuration: The gCore container is now defaulted to start with a service thread pool sized to 100;
- gHN profile:
- the RuntimeEnvironment section of the gHN profile is updated each the GHN is started;
- the name of the domain is now formed by the two last tokens of the host name (if available) or the complete IP address
Changes Related to Services
- changes for managing pre-conditions on WS-Topics:
- WS Core 4.0.4 released in 1.0.3 has been fixed to manage some corner cases;
- registered custom
StreamHandlerFactory
to cope with Java's classloading bug
- registered custom
- fault management:
-
getCause
on aGCUBEFault
returns aThrowable
of the remote exception; - serialisation and deserialisation of full, recursive stack-trace as fault detail;
-
- fixings:
-
GCUBEWSLiteResource.transformParams()
returnsObject[]
instead ofObject
-
GCUBELocalHome
persists link count decrements on remove
-
- code clean up
- restored
setScope(thread,scope)
methods for binary compatibility with previous release
- restored