Noel J. Bergman wrote:
What a timing! we are currently discussing exactly what is the best way to allow Cocoon to be run as a Mailet since that requires some architectural additions in the way Cocoon abstracts input and output.Chris,It is actually a fairly straightforward application of James. You'd want a matcher to pick up those messages (with the doc attached), a mailet that would extract the docs run it through some transform engine, and then emit messages with the revised content into the pipeline. What do you feel is missing from James? Some of the items you mention are protocols, not formats. For example, I can send SMS messages through a gateway provider using SMTP, as I do with Verizon. I'm also working on a Mailet to use AllTel's HTTP FORM gateway. All that is necessary is a delivery mailet, just as the RemoteDelivery mailet implements SMTP delivery. As for your transformations, since we use Avalon underneath, I am wondering how hard it would be to incorporate the Cocoon pipeline into James. I'll CC Stefano Mazzocchi to ask Stefano if he has any idea.
The cocoon architecture is designed to be abstracted from the input and output, but currently we implement two abstractions: servlet API and command line. Mailet API will be the next since Nicola is very interested in this as well.
Even Pier told me once that he would be interested in something like this since he is, in fact, already using XML->text serialization (but not thru Cocoon or James) to run the notification services his company runs.
The Cocoon dev team will be definately happy if the James people (or any other interested party) could help us in the process of deciding what is the best way of offering Cocoon services as a mailet.
A "standard way" for the web server to send a notification message would be, of course, to use a standard protocol designed for that purpose: SMTP. --- Noel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, December 30, 2002 16:37 To: [EMAIL PROTECTED] Subject: Notification server All, I'm looking for a generic "notification server" (receives an XML doc and user list and sends the doc formatted in a variety of ways using XSLT depending upon the destination - WAP, SMTP, SMS, instant messaging, HTML, etc). James seams like it can be used for this, but not explicitly designed for this (missing several formats that should be included for a generic notification server). This seams like a Jakarta kind of project, but James is about the closest thing I have found. Does anyone know of anything like this going on in the open-source community? Also, it seams like there should be a standard API for a web app to communicate with a notification server, so that the actual notification server implementation being used doesn't matter when coding the web app. I have looked around on javasoft and the JSR's, and haven't seen anything like this. Anyone know of anything like this in the works? Thanks, Chris
-- Stefano Mazzocchi <[EMAIL PROTECTED]> -------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
