<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://protegewiki.stanford.edu/index.php?action=history&amp;feed=atom&amp;title=Talk%3AEmbedding_OSGi</id>
		<title>Talk:Embedding OSGi - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://protegewiki.stanford.edu/index.php?action=history&amp;feed=atom&amp;title=Talk%3AEmbedding_OSGi"/>
		<link rel="alternate" type="text/html" href="https://protegewiki.stanford.edu/index.php?title=Talk:Embedding_OSGi&amp;action=history"/>
		<updated>2026-04-29T05:57:52Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.27.7</generator>

	<entry>
		<id>https://protegewiki.stanford.edu/index.php?title=Talk:Embedding_OSGi&amp;diff=10415&amp;oldid=prev</id>
		<title>Mike Riley: Created page with &quot;To the author of this article:   The link titled &quot;following demonstration&quot;, in the second paragraph, is invalid.  It is currently pointing to:  http://smi-protege/repos/protege/p...&quot;</title>
		<link rel="alternate" type="text/html" href="https://protegewiki.stanford.edu/index.php?title=Talk:Embedding_OSGi&amp;diff=10415&amp;oldid=prev"/>
				<updated>2011-09-02T18:20:24Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;To the author of this article:   The link titled &amp;quot;following demonstration&amp;quot;, in the second paragraph, is invalid.  It is currently pointing to:  http://smi-protege/repos/protege/p...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;To the author of this article:   The link titled &amp;quot;following demonstration&amp;quot;, in the second paragraph, is invalid.  It is currently pointing to:  http://smi-protege/repos/protege/protege4/misc/examples/embedded/trunk  &lt;br /&gt;
&lt;br /&gt;
Assuming that this link was intended to point to source-code download, I think it would be very helpful, especially for someone like myself that has never used OSGi before.  We are developing an [open source] java app, and are experiencing jar conflicts between different frameworks that we are using, and am considering OSGI for resolving the issue. If that doesn't work, we will split out the framework into a separate app, and wrap it with a rest service api.  Actually, in your opinion, what advantage would an OSGI solution have over this [rest] approach?...in terms of code/architecture complexity, and/or performance?&lt;br /&gt;
&lt;br /&gt;
Thanks in advance for your consideration.&lt;/div&gt;</summary>
		<author><name>Mike Riley</name></author>	</entry>

	</feed>