I would like to implement a service that requires some configuration. Amongst other things it needs to know the location of a certain file.
So I have defined an element for this purpose: <element name="file"> <attribute name="location" required="true"/> ... </element> It doesn't make sense to specify the file location more than once. But as far as I can see there is no way to prevent it: <contribution configuration-id="Test"> <file location="file1"/> <file location="file2"/> </contribution> Using <configuration-point occurs="1"> does not help. I think it would be better to have something like <element occurs="1"> for situations like this. If Hivemind knew that a certain element can only occur once it would also be possible to inject the corresponding object directly into the service, instead of injecting a list of objects. Of course this would also require that the configuration schema defines only one element. Any thoughts? Markus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
