[WICKET-6294] Check for non-empty baseUrl in BaseWebSocketBehavior

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 7.5.0
• Component/s: wicket-native-websocket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Vit Springl
• Created: 06/Dec/16 15:52
• Updated: 06/Dec/16 15:59
• Resolved: 06/Dec/16 15:58

Description

After upgrade to 7.5.0 the following exception is thrown when the WebSocketBehavior is rendered:

...
Caused by: java.lang.IllegalArgumentException: Argument 'baseUrl' may not be null or empty.
	at org.apache.wicket.util.lang.Args.notEmpty(Args.java:64) ~[wicket-util-7.5.0.jar:7.5.0]
	at org.apache.wicket.protocol.ws.api.BaseWebSocketBehavior.renderHead(BaseWebSocketBehavior.java:100) ~[wicket-native-websocket-core-7.5.0.jar:7.5.0]
	at org.apache.wicket.protocol.ws.api.WebSocketBehavior.renderHead(WebSocketBehavior.java:62) ~[wicket-native-websocket-core-7.5.0.jar:7.5.0]
...

It seems to me that an empty String should be accepted here. I have checked and it worked fine in 7.4.0 with an empty String in baseUrl. The same for filterPrefix. An empty String is actually set in certain cases in WebSocketSetting#getFilterPrefix().

Issue Links

• duplicates: WICKET-6262 IllegalArgumentException: Argument 'filterPrefix' may not be null or empty with WebSocketBehavior