Hi all,
I finally finished the refactoring of the URLStreamHandlerFactory and
ContentHandlerFactory stuff (see FELIX-38 for the submission).
As the factory registration process is influenced by the
Equinox/Eclipse solution, it would probably be good if someone could
look at the patch to see whet
Excellent. Thanks.
-> richard
Felix Meschberger wrote:
Hi Richard,
I cannot fix the situation of having Felix in different class loaders,
this is an inherent situation of the servlet API, where different web
applications are required to have different class loaders (AFAIK).
But I will take ca
Hi Richard,
I cannot fix the situation of having Felix in different class loaders,
this is an inherent situation of the servlet API, where different web
applications are required to have different class loaders (AFAIK).
But I will take care of Felix handling the situation correctly by
using refl
Felix Meschberger wrote:
Do you have a need for it now or are you just wish listing?
Unfortunately I have a need for this, as my application will run
inside a servlet container and must support running in an application
server and requires custom URL stream handlers
If you don't mind, I w
Hi Richard,
There is actually a JIRA issue for latter issue (don't know the number...i am
traveling).
Its FELIX-38 and contains a link to the respective Eclipse bug.
Do you have a need for it now or are you just wish listing?
Unfortunately I have a need for this, as my application will ru
sible, but I
wonder if it is worth it right now.
Do you have a need for it now or are you just wish listing?
-> richard
-Original Message-
From: "Felix Meschberger" <[EMAIL PROTECTED]>
Subj: Re: URL Handlers Service
Date: Wed 1. Nov 2006 7:10
Size:
Hi Karl,
Felix already does provide something like that. Have a look at:
Yes, I know and this is great. But this (1) class is package private,
hence not available from outside, and (2) if the Felix is instance
sets the framework.service.urlhandlers property to false the URL
handler support is
Hi Felix,
How about having a per-framework URL Handler registry just like the
URLHandlers class which is registered as a service. This service could
serve URLs and content handlers by calling the system URL factory
first (after checking for the "bundle:" protocol) and then the locally
registered
Hello Jeremy,
Jeremy Volkman wrote:
I assume you're referring to SecurityManager.getClassContext()?
Yes.
The only problem I foresee is if a SecurityManager is installed that
disallows creation of new SecurityManagers (there is a check for this
in the SecurityManager constructor). If you d
Hi Richard,
On 11/4/05, Richard S. Hall <[EMAIL PROTECTED]> wrote:
[snip]
>
> The approach I use to route incoming handler requests is to use the
> security class context, which gives me the call stack of classes. I then
> search backwards to find the first class loaded from a bundle and then
>
Upayavira wrote:
It is great to see you working hard on this. I get the impression that
this was quite a knotty one.
Actually, the implementation turned out to be pretty
straightforward...the difficulty was more just deciding on the approach.
This work has taken me a while because I have
Richard S. Hall wrote:
> [Warning! This will probably be long.]
>
> Ok, I am on the verge of committing my URL Handlers service
> modifications to Felix. Currently, URL Handlers is broken for Felix and
> this should fix that; it should also add explicit support for using URL
> Handlers with multip
apache.org
Subject: Re: URL Handlers Service
Kaegi, Simon wrote:
>Interesting stuff. (Hopefully this thread is still alive) I like your
>third approach best too.
>
>
Well, I don't know if the thread is active, but this issue still is. I
have started a first pass of the third ap
Kaegi, Simon wrote:
Interesting stuff. (Hopefully this thread is still alive)
I like your third approach best too.
Well, I don't know if the thread is active, but this issue still is. I
have started a first pass of the third approach and I will see where
that takes me.
You mention your
Interesting stuff. (Hopefully this thread is still alive)
I like your third approach best too.
The first approach excludes the 2nd, 3rd, ... framework from adding new
handlers which depending on the handler and how the framework uses it
might be very problematic and in some cases might prevent the
15 matches
Mail list logo
