Hi Praveen,

pmanvi <praveena.manvi <at> gmail.com> writes:

> ...
> 
> Do let me know if you find some solution to the same.

actually, in the end I got it working using Christoph's suggestion to use the
URL(scheme, host, port, path, handler) constructor. Unless that legacy system
you're using unwraps and reconstructs your URL objects somewhere down the
implementation (i.e., using the ctor that only takes a URL spec), this should
work just fine.

Of course it's still merely a workaround, because you have to manually detect
custom schemes and construct an appropriate handler for those. You could
obviously move this code to a factory, but you will effectively only be
duplicating what URLStreamHandlerFactory already does/is supposed to do... this
sort of shows how absurd this issue actually is... I'm kinda disappointed that
it receives so few attention on the Java issue tracker.

Anyway, HTH!

Best,
Matt


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to