[
https://issues.apache.org/jira/browse/WICKET-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935110#comment-17935110
]
ASF subversion and git services commented on WICKET-7150:
---------------------------------------------------------
Commit 40c2ca18cb857defa8b3976b02000602ed4d38f2 in wicket's branch
refs/heads/wicket-9.x from Martin Grigorov
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=40c2ca18cb ]
WICKET-7150: Do not check whether the javax impl is in use (#1121)
The non-JSR-356 impls were removed long time ago in favour of the
standard one.
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
(cherry picked from commit f821f7b4c0e184c1a69672ea3c1fd6332666c784)
> 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
> Priority: Major
> Fix For: 10.5.0
>
>
> 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)
