Peter Kriens wrote:
Well, I disagree. The bundle name is intended to be a short handle to
the bundle (start/stop etc). Using spaces makes tempts people to
change it to the description, for which we have a separate header.
Making very spacious names for bundles is very awkward, and tends to
become messy when used in lists. It also requires escaping if you have
to type the name in a shell. E.g. "start mybundle" is a lot easier to
handle then "start my\ fine\ acme\ bundle". There will be other places
where spaces need to be escaped.
I would say this use case seldom occurs. Most people just do "start
4"...with GUIs it is totally a non-issue.
Disallowing spaces does not stop people from making it long, it just
makes it look like this:
"ThisIsMyBundleName"
Instead of:
"This Is My Bundle Name"
I don't see the big difference.
We specifically have a description field that can tell you what the
bundle does. You can of course always abuse the name field for
advertising, but the name field was never meant to convey the exact
functionality of your bundle, it is a mnemonnic.
I don't think anyone was arguing for name being used to convey the exact
functionality of your bundle. It is an issue of "HTTP Service" versus
"HTTPService", that's all. I think everyone agrees that Bundle-Name
should be a reasonably short name.
-> richard
Anyway, it is a should and not a must. We were just trying to set some
conformity, which we can of course abolish in a next release.
Kind regards,
Peter Kriens
JM> Forwarding this to the OSGi general list as it is a spec question. Please
JM> continue any discussion there rather than cross posting.
JM> Jeff
JM> ----- Forwarded by Jeff McAffer/Ottawa/IBM on 03/17/2006 09:58 AM -----
JM> Jeff McAffer/Ottawa/IBM
JM> 03/17/2006 09:44 AM
JM> To
JM> [email protected]
JM> cc
JM> Subject
JM> Re: [jira] Created: (FELIX-48) Bundle names should conform to the spec and
JM> not contain spaces
JM> FWIW I think that "human readable" and "no spaces" are contradictory.
JM> Names should be meaningful. Names should be translatable. Names *should*
JM> have spaces.
JM> I have entered http://membercvs.osgi.org/bugs/show_bug.cgi?id=265 to look
JM> at this in future versions of the spec.
JM> Jeff
JM> "Marcel Offermans (JIRA)" <[EMAIL PROTECTED]>
JM> 03/17/2006 06:27 AM
JM> Please respond to
JM> felix-dev
JM> To
JM> [email protected]
JM> cc
JM> Subject
JM> [jira] Created: (FELIX-48) Bundle names should conform to the spec and not
JM> contain spaces
JM> Bundle names should conform to the spec and not contain spaces
JM> --------------------------------------------------------------
JM> Key: FELIX-48
JM> URL: http://issues.apache.org/jira/browse/FELIX-48
JM> Project: Felix
JM> Type: Bug
JM> Reporter: Marcel Offermans
JM> Assigned to: Richard S. Hall
JM> Priority: Trivial
JM> The OSGi specification (3.2.1.10) states that:
JM> The Bundle-Name header defines a readable name for this bundle. This
JM> should be a short, human-readable name containing no spaces.
JM> Currently, we do generate bundle names with spaces. Admittedly, this is
JM> done by many others too but I think we should stick to the specifications
JM> (even though "should" is not "must").
