Tuesday, May 22nd, 2007

QueWeb Customer Care GWT Application

Category: GWT, Showcase

Queplix has open sourced a GWT application called QueWeb Customer Care.

The application is an example of a desktop-looking app, with a rich tree based view that ties into a lot of data munging.


Posted by Dion Almaer at 12:58 pm

3.8 rating from 26 votes


Comments feed TrackBack URI

boy that apps too slow.. may be bcos of javascript writing those layouts when some left links are clicked

Comment by Mittal — May 22, 2007

Since we published the app on Google open source we had thousands of concurrent users on the demo at any point of time. We simply did not plan for the most powerful server for this task as we did not expect the number of users and downloads in the short few days since the Google endorsement. Also, the demo app is running over a public Internet backbone. That might explain the relative slowness as compared to a desktop application. If you download and install it on your local server it behaves as fast as the desktop app would. We support connection pools on JBoss and database so the transactional performance is excellent. Keep in mind however, that this is the Enterprise grade system, there are hundreds of workflows and rules etc. that are happening besides jsut “clicking on the tree”. If you need enterprise grade customer care/helpdesk system – download Brief Guide to the demo to see what the soluton does in a nutshell. Good luck!

Comment by Steven Yaskin — May 22, 2007

I heard it is idiotic to print the full trace of a security exception such as the one for the login page.

An advice from Mishka (Good boy! Oh he just barked)

Comment by Mishka — May 23, 2007

What security exception are you referring to?

Comment by Steven — May 23, 2007

this one maybe?

com.queplix.core.integrator.security.BadNameOrPasswordException: bad_password_exception
at com.queplix.core.modules.security.DatabaseLoginModule.doLogin(DatabaseLoginModule.java:78)
at com.queplix.core.integrator.security.AccessRightsManager.getUser(AccessRightsManager.java:114)
at com.queplix.core.integrator.security.WebLoginManager.setLogonSession(WebLoginManager.java:126)
at com.queplix.core.integrator.IntegratorLogin.login(IntegratorLogin.java:54)
at com.queplix.core.server.app.rpc.LoginServiceImpl.login(LoginServiceImpl.java:35)
at sun.reflect.GeneratedMethodAccessor3236.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:281)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)

Comment by Lil — May 24, 2007

i’ve just managed to change demo user password from demo to tester, and have verified that it worked. I’ve changed it back to demo, but someone else could be not so polite. Some users should have no priviliges to change their password.

Comment by Krzysztof — May 24, 2007

We are updating the demo version next week so that the demo account password could not be changed. What happened here is that originally we had people register for the demo and use their personal logins. Later, we decided to open the demo allowing bypassing the registration process; therefore we created the demo/demo account shared by everybody. Next week we will deploy the next version with bug fixes including disabled account changes based for the demo account. Thanks!

Comment by Steven — May 24, 2007

The permissions on changing the demo account have been made read only.

Comment by Steven — May 29, 2007

By the way, the full trace is available only if you click show more.. option in the dialog message. Keep in mind, everything we do had been requested by majority of the customers. Any errors you receive in QueWeb could be diagnosed and troubleshooted from the application, instead of spending time going through the logs on the Java server.

Comment by Steven — May 29, 2007

Leave a comment

You must be logged in to post a comment.