Hi Rodrigo,
Some changes to the LooCI components and event bus where made recently
with regards to specifying a componentID when a component is started
and including that componentID in the event header when the component
publishes an event. This allows more meaningfull interception of the
events for policy reasoning and might prevent loops. The changes
required LooCI components to be changed a little, so that's why you
might be experiencing a bit of trouble.
Just for the record, the most important changes made were:
- the initialise() method is now called with a componentID as a
parameter
- the subscriptions are now passed to the EventManager in a 2-dim
array. Each
row contains the sourcecomponent's ID as first element, followed by
the
eventTypes for which you subscribe. (This is not ideal, but will have
to do for
now.)
I suggest you try to use the following versions of LooCI and
examples:
- LooCI: check out the /src and /resources folders from /svn/trunk/
sunspot/runtime at the SVN repo of LooCI at our Google code site. This
is the latest version with the previous mentioned adaptations.
- examples: we didn't update all examples, but LightSensor,
LightFilter and LightDisplay should be running fine. You can find them
in the SVN repo under /svn/trunk/sunspot/examples
For the rest, the explanation at the Wiki should help you out with
deploying the libraries and examples to SunSPOTs. Note however, the
"Programming Applications from scratch" section is a bit out of date
and doesn't reflect the changes mentioned above. But they were little,
so it should not be that difficult to figure them out.
I'm sorry for the troubles this caused you and if you have any more
questions, please don't hesitate to ask!
Finally, I never tried to use LooCI with Solarium. You'll somehow need
to make sure the LooCI runtime library is available to the virtual
spots. I can only refer you to the Solarium manual and the forum at
sunspotworld.com
Best regards,
Klaas