Serge Knystautas wrote:
On 4/21/06, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
Stefano Bagnara wrote:
Why don't we simply put the mailet in the Jar and import the package in
config.xml ?
A mailet already is a class that handle a mail and could be able to send
the message to remote service.
one has to write a new mailet for each remote service type.
if this mailet is integrated within the James code base you have to link
to the remote service interfaces at build time. this is fine but leads
to third-party-lib pollution.
It sounds like I'm the only one interested in bundling these third
party libraries.
So long as licensing issues are addressed, I don't
see the downside to including jars that are used by optional mailets.
3rd party integration is an excellent thing.
probably many James adaptors do it already or would want to do it in an
easy & supported way. its good to have working samples.
as for the downsides: 3rd party libs evolve, receive bugfixes, change
APIs. it could become hard to track down which versions are supported if
few people use the feature or there are no automated tests for it.
but generally I am pro making those integrations available in a
convenient way.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
