There is point here that there could be troubles with migration of application from EAP 6.4.x to EAP 7.x as IIOP implementation has changed. The subsystem itself and JacORB as library provides a lot of configuration options [1] which aren't (probably) now available for EAP 7.0. If customer has used such settings he could be confused (annoyed).

It would be good to have a way or know a workaround how to convert jacorb settings to openjdk iiop.

For first there is for example a (long) list of subsystem attributes which were available in jacorb subsystem but are not in openjdk iiop. See

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
ior-settings=default/setting=transport-config
ior-settings=default/setting=as-context
ior-settings=default/setting=sas-context

Either some customers uses just settings of system properties to redefine JacORB behavior. In documentation [1] we have a bunch of config options (3.3 Configuration Properties
). Could OpenJDK IIOP covers that somehow?

[1] http://www.jacorb.org/documentation.html