You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Daniel Stoch (Jira)" <ji...@apache.org> on 2025/03/12 17:05:00 UTC

[jira] [Created] (WICKET-7150) Cyclic dependency between wicket-native-websocket-core and wicket-native-websocket-javax modules

Daniel Stoch created WICKET-7150:
------------------------------------

             Summary: Cyclic dependency between wicket-native-websocket-core and wicket-native-websocket-javax modules
                 Key: WICKET-7150
                 URL: https://issues.apache.org/jira/browse/WICKET-7150
             Project: Wicket
          Issue Type: Bug
          Components: wicket-native-websocket
    Affects Versions: 9.19.0
            Reporter: Daniel Stoch
            Assignee: Martin Tzvetanov Grigorov


There is a cyclic dependency issue between the wicket-native-websocket-core and wicket-native-websocket-javax modules. The wicket-native-websocket-core module has a dependency on the wicket-native-websocket-javax module through the WebSocketSettings class, which uses Class.forName("org.apache.wicket.protocol.ws.javax.JavaxWebSocketFilter").

This results in the wicket-native-websocket-core module importing the org.apache.wicket.protocol.ws.javax package in its MANIFEST.MF. Since the wicket-native-websocket-javax module already depends on the wicket-native-websocket-core module, this creates a cyclic dependency between these two modules.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)