[Rifidi-developers] Edge Server Refactoring

[Rifidi-Developers L. <rif...@li...>]

Jochen and I refactored the edge server over the past two days so that
service interfaces and service implementations reside in different
bundles.  This allows us to restart parts of the edge server without
restarting the whole thing.

So here is the list of projects that you will need to check out from svn
now:

org.rifidi.configuraiton
org.rifidi.edge.api
org.rifidi.edge.console
org.rifidi.edge.core
org.rifidi.edge.core.rmi.server
org.rifidi.edge.core.services
org.rifidi.edge.core.services.esper
org.rifidi.edge.core.services.jms
org.rifidi.edge.core.services.notifications
org.rifidi.edge.core.services.soap.cxf.internal
org.rifidi.edge.epcglobal.ale.api.logicalreader
org.rifidi.edge.epcglobal.ale.api.read
org.rifidi.edge.readerplugin.alien
org.rifidi.edge.target
org.rifidi.log4j.configuration

I think everything works now.  I tested Adding/Removing readers,
sessions, getting tags back, & ALE

Jochen: Since I talked to you yesterday, I added the
org.rifidi.edge.core.services.jms bundle which handles starting up the
core jms objects.  It was needed so that the services.notifications
bundle didn't have dependencies on services exported by core (since
before JMS objects were being exported to the OSGi registry from the
core bundle ).

Tobi: you will have to update the edge server and the edge client, since
some of these changes were renaming of API classes, which affects the
client

Matt: These changes will break your LLRP plugin.  I can help you
tomorrow to get things back in order.

-- 
Kyle Neumeier
Technical Lead
Pramari, LLC
Manchester, CT