Chris,
Sorry but I've lost track of this thread, but it appears that your problem
*still* hasn't been addressed.
I guess my question is:
Which version of the Turbine jar do you need, and does it include Raphael's
JSP fix?
Where can we get this jar from?
Quote form Martin Poesch Sept 5:
David Sean Taylor wrote:
Chris,
Sorry but I've lost track of this thread, but it appears that your problem
*still* hasn't been addressed.
I guess my question is:
Which version of the Turbine jar do you need, and does it include Raphael's
JSP fix?
Where can we get this jar from?
Quote form
Dave Carlson wrote:
I need to use the Saxon XSLT processor with Jetspeed for other portlet content
(and another application running in the same Tomcat instance). However, I was
getting errors when I added saxon as the default XSLT processor. I tracked
down a simple bug fix to
Santiago Gala wrote:
Dave Carlson wrote:
I need to use the Saxon XSLT processor with Jetspeed for other
portlet content
(and another application running in the same Tomcat instance).
However, I was
getting errors when I added saxon as the default XSLT processor. I
tracked
down a
taylor 01/09/12 23:11:04
Modified:webapp/wml stocks.wml weather.wml
Log:
- updated wml sample portlet content
Revision ChangesPath
1.3 +1 -1 jakarta-jetspeed/webapp/wml/stocks.wml
Index: stocks.wml
