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.MCAST_PORT_DEFAULT); setDomainStringProperty(JavaGroupsBridge.JGROUPS_CONFIG_URL_PROPERTY, javaGroupsFile, ""); if (StringUtils.equals(eventBridgefactory, JavaGroupsBridgeFactory.class.getName())) ... If I didn't add JGroupsModule as a DI module it crashed (forget the exact reason right now, but I can try it again later). Note: It didn't break ages ago when I was using 4.0.B1, but after I updated it to use 4.0.2. When using B1 I had access to the constants without needing to provide a JGroups dependency. Maybe best to duplicate the constants locally and drop the dependencies? I just don't like repeating things... mrg On Mon, Dec 20, 2021 at 1:37 AM Andrus Adamchik <aadamc...@gmail.com> wrote: > 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. > > Andrus > > > On Dec 19, 2021, at 6:35 PM, Michael Gentry <blackn...@gmail.com> wrote: > > > > While getting the JavaFX modeler running again, I was having issues with > > JGroups classes/interfaces not being found/defined, so I added version > 5.x > > to the POM and it didn't work. Then 4.x and it didn't work. Then 3.x and > it > > didn't work. Then 2.x and it finally worked. > > > > Does Cayenne only work with JGroups 2.x? * > > > > Thanks, > > > > mrg > > > > * I used 2.12.3.Final here... > >
