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
Serge Knystautas wrote:
On 4/20/06, Steve Brewin [EMAIL PROTECTED] wrote:
Serge Knystautas wrote:
Guys,
I was going to commit this, but wanted to run it by you
just since it
introduces another dependency.
Ugh! Surely this is an optional feature. If people want to
use
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.
On 4/22/06, Steve Brewin [EMAIL PROTECTED] wrote:
My concern wasn't really related to size. It was with creating a dependency
on a new and cool but not yet widely used API. In the same way as others
have expressed concern that we should not jump 'out of the fire in to the
frying pan' [old
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.
Maybe we should support fully qualified class names in the class
attribute for our mailets in
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
interesting aspect to have a RPC-mailet. maybe this could be done with a
more generic approach: a mailet which takes as configuration parameters
a. a jar (hessian.jar, activemq.jar, whatever is neccessary) which it
loads on its own
and
b. a class contained within the jar which is instantiated
On 4/20/06, Bernd Fondermann [EMAIL PROTECTED] wrote:
interesting aspect to have a RPC-mailet. maybe this could be done with a
more generic approach: a mailet which takes as configuration parameters
a. a jar (hessian.jar, activemq.jar, whatever is neccessary) which it
loads on its own
and
b.
Serge Knystautas wrote:
Guys,
I was going to commit this, but wanted to run it by you just since it
introduces another dependency.
Ugh! Surely this is an optional feature. If people want to use it only then
should they need to add the dependencies.
If and when we move to OSGi, choosing to
Guys,
I was going to commit this, but wanted to run it by you just since it
introduces another dependency.
The biggest challenge I face with developing mail-apps is that it's a
pain to restart James and manage all the dependencies. Also, my
mail-apps are typically just feature extensions of a
Serge Knystautas wrote:
I was going to commit this
-1, please, because:
it introduces another dependency.
I'd rather not introduce that dependency. HOWEVER, we have been talking
about the fact that we have much better support for multiple Mailet
packages, and I would be +1 to add this to an
11 matches
Mail list logo
