You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Matthew Broadhead <ma...@nbmlaw.co.uk> on 2017/11/25 22:32:06 UTC
@Singleton duplicate deployment ids
Hi,
I am sure I have had this problem before but I wondered if you could
clarify.
If I have 2 different webapps containing 2 singletons with the same
simple name I get
org.apache.openejb.assembler.classic.Assembler.createApplication
Application cannot be deployed as it contains deployment-ids which are
in use
if one is called
com.example.MySingleton
and the other is called
com.example2.MySingleton
then why do they clash?
What is the best way to avoid this?
Matthew
Re: @Singleton duplicate deployment ids
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Default id is the ejbname - historical reason. You can tune it with a
system property to add the app name in the id.
Le 25 nov. 2017 23:32, "Matthew Broadhead" <ma...@nbmlaw.co.uk>
a écrit :
> Hi,
> I am sure I have had this problem before but I wondered if you could
> clarify.
> If I have 2 different webapps containing 2 singletons with the same simple
> name I get
> org.apache.openejb.assembler.classic.Assembler.createApplication
> Application cannot be deployed as it contains deployment-ids which are in
> use
> if one is called
> com.example.MySingleton
> and the other is called
> com.example2.MySingleton
> then why do they clash?
> What is the best way to avoid this?
>
> Matthew
>