In the Http Service we actually attach the properties to the service itself.
But the remote shell has not any exported service right? In that case, I'm
not sure what would be the best approach.
On Mon, Oct 5, 2009 at 10:30 PM, Richard S. Hall wrote:
> On 10/5/09 21:37, Sten Roger Sandvik wrote:
>
On 10/5/09 21:37, Sten Roger Sandvik wrote:
BTW. It seems like a good feature to include. I actually used this in the
http service to crete a http "alive" osgi bundle.
Any suggestions how? Create some sort of dummy service to which it
attaches its property?
-> richard
On Mon, Oct 5, 20
BTW. It seems like a good feature to include. I actually used this in the
http service to crete a http "alive" osgi bundle.
On Mon, Oct 5, 2009 at 9:25 PM, Richard S. Hall wrote:
> So, is there any way to discover on which port number the remote shell is
> listening for connections? If the port i
Good you asked about this. I totally forgot to include this functionality in
the new Http Service. Added as a Jira task now. Yes, it was in 1.0.1 of
Jetty Http service.
On Mon, Oct 5, 2009 at 9:25 PM, Richard S. Hall wrote:
> So, is there any way to discover on which port number the remote shell
So, is there any way to discover on which port number the remote shell
is listening for connections? If the port is configured to 0, then it
will choose an open port, but how do we know which it is?
In the HTTP Service impl, I believe we attach a service property
indicating the port, but in th
