sense in this context. Might be better to improve EjbUtility and downstream
> to register it once and not fail a deployment if the same class shows up
> again in another BaseEjbBean.
>
> Open to thoughts on the right change.
For now I just added a DuplicateDefinitionException and made BeanMa
On Aug 4, 2010, at 12:18 AM, Mark Struberg wrote:
> But maybe I miss something: what do you mean with different meta-data in this
> context?
For example, something like this:
BeanOne
org.foo.MyEjbClass
Stateful
!
But maybe I miss something: what do you mean with different meta-data in this
context?
LieGrue,
strub
- Original Message
> From: David Blevins
> To: dev@openwebbeans.apache.org
> Sent: Wed, August 4, 2010 8:55:39 AM
> Subject: Re: EJBUtility.fireEvents
>
> Ok, so t
njected with @New (thus the name)
>
> LieGrue,
> strub
>
>
>
>
> - Original Message
>> From: Gurkan Erdogdu
>> To: dev@openwebbeans.apache.org
>> Sent: Wed, August 4, 2010 7:58:47 AM
>> Subject: Re: EJBUtility.fireEvents
>>
>>
in other words, we are adding
1.) the original bean
2.) the bean which can be injected with @New (thus the name)
LieGrue,
strub
- Original Message
> From: Gurkan Erdogdu
> To: dev@openwebbeans.apache.org
> Sent: Wed, August 4, 2010 7:58:47 AM
> Subject: Re: EJBUtilit
--Gurkan
From: David Blevins
To: dev@openwebbeans.apache.org
Sent: Wed, August 4, 2010 1:40:22 AM
Subject: EJBUtility.fireEvents
Curious on this part of that method:
manager.addBean(WebBeansUtil.createNewBean(ejbBean));
manager.addBe
Curious on this part of that method:
manager.addBean(WebBeansUtil.createNewBean(ejbBean));
manager.addBean(ejbBean);
Wondering why we need to essentially add the bean twice. Running into an issue
as the NewBean impl uses only class information to construct the un
