I have a double layer between openkeepass (the library I am using) and the gui

there is a MainController that is used by the gui and the maincontroller directs to a repository class that encapsulates the library

so I could think about having the repository do the translation between poko and pojo

this is a set back

@ron maybe the tradeoff is that the treeview isn't data driven - are you able to change the domain objects themselves?

yes that is all done in the repository

and the reason that they can't use observable lists is?

I need to think about that

ah yes, the domain objects are in effect jaxb elements this the Group object:

@User uploaded a file: Untitled

@gtnarg I also do what's the equivalent of an event bus notification after the POJOs get changed. Some code can be optimistic and anticipate a successful update, but loosely-coupled code will want to know about the change.

I use the evenbus now

this is the update code

for apps where there is a singular relationship between view and model, like a basic CRUD, the layers just seem like overhead but for larger apps that start sharing models, there is a lot of value

@carlw - with a list update how do you detect the change or do you manually fire off an event when you are about to make the change?

I fire the event

@gtnarg I call a model update, capture the event by a view model that has access to something that's observable (or multiple somethings). the view is automatically updated

there's a Task in the middle of this

hmmz the only place where I have this issue is with the groupview, the entryview is fine as that is always packed in a sortedfilteredlist

I'd be inclined to create the treeitem manually and add a listener which detects the new item and then updates the domain model. Is there somewhere in the code where these items get created on the domain layer (i.e., not initiated through the gui)?

@carlw - so are proposing a populate method which listens for event bus messages and updates in response?

@gtnarg yeah. and i'm not recommending this for every app, but the app I'm thinking about has a big update problem. One aspect of the program can update the javafx data structures optimistically then follow up with a model call. For example, add to a treeview, then update a pojo collection. However, this puts that code in a special status, wanting to ignore notification from the event bus. it's more consistent if everyone responds to the notifications as though someone else initiated it if you have a strong view/model pairing, then i might be more direct. but i've seen the simple case grow rapidly

i also make the initiator responsible for the async call

i'm just wondering in @ron case if it's worth the effort of making it data driven?

Not sure, my suggestion is from a steady stream of tickets related to inconsistent data. The update problem to me is really serious because, at the developer level, you're not really empowered to have an expansive testing session. Sometimes even with good practices, it's "get in / get out" and not encouraged to drift into other areas

@ron - I don't think you are precluded from using ObservableList with JAXB - see http://stackoverflow.com/q/33190431/4931921

@gtnarg Problem is that the domain objects (like Group) are from an external project (https://github.com/cternes/openkeepass)

it would mean splitting of