Alin,
On 18.03.2009, at 17:43, Alin Dreghiciu wrote:
On Wed, Mar 18, 2009 at 6:24 PM, Heiko <[email protected]> wrote:
The only thing I wonder (also with your solution) is what will
happen if one
HttpService does not start because another HttpService in another
OSGi
runtime already blocks the default port. Would it work to test free
ports
and then configure the HttpService via Config Admin? Would it
(re-)start
then?
Heiko
If you mean that Pax Web is testing the free ports and reconfigure
itself then that is not the case. Pax Web will just use the ports
specified.
No, I do not expect a miracle or some kind of christmas present right
now ;-)
But if you provide that functionality by yourself (scan for free
ports) and then reconfigure via Configuration Admin, Pax Web will
reconfigure itself to the new port values.
That was my plan. But I wonder whether I can configure Pax Web with an
invalid/used port.
What will happen then beside of some exceptions in my log file? Will
Pax Web be still alive to be reconfigured for another try?
If you find it useful we can easy implement also the part where Pax
Web will find it's free port and use it, since we already have such a
functionality from Pax Exam.
YES: I do find that useful! Is it already christmas time?
Question is then how you will know what
port to use? Of course that I can publish the found value as
HttpService property, but still.
Hm, good question.
I think in my use case the service property will be just fine. But
there might be other use cases ...
What about another service which is just an Array of ports?
By the way: I fixed the PID in the Wiki (http://wiki.ops4j.org/display/ops4j/Pax+Web+-+Configuration
). Hope that's OK.
Cheers
Heiko
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
