@borboss the best i can come up with is to handle the exception in the lambda that would throw the exception, returning a default Id like -1 for the next part of the stream. then, use a filter() to make sure that the -1 is not emitted to the subscriber

@borboss i was just experimenting with onError/ExceptionResumeNext. they will substitute a default Profile in if there is a failure. that doesn’t seem like what you want either

@carlw Yeah, I also found it. I might just make an extension function for myself, that would subscribe and pass onError to the CopositeObservable, that handles the error values

@carlw Thanks!

@borboss it’ll call your onError, but will it halt all processing?

@carlw I just have the ViewerModel with overriden onCommit() and inside onCommit I just create the new observable, that makes update on the DB, and that add it to the CompositeObservable of the controller. The problem with the exception, that sometimes is thrown from the Observable, that updates the db. (RxJava -jdbc). If I just add it to the CompositeObservable of the controller, the latter will terminate on error. And Gui becomes unresponsive. And all my error messages were in the onError methods of subscriptions. So now I just subscribe to observable in the onCommit method, and print the error if there was an error Anyway I just came to your idea of wrapping the exception, and passing it to the appropireate place

I'm using some nested views and tab panes and forwarding savable/refreshable save as well as save/refresh to the embedded views inside the tabs. Will make a screencast about this, because it will definitely be interesting if you create nested views.

@edvin That would be cool 😉 I have quite a lot nested views

@borboss Cool! Will post here when I have made the screencast 🙂

@edvin Well right now I have the view, that creates a couple of primitive ItemViewModels and passes a lambda to them, to invoke on onCommit. I just have a question - validator is a cool thing, but some validations need to look in the db. For example to check, whether the user with the same name exists. Is it possible now to do such validations, so they work together with commit?

Like i have a field with username, press “Add user” button, the commit is attempted, if it was successfull, it displayes some success message, if not, the username field is highlighted with the message “choose another name, please"

@borboss It's possible, but right now it happens on the UI thread. I think we'd need to adapt for async validation. Not sure how that would work yet though 🙂

I just added

TabPane.uiComponent

which will retrieve the View or Fragment that is docked in the currently selected Tab.

async await? 😉

@borboss Not sure how the rest of the validation system will react to that, it might also need adaptation to support this.

It's working 🙂 Finally! This was harder than expected, but now you can nest an arbitrary number of Nodes with TabPanes in them and forward refreshable/savable save as well as save/refresh actions to the bottom most selected tab etc. Pretty cool.

I mean, to UIComponents nested inside those Tabs.

If the top most element is a Workspace, the buttons in the workspace will of course also respect this.

Looking at the config feature again now.

@ron Maybe the

loadJsonModel

and friends should be extension functions on InputStream, Path and String instead of a standalone function?

And

string.toJsonObject()

and so on.

Hmmz works quite well now

@ron I'll stop obsessing over it 🙂

Did you look at the config PR? The

orElse

And I think the set(Pair<string, Any>) might be too broad it invites to put a class on it they did not have a toString,

@ron Yes, but I didn't use the PR, I just took some cues from it.

I will explain shortly, getting a visit from an entrepreneur any minute now.

Ok

@ron we discussed already that kotlin has the Elvis operator wich is doing the same as

orElse

if I am not mistaken the

set

function is the same as the one that exists already in coponent