<?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: The dm Shell</title>
	<atom:link href="http://blog.springsource.com/2009/10/15/the-dm-shell/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.com/2009/10/15/the-dm-shell/</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Sat, 20 Mar 2010 12:14:29 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Frost</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-171466</link>
		<dc:creator>Chris Frost</dc:creator>
		<pubDate>Tue, 02 Mar 2010 13:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-171466</guid>
		<description>Great, thanks for posting that Dennis. 

As I say we never looked in to how people would extend the Shell. We could make it a little easier I agree but there is nothing wrong with editing the config. We put it out in text files for just that reason :)
I like the idea of a separate annotation for User Commands. 

I&#039;d stick with the Command annotation as well.</description>
		<content:encoded><![CDATA[<p>Great, thanks for posting that Dennis. </p>
<p>As I say we never looked in to how people would extend the Shell. We could make it a little easier I agree but there is nothing wrong with editing the config. We put it out in text files for just that reason <img src='http://blog.springsource.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
I like the idea of a separate annotation for User Commands. </p>
<p>I&#039;d stick with the Command annotation as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis Kramer</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-171464</link>
		<dc:creator>Denis Kramer</dc:creator>
		<pubDate>Tue, 02 Mar 2010 12:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-171464</guid>
		<description>Hi Chris,

thanks. That exactly what I did. Just thought there might be a way that works without customizing the DM server config. 
Anyway, for the record, here the detailed description:

- I created a tagging interface &quot;UserCommand&quot; that marks all my command implementations in the user region and has no methods.

To bridge the services of the user region into the kernel, the following changes are made to the DM Server config file com.springsource.kernel.userregion.properties:
*  Add to packageImports: com.springsource.kernel.shell;version=&quot;[2.0.0,2.0.1)&quot; to make the Command annotation available in the user region.
* Add to serviceExports: &quot;.UserCommand&quot; to bridge all Services that implement UserCommand to the kernel 

So far, it works like a charm. To use CommandCompleter as well one just needs to add this interface to serviceExports as well. I did not yet used the ServiceRegistry based command resolver, just the one based on the Command annotation.

I could not find a way to bridge services based on annotations. May I suggest to include a tagging interface in com.springsource.shell? This way, this procedure would be less of a hack. :-)

Cheers, Denis</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>thanks. That exactly what I did. Just thought there might be a way that works without customizing the DM server config.<br />
Anyway, for the record, here the detailed description:</p>
<p>- I created a tagging interface &#034;UserCommand&#034; that marks all my command implementations in the user region and has no methods.</p>
<p>To bridge the services of the user region into the kernel, the following changes are made to the DM Server config file com.springsource.kernel.userregion.properties:<br />
*  Add to packageImports: com.springsource.kernel.shell;version=&#034;[2.0.0,2.0.1)&#034; to make the Command annotation available in the user region.<br />
* Add to serviceExports: &#034;.UserCommand&#034; to bridge all Services that implement UserCommand to the kernel </p>
<p>So far, it works like a charm. To use CommandCompleter as well one just needs to add this interface to serviceExports as well. I did not yet used the ServiceRegistry based command resolver, just the one based on the Command annotation.</p>
<p>I could not find a way to bridge services based on annotations. May I suggest to include a tagging interface in com.springsource.shell? This way, this procedure would be less of a hack. <img src='http://blog.springsource.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Cheers, Denis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Frost</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-171463</link>
		<dc:creator>Chris Frost</dc:creator>
		<pubDate>Tue, 02 Mar 2010 11:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-171463</guid>
		<description>Hi Denis,

The shell has had a bit of a rewrite since this blog post went out. The Shell is run in the Kernel region and not available to the user region. Although we do not support the addition of new commands I don&#039;t think it would be very hard. From your comment I&#039;m guessing you&#039;ve had a look at the code. All you would need to do is deploy a normal bundle that publishes commands in the same way that the other ones do. Then edit the config files to allow your service to be mapped up to the kernel region. I think you would only need to add your service to the &#039;serviceExports&#039; list in the &#039;com.springsource.kernel.userregion.properties&#039; file. I&#039;d be interested to know how you get on as we haven&#039;t tried this with the new shell system.

Thanks, Chris.</description>
		<content:encoded><![CDATA[<p>Hi Denis,</p>
<p>The shell has had a bit of a rewrite since this blog post went out. The Shell is run in the Kernel region and not available to the user region. Although we do not support the addition of new commands I don&#039;t think it would be very hard. From your comment I&#039;m guessing you&#039;ve had a look at the code. All you would need to do is deploy a normal bundle that publishes commands in the same way that the other ones do. Then edit the config files to allow your service to be mapped up to the kernel region. I think you would only need to add your service to the &#039;serviceExports&#039; list in the &#039;com.springsource.kernel.userregion.properties&#039; file. I&#039;d be interested to know how you get on as we haven&#039;t tried this with the new shell system.</p>
<p>Thanks, Chris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis Kramer</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-171451</link>
		<dc:creator>Denis Kramer</dc:creator>
		<pubDate>Mon, 01 Mar 2010 18:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-171451</guid>
		<description>@Chris:

Does the service property based discovery actually work with services that are not provided as part of the kernel? How can I make the shell aware of a command provided as service in the user realm?

Cheers,
Denis</description>
		<content:encoded><![CDATA[<p>@Chris:</p>
<p>Does the service property based discovery actually work with services that are not provided as part of the kernel? How can I make the shell aware of a command provided as service in the user realm?</p>
<p>Cheers,<br />
Denis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Frost</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-168929</link>
		<dc:creator>Chris Frost</dc:creator>
		<pubDate>Wed, 21 Oct 2009 16:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-168929</guid>
		<description>@Mike

Well, the dm Shell is our own implementation, any similarities are coincidental. I&#039;m glad you like it though.

Chris.</description>
		<content:encoded><![CDATA[<p>@Mike</p>
<p>Well, the dm Shell is our own implementation, any similarities are coincidental. I&#039;m glad you like it though.</p>
<p>Chris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-168928</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 21 Oct 2009 15:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-168928</guid>
		<description>Based on Felix or Karaf I see...

Very good, I always liked their commandline interfaces better anyway.</description>
		<content:encoded><![CDATA[<p>Based on Felix or Karaf I see&#8230;</p>
<p>Very good, I always liked their commandline interfaces better anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Frost</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-168905</link>
		<dc:creator>Chris Frost</dc:creator>
		<pubDate>Tue, 20 Oct 2009 08:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-168905</guid>
		<description>@Sudheer

Have you tried the packages command, by the sounds of it this should give you most of what you want. If not could you give me some more detail? As for the tree structure for uses conflicts, I can see how this would help. I have raised a Jira for it so it gets discussed in the team. Users conflicts are hard to resolve, we will need to be careful with any interface we create for their resolution. (https://issuetracker.springsource.com/browse/DMS-1765)

@Alex

We are making some enhancements to the services information in our current sprint which should help you a lot. I&#039;m going to ask someone working on the Hyperic integration to comment on your 2nd point.

Thanks to both of you for your comments.</description>
		<content:encoded><![CDATA[<p>@Sudheer</p>
<p>Have you tried the packages command, by the sounds of it this should give you most of what you want. If not could you give me some more detail? As for the tree structure for uses conflicts, I can see how this would help. I have raised a Jira for it so it gets discussed in the team. Users conflicts are hard to resolve, we will need to be careful with any interface we create for their resolution. (<a href="https://issuetracker.springsource.com/browse/DMS-1765" rel="nofollow">https://issuetracker.springsource.com/browse/DMS-1765</a>)</p>
<p>@Alex</p>
<p>We are making some enhancements to the services information in our current sprint which should help you a lot. I&#039;m going to ask someone working on the Hyperic integration to comment on your 2nd point.</p>
<p>Thanks to both of you for your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simplaso &#187; New Post</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-168902</link>
		<dc:creator>Simplaso &#187; New Post</dc:creator>
		<pubDate>Tue, 20 Oct 2009 04:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-168902</guid>
		<description>[...] the Admin Console? (I can almost hear you ask.) Well, the answer is also provided in M5—use the Shell either locally or remotely (over ssh). You’d think we planned this, or [...]</description>
		<content:encoded><![CDATA[<p>[...] the Admin Console? (I can almost hear you ask.) Well, the answer is also provided in M5—use the Shell either locally or remotely (over ssh). You’d think we planned this, or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-168898</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 19 Oct 2009 21:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-168898</guid>
		<description>Hi,

just two suggestions:
1. we&#039;re using dm Servers &quot;Bundle Overview&quot; tab inside of STS very often to resolve resolution errors as it shows which of the exported services are currently being consumed by which other bundles. It would be nice if you could enrich the output of the &quot;bundle details&quot; command mentioned above with this information

2. Enhance dm Server-Hyperic HQ integration in the way that
  a) the dm Shell of the currently selected dm Server node can be accessed from within Hyperic
  b) ONE dm Shell can be send (from within HQ) to a group of dm Servers and the outputs of each instance is sent back and made available in Hyperic
  c) resolution conflicts/ problems - as mentioned above - can be seen within Hyperic (Actually I&#039;m not too sure whether this can not already be realized with the current version of Hyperic)

Thanks in advance and please keep up the good work!

Regards
Alex</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>just two suggestions:<br />
1. we&#039;re using dm Servers &#034;Bundle Overview&#034; tab inside of STS very often to resolve resolution errors as it shows which of the exported services are currently being consumed by which other bundles. It would be nice if you could enrich the output of the &#034;bundle details&#034; command mentioned above with this information</p>
<p>2. Enhance dm Server-Hyperic HQ integration in the way that<br />
  a) the dm Shell of the currently selected dm Server node can be accessed from within Hyperic<br />
  b) ONE dm Shell can be send (from within HQ) to a group of dm Servers and the outputs of each instance is sent back and made available in Hyperic<br />
  c) resolution conflicts/ problems &#8211; as mentioned above &#8211; can be seen within Hyperic (Actually I&#039;m not too sure whether this can not already be realized with the current version of Hyperic)</p>
<p>Thanks in advance and please keep up the good work!</p>
<p>Regards<br />
Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sudheer Krishna</title>
		<link>http://blog.springsource.com/2009/10/15/the-dm-shell/comment-page-1/#comment-168864</link>
		<dc:creator>Sudheer Krishna</dc:creator>
		<pubDate>Sat, 17 Oct 2009 07:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2969#comment-168864</guid>
		<description>I have really found debugging very difficult when i have many bundles installed.

It would be a great help if some utility commands can be provided in the console which will help me in debugging.

My great concern was import/export packages and sometime i run with uses conflict.

During this time some utility like 

Given a package name - i want the bundles exposing it

                      - different versions available along with bundles exposing it.


Some tree structure which helps me resolve uses conflict etc would be greatly appreciated.

Regards,
Sudheer Krishna</description>
		<content:encoded><![CDATA[<p>I have really found debugging very difficult when i have many bundles installed.</p>
<p>It would be a great help if some utility commands can be provided in the console which will help me in debugging.</p>
<p>My great concern was import/export packages and sometime i run with uses conflict.</p>
<p>During this time some utility like </p>
<p>Given a package name &#8211; i want the bundles exposing it</p>
<p>                      &#8211; different versions available along with bundles exposing it.</p>
<p>Some tree structure which helps me resolve uses conflict etc would be greatly appreciated.</p>
<p>Regards,<br />
Sudheer Krishna</p>
]]></content:encoded>
	</item>
</channel>
</rss>
