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

[Tomasz Adamski (JIRA)]

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

Tomasz Adamski commented on WFLY-1077:
--------------------------------------

JBoss EAP (Jacorb) <-> Wildfly (IIOP-OpenJDK) compatibility test 2

Configuration:
Web application consisting of secure servlet and transactional EJB deployed on server A.
EAR with transaction EJB deployed on server B.
Execution:
1. User opens web browser and authenicates using basic logging.
2. Bean on server A authenticates Principal.
3. Bean on server A starts JTS transaction.
4. Bean on server A invokes remotely (using iiop) bean on server B.
5. Bean on server B authenicates Principal.
6. Bean on server B writes data to mock XAResource.
7. 2 phase commit protocol starts.
8. Byteman script kill server B during prepare.
9. Checks are made to assure that transaction has been rolled back on both servers.
Result:
There was a problem with reference narrowing which works differently in JacORB and Openjdk ORB.
After fix to narrow problem is made tests in jboss-eap=A;wildfly=B and jboss-eap=B;wildfly=A are passed - transaction is rolled back on both servers.
>From interoperability point of view it was important to check that IOR which is stored and used during recovery to construct object reference between two different ORB instances work correctly - it does.


> 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.8#6338)