Enterprise Client Community

We had an hardware crash within our hosted root server. The system was exchanged and is up and running again.

All forum data was backed up, there's no data loss.

Sorry for the inconvenience! Björn

...we'll take a look...
Björn

...is added with 20080811...
Björn

...both features are available with this week's version 20080811...
Björn

No, one menu item is associate-able with one hotkey only. But you can define multiple menut items pointing to the same processing. Maybe for the user it may look a bit strange, to see two menu items with the same text - but at least it's possible.

Björn

Hi,

yes, you are right. There seems to be a jasper library missing (we reduced the jasper libraries to a minimum, so taht the amount of classes sent to the client is reduced...):

Code:

 Exception in thread "AWT-EventQueue-1" java.lang.NoClassDefFoundError: com/lowagie/text/pdf/FontMapper
         at net.sf.jasperreports.view.save.JRPdfSaveContributor.save(JRPdfSaveContributor.java:107)
         at net.sf.jasperreports.view.JRViewer.btnSaveActionPerformed(JRViewer.java:1128)
         at net.sf.jasperreports.view.JRViewer$3.actionPerformed(JRViewer.java:668)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at org.eclnt.client.page.BlockingEventQueue.dispatchEvent(BlockingEventQueue.java:82)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)

We'll check and add the missing library. (We cannot just pass it to you, because all libraries sent to the client are signed with one and the same signature.)

Thanks!

Björn

...problem solved after short call: problem had nothing to do with "HTML" but with missing directory...

Björn

...infos and download: http://www.CaptainCasa.com ==> DevZone...

Björn

Some comment: in the meantime the scenario is working. There were some hurdles in addition. I just summarize, maybe some of you come into similar scenarios.

Between Tomcat and Client there are a couple of systems, that do important things, but sometimes are not nice from Enterprise Client point of view ;-):

(.) One system in between was checking the http response to be a properly formed HTML page... i.e. it added <html> and <body> tags around the beautiful XML that is produced by our server side JSF components.

(.) the same system (at least we believe so...) converted <input .../> into <input ...> (no slash). Well in HTML this OK, but if this comes to the client, then the client tells you that there is an end tag missing.

(.) ...and the URL in the <form ...> tag was updatey as well.

It is always quite difficult in a complex scenario to identify this "between system", and even if so, then it is difficult to configure these systems properly (you need to start discussion with your sys admins etc. etc.). So , we adapted the Enterprise Client to react on mal-formed XML, html/body tags, etc.

Conclusion: when leaving the simple Tomcat scenario and going into the "real" scenarios, then it is very useful to exactly have a look into the repsonse coming from Tomcat, and compare it with the response actually arriving in the CaptainCasa client.

To monitor: switch on the client logging. Set loglevel=ALL then the whole http content will be written to log. To see the log switch on the monitoring in the Java system configuration (Java Console).

Björn

...yes, both features are useful: we will implement them quite short term.
Björn

..short answer: yes...!
Björn

Hello,

hmm, we just use the normal Look and Feel operations:

Code:

 ...
    UIManager.setLookAndFeel(sLookandfeel);
 ...

We either use the system default or the CaptainCasa. After setting the look and feel, we may update the font settings (size) according to the size factor that you define within the client environment.

In your scenario: is it possible that the outside UI is setting the Look & Feel as well? And the last one wins...?

Björn

Hi Frauke,

the method is a direct pass through of Servlet methods, i.e. no own logic involved.

Code:

     public static String getServletTempDirectory()
     {
         File f = (File)s_servletContext.getAttribute("javax.servlet.context.tempdir");
         String result = f.getAbsolutePath();
         result = result.replace('\\','/');
         if (!result.endsWith("/")) result = result + "/";
         return result;
     }

Björn

...will take a look...
Björn

Hi Antje,

problem is fixed and available ...on your request...!

Björn