Thanks for your reply.
As you said, by using a system.properties file as follows:
java.protocol.handler.pkgs=gnu.java.net.protocol
I can leave the code unaltered and run the framework as follows:
java -jar bin/felix.jar
I've found that the problem resides with the maven.felix.plugin. I
somehow need to set the system property as part of the integration
test phase in maven. I have tried passing the system property like so:
mvn
-Dfelix.system.properties=file:/home/krobinson/Desktop/work/6/felix/trunk/main/conf/system.properties
install
This does not work.
Looking at the debug info (in my post) I can see it also uses
Felix.java. Any ideas?
ken.
On 1/31/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
Ken Robinson wrote:
> I have then changed the file URLHandlers as follows but still get the
> same message:
> private static final String DEFAULT_STREAM_HANDLER_PACKAGE =
> "gnu.java.net.protocol";
> // private static final String DEFAULT_STREAM_HANDLER_PACKAGE =
> "sun.net.www.protocol";
>
> //private static final String DEFAULT_CONTENT_HANDLER_PACKAGE =
> "sun.net.www.content";
> private static final String DEFAULT_CONTENT_HANDLER_PACKAGE =
> "gnu.java.net.content";
>
> Is there something else I can do to get it working on jamvm and gnu
> classpath?
Yes, you definitely need to change these values. Are you sure those are
the correct values? In other words, did you look in the GNU Classpath
source, for example, and see if gnu.java.net.protocol.file.Handler exists?
BTW, you are not required to modify the source code, you can also just
set the "java.protocol.handler.pkgs" and "java.content.handler.pkgs"
system properties appropriately.
When searching for a handler, the URL Handlers service simply does a
class load probe in all listed packages using the following pattern:
<pkg-prefix>.<protocol>.Handler
So, there should be a class named "gnu.java.net.protocol.file.Handler"
in your situation.
I am pretty sure someone else got this working, maybe they have
something to add.
-> richard
