Simplified "Singleton" pattern in WELD

[hirowla.ian.rowlands.three.com.au]

I was just wondering if this was the best way to do a singleton pattern using Weld (I'm not talking about EJBs, I know that's a bit different):

• Mark a bean as application scoped


• Use @Inject to inject the class, but don't use @New (to force a new one).

Would this work in a clustered application, across different servers, or would this be specific to one JVM? Also, is there an easy way to ensure that @New can't be requested?

Or am I looking for a cheap way around the Singleton pattern and should just stick to the traditional way?

Thanks,

Ian

[nickarls]

I'm not sure how synchronous access would work for distributed, application scoped components so I would go for a EJB. Not that I'm sure how it works there either but I would guess they have thought about it :-)

[gavin.king]

For a real cluster-scoped singleton, you would need to implement a @ClusterScoped scope, on top of something like JBossCache or infinispan.