<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SpringSource manifest headers registered with OSGi</title>
	<atom:link href="http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Fri, 19 Mar 2010 05:36:47 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alin Dreghiciu</title>
		<link>http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/comment-page-1/#comment-130650</link>
		<dc:creator>Alin Dreghiciu</dc:creator>
		<pubDate>Thu, 27 Nov 2008 21:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=767#comment-130650</guid>
		<description>I would have voted for the decorated ones. The fact that people make mistakes on a header name could happen very easy on any kind of name (e.g. easy to say Web-FilterMapping instead of Web-FilterMappings).
But if we would had the decorated ones it will at least:
* people do not think that those headers are standard OSGi headers and expect them to work &quot;all over the place&quot;, e.g. Import-Bundle will only work on SpringSource DM Server and they can be taken as standard headers by people
* people could easy find by the prefix a hint where to look for that header 

But I guess this discussion should be on the OSGi Alliance list not here :)</description>
		<content:encoded><![CDATA[<p>I would have voted for the decorated ones. The fact that people make mistakes on a header name could happen very easy on any kind of name (e.g. easy to say Web-FilterMapping instead of Web-FilterMappings).<br />
But if we would had the decorated ones it will at least:<br />
* people do not think that those headers are standard OSGi headers and expect them to work &#034;all over the place&#034;, e.g. Import-Bundle will only work on SpringSource DM Server and they can be taken as standard headers by people<br />
* people could easy find by the prefix a hint where to look for that header </p>
<p>But I guess this discussion should be on the OSGi Alliance list not here <img src='http://blog.springsource.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glyn Normington</title>
		<link>http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/comment-page-1/#comment-130640</link>
		<dc:creator>Glyn Normington</dc:creator>
		<pubDate>Thu, 27 Nov 2008 17:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=767#comment-130640</guid>
		<description>Yes, that would be possible and the OSGi Core Platform Expert Group did consider it, but registration of &#039;undecorated&#039; headers was preferred. The sort of issue you get into is that SpringSource would probably be given &quot;SpringSource-&quot; as a prefix and then users would make mistakes like spelling it &quot;Spring-Source-&quot;.

Only time will tell whether this decision was a good one, but the undecorated header names seem more usable at the moment.</description>
		<content:encoded><![CDATA[<p>Yes, that would be possible and the OSGi Core Platform Expert Group did consider it, but registration of &#039;undecorated&#039; headers was preferred. The sort of issue you get into is that SpringSource would probably be given &#034;SpringSource-&#034; as a prefix and then users would make mistakes like spelling it &#034;Spring-Source-&#034;.</p>
<p>Only time will tell whether this decision was a good one, but the undecorated header names seem more usable at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart McCulloch</title>
		<link>http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/comment-page-1/#comment-130638</link>
		<dc:creator>Stuart McCulloch</dc:creator>
		<pubDate>Thu, 27 Nov 2008 16:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=767#comment-130638</guid>
		<description>Josef, unfortunately you can&#039;t use &#039;:&#039; in manifest header names

from the Jar spec:

  header:      name : value
  name:        alphanum *headerchar
  alphanum:    {A-Z} &#124; {a-z} &#124; {0-9}
  headerchar:  alphanum &#124; - &#124; _

but I guess you could always use &#039;-&#039; in its place (say Spring-...)</description>
		<content:encoded><![CDATA[<p>Josef, unfortunately you can&#039;t use &#039;:&#039; in manifest header names</p>
<p>from the Jar spec:</p>
<p>  header:      name : value<br />
  name:        alphanum *headerchar<br />
  alphanum:    {A-Z} | {a-z} | {0-9}<br />
  headerchar:  alphanum | &#8211; | _</p>
<p>but I guess you could always use &#039;-&#039; in its place (say Spring-&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: josef betancourt</title>
		<link>http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/comment-page-1/#comment-130634</link>
		<dc:creator>josef betancourt</dc:creator>
		<pubDate>Thu, 27 Nov 2008 15:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=767#comment-130634</guid>
		<description>Apparently these will grow as other organizations and applications begin to use OSGi.  Would it make sense to instead use simple name spaces?  Like &quot;spring:Web-ContextPath&quot;. Thus, companies can also reserve name spaces instead of just adding to the default.   One exception to this is further complexity to the the manifest processing, perhaps.

Though they have raised many critiques in the XML world (especially on attributes), name spaces have been useful.

Just wondering.</description>
		<content:encoded><![CDATA[<p>Apparently these will grow as other organizations and applications begin to use OSGi.  Would it make sense to instead use simple name spaces?  Like &#034;spring:Web-ContextPath&#034;. Thus, companies can also reserve name spaces instead of just adding to the default.   One exception to this is further complexity to the the manifest processing, perhaps.</p>
<p>Though they have raised many critiques in the XML world (especially on attributes), name spaces have been useful.</p>
<p>Just wondering.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
