Details
-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.DR8
-
None
Description
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
<subsystem xmlns="urn:jboss:domain:jacorb:1.4"> <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl"> <initializers transactions="spec" security="identity"/> </orb> </subsystem>
I think that the IIOP OpenJDK subsystem should define the socket binding as well. I mean instead of
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0"> <initializers transactions="spec" security="identity"/> </subsystem>
the default configuration could be
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0"> <orb ssl-socket-binding=\"iiop-ssl\" socket-binding=\"iiop\"/> <initializers transactions="spec" security="identity"/> </subsystem>
Attachments
Issue Links
- is cloned by
-
-
- Closed
-
