Noel, I'm in favour of a JCA deployment option because it would let people embed mail functionality in J2EE applications making it available to systems assembled from J2EE components.
The big win this would have would be that administrators wouldn't have to get right out of their comfort zone, the email functionality could be monitored and operated through the same administration toolsets they currently use for managing their *other* J2EE applications. The cost of ownership of James isn't all about through-put and hardware, it is also about the cost of administering applications and training, and retaining, specialist administrators. If James installations could be administered by people with a commonly available skills profile, and tools which are already in place, it would be a real benefit. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
