Hello Dennis, Are you sure you're using the new code, as this is exactly the same line that I fixed?
Stepping though the code is a matter of launching the JVM with remote debugging parameters and then connecting to it from Eclipse. Should be pretty straightforward. Greetings, Marcel On 6 Jan 2011, at 3:30 , Dennis Crissman wrote: > > Marcel, > > I see that you fixed this error, however I am getting another one now that is > similar (see below). > > Additionally, I would like to be able to step through the code in Eclipse. > Maybe I missed the documentation for that somewhere? > > Error in C:\path\Apache-Ace\ace-devserver\store : Low Range is higher than > High Range: 4.1.3-4.1.3 > java.lang.IllegalArgumentException: Low Range is higher than High Range: > 4.1.3-4.1.3 > at > org.osgi.impl.bundle.obr.resource.VersionRange.<init>(VersionRange.java:44) > at > org.osgi.impl.bundle.obr.resource.ManifestEntry.addParameter(ManifestEntry.java:93) > at > org.osgi.impl.bundle.obr.resource.Manifest.getEntries(Manifest.java:211) > at org.osgi.impl.bundle.obr.resource.Manifest.entry(Manifest.java:124) > at org.osgi.impl.bundle.obr.resource.Manifest.parse(Manifest.java:74) > at org.osgi.impl.bundle.obr.resource.Manifest.<init>(Manifest.java:42) > at > org.osgi.impl.bundle.obr.resource.BundleInfo.<init>(BundleInfo.java:60) > at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:204)g! > at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:195) > at org.osgi.impl.bundle.bindex.Index.main(Index.java:118) > at > org.apache.ace.obr.metadata.bindex.BIndexMetadataGenerator.generateMetadata(BIndexMetadataGenerator.java:40) > at > org.apache.ace.obr.storage.file.BundleFileStore.generateMetadata(BundleFileStore.java:136) > at > org.apache.ace.obr.storage.file.BundleFileStore.start(BundleFileStore.java:53) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.felix.dm.InvocationUtil.invokeMethod(InvocationUtil.java:45) > at > org.apache.felix.dm.InvocationUtil.invokeCallbackMethod(InvocationUtil.java:13) > at > org.apache.felix.dm.impl.ComponentImpl.invokeCallbackMethod(ComponentImpl.java:684) > at > org.apache.felix.dm.impl.ComponentImpl.invoke(ComponentImpl.java:675) > at > org.apache.felix.dm.impl.ComponentImpl.bindService(ComponentImpl.java:620) > at > org.apache.felix.dm.impl.ComponentImpl.access$400(ComponentImpl.java:52) > at org.apache.felix.dm.impl.ComponentImpl$7.run(ComponentImpl.java:178) > at > org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:47) > at > org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84) > at > org.apache.felix.dm.impl.SerialExecutor.access$000(SerialExecutor.java:33) > at > org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:50) > at > org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84) > at > org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:68) > at > org.apache.felix.dm.impl.ComponentImpl.calculateStateChanges(ComponentImpl.java:228) > at > org.apache.felix.dm.impl.ComponentImpl.dependencyAvailable(ComponentImpl.java:371) > at > org.apache.felix.dm.impl.dependencies.ConfigurationDependencyImpl.updated(ConfigurationDependencyImpl.java:207) > at > org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1112) > at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:88) > > Thanks, > Dennis Crissman > >> From: [email protected] >> Subject: Re: Gateway discovery >> Date: Wed, 5 Jan 2011 08:21:11 +0100 >> To: [email protected] >> >> Hello Dennis, >> >> On 5 Jan 2011, at 4:44 , Dennis Crissman wrote: >> >>> 1. How do I connect a gateway to a server? >> >> A gateway uses its Discovery service to find out where the server is it >> should connect to. This service basically returns a URL. The default >> implementation of that service can be configured using ConfigurationAdmin >> (see ace-discovery-property). The PID of that configuration is >> "org.apache.ace.discovery.property" and the single key you need to supply is >> "serverURL". >> >> If you want to change the default when building the ace-target-devgateway >> assembly, look in: >> >> ace-target-devgateway/src/main/resources/conf/org.apache.ace.discovery.property.cfg >> >> and change the default (localhost) to something different. >> >> >>> 2. When I start the server, I get the following error. >>> {code} >>> Error in >>> C:\path\Apache-Ace\ace-target-devserver-0.8.0-SNAPSHOT-distribution\ace-devserver\store >>> : Low Range is higher than High Range: 4.1.3-4.1.3 >>> java.lang.IllegalArgumentException: Low Range is higher than High Range: >>> 4.1.3-4.1.3 >>> at >>> org.osgi.impl.bundle.obr.resource.VersionRange.<init>(VersionRange.java:44) >>> at >>> org.osgi.impl.bundle.obr.resource.ManifestEntry.addParameter(ManifestEntry.java:93) >> >> You've ran into https://issues.apache.org/jira/browse/ACE-95 which is still >> open. I did not have time myself to look into it yet, but that should be in >> ace-obr-metadata. I'll try to look into it when I have time, but feel free >> to supply a patch if you've figured it out before me! >> >> Greetings, Marcel >> >> >
