Jason Webb wrote:
On a related note (and will I'm in that area) I'd like to depracate
remove(MailImpl)
remove(String)
And replace them with remove(collectionString)
I would like to promote remove(collectionString) as the primary access
method for repositories, rather than the single remove
Serge,
I committed on August 18 a change to sqlResources.xml to become mail attributes
enabled by default.
As I'm now using a very slow and expensive Internet connection (using my cell phone as
a modem), I have to wait until beginning of September to write a comprehensive note in
wiki about
I'd like to depracate
remove(MailImpl)
remove(String)
And replace them with remove(collectionMailImpl)
There are sufficient cases where single remove is natural in the API. I'd
sooner deprecate remove(String), and eventually make it private. But that's
not practical, yet, either. In
Adding commands to the remote manager to enumerate what matchers and
mailets are available. Something like:
listmatchers
Matchers are available from the following packages
[,org.apache.james.transport.matcher]
AttachmentFileNameIs
...
and then listmailets.
Just thought I'd throw it out.
--
Nice thought. Want to bugzilla it?
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22610.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
