On Sat, 2003-01-18 at 16:25, Jules Gosnell wrote:

> I haven't tried it, but if you have a Jasper that implements JSP2.0, try 
> replacing the jasper jars in jbossweb.sar with it and see if it works...
> 
> If not, they have changed the external API and we may have to make 
> adjustments. I don't see why they should need to do this, Jasper is just 
> another servlet that should run in any compliant servlet-container, 
> which Jetty is.

If this is true then that is excellent news.  Too be honest I am more
interested in JSP 2.0 support in Jetty than in Tomcat as I switched to
Jetty some time ago. :-)

But I knew that Jetty used Jasper, but I wasn't aware that the
integration was (theoretically) so simple.

> Try it and come back to the list with your findings,

Alas someone else will probably beat me to it.  It will be some time
before I get to this part of my refactoring.  Hence my original
question, I was just wondering how long it would be, it sounds from your
comments that JSP 2.0 will be ready a while before I am.
But if I do end up working on it first, you can be sure that I'll post
my findings here and I'll help in any way I can.

> What have they got in JSP2.0 that is exciting ? I haven't yet had time 
> to look at the spec.

There are quite a few things that are new in JSP that I have been
getting quite excited about.

I have never previously been a fan of JSP because in my mind it did not
sufficiently separate the presentation and business logic layers.
Custom tags were a step to solve this, but it was too "hard" of a
solution whereby all the logic had to be set up in java classes.

However, JSP has introduced a new server side scripting language called
"EL" which seems to me to be exactly what was needed.  This is a welcome
addition if like me you have never been keen on the idea of having java
code embedded in templates.

You can create pure XML pages in JSP now, and switch off any embedded
Java, instead opting for the lighter weight EL scripting language.  You
can then add your presentation layer using servlet filters doing XSLT
transformations for example.
If you use such a methodology, it forces you to put all of your meaty
code in Java classes where it belongs, but still gives you the freedom
to do scripting in the template.

You can also create custom tags in pure EL.

The strange thing for me is that I have been mentally designing a new
XML based web-framework that would use JPython as a scripting language.

After reading the JSP 2.0 spec. however, I realised that I can now
achieve the same design goals using the new features of JSP.

The only area which I think is still a little weak is that in the
servlet API, filters can only be configured at deploy time.  I would
like to be able to pick different output "filters" at runtime.

This should be relatively easy to work around however.

-- 
Peter Beck BEng (hons)  - Managing Director, Electrostrata Ltd.
http://www.electrostrata.com  --+-+--  Experts in e-business and e-commerce



-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to