Hello,
This is the use case I'm implementing... My first real OSGi project is a
web front end for a lightweight ERP platform that bundles a AJAX/JS GUI
framework (the back office, no OSGi), where the front end (OSGi) runs in a
separate process with an embedded Jetty web server. The front end
That sounds perfect for what I'm trying to do!
Quoting Marcel Offermans marcel.offerm...@luminis.nl:
On 14 Jul 2011, at 23:00 , john.dun...@exceter.com wrote:
I would like to hide the update mechanism from the end user. As far
as the client is be concerned, the application should be
Hello John,
Probably makes sense to follow up on the ACE mailing list. We don't yet have
users list so feel free to use the ace-dev list for that (I cc'ed this mail
to it as well).
Greetings, Marcel
On 15 Jul 2011, at 15:36 , john.dun...@exceter.com john.dun...@exceter.com
wrote:
That
I'm interested in using OSGI as an update mechanism in a swing based
app. However, I'm concerned that managing the extremely dynamic nature
of OSGI is too difficult.
How can guarantee that the client's OSGI container will remain in a
known state which is identical to the state of the OSGI
On 7/14/11 13:33, john.dun...@exceter.com wrote:
I'm interested in using OSGI as an update mechanism in a swing based
app. However, I'm concerned that managing the extremely dynamic nature
of OSGI is too difficult.
How can guarantee that the client's OSGI container will remain in a
known
I would like to hide the update mechanism from the end user. As far as
the client is be concerned, the application should be versioned as a
whole. For example, I would like the client to see that an update from
version 1.2.3.4 to 1.2.3.5 is available. Behind the scenes the update
would
On 7/14/11 17:00, john.dun...@exceter.com wrote:
I would like to hide the update mechanism from the end user. As far as
the client is be concerned, the application should be versioned as a
whole. For example, I would like the client to see that an update from
version 1.2.3.4 to 1.2.3.5 is
On 14 Jul 2011, at 23:00 , john.dun...@exceter.com wrote:
I would like to hide the update mechanism from the end user. As far as the
client is be concerned, the application should be versioned as a whole. For
example, I would like the client to see that an update from version 1.2.3.4
to
8 matches
Mail list logo
