[
https://issues.apache.org/jira/browse/FELIX-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882337#action_12882337
]
Derek Baum commented on FELIX-2446:
-----------------------------------
the whole gosh_profile is now enclosed in a try {} block, so it doesn't abort
startup if an error occurs:
$ java -jar bin/felix.jar
bundle://4.0:1/gosh_profile: ERROR: java.io.IOException: Resource does not
exist: bundle://4.0:1/motdx
> [Gogo] The bundle context command is not registered with a scope in
> gosh_profile
> --------------------------------------------------------------------------------
>
> Key: FELIX-2446
> URL: https://issues.apache.org/jira/browse/FELIX-2446
> Project: Felix
> Issue Type: Bug
> Components: Gogo Shell
> Affects Versions: gogo-0.6.0
> Reporter: Richard S. Hall
> Assignee: Derek Baum
> Fix For: gogo-0.8.0
>
>
> The default gosh_profile shell registers the bundle context as a command, but
> it is not assigned any scope. This apparently is problematic for anyone else
> registering a command with overlapping names as what is on bundle context.
> For example, registering a command named "bundle" causes the following
> gosh_profile line to fail:
> addcommand system ((bundle 1) loadclass java.lang.System)
> I am not sure why or how it is shadowing it, since it seems like the order
> should favor the built-in commands, but apparently. Regardless, if we had a
> scope assigned to this we could be precise in our gosh_profile shell (e.g.,
> gogo:bundle) to avoid this issue altogether.
> To make matters worse, this causes the entire shell bundle to die...it might
> be nice if it continued to function even if there are errors in the
> gosh_profile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
