> setDomainStringProperty(JavaGroupsBridge.MCAST_ADDRESS_PROPERTY,
> multicastAddress, JavaGroupsBridge.MCAST_ADDRESS_DEFAULT);
> setDomainStringProperty(JavaGroupsBridge.MCAST_PORT_PROPERTY,
> multicastPort, JavaGroupsBridge.MCAST_PORT_DEFAULT);
> setDomainStringProperty(JavaGroupsBridge.JGROUPS_C
Well, I was pulling in cayenne-jgroups primarily to access constants, such
as:
setDomainStringProperty(JavaGroupsBridge.MCAST_ADDRESS_PROPERTY,
multicastAddress, JavaGroupsBridge.MCAST_ADDRESS_DEFAULT);
setDomainStringProperty(JavaGroupsBridge.MCAST_PORT_PROPERTY,
multicastPort, JavaGroupsBridge.M
FWIW, I was about to suggest removing "cayenne-jgroups" from Cayenne 5.0 as an
old and unreliable piece of software we don't want to support :)
As far as the Modeler goes it should not depend on JGroups at all. All the
events in the Modeler are in-process and can be passed around within the JVM