Thank you for your response, I successfully got the globalAlternatives to
work, except one issue. I have an interface and two default
implementations. Both implementations are active because of a qualifier
because of an enum value.
@MyQualifier(MyEnum.PROP1)
class MyImpl1 implements MyInterface{
...
}
@MyQualifier(MyEnum.PROP2)
class MyImpl2 implements MyInterface{
...
}
Now I need to replace both of these implementations, but filling the
apache-deltaspike.properties with the following:
globalAlternatives.com.example.MyInterface=com.example.OtherImpl1
globalAlternatives.com.example.MyInterface=com.example.OtherImpl2
doesn't work because com.example.MyInterface is the key so it is only
activating one of the lines.
Do you think it is possible to do what I am trying to achieve? If so, can
you lend some advice?
Thank you
On Thu, May 30, 2013 at 2:52 PM, Cody Lerum <[email protected]> wrote:
> If this is in 0.4 then an example for enabling the
> BeanManagedUserTransactionStrategy
> for Transaction support would be
>
> /src/main/resources/META-INF/apache-deltaspike.properties
>
> contents are
>
>
> globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.BeanManagedUserTransactionStrategy
>
> The prefix of "globalAlternatives." is required in 0.4
>
> The location as built in my war it ends up @
>
> myApp.war\WEB-INF\classes\META-INF\apache-deltaspike.properties
>
>
>
> On Thu, May 30, 2013 at 10:11 AM, Marco Corona
> <[email protected]>wrote:
>
> > Hello,
> > I have been trying to figure out how enable global alternatives, yet I
> > can't seem to find much documentation on the issue at all. Can anyone
> point
> > me in the right direction or even give me an example?
> > Thank you,
> > Marco Corona
> >
>
