[
http://issues.ops4j.org/jira/browse/PAXRUNNER-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11188
]
Alin Dreghiciu commented on PAXRUNNER-127:
------------------------------------------
Stuart,
After the last changes I saw that once the framework is tarted if you hit
Ctrl+C, there are a lot of exception as bellow. Please check that out also.
java.io.IOException: Stream closed
at
java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
at java.io.BufferedInputStream.read(BufferedInputStream.java:304)
at org.ops4j.pax.runner.platform.internal.Pipe.run(Pipe.java:95)
at java.lang.Thread.run(Thread.java:613)
> Provide a way to start OSGi framework using an external Java runner service
> ---------------------------------------------------------------------------
>
> Key: PAXRUNNER-127
> URL: http://issues.ops4j.org/jira/browse/PAXRUNNER-127
> Project: Pax Runner
> Issue Type: New Feature
> Components: platform extender, runner
> Affects Versions: 0.7.2
> Reporter: Stuart McCulloch
> Assignee: Stuart McCulloch
> Fix For: 0.8.0
>
>
> Currently Pax-Runner doesn't work well in Eclipse debug mode, because the
> process being debugged is the launching process not the OSGi framework.
> Eclipse does support tracking and debugging of additional processes, but this
> requires improving Pax-Runner to support starting the OSGi framework as
> daemon process (no waitFor) and returning the started Process through the
> Pax-Runner API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
