Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-6294

Check for non-empty baseUrl in BaseWebSocketBehavior

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 7.5.0
    • Fix Version/s: None
    • Labels:
      None

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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mgrigorov Martin Grigorov
                Reporter:
                Vit Springl Vit Springl
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: