From: Sven Linstaedt <[email protected]>
Subject: Re: September Report Content
To: [email protected]
Date: Wednesday, September 2, 2009, 9:23 PM
That is an interesting point. As far
as I know the jsr 299 spec does not say
anything about reusage of jsf2 annotations. jsf2 has it's
own petite DI
container with scopes and injection points, but also
defines some extra
stereotypes in addtion to ManagedBean like FacesComponent,
FacesBehavior,
FacesConverter, FacesRenderer and some else, which will be
registered for
their appropriate usage.
I would like to see the registration, instantiation and
injection of all
those component types to be handled by one mechanism, so
developers won't
get confused by the way annotations of jsr 214 and 299 are
working together.
br, Sven
2009/9/2 Mark Struberg <[email protected]>
Hi!
Theoretically OWB should work with all JSF
implementations, but I'm note
sure if it is really that seamless.
E.g. JSF2 also has scope annotations etc and I haven't
yet read about what
happens to them in the JSR-299 spec.
I also wrote ex gratia, so MyFaces would only be the
prefered test
container since it is an Apache project too.
We have all the sources and I also know a lot of the
people who wrote
MyFaces initially.
But yes, it should finally also work with Mojarra!
LieGrue,
strub
----- Original Message ----
From: Gurkan Erdogdu <[email protected]>
To: [email protected]
Sent: Wednesday, September 2, 2009 8:06:34 AM
Subject: Re: September Report Content
Hi;
Just for curiosity: What kind of
integration do you have in mind?
Should
not OWB be integratable with all JSF
implementations?
Yeah, this is the aim of OWB project. Because JSF
2.0 will also be part
of
the Java EE 6, perfectly OWB lives with it.
Besides, there are some re-definition of the
terms in the JSF 2 spec. For
example, it also defines "Managed Bean Concept".
And you already
expressed
that "resource handling" scenario in JSF 2
has resulted with an
exception
in a situation OWB + JSF 2.
Maybe Mark, could explain more on the integration
points that they are
necessary for working OWB + JSF 2 together?
Should we add our aim to integrate
with JSF-2-0 like e.g. MyFaces
trunk?
Mark, what do you want to express with saying
MyFaces trunk? Do you mean
integration implementation will be done on
MyFaces code base?
Maybe Matthias can help on JSF 2 integration and
sheds light.
--Gurkan
2009/9/2 Sven Linstaedt
Just for curiosity: What kind of integration
do you have in mind?
Should
not OWB be integratable with all JSF
implementations?
br, Sven
Am 01.09.2009 um 23:12 schrieb Mark Struberg
:
fine so far.
Should we add our aim to integrate with
JSF-2-0 like e.g. MyFaces
trunk?
LieGrue,
strub
----- Original Message ----
From: Gurkan Erdogdu
To: [email protected]
Sent: Tuesday, September 1, 2009
10:01:26 PM
Subject: September Report Content
Hi guys;
Reporting schedule is coming soon,
last day to send report is
September
9. I
will want to include below content
into our report page as a last 3
months
efforts;
WDYT? All your comments are
welcome!
--Gurkan
-----------------------------------
!OpenWebBeans will be an
ASL-licensed implementation of the JSR-299:
Contexts
and Dependency Injection for the
Java EE platform which is defined as
JSR-299.
!OpenWebBeans entered the incubator
in October 26, 2008. The
following
items
have been made after the last
report
* We cut a M3 release (under vote)
* We implemented new spec features,
(Portable Extensions, and changed
APIs)
* We created a JSR-330 API and
integrated with it
* We integrated with embeddable
OpenEJB in Tomcat to support EJB
Beans
* We implemented 2 new samples
related with EJB Beans and JMS
Injections
* We started a progress to integrate
OWB with Apache Geronimo
Belows are the next steps;
* We will release the M4 version.
* We will integrate with Apache
Geronimo
* We will create more documentation
in the wiki
* We will continue to attract new
committers into the project.
* We will strive to create more
community and increase the use of
u...@list
--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com
