Ulrich Mayring wrote:
>
> Berin Loritsch wrote:
> >
> > In it, you will find alot of userful information about the
> > inner workings of Avalon's Framework, and the design patterns
> > surrounding it. Because Avalon is what Cocoon is built on,
> > you will find out how and why Cocoon is architected.
> >
> > Please feel free to comment on the paper.
>
> Is there a particular reason why Cocoon2 is not integrated into Avalon
> as a .sar application or a block? I noticed some parts of Avalon are
> distributed with Cocoon2 in the form of an "avalon.jar" - is that the
> recommended way to distribute applications using the Avalon framework?
For Cocoon to be used as a Web service (aka Servlet), it must have all
the classes used. Therefore, it needs the avalon jars (avalon-framework.jar
and avalon-excalibur.jar). When it is embedded in a Avalon Phoenix server,
then it needs the .sar approach. At this time, there has been little
investment of time into making Cocoon an embedded service for Phoenix.
While it is possible, there really hasn't been a clammoring need for
it yet. If you are willing to put in the effort, then by all means,
we would be more than happy to have the assistance.
What needs to be done is a Phoenix specific implementation for Cocoon's
Environment interfaces--and publish the Service interface and write
a descriptor.
The hardest part is the Environment integration.
S/MIME Cryptographic Signature
