On 4/21/11 11:15, Derek Baum wrote:
On 21 April 2011 15:57, Richard S. Hall<[email protected]> wrote:
On 4/21/11 9:00, Derek Baum wrote:
I tripped across this yesterday.
I've explained the problem in this jira:
https://issues.apache.org/jira/browse/FELIX-2927
The work-around is to replace
bundle 0
with
(bundles) 0
I suppose you could also do:
bundle "System Bundle"
Right?
-> richard
Not unless "System Bundle" happens to be the location of the bundle:
public Bundle getBundle( String location )
Parameter location - The location of the bundle to retrieve.
"System Bundle" is the standard location of the system bundle...it is in
o.o.f.Constants.
-> richard
Returns - the bundle with the specified location.
A Bundle object or null if the location does not match any installed bundle.
Since: 1.6
Derek
the former attempts to invoke getBundle(long) but actually invokes
getBundle(String)
the latter invokes getBundles() and then returns the first element.
On 21 April 2011 12:53, Kirchev, Lazar<[email protected]> wrote:
Hello,
I am using Gogo 0.8.0 and I run it with Equinox. I noticed that
when Gogo starts, an exception is printed before the Gogo prompt
becomes available. The exception is caused by the execution of the
default gosh_profile script in org.apache.felix.gogo.shell bundle.
Particularly the fragment ${.context} bundle 0 in addcommand system
((${.context} bundle 0) loadclass java.lang.System) is not
evaluated correctly. The evaluation tries to call
BundleContext.getBundle(String location) with argument 0, instead
of BundleContext.getBundle(long id). The evaluation returns null,
because there is no bundle with such location and the whole
evaluation fails with the exception
bundleresource://3.fwk25675100/gosh_profile: ERROR:
java.lang.RuntimeException: Command name evaluates to null:
${.context} bundle 0.
Any workaround for this? However, it is not a big problem, since
the shell is fully operational after that.
Regards, Lazar
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
