I guess my last sentence did not communicate my idea. Re-reading it I
see that it was poorly constructed.
Yes, for update() but I was speaking of update(InputStream). A
developer would pass the input stream with what intentions? The spec
says that it merely stops and starts the framework and, so, the input
stream is superfluous. IMO, we should throw an exception to inform
the developer that what ever he thought was going to happen with that
input stream isn't going to come to pass.
Regards,
Alan
On Feb 20, 2008, at 10:46 AM, BJ Hargrave wrote:
It is the logical extension of the system bundle which represents the
framework. If SystemBundle.stop stops the framework and
SystemBundle.start
starts the framework, the SystemBundle.update would stop and then
start
the framework. If the framework implementor has some additional update
semantics for their framework, they could also occur here.
--
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]
office: +1 386 848 1781
mobile: +1 386 848 3788
From:
Alan Cabrera <[EMAIL PROTECTED]>
To:
OSGi Mail List Developer <[email protected]>
Date:
2008-02-20 13:18
Subject:
[osgi-dev] update(InputStream) for system bundle
IMO, it should throw a bundle exception. Maybe I'm being dense. What
would the reason be for it to stop and start the framework?
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://www2.osgi.org/mailman/listinfo/osgi-dev
