[webbeans-dev] Status update
by Pete Muir
There are two issues remaining for alpha1:
* dependent context destruction. I have this about 75% implemented
locally, I shall finish it tomorrow.
* EE (EJB) integration
EE Integration status:
* code base has been refactored to correctly wire both real and mock
EJBDescriptors through to EJB lookup and EnterpriseBean
* JBoss5 EJB3 is now exposing the correct metadata
* JBoss 5 Bridge code is written, needs testing and write up (later/
tomorrow)
* Embedded EJB3 (for testing EnterpriseBean lifecycle in RI unit
tests) won't be ready for use in our alpha1
* JBoss5 bridge code currently has no unit tests. Testing of this for
the alpha1 will be through the examples and real deployments
* We need an EJB example, I'll write one based around the
SentanceTranslator (tomorrow)
Gavin, is there anything else you want us to do before alpha1?
I've attached the current deployer and example. To use, just unzip the
deployer inside $JBOSS_HOME/server/default/deployers and copy the war
to $JBOSS_HOME/server/default/deploy and start JBoss5.
16 years
[webbeans-dev] EJB lifecycle
by Pete Muir
Section 6.9 says that we should intercept the @PostConstruct of an EJB
to do injection, initialization, interceptor stack binding etc. And
this works well :-)
So, what I've done is:
@PostConstruct
public void postConstruct(InvocationContext invocationContext)
{
Class<?> beanClass = invocationContext.getTarget().getClass();
Bean<?> bean =
CurrentManager.rootManager().getBeanMap().get(beanClass);
if (bean instanceof EnterpriseBean)
{
EnterpriseBean<Object> enterpriseBean =
(EnterpriseBean<Object>) bean;
enterpriseBean.postConstruct(invocationContext.getTarget());
}
To get the relevant Bean, and then run the post construct tasks. I can
see two flaws here. First, accessing the manager through current
manager, second that there could be multiple Enterprise Beans
registered for a particular bean class. In Seam there is some
ThreadLocal used to hold the currently invoking bean. Does this seem
like the best approach, or am I missing the obvious?
16 years
[webbeans-dev] Re: [seam-dev] EJB3 Releases
by Pete Muir
[Move to webbeans-dev]
Thanks man :-) I just finished the EJB example, and updated to this
release - all looks good!
On 18 Dec 2008, at 21:06, Andrew Lee Rubinger wrote:
> I've released:
>
> jboss-ejb3-as-int:1.0.0-Beta11
> jboss-ejb3-plugin-1.0.0-Alpha1
>
> ...and their dependencies.
>
> These have been updated in AS trunk and Branch_5_0. I'm still
> waiting on the Hudson results from the larger TestSuites.
>
> Seam guys, you now have a proper dependency in the form of the Plugin.
>
> Anil, this will bring into AS the security manager support we'd
> discussed a couple weeks back.
>
> S,
> ALR
>
> --
> Andrew Lee Rubinger
> Sr. Software Engineer
> JBoss, a division of Red Hat, Inc.
> http://exitcondition.alrubinger.com
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
16 years
[webbeans-dev] [10.2 XML Configuration]
by Gurkan Erdogdu
Hi;
In part 10.2 it says that
If the annotation type is already declared as a binding type, interceptor binding type or stereotype using annotations, the
annotations are ignored by the Web Bean manager and the XML-based declaration is used.
What does it mean?
For example I have a component
@PaymentType
class Payment{}
where @PaymentType is an binding type, that is annotated with @BindingType.
In some webbeans-xml file, there is also binding type
<myapp:PaymentType>
<BindingType/>
</myapp:PaymentType>.
It means that while webbeans manager scans the Payment component, it does not use @PaymentType on the class level?
Thanks;
Gurkan Erdogdu
16 years
