nice to see you here.

The main difference is that in OSGi a configuration of a bundle or a service can be updated at runtime. You can use the ConfigurationAdmin service to add or update configurations.

In contrast a configuration of a Tapestry service is passed to the service at creation time. This means for singleton services that the configuration is created only once, for per-request services every time a new instance is created. The configuration is created by calling the contribution methods. There is no way to change the configuration after the service has been created.

A further difference is the configuration object. In OSGi a Configuration consists of a dictionary. The values types of the dictionary are limited to single values or arrays of String, Integer, Long, Float, Double, Byte, Short, Character, Boolean. In Tapestry a service configuration can also consist of further services available in the service registry.