You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by ji...@apache.org on 2004/06/14 17:55:09 UTC

[jira] Resolved: (JAMES-297) Expose component manager in org.apache.james.James to support Avalon powered Mailets

Message:

   The following issue has been resolved as WON'T FIX.

   Resolver: Danny Angus
       Date: Mon, 14 Jun 2004 8:54 AM

The Mailet API will never expose Avalon. Ever, period.
James currently does, but it is important to realise that James implements the Mailet API using Avalon, but there is no dependance by the Mailet API on any API's other than those provided in J2SE & J2EE.
There is a plan in hand to implement JNDI in James for service access, this could be used to register and look-up avalon resources in a non "vendor specific" way.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-297

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-297
    Summary: Expose component manager in org.apache.james.James to support Avalon powered Mailets
       Type: Improvement

     Status: Resolved
   Priority: Minor
 Resolution: WON'T FIX

    Project: James
 Components: 
             James Core
   Versions:
             3.0

   Assignee: 
   Reporter: Albert Kwong

    Created: Sun, 13 Jun 2004 11:54 PM
    Updated: Mon, 14 Jun 2004 8:54 AM
Environment: Any

Description:
We are creating mailets that relies on Avalon components to provide services.  There doesn't seem to be any existing interface for accomplishing this task.  Thus, we suggest to add the resolve (key) and release (obj) methods.  

If we can add the methods to the MailetContext interface, that would be even better of course. :)


Example (org.apache.james.James)

    /**
     * Looks up an Avalon component.
     */
    public Object resolve (String key) throws MessagingException 
    { 
        try
        {
            return compMgr.lookup (key); 
        }
        catch (ServiceException e) { throw new MessagingException ("Failed to lookup component. key='" + key + "'"); }
    }

    /**
     * Releases an Avalon component.
     */
    public void release (Object obj) 
    { 
        compMgr.release (obj); 
    }



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [jira] Resolved: (JAMES-297) Expose component manager in org.apache.james.James to support Avalon powered Mailets

Posted by Stephen McConnell <mc...@apache.org>.
jira@apache.org wrote:

> Message:
> 
>    The following issue has been resolved as WON'T FIX.
> 
>    Resolver: Danny Angus
>        Date: Mon, 14 Jun 2004 8:54 AM
> 
> The Mailet API will never expose Avalon. Ever, period.

Dany - it seems to me that your confusing services with a component 
model.  Exposing a mechanisms on the mailet to lookup a service using a 
key does introduce any Avalon API.

Stephen.

-- 

|---------------------------------------|
| Magic by Merlin                       |
| Production by Avalon                  |
|                                       |
| http://avalon.apache.org              |
|---------------------------------------|

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org