Without knowing your details, I suspect that you have a common setup
problem, namely that an ES can not use itself to store its
configuration.
Therefor, you need to stick the Configuration in a separate module
(Rickard reports that he has stuck all Conf in its own layer at the
bottom) and in that module there is another config-less, module-
visible ES and the S3 config is visible to the S3 ES.
Does that make sense?
Definitely !
But using different modules to store the config sounds complicated to
me.
I plan to ignore any ES request originating from the Configuration
service until the Configuration service is itself activated.
It is not the best solution but, it is quite logical that a
Configuration cannot be stored in an ES using the same Configuration
service!
Thanks Niclas
phil
-- Niclas
On Aug 22, 2009 9:00 PM, "philippe van dyck" <[email protected]>
wrote:
Hi,
Since Rickard's change in the Configuration creation mechanism
(commit c08f7b35455e9d62db99f654e20e158c57a4c23c) I have a problem
in the S3 ES.
I use a Configuration object in the ES to specify credentials for
S3 in the ES activate() method.
The added buildUow.complete(); of
qi4jRuntimeImpl.getConfigurationInstance(...) creates a
StackOverflow because the UoW completion tries to activate the ES
again.
Should I avoid using Configuration in an ES activate() method ?
Cheers,
Philippe
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
