Have you tried @Alternative? You'll have to enable it in beans.xml.

On Thu, Jan 12, 2012 at 15:02, michal.kaplon@poczta.fm <michal.kaplon@poczta.fm> wrote:

Recently we found a bug in JpaIdentityStore class. In line 2114 query
string is build this way:

queryString.append("select distinct ior. " +
modelProperties.get(PROPERTY_RELATIONSHIP_TO).getName() + "from "

which produces unparseable query. Since it is in 3.1.0.Final, waiting
for the next release probably isn't the best solution :)
That's why I need to replace default JpaIdentityStore with my custom
implementation. How can I do that?

I've tried to reconfigure JpaIdentityStoreConfiguration via XML, but
identityStoreClass remains unchanged. Very strange thing, especially
that server log says the bean is reconfigured. Is that because
IdentityStoreConfiguration.identityStoreClass is private field?
IdentityStoreConfiguration itself cannot be configured, because it is

Next try was to @Specialize JpaIdentityStoreConfiguration, however it
also failed. This issue smells like @AplicationScoped beans cannot be
specialized, which is also weird.

Any help will be appreciated.

Best regards,

seam-dev mailing list

Jason Porter

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu