Thanks, Dan.
I’ve read the discussion between the 2 alternatives. Also that there are some
plans to “extend” support for CDI-style. Really interesting.
Regards,
Oscar
El 13/11/2014, a las 1:51, Dan Haywood d...@haywood-associates.co.uk
escribió:
I've raised ISIS-948 for this.
On
My ideas about how to leverage CDI are slowly forming. I envisage that
there being a CDI container that bootstraps the various singleton and
request-scoped services, and then the rest of the runtime reaches in for
objects as needs be. Meanwhile, if I can identify a component/piece of
Oscar,
fyi (as you might have noticed) I decided to further refactor the
EventBusService so that the underlying guava EventBus is now in effect a
singleton, rather than request-scoped. Many fewer moving parts, at the
expense of a lack of symmetry.
The noteworthy changes are:
- both
I've raised ISIS-948 for this.
On 21 October 2014 10:38, GESCONSULTOR - Óscar Bou o@gesconsultor.com
wrote:
Thanks for your response, Dan.
Have you seen the usage pattern at [1] using @PostConstruct and
@PreDestroy?
Probably it could be used for both request-scoped and singleton
There's a thread discussing the multiple registration and unregister exception
thrown subjects here [1].
Perhaps a similar implementation on the EventBusService will also do the trick.
Any opinions?
Thanks,
Oscar
[1] https://code.google.com/p/guava-libraries/issues/detail?id=784
El
Hi Oscar,
I need to think this through a bit... I have a strong suspicion that what
we have is too complex. My thinking is that I've implemented the
registration/deregistratrion for each request/transaction. However, given
that services are basically singletons, I'm wondering if there is any
Thanks for your response, Dan.
Have you seen the usage pattern at [1] using @PostConstruct and @PreDestroy?
Probably it could be used for both request-scoped and singleton services, don't
you think?
Thanks,
Oscar
[1] http://es.slideshare.net/koneru/guavas-event-bus
El 21/10/2014, a
Just to clarify in order to being able to determine the root cause.
We are currently registering the EventBusService as this:
public class AssetsRiskInformation extends
AbstractSingletonMultiTenantObjectRepositoryAndFactoryAssetRiskInformation {
...
// {{ injected: EventBusService
