[jboss-jira] [JBoss JIRA] (WFLY-1077) JDK ORB Subsystem

[Jason Greene (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945689#comment-12945689 ] 

Jason Greene commented on WFLY-1077:
------------------------------------

[~andrigmiller] - Sure it's good to look at all the options.

Right to solve these issues what we really need is a decoupled Oracle corba project. Unfortunately they only have two options, one tightly coupled to the JDK and one tightly coupled to glassfish. In the past we looked at both options and thought the JDK variant was better/easier to reuse. It looks like their model is that they fork the JDK orb every so often and add in glassfish hooks/features. So in theory we would basically do the same, fork off the JDK code every so often, try to minimize the code impact, and then sync it frequently with the JDK patch stream.

The problem with 3-4 is that IBM has their own orb in their JDK. So integrating with the IBM ORB would require different integration code. Aside from EJB integration, which requires access to JDK internals, Naryana for example had to do a lot of work to add support for the OpenJDK ORB, and I suspect it would be a similar undertaking for IBM.  Although we have not analyzed what would be required, but that might be a big task in and of itself since I'm not sure the source is even available.  So IMO, just building on what the JVM gives would actually amount to more development work, and more QE. Since internal classes have to be used, if the JVM vendor decides to rename a method or a package then we have to deal with it, potentially meaning component updates in CP releases. 

As to the bug fixes, there was a thread awhile back where Norman also wanted to get a serious NIO fix in, and Andrew Haley informed him that while we can expedite updates into the RHEL/Fedora builds we ship, it's hard to get OpenJDK to move faster with official builds. What really surprised me is that my update wasn't just on an issue tracker, it was merged into the official 8 tree and back ported into the 7 tree. They just kept doing smaller updates in between the merge and the release that finally included it, which were mostly security updates.


                
> JDK ORB Subsystem
> -----------------
>
>                 Key: WFLY-1077
>                 URL: https://issues.jboss.org/browse/WFLY-1077
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: IIOP
>            Reporter: Dimitris Andreadis
>            Assignee: Stuart Douglas
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira