Yes, the power of xml is Soap. And actually this is the main reason
behind my question: web-services.

I have worked on xsp, like it and dislike it!

As i understand from this discussion, cocoon and struts are not
possible to integrate, or at least work together.

Thanks, Rabih.

--- In [EMAIL PROTECTED], "Oguz Kologlu" <[EMAIL PROTECTED]> wrote:
> There is actually a lot of work being done on cocoon.
>
> Cocoon in fact resembles struts in many ways - the developers will
freely
> admit they take the best ideas from each project to integrate into
cocoon.
>
> Some of the features:
> - schematron ( same as validators )
> - internationalisation support
> - sub applications
> - xmlforms ( similar to form beans ) ( w3c standard )
> etc, etc.
>
> There are also xsp's ( xml -> jsp ) but I have never used them.
>
> I think one of the shortfalls of cocoon is pipeline processing
where you
> cannot change the direction of a pipeline once processing has begun
( since
> processing is based on sax events). We have worked around this with
a
> variety of custom actions but it would be a hard work in a small
team where
> you don't have much time for R&D (play time).
>
> Another issue is that it is very loosely coupled and you can easily
end up
> lost in a large project - especially for newbies.
>
> Having said that, you can get work done very quickly as well.
>
> It is worth evaluating - you can cut out a couple of layers of
processing
> using cocoon instead of struts/JSF/clxx.
>
> hope this helps
>
> Oz
>
> -----Original Message-----
> From: Rabih Yazbeck [mailto:rablists@y...]
> Sent: Wednesday, 12 February 2003 10:46 PM
> To: 'Struts Users Mailing List'
> Subject: RE: Need Advise: use Struts/XSLT
>
>
> What about Cocoon integration with Struts? Is it possible that
cocoon
> handle the presentation layer while Sturts focus on the controller?
>
> Even though Cocoon has released a version 2, but I think there is
> anymore much work on Cocoon, am I right?
>
> Thanks, and yes I believe in the power of XML/XSLT.. World is moving
> toward this approach, and I wish there is more support for it in
Struts.
>
> -
> Rabih
>
> -----Original Message-----
> From: ROSSEL Olivier [mailto:olivier.rossel@a...]
> Sent: 12 February 2003 10:29
> To: 'Struts Users Mailing List'
> Subject: RE: Need Advise: use Struts/XSLT
>
> >> -----Message d'origine-----
> >> De: Oguz Kologlu [mailto:ozkologlu@o...]
> >> Date: mercredi 12 février 2003 11:15
> >> À: Struts Users Mailing List
> >> Objet: RE: Need Advise: use Struts/XSLT
> >>
> >>
> >> Hi,
> >>
> >> There is an article on theserverside.com that discusses this
issue
> at:
> >>
> >
> >To oversimplify - it says you should develop JSP "Documents" ( well
> formed
> >xml ) and use xslt for presentation/rendering/i18n etc.
>
> XSLT is very powerful if you can manage things in your XSLT such as
> document(url)
> where the URL is also a dynamic XML document.
> Aggregation is also a very useful feature.
>
> To me the (too basic) process of 1 XML-> 1 XSLT->whatever is not
that
> useful.
> For example it is interesting to have 2 XMLs-> 1 XSLT-> 1 XSLT-
>whatever
> or
> to
> have XML->XSLT->whatever
>             ^
>             |
>           XSLT
>             ^
>             |
>            XML
>
> I admit that it is quite an advanced usage of XML pipelines.
> Cocoon handles that very nicely.
>
> PS: for those who don't understand the power of the last pipeline
> discribed,
> think about such a pipeline:
> XML->XSLT->whatever
>       ^
>       |
>      XSLT
>       ^
>       |
>      XHTML
>
> Struts ceates the XML.
> Dreamweaver creates the XHTML (with custom tags to be XSLT-
processed).
> Did you say "total separation of concerns"?
>
> This e-mail is intended only for the above addressee. It may contain
> privileged information. If you are not the addressee you must not
copy,
> distribute, disclose or use any of the information in it. If you
have
> received it in error please delete it and immediately notify the
sender.
> Security Notice: all e-mail, sent to or from this address, may be
> accessed by someone other than the recipient, for system management
and
> security reasons. This access is controlled under Regulation of
> Investigatory Powers Act 2000, Lawful Business Practises.
>
> --------------------------------------------------------------------
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> --------------------------------------------------------------------
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> --------------------------------------------------------------------
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to