You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by titou10 titou10 <ti...@gmail.com> on 2013/02/11 22:07:39 UTC
DeltaSpike roadmap? + "can we help" ?
Hi,
Q: is there a roadmap somewhere that describe the next milestones for
DeltaSpike?
We are about to start a new project based on our new dev stack based
on JSF 2.0/CDI/WebSphere v8.5 + DS (and CODI in the meantime). Our
previosu stack is based on Seam 2/JSF 1.2/WAS v7.0
I know that the answer is probably "it will be available when it will
be ready"... but we would know when we can expect DS to be at least in
a beta state, at least for the JPA and JSF modules.
Also is it possible at this time to participate to the development of
DS in order to maybe acceleerate the development if needed or is the
project still in a state that does not accommodate extra commiters?
What are the needs for the project in this area?
Thx.
Denis Forveille aka titou10
Re: DeltaSpike roadmap? + "can we help" ?
Posted by Gerhard Petracek <ge...@gmail.com>.
hi denis,
#1
if you use the default behaviour (= transaction-type resource-local),
you just need to inject the entity-manager and call
EntityManager#getTransaction and then EntityTransaction#setRollbackOnly.
#2
codi scopes will get added for sure (it's just a matter of time, since we
will align the window-handling with jsf 2.2).
(for now you can use codi in parallel.)
#3
i'll talk with ed about the @ViewScoped topic you mentioned.
#4
we have a jsf-message integration already and we don't plan to change the
basic approach without a good reason (keeping messages across redirects
depends on #2).
#5
if you would like to help with examples, please start a new thread about it.
#6
sometimes you get new ideas while writing examples and/or documentation.
-> if something changes, we have to update those parts (that can happen
until v1).
however, there are several parts with a quite stable api.
regards,
gerhard
2013/2/20 titou10 titou10 <ti...@gmail.com>
> Thx Gerhard for the information
>
> About the feedback, what we need ASAP to start with DS is (Maybe
> solutions are exist already e):
> - in the JPA module, when using the @Transactional annotation, a way
> to trigger a rollback without throwing an exception. Similar to
> ejbCtxt.setRollbacklOnly(). Maybe use an injectable CDI component in
> the @TransactionScope named TransactionContext (=ejb context) with a
> setRollbackOnly method?
> - in the JSF module:
> - an equivalent of Seam 2 "workspaces": CODI "Window" scope seems to
> be OK for this one
> - enhanced conversation scope "a la CODI" (parallel, multiple etc.)
> - CDI equivalent of all the JSF scopes: almost seem to be there
> - an equivalent of the Seam 2 "Page Scope", usable on classes and
> also on producers (the CDIfied JSF ViewScope can not be used on
> producers..). Not sure that CODI "ViewAccessScope" is equivalent to
> this has it can span multiple views. Seam 2 Page scope is associated
> with a "view" an has the same lifecycle. We use it a lot (eg to keep
> references tables with data selectable on drop-down list on the page)
> - an CDI component equivalent of Seam 2 "FacesMessage" used to
> display messages on the same or on the next page after a redirect (eg.
> confirmation messages) and has methods like fm.addToControl(),
> fm.addFromResourceBundle(severity,key from jsf res bundle) etc.
>
> Would be glad to help on this if needed
>
> About the existing modules:
> - the security module is something we will not use. I've developed
> some component to integrate our CDI apps with Apache Shiro. We don't
> use fine grained permissions, only role permissions and CDIfied Shiro
> "Subject" and a standard way to define a custom realm.
> - we will not use typesafe navigation as we prefer to use string base
> constants for oucomes (won't argue on this ..lol)
> - not sure about the "Config" thing. Not clear at all what it is from
> the WiKi and why we would need this
>
> About the examples, what kind of examples would you like given the
> current state of DS?
>
> About the content of the Wiki and the documentation, IIMHO it is very
> difficult for external people to contribute now, given that things are
> moving and are the code and concepts still being discussed (JSF scopes
> etc.)
>
> Denis
>
> 2013/2/11 Gerhard Petracek <ge...@gmail.com>:
> > hi denis,
> >
> > there is no fixed roadmap.
> >
> > several real-world projects use ds v0.3 in production.
> > (it's possible that the api changes until v1.0, however, currently it
> looks
> > pretty stable.)
> >
> > some missing parts of the jsf module depend on the scopes we are going to
> > add.
> >
> > you are very welcome to join the effort at any time (see [1]).
> > what we really need a lot is e.g. more feedback (esp. before v1),
> examples
> > and new/updated content for our site [2].
> >
> > regards,
> > gerhard
> >
> > [1] http://incubator.apache.org/deltaspike/community.html
> > [2] https://svn.apache.org/repos/asf/incubator/deltaspike/site/trunk/
> >
> >
> >
> > 2013/2/11 titou10 titou10 <ti...@gmail.com>
> >
> >> Hi,
> >> Q: is there a roadmap somewhere that describe the next milestones for
> >> DeltaSpike?
> >>
> >> We are about to start a new project based on our new dev stack based
> >> on JSF 2.0/CDI/WebSphere v8.5 + DS (and CODI in the meantime). Our
> >> previosu stack is based on Seam 2/JSF 1.2/WAS v7.0
> >>
> >> I know that the answer is probably "it will be available when it will
> >> be ready"... but we would know when we can expect DS to be at least in
> >> a beta state, at least for the JPA and JSF modules.
> >>
> >> Also is it possible at this time to participate to the development of
> >> DS in order to maybe acceleerate the development if needed or is the
> >> project still in a state that does not accommodate extra commiters?
> >> What are the needs for the project in this area?
> >>
> >> Thx.
> >> Denis Forveille aka titou10
> >>
>
Re: DeltaSpike roadmap? + "can we help" ?
Posted by titou10 titou10 <ti...@gmail.com>.
Thx Gerhard for the information
About the feedback, what we need ASAP to start with DS is (Maybe
solutions are exist already e):
- in the JPA module, when using the @Transactional annotation, a way
to trigger a rollback without throwing an exception. Similar to
ejbCtxt.setRollbacklOnly(). Maybe use an injectable CDI component in
the @TransactionScope named TransactionContext (=ejb context) with a
setRollbackOnly method?
- in the JSF module:
- an equivalent of Seam 2 "workspaces": CODI "Window" scope seems to
be OK for this one
- enhanced conversation scope "a la CODI" (parallel, multiple etc.)
- CDI equivalent of all the JSF scopes: almost seem to be there
- an equivalent of the Seam 2 "Page Scope", usable on classes and
also on producers (the CDIfied JSF ViewScope can not be used on
producers..). Not sure that CODI "ViewAccessScope" is equivalent to
this has it can span multiple views. Seam 2 Page scope is associated
with a "view" an has the same lifecycle. We use it a lot (eg to keep
references tables with data selectable on drop-down list on the page)
- an CDI component equivalent of Seam 2 "FacesMessage" used to
display messages on the same or on the next page after a redirect (eg.
confirmation messages) and has methods like fm.addToControl(),
fm.addFromResourceBundle(severity,key from jsf res bundle) etc.
Would be glad to help on this if needed
About the existing modules:
- the security module is something we will not use. I've developed
some component to integrate our CDI apps with Apache Shiro. We don't
use fine grained permissions, only role permissions and CDIfied Shiro
"Subject" and a standard way to define a custom realm.
- we will not use typesafe navigation as we prefer to use string base
constants for oucomes (won't argue on this ..lol)
- not sure about the "Config" thing. Not clear at all what it is from
the WiKi and why we would need this
About the examples, what kind of examples would you like given the
current state of DS?
About the content of the Wiki and the documentation, IIMHO it is very
difficult for external people to contribute now, given that things are
moving and are the code and concepts still being discussed (JSF scopes
etc.)
Denis
2013/2/11 Gerhard Petracek <ge...@gmail.com>:
> hi denis,
>
> there is no fixed roadmap.
>
> several real-world projects use ds v0.3 in production.
> (it's possible that the api changes until v1.0, however, currently it looks
> pretty stable.)
>
> some missing parts of the jsf module depend on the scopes we are going to
> add.
>
> you are very welcome to join the effort at any time (see [1]).
> what we really need a lot is e.g. more feedback (esp. before v1), examples
> and new/updated content for our site [2].
>
> regards,
> gerhard
>
> [1] http://incubator.apache.org/deltaspike/community.html
> [2] https://svn.apache.org/repos/asf/incubator/deltaspike/site/trunk/
>
>
>
> 2013/2/11 titou10 titou10 <ti...@gmail.com>
>
>> Hi,
>> Q: is there a roadmap somewhere that describe the next milestones for
>> DeltaSpike?
>>
>> We are about to start a new project based on our new dev stack based
>> on JSF 2.0/CDI/WebSphere v8.5 + DS (and CODI in the meantime). Our
>> previosu stack is based on Seam 2/JSF 1.2/WAS v7.0
>>
>> I know that the answer is probably "it will be available when it will
>> be ready"... but we would know when we can expect DS to be at least in
>> a beta state, at least for the JPA and JSF modules.
>>
>> Also is it possible at this time to participate to the development of
>> DS in order to maybe acceleerate the development if needed or is the
>> project still in a state that does not accommodate extra commiters?
>> What are the needs for the project in this area?
>>
>> Thx.
>> Denis Forveille aka titou10
>>
Re: DeltaSpike roadmap? + "can we help" ?
Posted by Gerhard Petracek <ge...@gmail.com>.
hi denis,
there is no fixed roadmap.
several real-world projects use ds v0.3 in production.
(it's possible that the api changes until v1.0, however, currently it looks
pretty stable.)
some missing parts of the jsf module depend on the scopes we are going to
add.
you are very welcome to join the effort at any time (see [1]).
what we really need a lot is e.g. more feedback (esp. before v1), examples
and new/updated content for our site [2].
regards,
gerhard
[1] http://incubator.apache.org/deltaspike/community.html
[2] https://svn.apache.org/repos/asf/incubator/deltaspike/site/trunk/
2013/2/11 titou10 titou10 <ti...@gmail.com>
> Hi,
> Q: is there a roadmap somewhere that describe the next milestones for
> DeltaSpike?
>
> We are about to start a new project based on our new dev stack based
> on JSF 2.0/CDI/WebSphere v8.5 + DS (and CODI in the meantime). Our
> previosu stack is based on Seam 2/JSF 1.2/WAS v7.0
>
> I know that the answer is probably "it will be available when it will
> be ready"... but we would know when we can expect DS to be at least in
> a beta state, at least for the JPA and JSF modules.
>
> Also is it possible at this time to participate to the development of
> DS in order to maybe acceleerate the development if needed or is the
> project still in a state that does not accommodate extra commiters?
> What are the needs for the project in this area?
>
> Thx.
> Denis Forveille aka titou10
>