I’m going to open a bug for this, but…
We have a Liferay cluster of 2 systems sharing one database. To perform an update, we take one of the systems out of the cluster and deploy our updates. When it is ready, we’ll switch traffic to the updated system and perform the update on the other system. We purposefully handle deployments this way so we can test fully before making the changes live…
Normally this process works, but we have some custom Vaadin components that we sometimes update and deploy. When we deploy these updates, we use the Vaadin Control Panel for Liferay to recompile the widgetset so the server outside of the cluster has the right widgetset for testing to be successful.
Today we noticed, however, that something is getting set in the database that ends up breaking the system that has not been updated. For example, the system in the cluster has components-1.0 but the one that is being updated has components-1.1.
As soon as we compile the widgetset to get components-1.1 active, the server w/ components-1.0 gets the “Widgetset does not contain implementation for…” error, basically because it is looking for components-1.1 but it isn’t there yet.
So the question is, what needs to change so that Vaadin would refer to just “components” rather than “components-1.0” or “components-1.1”? I don’t want the system that the users are using to start failing because it hasn’t been updated yet…