Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <23030099.337481278978769358.JavaMail.jira@thor>
Date: Mon, 12 Jul 2010 19:52:49 -0400 (EDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Created: (ARIES-356) Make jndi proxy creation more flexible
 and, in the aries context, optional
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Make jndi proxy creation more flexible and, in the aries context, optional
--------------------------------------------------------------------------

                 Key: ARIES-356
                 URL: https://issues.apache.org/jira/browse/ARIES-356
             Project: Aries
          Issue Type: Improvement
          Components: JNDI
    Affects Versions: 0.2
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 0.2


There are a lot of cases when the current proxy creation fails, such as when a class is in the set of interfaces we're trying to proxy.  We should:

1.allow using cglib to proxy classes.
2. if the class can't be proxied, and a proxy is required (in the osgi: namespace) leave it out
3. (behavior up for debate) in the aries:services namespace, if there is a problem proxying, just return the raw service.

An example of when a service can't be proxied is it is a final class such as javax.mail.Session.

There's discussion on the dev list about what is appropriate for (3).  I'm committing my proposal to give us something concrete to discuss.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.