[jira] [Created] (WICKET-6294) Check for non-empty baseUrl in BaseWebSocketBehavior

["Vit Springl (JIRA)" <ji...@apache.org>]

Vit Springl created WICKET-6294:
-----------------------------------

             Summary: Check for non-empty baseUrl in BaseWebSocketBehavior
                 Key: WICKET-6294
                 URL: https://issues.apache.org/jira/browse/WICKET-6294
             Project: Wicket
          Issue Type: Bug
          Components: wicket-native-websocket
    Affects Versions: 7.5.0
            Reporter: Vit Springl
            Assignee: Martin Grigorov


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

{code}
...
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]
...
{code}

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()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)