|
| Re: [NEON] Hot Swapping UI changes made in Java [message #1755821 is a reply to message #1755760] |
Wed, 08 March 2017 12:44  |
|
It's important to understand that the Html UI part of Scout only renders the current state of the Java model that exists in the Scout client on the UI server. Typically a Scout developer works with getConfigured* methods to define properties in the Scout model. These getConfigured* methods are only called in the initConfig() method, which is called by the constructor of a Scout object. This means when you add a new getConfigured* method to a field in a Form, this will have no effect on an existing instance of that Form (even when your VM can handle hot code swapping).
However, you could change the _properties_ of a Scout object directly in the Java Debugger and then perform a reload in the browser. Basically initConfig does the same thing: it reads the value returned by getConfigured* and then sets the according property via a setter method.
When you work with forms the simple solution is to close the current form and open the form again, which will create a new instance and call all getConfigured* methods.
Some Scout objects (like outlines) are only instantiated one time for each ClientSession. In that case you can simply kill the current session, either programatically or by calling the /logout URL. When you login again (or call the start URL of your Scout app) you'll get a new ClientSession and also new instances of your outlines.
Eclipse Scout Homepage | Documentation | GitHub
|
|
|
Powered by
FUDForum. Page generated in 0.03365 seconds
] 
Search
Help
Register
Login
Home
