tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Created: (OPENEJB-280) Corba classes should be in their own jar
Date Sat, 07 Oct 2006 18:12:19 GMT
Corba classes should be in their own jar

                 Key: OPENEJB-280
             Project: OpenEJB
          Issue Type: Improvement
          Components: corba
    Affects Versions: 2.2
            Reporter: David Jencks
         Assigned To: David Jencks
             Fix For: 2.2

The corba classes in openejb-core should be in their own jar.  Then that jar can be a dependency
of both the yoko and sun corba integrations.  Currently yoko has to be included in the same
classloader as openejb-core so that UtilDelegateImpl can load its delegate using its own classloader:

    public UtilDelegateImpl() throws ClassNotFoundException, IllegalAccessException, InstantiationException
        String value = System.getProperty(DELEGATE_NAME);
        if (value == null) {
            log.error("No delegate specfied via " + DELEGATE_NAME);
            throw new IllegalStateException("The property " + DELEGATE_NAME + " must be defined!");

        if (log.isDebugEnabled()) log.debug("Set delegate " + value);
        delegate = (UtilDelegate) Class.forName(value).newInstance();

We might get some traction by using the TCCL here but I think it would be more reliable and
better structure to separate the corba classes into another jar.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message