cse这种cse://appId:serviceName/path调用方式，会在URI内部抛出一个URISyntaxException异常

大致原因是在CseUriTemplateHandler中的createUri方法会调用new URI方法创建一个url对象，而cse的url中appId:ServiceName会被解析为port，导致URI内部抛出URISyntaxException异常，进入异常捕获的逻辑

在高并发场景下，这里成为了性能瓶颈，是否可以考虑新增一种appId.ServiceName的形式呢？

Start in CseUriTemplateHandler.createUri and trace how new URI handles the cse://appId:ServiceName/path form and its exception path. Determine the intended alternative syntax and verify that the supported form avoids URISyntaxException in concurrent use while preserving the URI behavior described in the issue.

Written by the indexing model from the issue text.