[jbossts-issues] [JBoss JIRA] (JBTM-934) Ensure that Narayana (trunk) can build a JTS that works with the JDK ORB

[Michael Musgrove (Commented) (JIRA)]

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

Michael Musgrove commented on JBTM-934:
---------------------------------------

Thanks to Tom for pointing out that we must use the version of orb.idl supplied with the compiler (it's allowed to be non portable).

The other issue is that idlj (the compiler distributed with the standard JDK) does not support the local keyword. This keyword is used by ArjunaJTS/jts/idl/omg/XA.idl (interface Connector and CurrentConnection which we don't use, and if we did they would simply have to be treated as non-local).

The svn commit for the pom changes removes the local keyword from these two interfaces.

To use the idlj compiler build with the profile -P idlj
The jacorb profile is active by default.
                
> Ensure that Narayana (trunk) can build a JTS that works with the JDK ORB
> ------------------------------------------------------------------------
>
>                 Key: JBTM-934
>                 URL: https://issues.jboss.org/browse/JBTM-934
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Build System, JTS
>            Reporter: Tom Jenkinson
>            Assignee: Michael Musgrove
>             Fix For: 5.0.0.M2
>
>
> It is suggested to make use of *maven profiles* that determine which ORB to test against and potentially build against.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira