Enterprise Client Community

Hi,

Tomcat by default tries to persist sessions when being shut down: this means that your application needs to 100% work with serializable objects.

If your application is not fully serializable this will result in nice Tomcat error messages when Tomcat starts up.

Please check Tomcat's /tomcat/conf/context.xml file and change the parameter as follows:

Code:

 <Context>
     ...
     ...	
     <!-- Uncomment this to disable session persistence across Tomcat restarts -->
     <Manager pathname="" />
     ...
     ...	
 </Context>

This will switch off the session persistence management in Tomcat.

Björn

BTW: the layout editor and the demo applications are currently not checked to be serializable.

good..!

BTW: I could imagine the same happens with column sequence (user dragging & dropping columns...).
There is a method setModcolumnsequence() as well, which then also should be passed a null value.

Björn

Hi,

this has to do with the internal keeping of modified widths.

Could you please call the FIXGRIDListBinding's method:

Code:

 FIXGRIDListBinding.setModcolumnswidths(null);

when updating the grid's column structure.

I have not checked everything, so I hope this does not cause a null pointer...

Björn

PS: thanks for isolating the code in this perfect way...!

Hi Frauke and Tobias,

the icon which is cut off: we cannot reproduce... our icons are still well-formed. Could you give us more details on this? Thanks!

Explicitly calling an event before/after pressing the button: could this not be done as part of the processing that you start with the URL? I.e. servlet URL which does not point to a straight file, but to a program which then "unpacks" data on request.

I would like to avoid some "ping pong" between the client and the server, which is always a bit suspicious to fail...

Björn

Currently there is no version-ticker in the delivery; but you are right... this is a thing we will add very short term.

About release notes: to keep efforts low we want to have one place where to find the history + all the infos about versions: this is the devzone. What we will do: in the installation files we will add the URL to the post-installation text.

Björn

...have you scrolled down a bit...?

Björn

...it's a shame: we published the 20080414 yesterday, and now we publish a 20080415 one day later... But: a nice bug was found when working with the Dispatcher framework - see the release notes for the update 20080415.

We try to keep quiet with updates now ;-), till next Monday.

Björn

In the layout editor you see "on the right" the resolution of beans. The resolution on the one hand follows the set/get property (through introspection), on the other hand it follows the Dispatcher-mechanism (dynamic access to beans).

In the resolution of Dispatcher-beans there is an error, which was told to us yesterday: the bean expression that is generated for each bean contains a part of the package name... But: it must only contain the class name, without package name.

There is a fix for the editor's web application available (pls. email to us) - or: we are just uploading a fixed version (20080415) which solves the problem as well.

Thanks to the ones telling us about the bug...!
Björn

This is the extended list of keycodes with "special characteres": anything important missing...?

Code:

         switch (keyCode) 
         {
             case 10:  return "Return";
             case 27:  return "ESC";
             case 32:  return "Space";
             case 33:  return "" + (char)8607; // page up
             case 34:  return "" + (char)8609; // page down
             case 35:  return "End";
             case 36:  return "Begin";
             case 37:  return "" + (char)8592; // cursor left
             case 38:  return "" + (char)8593; // cursor up
             case 39:  return "" + (char)8594; // cursor right
             case 40:  return "" + (char)8595; // cursor down
             case 112: return "F1";
             case 113: return "F2";
             case 114: return "F3";
             case 115: return "F4";
             case 116: return "F5";
             case 117: return "F6";
             case 118: return "F7";
             case 119: return "F8";
             case 120: return "F9";
             case 121: return "F10";
             case 122: return "F11";
             case 123: return "F12";
             case 127: return "DEL";
         }

Björn

...this was a tricky situation, but the solution interesting for ohters as well:

In the scenario the client for accessing the layout editor was not running on the same machine than the layout editor environment itself. For this reason the resolution of "localhost" did not work...

Each project has a project configuration file in which the "host:port" of the deployment environment is registered. After updating the "locahost:8080" to "xx.xx.xx.xx:8080" everything worked fine.

Björn

...darf ich Sie um mehr Details bitten? Was machen Sie, um zu der Meldung zu gelangen? Am besten noch einen Screenshot.

Danke! Björn Müller

...there are already some "special keys" which are transferred into correct character representations. We missed the DEL... (and others as well). We will make our internally kept translation table a bit longer...

Same with language...

Both apsects are treated as bug and will be solved short term.

Björn

...oh yes, it was added with the update of last week. Before catching last week's build: we will publish a new update in something like 30-60 minutes. Maybe you wait some minutes (it's lunch break anyway...)

Björn

OK, is fixed...
Björn

We're just about to deliver a version update today. The fix will be part of today's update.

...yes, can reproduce...
Thanks, we will check.
Björn