Whats the drawback for @ApplicationScoped eg.
@Repository
@ApplicationScoped
public interface UserRepository extends EntityRepository<User, Long> {
User findOptionalByUsernameEqual(String username);
}
On 16 December 2014 at 14:23, Thomas Andraschko <[email protected]
> wrote:
>
> :D
>
> IMO it also doesn't make sense to serialize repositories!
>
> 2014-12-16 14:16 GMT+01:00 Thomas Hug <[email protected]>:
> >
> > Officially declaring this the "Thomas" thread ;-)
> >
> > Agree with Thomas that going for AppScope is probably the simplest
> > workaround for now. I remember some efforts for serialization (as OWB
> > complained for some cases) but overall it does not work well when you
> have
> > to inject EMs or use Instance<>. Fixing this properly might require a
> major
> > refactoring.
> >
> > On Tue, Dec 16, 2014 at 8:17 AM, Thomas Andraschko <
> > [email protected]> wrote:
> > >
> > > Hi,
> > >
> > > i would make your repositories AppScoped.
> > > Unfortunately AppScoped doesn't work for abstract repositories :/ I
> still
> > > have the same problem ->
> > > https://issues.apache.org/jira/browse/DELTASPIKE-647
> > >
> > >
> > > 2014-12-15 23:47 GMT+01:00 Thomas Frühbeck <[email protected]>:
> > > >
> > > > Hi,
> > > >
> > > > we are integrating Data module of DS as vital part of our persistence
> > > > layer, but unfortunately Repositories are not Serializable, so that
> > SFSB
> > > or
> > > > SessionScoped beans with Dependent scoped dependencies on
> Repositories
> > > will
> > > > fail in cluster configurations.
> > > >
> > > > Due to some recent overuse of scoped dependencies we would like to
> > > refrain
> > > > from again starting to scope vital infrastructure.
> > > >
> > > > Can you give some advice, which way to solve this problem?
> > > >
> > > > Many thanks for your dedication to DeltaSpike and your help,
> > > > Thomas
> > > >
> > >
> >
>
