How to guarantee a class is never exposed to the client side with Vaadin

Question

I understand that Vaadin uses some logic to expose the UI code, and then calls the server to access the code through Javascript. However, let's say that I have Listener, for example, with some code that references other classes. So, let's say I have something like:

PojoClass data = DatabaseClass.getDataFromDatabase();
doSomeProcessingOnData(data);
..
myTextField.setValue(data.getSomeValue());
..

Now, how can I be sure that the code is DatabaseClassnot displayed as Javascript. I suppose this happens, but more specifically, how can you say that a method doSomeProcessingOnData(data)that can have calls to say that 4-5 different classes that have some internal IP property are not affected? I understand what PojoClasswill be displayed, but I do not want the internal objects to doSomeProcessingOnData(data)be displayed.

Answer 1

Business logic stays on the server side

The business logic of your Vaadin application remains server-side in pure Java. Therefore, no exposure risk.

Vaadin removes the user interface to the client.

, JavaScript ClickListener . Java , Vaadin JavaScript . , Java , , -, , , "Grand Total", , . : " " → "Grand Total textField ".

Vaadin - XWindows.