Karl,
Yes, It should work fine. I'll try as you suggest.
Thanks a lot !
/pierre
Karl Pauls wrote:
Ok. Well, from my interpretation of the spec, this isn't possible
using an URLStreamHandler because of the build-in handlers being
preferred (and for good reasons).
However, it does sound to me li
Apparently, this part of the spec has been weakened for the next release
since neither Equinox nor KF actually enforced it.
Perhaps we should add an option for allowing overriding too.
-> richard
Pierre De Rop wrote:
Karl,
Yes, It should work fine. I'll try as you suggest.
Thanks a lot !
/p
Well, maybe. The issue is that it is not impossible that the jvm
already used a handler and then we are stuck (assuming the hack with
flushing the cache doesn't work). I agree that this is a corner case
but still. We should probably create a jira issue to track this and
come-up with a suggestion fo
Karl Pauls wrote:
Well, maybe. The issue is that it is not impossible that the jvm
already used a handler and then we are stuck (assuming the hack with
flushing the cache doesn't work). I agree that this is a corner case
but still. We should probably create a jira issue to track this and
come-up
> Karl Pauls wrote:
>>
>> Well, maybe. The issue is that it is not impossible that the jvm
>> already used a handler and then we are stuck (assuming the hack with
>> flushing the cache doesn't work). I agree that this is a corner case
>> but still. We should probably create a jira issue to track th
Hi Karl,
I come back to you on this problem.
I understand it's possible to provide an http/https URLStream handler,
by exposing some classes along with the classpath (like you suggested).
But the point is: we have implemented the http/https URL Stream handler
service in a bundle (our http conta
We created issue FELIX-756 a while ago to track this. Please go and
add your comment there.
I just assigned the issue to me and can try to look into it.
regards,
Karl
On Tue, Oct 21, 2008 at 10:48 AM, Pierre De Rop
<[EMAIL PROTECTED]> wrote:
> Hi Karl,
>
> I come back to you on this problem.
>
Hi Pierre,
I did implement the feature. You can now start the current trunk with
-Dfelix.service.urlhandlers.override=true in order to allow
URLStreamHandler and ContentHandler services to override the built-in
handlers. Please test and close the JIRA issue if it works for you.
regards,
Karl
On
I'm sorry Karl, I just missed the jira issue. I will add my comments in it.
thanks
/pierre
Karl Pauls wrote:
We created issue FELIX-756 a while ago to track this. Please go and
add your comment there.
I just assigned the issue to me and can try to look into it.
regards,
Karl
On Tue, Oct 21,
9 matches
Mail list logo