]
Tomasz Adamski commented on WFLY-5152:
--------------------------------------
TODO:
Subsystem iiop-openjdk should define port bindings in default
configuration
---------------------------------------------------------------------------
Key: WFLY-5152
URL:
https://issues.jboss.org/browse/WFLY-5152
Project: WildFly
Issue Type: Bug
Components: IIOP
Affects Versions: 10.0.0.Beta1
Reporter: Ondřej Chaloupka
Assignee: Tomasz Adamski
Priority: Minor
Default configuration that is shipped with EAP/WFLY for iiop-openjdk subsystem does not
contain port binding. This could be a bit confusing for users when looking on
configuration file and if they check for strings/ports {{iiop}} and {{iiop-ssl}} they are
not mentioned in configuration file. Course the name suggests what they are for but I
think that configuration file should avoid such implicit usage which came from default
values settings.
JacORB subsystem in EAP 6.4 looked like
{code}
<subsystem xmlns="urn:jboss:domain:jacorb:1.4">
<orb socket-binding="jacorb"
ssl-socket-binding="jacorb-ssl">
<initializers transactions="spec"
security="identity"/>
</orb>
</subsystem>
{code}
I think that the IIOP OpenJDK subsystem should define the socket binding as well. I mean
instead of
{code}
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0">
<initializers transactions="spec"
security="identity"/>
</subsystem>
{code}
the default configuration could be
{code}
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0">
<orb ssl-socket-binding=\"iiop-ssl\"
socket-binding=\"iiop\"/>
<initializers transactions="spec"
security="identity"/>
</subsystem>
{code}