Hi Rob,
I had a first go at the new alpha version. Didn't get into too much convolute stuff with it but used a simple Report on a foundset with grouping on a field and access to fields of a relation.
Good news is that it's working great in developer and in smart client
Bad news is that it's not workinf at all in the web client
I got that Exception in the console when I launched the server from the .bat file and tried it:
- Code: Select all
2009-06-07 20:45:04 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: "Servlet.service()" pour la servlet servoy_webclient a généré une exception
javax.servlet.ServletException: L'exécution de la servlet a lancé une exception
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:896)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:705)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2049)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
It might be that, if I understand your new design correctly, the report being now run on the client side, this is fine when you are in a java client, but can't work in a browser.
For the web browser, I think that you will still have to run the report on the server and either do it "the old way" with SQL or send back a serialized foundset (or dataset, or tableModel): this part of going back and forth to the server will be the only possible way in a browser, I'm afraid.
Anyway, this is already a great improvement, and once the web client issue is fixed, you wil be very close to a usable solution, I'm sure.
Thanks again for you efforts on this one.
Keep up the good work!