-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
Migration guide: Section: 3.2. JacORB Subsystem Configuration Changes
Currently there is information about jacorb attributes in this way
The following element attributes are no longer supported and must be removed. Table 3.1. Attributes to Remove Element Unsupported Attributes <orb> client-timeout max-managed-buf-size max-server-connections outbuf-cache-timeout outbuf-size connection retries retry-interval name server-timeout <poa> queue-min queue-max pool-size max-threads The following on-off properties must be set to "off" or be removed. Table 3.2. Attributes to Turn Off or Remove Element Attributes to Set to Off <orb> cache-poa-names cache-typecodes print-version use-bom use-imr <interop> (all except sun) comet iona chunk-custom-rmi-valuetypes indirection-encoding-disable lax-boolean-encoding strict-check-on-tc-creation <poa/> monitoring queue-wait
This is quite strange. I haven't caught why there is information about attribute to be set off or remove. From my testing I can say that this is list of the attributes which are deprecated and will not have any runtime effect. That means they should be removed from orb configuration (it will be done by migrate operation in case). Personally I don't see why they should be set as off when they are not a part of the model. But I can be wrong here.
strict-check-on-tc-creation
use-imr
comet
name
pool-size
max-threads
cache-poa-names
use-bom
max-server-connections
cache-typecodes
max-managed-buf-size
iona
indirection-encoding-disable
client-timeout
chunk-custom-rmi-valuetypes
queue-min
queue-max
retry-interval
queue-wait
print-version
outbuf-cache-timeout
server-timeout
outbuf-size
monitoring
sun
retries
lax-boolean-encoding
Then later on there should be mentioned that most of attributes that were in jacorb subsytem configured with values on or off is now in openjdk iiop subsytem configured with values true and false instead.
Other thing is that some values that are valued by enumeration was changed in possible values as well. For example transactions could be set as on, off, spec and in openjdk orb are permitted values full, none, spec.
- duplicates
-
JBEAP-2621 Migration guide: ORB - document what is replacement for missing configuration options from JacORB to OpenJDK ORB
- Closed