« Return to Thread: Related subjects, listeners and lists with out-of-pipeline dependencies

Re: Related subjects, listeners and lists with out-of-pipeline dependencies

by Holger Brands :: Rate this Message:

Reply to Author | View in Thread

Hey Kevin,

>[snip]
> If I'm thinking
> about it correctly, what I need to say is that the 'parent' listener
> is dependent on subject 'child', so I'd think that the following call
> would suffice:
>
> publisher.setRelatedListener(parent, child)
>
> To paraphrase the javadoc, this would make it so "Child's dependencies
> are satisfied before Parent is notified"

I'd say, your interpretation is correct. I'd have tried the same...

>
> but when I specify this, I get an exception on the next source list
> mutation:
>
> java.lang.UnsupportedOperationException
>  at ca.odell.glazedlists.event.SequenceDependenciesEventPublisher$
> NoOpEventFormat.fire(SequenceDependenciesEventPublisher.java:406)
> [snip]
> If anyone can point out what I might be doing wrong, I'd really
> appreciate it.

I guess the problem in your case is, that "child" (the second parameter
to method setRelatedListener(...)) is not only a pure ListEventListener, but
also a producer of ListEvents.
(The current usages of setRelatedListener in the GL code base only
deal with pure listeners as second parameter.)
So this appears to be a shortcoming of the current implementation in GL,
rather than a mistake on your side.

Jesse, James please correct me if I'm wrong...;-)

Holger
____________________________________________________________
Text: GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

 « Return to Thread: Related subjects, listeners and lists with out-of-pipeline dependencies