[KT2L] Suspecte Assertation Exception mit Vaadin in Selenium Chrome Driver

Für einen Abend Kopfschmerzen hat mich eine merkwürdige Exception gekostet, die nur in den Tests mit Selenium auftritt. In der Entwicklung ist die Exception nicht aufgetaucht.

Eingrenzen konnte ich die Quelle zumindest im Source-Code auf eine Änderung in der DeskTabBar. Hier habe ich anstelle von einem setContent( newPanel ) nun alle Panels in ein Layout gepackt und nur das Panel sichtbar, das aktuell aktiv ist. Damit gehen die Inhalte des Panels nicht verloren, bzw. muss nicht neu gerendert werden (vor allem mit Addons gibt es hier oft Probleme, z.B. vis und xTerm).

Bei der Änderung wird an jeden Panel die CSS-Class 'hidden' angehängt. Genau dieser Befehl löst die `Assertation: null` Exception von Vaadin aus. Die Exception wird in einem anderen Thread geworfen.

Als Lösung kann DaskTabBar nun beide Strategien umsetzen. In den Selenium-Tests wird das Alte Vorgehen genutzt, im Betrieb das Verbesserte.


Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

Sonatype Nexus fails with random "peer not authenticated" errors behind ingress

 After installing nexus3 server in a kubernetes environment in the first view everything looks good. Server is running an accessible from the world. Users and roles are defined and working. But already in the first hours of working with the repository there are problems. The trick was retry the failed activity and everything went ok. It turned out that heavy activities failed a lot of times and a lot of retries have to be done to finish the tasks. Annoying if a release deploy failed. You need to increase the version number every time. There were a few support in the internet for the problems most of the time handling SSL problems between maven and nexus. But it did not fix the problem. It looks like maven and the used http library wagon have got problems with pooled connections if using ingress (a test with a standalone installation did not show the problem)  - The 'deep' reason is not really clear for me, need to invest more time for it. The solution is to deny wagon to use p...
Mehr anzeigen

[mhus lib] Reorg in generation 7 nearly finished

 The generation 7 shows massive reorganisations and reimplementations. After renaming repository names (moved the 'cherry' prefix to 'mhus') the reorg is finished and the sources are ready for a more stable generation 8. Generation 8 will add new features to work with none OSGi services in cloud environments. Actual changes: cherry-reactiive -> mhus-reactive cherry-vault -> mhus-vault cherry-web -> mhus-web mhus-osgi-cluster -> mhus-cluster
Mehr anzeigen

[mhus lib] Implemented Bearer JWS tokens

 mhus now supports bearer tokens for authentication. I used the project jjwt to implement the tokens and added dependencies of the current version 0.11.2. The token is implemented to be used with apache shiro. A new service JwtProvider implements creation and reading of the tokens. The keys if not exists will be created and stored in the keychain. Private and public keys in separate key sources. In this way the public keys can be published to other nodes. A new interface BearerRealm must be used to mark realms with Bearer support. Using the interface a token can be created from the realm implementation. You should use the AccessUtil to create tokens. The authentication is already implemented in rest and micro calls. Via rest a node '/jwt_token' can be used to create a token - expires after one hour - and use it as authentication. To use jjwt with osgi I as forced to create a port project. First the 'feature' character of the bundles is not supported in the current felix...
Mehr anzeigen