Guys... On 23/08/05, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > > Okay, so I guess there isn't really any advantage for us to > > spend the time to support this. If a common set of reusable > > processor plugins for both servers and standards that authors > > can use to assure compatibility for all Mailet 2.0 compliant > > servers isn't a realizable goal then I won't spend anymore > > time on this. Thanks for listening. > > Probably I've not been clear enough.
What are we really aiming for here, isn't it... Define service definitions for the _services_ (i.e. message persistence "store()", onbound transport "spool()", DSN "bounce()", whatever) which are required by Mailets and JBMS & agree a portable standard service lookup mechanism (using JNDI seems most obvious). We can then retreat to our corners, write competing container specific implementations and slug it out privately while our users see a convergence of approach from Apache & JBOSS which will hopefully end up with users having the ability to write portable mail processing code. If thats not what Andy's goal is what is it? It sure as hell ought to be "our" goal, I mean... it used to be, has anything changed that? d.
