[
https://issues.jboss.org/browse/WFLY-1077?page=com.atlassian.jira.plugin....
]
Frank Langelage commented on WFLY-1077:
---------------------------------------
Now with wildfly.iiop in place, I see DEBUG messages, although category
"org.wildfly" is set to INFO. To get rid of the debug messages a category with
name "package org.wildfly.iiop" needs to be defined.
I think the Logger creation
IIOPLogger ROOT_LOGGER = Logger.getMessageLogger(IIOPLogger.class,
IIOPLogger.class.getPackage().toString());
in
iiop-openjdk/src/main/java/org/wildfly/iiop/openjdk/logging/IIOPLogger.java
should be changed, aligned with those in other subsystems.
15.01. 21:47:16,363 INFO [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#launchServices] WFLYIIOP0001: Activating IIOP
Subsystem
15.01. 21:47:18,803 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Starting service
jboss.iiop-openjdk.orb-service
15.01. 21:47:18,905 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Starting service
jboss.iiop-openjdk.ior-security-config
15.01. 21:47:22,710 INFO [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] WFLYIIOP0009: CORBA ORB Service started
15.01. 21:47:27,129 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Starting service
jboss.iiop-openjdk.poa-service.rootpoa
15.01. 21:47:28,759 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Starting service
jboss.iiop-openjdk.poa-service.irpoa
15.01. 21:47:28,766 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Starting service
jboss.iiop-openjdk.poa-service.namingpoa
15.01. 21:47:28,818 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Starting service
jboss.iiop-openjdk.naming-service
15.01. 21:47:29,090 INFO [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] WFLYIIOP0008: CORBA Naming Service
started
15.01. 21:47:29,120 DEBUG [package org.wildfly.iiop.openjdk.logging, WildFly: IIOP Openjdk
Subsystem, version 9.0.0.Alpha2-SNAPSHOT#start] Naming:
[IOR:000000000000002b49444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e3000000000000100000000000000f0000102000000000a3132372e302e302e31000dc800000039afabcb00000000220000000100000001000000000000000200000008526f6f74504f4100000000074e616d696e67000000000004726f6f741400000000000005000000010000002000000000000100010000000205010001000100200001010900000001000101000000002600000002000200000000000300000014000000000000000a3132372e302e302e31000dc900000014000000080000001a00000dc90000002100000030000000000000000100000000000000220000000000000000000000000000000000000000000000000000000000000000]
JDK ORB Subsystem
-----------------
Key: WFLY-1077
URL:
https://issues.jboss.org/browse/WFLY-1077
Project: WildFly
Issue Type: Feature Request
Components: IIOP
Reporter: Dimitris Andreadis
Assignee: Tomasz Adamski
Implement a JDK ORB subsystem that can act as a replacement for the JacORB subsystem.
AFAIK, most/all JDK ORBs are based on the Sun ORB.
Ideally the 2 ORBs (JDK & JacORB) would be both supported in case we need to go
through a transition period, or we need to support a particular interop scenario for which
interop communication has issues.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)