Ok, I could reproduce that failure after downloading a tomcat5.0.30 from
the apache site instead of using the tomcat which is in the openlaszlo svn.
On 3/30/2010 7:53 PM, André Bargull wrote:
Which java version is used? According to the java docs [1], the 2nd
argument is of type Object and by auto-boxing, an integer value should
work.
[1]
http://java.sun.com/javaee/5/docs/api/javax/servlet/jsp/JspContext.html#setAttribute%28java.lang.String,%20java.lang.Object%29
On 3/30/2010 7:47 PM, P T Withington wrote:
I just built locally and I am getting this;
An error occurred at line: 14 in the jsp file:
/demos/calendar/calendardata/vcal.jspx
Generated servlet error:
/usr/local/tomcat/jakarta-tomcat-5.0.30/work/Catalina/localhost/trunk/org/apache/jsp/demos/calendar/calendardata/vcal_jspx.java:89:
cannot find symbol
symbol : method setAttribute(java.lang.String,int)
location: class javax.servlet.jsp.PageContext
pageContext.setAttribute("currentyear",
Calendar.getInstance().get(Calendar.YEAR));
^
1 error
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:437)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:497)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:476)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:464)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
On 2010-03-30, at 13:36, André Bargull wrote:
I'm always restarting the complete server when testing compiler
changes...
http://labs.openlaszlo.org/trunk-nightly/demos/calendar/calendardata/vcal.jspx
org.apache.jasper.JasperException:
/demos/calendar/calendardata/vcal.jspx(10,48) Could not add one or
more tag libraries.
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:88)
org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:212)
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:197)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:101)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:156)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:296)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:277)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:265)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:564)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:299)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
So it's not just something about your environment. But hard to tell
from here why the labs server is choking, because I don't know which
Tomcat version is used and which libraries it uses.
On 3/30/2010 7:11 PM, Max Carlson wrote:
Okay, that's good. It must be something with my environment then.
Unfortunately the symlink approach doesn't help when working on the
compiler - I often need to undeploy/deploy to test a change...
Regards,
Max Carlson
OpenLaszlo.org
On 3/30/10 1:34 AM, André Bargull wrote:
I've just tried the Tomcat which is shipped with OpenLaszlo (it's
Tomcat
5.0.24) and vcal.jspx worked for me. (Btw I'm using Tomcat 6.0.26 for
normal development).
Instead of 'ant webapp-deploy', I've created a symlink in the
Tomcat's
webapps directory pointing to my trunk directory. IMO that's more
comfortable than re-deploying the webapp every time.
On 3/30/2010 1:01 AM, Max Carlson wrote:
Does anyone know how to keep the Tomcat 5.5 manager from copying
_all_
the files when I deploy OL using 'ant webapp-deploy'? It's driven me
back to Tomcat 5.0.30 for now :(
Regards,
Max Carlson
OpenLaszlo.org
On 3/29/10 2:56 PM, André Bargull wrote:
Forgot to mention:
If you just want to test the transformation, you can directly
query the
jsp with:
http://localhost:8080/trunk/demos/calendar/calendardata/vcal.jspx?month=1&year=2010
On 3/29/2010 11:51 PM, André Bargull wrote:
If that doesn't work, could you replace
demos/calendar/calendardata/vcal.xsl with the attached file. The
changed file just adds the exception message:
<c:if test="${not empty ex}">
<error message="xsl-transformation error: ${ex}"/>
</c:if>
On 3/29/2010 11:43 PM, André Bargull wrote:
Did you restart the tomcat server, so it takes the changes in
web.xml.
On 3/29/2010 11:39 PM, Max Carlson wrote:
This change doesn't work for me when I launch the calendar on a
clean
build of trunk on OS X. I keep getting XML responses like:
<resultset><body><error message="xsl-transformation error"
/></body><headers /></resultset>
Regards,
Max Carlson
OpenLaszlo.org
On 3/29/10 12:23 PM, P T Withington wrote:
Lovely! Approved.
On 2010-03-26, at 22:25, André Bargull wrote:
Change 20100327-bargull-dDZ by barg...@bargull02 on 2010-03-27
01:32:27
in /home/anba/src/svn/openlaszlo/trunk
for http://svn.openlaszlo.org/openlaszlo/trunk
Summary: resolve calendar data issue once and for all
Bugs Fixed: LPP-8754 (Calendar - Can not edit new event since
Event
Info panel didn't display completely)
Technical Reviewer: ptw
QA Reviewer: (pending)
Doc Reviewer: (pending)
Details:
Every year the same procedure:
- calendar demo doesn't work properly
-> necessary calendar data is added
See LPP-4900, LPP-7667 and now LPP-8754
I don't want to repeat that procedure again for 2011,
therefore
the
calendar data is now automatically created.
The new "vcal_xxxx-x-01.xml" files are copies of the year 2007
data,
I've only renamed the<year2007> element to<year> and
cleared the
"year" attribute in<start> and<end>. The calendar demo
expects the
data in a certain format and to create that format from the
template
xml-files a xsl-file is used ("vcal.xsl"). The demo now
requests
the
data from "vcal.jspx", which uses taglibs to trigger the
xsl-transformation and returns the created xml data.
While testing the change, I've noticed that the event text
isn't
fully displayed. Changing the text-height in eventselector.lzs
fixed
that problem.
Tests:
run calendar demo (swf8, swf10, dhtml)
