I have also been considering such an idea. I have not spent the time to look into Cocoon's architecture in enough detail yet, but it seems I would just need to set up my own class that performs all the duties that the Cocoon servlet performs.
I recently had the opportunity to meet with some other members of this list, and we tossed the idea around. Someone mentioned that there is currently work in progress to abstract the request/response model because of the command line interface. It would seem that if one wanted to use Cocoon as a data pipeline for a different type of application than command line or HTTP, one would want to sync up with the people doing this.
My particular idea was to repurpose Cocoon's pipeline architecture as an EAI front end. That is, it would be responsible for communications between organizations and applications. I have recently been looking around to see if there is any other appropriately licensed software that is more suited to this particular use case, but so far haven't found any. However, I have found the werkflow project to be interesting if considered in conjunction with Cocoon.
Anyone else been thinking along these lines?
-- Ryan Hoegg ISIS Networks http://www.isisnetworks.net
Luca Zago wrote:
Hi Laurent,
yes sure, this is for sure a workaround. Bu my doubts are more about the architecture of cocoon. For example how to implement a service that take an xml from a source and write it on dB without sending the request by an HTTP Connection? Is it possible to make an XML persistence (like a serializer could be) to a relational DB?
Cocoon could have all the methods to do it, through a configurable pipeline for example, I was wondering if it could be possible to do it by an API outside the webapp framework?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
