You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Typrowitz, Jim" <jt...@solant.com> on 2000/09/27 19:03:21 UTC
JSP vs. Cocoon for Website
Dear Cocoon Users,
I'm having a difficult time in deciding whether to use JSP or Cocoon for
developing a Web Site which will sell items, have a fair amount of database
activity, and security issues. The site will also be sold to others and
personalized, within reason. I see that Cocoon with its XML/XSL technology
is a clear winner for publishing. But I'm not sure about developing this
particular Website.
Here is how I see it and I would appreciate any comments and definitely
anything I missed with Cocoon as I'm new to it.
Cocoon offers a lot of XML/XSL technology. I know XML is THE buzz word
lately, but I don't want to use Cocoon just for this.
JSP is part of the J2EE standard, Cocoon has specific extensions like XSP,
SQL Processor, etc., technology that would seem to lock me into Cocoon. If
I get mad at my J2EE vendor I can dump them for one of another dozen, with
very little change.
The site will have minimum content, but will have a lot of user interaction,
collecting information for quotes, etc.
Since my site will be customized for different customers with most of the
data in the database already, I don't see that I could take advantage of
XML files. I believe I would need to create, in Cocoon terms, a producer.
Based on this I need to write a Java producer and thus Cocoon doesn't help
me in this respect, as I need to create the XML on the fly anyway. I could
use the SQL Processor with Cocoon, but the client I am building the site for
has a lot of stored procedures to calculate complex values. It doesn't
appear that Cocoon supports Stored Procedures, as they are database
specific. It seems I would be back to writing a producer.
Both the JSP taglib and the XSL style sheet have similar logic statements,
or processing instructions, allowing (for mostly) the separation of content,
formatting and logic. The logic area seems to be one area though that
Cocoon offers a definite advantage. I would have to write more Java code
using JSP, whereas I could take advantage of built-in capabilities of XSLT.
If I use JSP I believe I would be able to take better advantage of the J2EE
application server's fail-over capability, which the client already owns.
It appears I can provide better security with JSP by using ACL's within the
application server.
It is possible the site will be used later to interface with WML and WAP.
Again, it seems as though Cocoon would take less time because of built-in
XSLT capabilities.
The final decision seems to come down to content, formatting, logic and
security. As far as providing content I see JSP and Cocoon as even, since I
need to write an XML producer in either case. For formatting, again, I see
them as about even as I need to put in the HTML in either JSP or XSL. The
advantage on logic would go to Cocoon since I could take advantage of XSLT,
thus writing less code. The advantage on security would seem to go to JSP.
Re: JSP vs. Cocoon for Website
Posted by Viktors Rotanovs <vi...@riga.nu>.
Hi Jim,
you can use Enhydra or Turbine for interaction and
Cocoon for output. Cocoon is THE winner when you
have to deal with presentation, but is not very good
for complex interaction.
On Wed, 27 Sep 2000, you wrote:
> Dear Cocoon Users,
>
> I'm having a difficult time in deciding whether to use JSP or Cocoon for
> developing a Web Site which will sell items, have a fair amount of database
> activity, and security issues. The site will also be sold to others and
> personalized, within reason. I see that Cocoon with its XML/XSL technology
> is a clear winner for publishing. But I'm not sure about developing this
> particular Website.
>
> Here is how I see it and I would appreciate any comments and definitely
> anything I missed with Cocoon as I'm new to it.
>
> Cocoon offers a lot of XML/XSL technology. I know XML is THE buzz word
> lately, but I don't want to use Cocoon just for this.
>
> JSP is part of the J2EE standard, Cocoon has specific extensions like XSP,
> SQL Processor, etc., technology that would seem to lock me into Cocoon. If
> I get mad at my J2EE vendor I can dump them for one of another dozen, with
> very little change.
>
> The site will have minimum content, but will have a lot of user
> interaction, collecting information for quotes, etc.
>
> Since my site will be customized for different customers with most of the
> data in the database already, I don't see that I could take advantage of
> XML files. I believe I would need to create, in Cocoon terms, a producer.
> Based on this I need to write a Java producer and thus Cocoon doesn't help
> me in this respect, as I need to create the XML on the fly anyway. I could
> use the SQL Processor with Cocoon, but the client I am building the site
> for has a lot of stored procedures to calculate complex values. It doesn't
> appear that Cocoon supports Stored Procedures, as they are database
> specific. It seems I would be back to writing a producer.
>
> Both the JSP taglib and the XSL style sheet have similar logic statements,
> or processing instructions, allowing (for mostly) the separation of
> content, formatting and logic. The logic area seems to be one area though
> that Cocoon offers a definite advantage. I would have to write more Java
> code using JSP, whereas I could take advantage of built-in capabilities of
> XSLT.
>
>
> If I use JSP I believe I would be able to take better advantage of the J2EE
> application server's fail-over capability, which the client already owns.
>
> It appears I can provide better security with JSP by using ACL's within the
> application server.
>
> It is possible the site will be used later to interface with WML and WAP.
> Again, it seems as though Cocoon would take less time because of built-in
> XSLT capabilities.
>
> The final decision seems to come down to content, formatting, logic and
> security. As far as providing content I see JSP and Cocoon as even, since
> I need to write an XML producer in either case. For formatting, again, I
> see them as about even as I need to put in the HTML in either JSP or XSL.
> The advantage on logic would go to Cocoon since I could take advantage of
> XSLT, thus writing less code. The advantage on security would seem to go
> to JSP.
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Best Wishes,
Viktors Rotanovs
I create websites that attract more clients. http://riga.nu/
Riga Latvia +371, Phone 7377-142, GSM 9173-000, FAX 7377-472
Re: JSP vs. Cocoon for Website
Posted by Berin Loritsch <bl...@infoplanning.com>.
----- Original Message -----
From: "Typrowitz, Jim" <jt...@solant.com>
To: <co...@xml.apache.org>
Sent: Wednesday, September 27, 2000 1:03 PM
Subject: JSP vs. Cocoon for Website
> Dear Cocoon Users,
>
> I'm having a difficult time in deciding whether to use JSP or Cocoon for
> developing a Web Site which will sell items, have a fair amount of database
> activity, and security issues. The site will also be sold to others and
> personalized, within reason. I see that Cocoon with its XML/XSL technology
> is a clear winner for publishing. But I'm not sure about developing this
> particular Website.
Hopefully I can help, and dispell any myths.
> Here is how I see it and I would appreciate any comments and definitely
> anything I missed with Cocoon as I'm new to it.
>
> Cocoon offers a lot of XML/XSL technology. I know XML is THE buzz word
> lately, but I don't want to use Cocoon just for this.
That is a smart mentality...
> JSP is part of the J2EE standard, Cocoon has specific extensions like XSP,
> SQL Processor, etc., technology that would seem to lock me into Cocoon. If
> I get mad at my J2EE vendor I can dump them for one of another dozen, with
> very little change.
Remember that Cocoon is a Servlet, and by extension part of the J2EE standard
as well. If you get mad at your J2EE vendor, you can still dump them and
continue to use Cocoon--with no change. While you don't *have* to use SQL
Processor/XSP, etc. they are good tools that make your job a lot easier.
> The site will have minimum content, but will have a lot of user interaction,
> collecting information for quotes, etc.
I haven't looked too deeply at the FP taglib for Cocoon, but it promisses to
be very exciting for this.
> Since my site will be customized for different customers with most of the
> data in the database already, I don't see that I could take advantage of
> XML files. I believe I would need to create, in Cocoon terms, a producer.
> Based on this I need to write a Java producer and thus Cocoon doesn't help
> me in this respect, as I need to create the XML on the fly anyway. I could
> use the SQL Processor with Cocoon, but the client I am building the site for
> has a lot of stored procedures to calculate complex values. It doesn't
> appear that Cocoon supports Stored Procedures, as they are database
> specific. It seems I would be back to writing a producer.
You can use XSP to do the logic for you. Another approach is to use EJBs
and include a toXML() method that serializes the Entity Bean to an XML
string. Remember that the SQL Processor and SQL taglib both work with
JDBC. It would be as easy to execute stored procedures as it is to do
that with JDBC.
> Both the JSP taglib and the XSL style sheet have similar logic statements,
> or processing instructions, allowing (for mostly) the separation of content,
> formatting and logic. The logic area seems to be one area though that
> Cocoon offers a definite advantage. I would have to write more Java code
> using JSP, whereas I could take advantage of built-in capabilities of XSLT.
If you need to use JSP to create your XML and process the results with Cocoon,
it would be possible. If that is unfeasable you can still leverage the benifits
of XML/XSLT through your own custom implementation. Cocoon just makes that part
a lot easier.
> If I use JSP I believe I would be able to take better advantage of the J2EE
> application server's fail-over capability, which the client already owns.
Would that work for Servlets as well? Cocoon does not circumvent the fail-over
capabilities. The only reason it is forced to live in the main classpath is
because XSP uses the compiler that requires all referenced classes to be in
its classpath. With Cocoon 2 (aka C2), they have already made some headway
in that area--but it is not complete.
> It appears I can provide better security with JSP by using ACL's within the
> application server.
Can that happen with servlets? Honestly, the major security risks deal with
things behind the scenes like RPC (remote procedure calls) and clear text
messaging. I find it hard to believe that the ACL's would only work with
JSP.
> It is possible the site will be used later to interface with WML and WAP.
> Again, it seems as though Cocoon would take less time because of built-in
> XSLT capabilities.
As mentioned before, if you decide not to use Cocoon, you can still have your
application use XSLT--you just have to wire the plumbing yourself.
> The final decision seems to come down to content, formatting, logic and
> security. As far as providing content I see JSP and Cocoon as even, since I
> need to write an XML producer in either case. For formatting, again, I see
> them as about even as I need to put in the HTML in either JSP or XSL. The
> advantage on logic would go to Cocoon since I could take advantage of XSLT,
> thus writing less code. The advantage on security would seem to go to JSP.
If you can set security and fail-over for servlets then you can do that for
Cocoon as well. Cocoon is a servlet that lives in a J2EE standard environment.
As such, you can take advantage of anything that servlets can take advantage.
Re: JSP vs. Cocoon for Website
Posted by Viktors Rotanovs <vi...@riga.nu>.
Hi again,
I forgot to mention, if the site will be mainly shop and
you don not have to use Java, take a look at
Akopia Interchange (formely Minivend), it is quite
powerful if you want to build advanced shop (or mall).
You can also patch Interchange to produce XML and
then format it with Cocoon.
Interchange: http://www.minivend.com/ , http://www.akopia.com/
Enhydra: http://www.enhydra.org/
Turbine: http://java.apache.org/turbine/
On Wed, 27 Sep 2000, you wrote:
> Dear Cocoon Users,
>
> I'm having a difficult time in deciding whether to use JSP or Cocoon for
> developing a Web Site which will sell items, have a fair amount of database
> activity, and security issues. The site will also be sold to others and
> personalized, within reason. I see that Cocoon with its XML/XSL technology
> is a clear winner for publishing. But I'm not sure about developing this
> particular Website.
>
> Here is how I see it and I would appreciate any comments and definitely
> anything I missed with Cocoon as I'm new to it.
>
> Cocoon offers a lot of XML/XSL technology. I know XML is THE buzz word
> lately, but I don't want to use Cocoon just for this.
>
> JSP is part of the J2EE standard, Cocoon has specific extensions like XSP,
> SQL Processor, etc., technology that would seem to lock me into Cocoon. If
> I get mad at my J2EE vendor I can dump them for one of another dozen, with
> very little change.
>
> The site will have minimum content, but will have a lot of user
> interaction, collecting information for quotes, etc.
>
> Since my site will be customized for different customers with most of the
> data in the database already, I don't see that I could take advantage of
> XML files. I believe I would need to create, in Cocoon terms, a producer.
> Based on this I need to write a Java producer and thus Cocoon doesn't help
> me in this respect, as I need to create the XML on the fly anyway. I could
> use the SQL Processor with Cocoon, but the client I am building the site
> for has a lot of stored procedures to calculate complex values. It doesn't
> appear that Cocoon supports Stored Procedures, as they are database
> specific. It seems I would be back to writing a producer.
>
> Both the JSP taglib and the XSL style sheet have similar logic statements,
> or processing instructions, allowing (for mostly) the separation of
> content, formatting and logic. The logic area seems to be one area though
> that Cocoon offers a definite advantage. I would have to write more Java
> code using JSP, whereas I could take advantage of built-in capabilities of
> XSLT.
>
>
> If I use JSP I believe I would be able to take better advantage of the J2EE
> application server's fail-over capability, which the client already owns.
>
> It appears I can provide better security with JSP by using ACL's within the
> application server.
>
> It is possible the site will be used later to interface with WML and WAP.
> Again, it seems as though Cocoon would take less time because of built-in
> XSLT capabilities.
>
> The final decision seems to come down to content, formatting, logic and
> security. As far as providing content I see JSP and Cocoon as even, since
> I need to write an XML producer in either case. For formatting, again, I
> see them as about even as I need to put in the HTML in either JSP or XSL.
> The advantage on logic would go to Cocoon since I could take advantage of
> XSLT, thus writing less code. The advantage on security would seem to go
> to JSP.
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Best Wishes,
Viktors Rotanovs
I create websites that attract more clients. http://riga.nu/
Riga Latvia +371, Phone 7377-142, GSM 9173-000, FAX 7377-472
Re: STRUTS and Cocoon (was JSP vs. Cocoon for Website)
Posted by Luca Filipozzi <lf...@emyr.net>.
On Tue, Oct 24, 2000 at 09:54:51PM -0700, Chris Meyer wrote:
> >One configuration I am using is like this.
> >
> >ejb container: Inprise Application Server 4.1
> >servlet/jsp container: Resin 1.2
> >web publishing framework: Cocoon 1.8 with STRUTS
> >
> >In my case the jsp's produce xml and are controlled by a STRUTS controller
> >servlet. The xml served up by Cocoon to produce WML,HTML,and PDF.
> >
> >STRUTS is a great way to interact with forms. It implements a MVC
> Can you describe in detail how you are using STRUTS with Cocoon?
Yes, please!! I'm also interested in getting some more details on how you got
the various components working together.
Personally, I'm considering using Tomcat for my servlet container and JBoss for
my ejb container (www.jboss.org). Tomcat and EJB are released under DFSG-free
licenses, and that's important to me.
Luca
--
Luca Filipozzi
[dpkg] We are the apt. Resistance is futile. You will be packaged.
RE: AW: assigning variable to select attribute
Posted by Per Kreipke <pe...@onclave.com>.
Couple of things:
- shouldn't <xsl:content> be <xsp:content>?
- I guess what you're trying to do is dynamically determine the domain child
to select.
I'm not sure you can in one pass of the XSP file, but you could try the
following.
Use <xsp:attribute>.
I haven't done this myself, but I think what you might be looking for:
<fp:write to="external-item">
<xsp:attribute
name="select">domain[child::<xsp:expr>domainName</xsp:expr></xsp:attribute>
<xsp:expr>act</xsp:expr>
</fp:write>
> thanks for reply, but i didn't understand the answer. please read the
> below peace of source code in order to understand my problem. what may i
> assign in the select attribute instead of the variable domainName.
>
> <xsp:logic>
> Enumeration e = request.getParameterNames();
>
> if ((e != null) && (e.hasMoreElements())) {
> <xsl:content>
> <xsp:logic>
> while (e.hasMoreElements())
> String domainName = (String) e.nextElement();
> String act = request.getParameter(domainName);
>
> if(domainName.indexOf('.')!= -1 ){
> <item>
> <fp:write
> select="domain[child::name=domainName]/action" to="external-item">
> <xsp:expr>act</xsp:expr>
> </fp:write>
> </item>
> }
> }
> </xsp:logic>
> </xsl:content>
> }
> </xsp:logic>
Re: AW: assigning variable to select attribute
Posted by Ehab Jewabreh <e....@bonelabs.com>.
Hi,
thanks for reply, but i didn't understand the answer. please read the
below peace of source code in order to understand my problem. what may i
assign in the select attribute instead of the variable domainName.
<xsp:logic>
Enumeration e = request.getParameterNames();
if ((e != null) && (e.hasMoreElements())) {
<xsl:content>
<xsp:logic>
while (e.hasMoreElements()) {
String domainName = (String) e.nextElement();
String act = request.getParameter(domainName);
if(domainName.indexOf('.')!= -1 ){
<item>
<fp:write
select="domain[child::name=domainName]/action" to="external-item">
<xsp:expr>act</xsp:expr>
</fp:write>
</item>
}
}
</xsp:logic>
</xsl:content>
}
</xsp:logic>
Gabi Brysch wrote:
>
> hi,
>
> >>>is there anybody, who can help a cocoon beginner to solve this problem:
>
> >>>when i assign the variable "domainName" in the select attribute i get a
> >>>null pointer exception.
>
> >>>domainName ="sun.com";
> >>><fp:write select="domain[child::name=domainName]/action"
> >>>to="external-item">
> >>> <xsp:expr>act</xsp:expr>
> >>> </fp:write>
>
> does it work if you don't use a variable like ???
> ...
> <fp:write select="domain[child::name='sun.com']/action" to="external-item">
> ...
>
> did you use any 'tag' to declare the variable domainName ???
>
> GABI
>
>
>
> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
AW: assigning variable to select attribute
Posted by Gabi Brysch <br...@inxnet.de>.
hi,
>>>is there anybody, who can help a cocoon beginner to solve this problem:
>>>when i assign the variable "domainName" in the select attribute i get a
>>>null pointer exception.
>>>domainName ="sun.com";
>>><fp:write select="domain[child::name=domainName]/action"
>>>to="external-item">
>>> <xsp:expr>act</xsp:expr>
>>> </fp:write>
does it work if you don't use a variable like ???
...
<fp:write select="domain[child::name='sun.com']/action" to="external-item">
...
did you use any 'tag' to declare the variable domainName ???
GABI
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
assigning variable to select attribute
Posted by Ehab Jewabreh <e....@bonelabs.com>.
Hello everybody,
is there anybody, who can help a cocoon beginner to solve this problem:
when i assign the variable "domainName" in the select attribute i get a
null pointer exception.
domainName ="sun.com";
<fp:write select="domain[child::name=domainName]/action"
to="external-item">
<xsp:expr>act</xsp:expr>
</fp:write>
is it possible to do this?how?
Thanks.
Re: compare two variables
Posted by Rob van der Zeijden <r....@tiscon.de>.
Thanks Gaby.
AW: compare two variables
Posted by Gabi Brysch <br...@inxnet.de>.
Hi,
>>>how can I compare two variables in XSL. For example:
>>>if (nrOfColumns != nrOfColumnsFile)
<!-- you can do it with parameters like this -->
<xsl:param name="var1">test</xsl:param>
<xsl:param name="var2">test2</xsl:param>
<xsl:if test="not($test=$test2)">
<!-- do some action if comparison is true -->
</xsl:if>
or
>>>if (nrOfColumns == nrOfColumnsFile)
<xsl:param name="var1">test</xsl:param>
<xsl:param name="var2">test2</xsl:param>
<xsl:if test="$test=$test2">
<!-- do some action if comparison is true -->
</xsl:if>
instead of xsl:if, you can use:
<xsl:choose>
<xsl:when test="$test=$test2>
<!-- do something if condition is true -->
</xsl:when>
<xsl:otherwise>
<!-- do something if condition is not true -->
</xsl:otherwise>
</xsl:choose>
i think instead of using xsl:param you can use attributes instead
like:
<xsl:if test="@attribut=$test">
<!-- do something if true -->
</xsl:if>
i hope with this examples you can go on with xslt !?
bye, GABI
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
compare two variables
Posted by Rob van der Zeijden <r....@tiscon.de>.
Hi,
how can I compare two variables in XSL. For example:
if (nrOfColumns != nrOfColumnsFile)
or
if (nrOfColumns == nrOfColumnsFile)
Thanks.
STRUTS and Cocoon (was JSP vs. Cocoon for Website)
Posted by Chris Meyer <cm...@ultratask.com>.
>One configuration I am using is like this.
>
>ejb container: Inprise Application Server 4.1
>servlet/jsp container: Resin 1.2
>web publishing framework: Cocoon 1.8 with STRUTS
>
>In my case the jsp's produce xml and are controlled by a STRUTS controller
>servlet. The xml served up by Cocoon to produce WML,HTML,and PDF.
>
>STRUTS is a great way to interact with forms. It implements a MVC
>Pattern and is
>really slick. I give it two thumbs up. Also for internationalization it really
>pays dividends.
>
>This has made for very speedy and easy to maintain development.
>Check it out! :o)
Hi Russ,
Can you describe in detail how you are using STRUTS with Cocoon?
Specically: what version of Struts? how do you configure your web app?
Thanks,
Chris
RE: JSP vs. Cocoon for Website
Posted by Russ White <ru...@earthlink.net>.
Jim,
Why not use both JSP and XML/XSP with Cocoon? That's what I do. I am working on
a case like yours right now, and I am close to releasing my solution.
As far as standards like J2EE I think you can relax on that one. Cocoon is not
going bust any time soon. :o) There is a tidal wave of developers moving toward
the Cocoon publishing framework.
One configuration I am using is like this.
ejb container: Inprise Application Server 4.1
servlet/jsp container: Resin 1.2
web publishing framework: Cocoon 1.8 with STRUTS
In my case the jsp's produce xml and are controlled by a STRUTS controller
servlet. The xml served up by Cocoon to produce WML,HTML,and PDF.
STRUTS is a great way to interact with forms. It implements a MVC Pattern and is
really slick. I give it two thumbs up. Also for internationalization it really
pays dividends.
This has made for very speedy and easy to maintain development.
Check it out! :o)
HTH
G'day!
Russ
> -----Original Message-----
> From: Typrowitz, Jim [mailto:jtyprowitz@solant.com]
> Sent: Wednesday, September 27, 2000 1:03 PM
> To: 'cocoon-users@xml.apache.org'
> Subject: JSP vs. Cocoon for Website
>
>
> Dear Cocoon Users,
>
> I'm having a difficult time in deciding whether to use JSP or Cocoon for
> developing a Web Site which will sell items, have a fair amount of database
> activity, and security issues. The site will also be sold to others and
> personalized, within reason. I see that Cocoon with its XML/XSL technology
> is a clear winner for publishing. But I'm not sure about developing this
> particular Website.
>
> Here is how I see it and I would appreciate any comments and definitely
> anything I missed with Cocoon as I'm new to it.
>
> Cocoon offers a lot of XML/XSL technology. I know XML is THE buzz word
> lately, but I don't want to use Cocoon just for this.
>
> JSP is part of the J2EE standard, Cocoon has specific extensions like XSP,
> SQL Processor, etc., technology that would seem to lock me into Cocoon. If
> I get mad at my J2EE vendor I can dump them for one of another dozen, with
> very little change.
>
> The site will have minimum content, but will have a lot of user interaction,
> collecting information for quotes, etc.
>
> Since my site will be customized for different customers with most of the
> data in the database already, I don't see that I could take advantage of
> XML files. I believe I would need to create, in Cocoon terms, a producer.
> Based on this I need to write a Java producer and thus Cocoon doesn't help
> me in this respect, as I need to create the XML on the fly anyway. I could
> use the SQL Processor with Cocoon, but the client I am building the site for
> has a lot of stored procedures to calculate complex values. It doesn't
> appear that Cocoon supports Stored Procedures, as they are database
> specific. It seems I would be back to writing a producer.
>
> Both the JSP taglib and the XSL style sheet have similar logic statements,
> or processing instructions, allowing (for mostly) the separation of content,
> formatting and logic. The logic area seems to be one area though that
> Cocoon offers a definite advantage. I would have to write more Java code
> using JSP, whereas I could take advantage of built-in capabilities of XSLT.
>
>
> If I use JSP I believe I would be able to take better advantage of the J2EE
> application server's fail-over capability, which the client already owns.
>
> It appears I can provide better security with JSP by using ACL's within the
> application server.
>
> It is possible the site will be used later to interface with WML and WAP.
> Again, it seems as though Cocoon would take less time because of built-in
> XSLT capabilities.
>
> The final decision seems to come down to content, formatting, logic and
> security. As far as providing content I see JSP and Cocoon as even, since I
> need to write an XML producer in either case. For formatting, again, I see
> them as about even as I need to put in the HTML in either JSP or XSL. The
> advantage on logic would go to Cocoon since I could take advantage of XSLT,
> thus writing less code. The advantage on security would seem to go to JSP.
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>