Hello all,
Please check [1] before you answer.
I'd like to propose the addition of a new module for integrating Spring
with CDI. We have discussed this on the e-mail list but let me provide a
quick rationale for it.
- it eases adoption of CDI and, by extension, Java EE, in environments
[
https://issues.apache.org/jira/browse/DELTASPIKE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-41.
-
Resolution: Fixed
add examples for v0.1
-
[
https://issues.apache.org/jira/browse/DELTASPIKE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-2.
Resolution: Fixed
deltaspike java-se feature ranking
[
https://issues.apache.org/jira/browse/DELTASPIKE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-255.
--
Resolution: Won't Fix
We have quite some Extensions which themself do a @Observes
[
https://issues.apache.org/jira/browse/DELTASPIKE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-279.
--
Resolution: Fixed
unit tests added
import JSF-Scope_to_CDI-Scope
[
https://issues.apache.org/jira/browse/DELTASPIKE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476005#comment-13476005
]
Mark Struberg commented on DELTASPIKE-59:
-
we discussed this on the list for
[
https://issues.apache.org/jira/browse/DELTASPIKE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-162.
--
Resolution: Fixed
add examples for v0.2
-
[
https://issues.apache.org/jira/browse/DELTASPIKE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-89.
-
Resolution: Fixed
we should add the javadoc improvements to their respective
[
https://issues.apache.org/jira/browse/DELTASPIKE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476007#comment-13476007
]
Mark Struberg commented on DELTASPIKE-122:
--
What was the outcome of the
great stuff, +1!
Just to help me understand a bit better. This module will cover a Spring-CDI
bridge, so you boot Spring and a CDI container and route the beans between both
of them, right?
Just for getting the whole picture: Another way is to just interpret the spring
beans.xml and serve it
+1 (since DS manages spring context lifecycle)
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
+1 it would definitively improve Java EE and CDI adoption.
Antoine SABOT-DURAND
Le 15 oct. 2012 à 09:41, Romain Manni-Bucau rmannibu...@gmail.com a écrit :
+1 (since DS manages spring context lifecycle)
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog:
Hi folks!
I finally like to start working on JSF scopes for DeltaSpike.
We already have the following 2 features implemented and working (including
unit tests):
* JFS @ViewScoped Context support
* JSF-2-CDI scope mapping.
* injecting typesafe JSF messages
The next item on my list is the
*
[
https://issues.apache.org/jira/browse/DELTASPIKE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-207.
--
Resolution: Fixed
Fix Version/s: 0.3-incubating
memory leak in
[
https://issues.apache.org/jira/browse/DELTASPIKE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-229.
--
Resolution: Fixed
This got committed as part of DELTASPIKE-281
There are two issues I am aware of:
1) The injectable Servlet artifacts should define a deltaspike-specific
qualifier in order to prevent conflict with CDI 1.1 which defines these
artifacts in the @Default space.
2) There was an issue in solder related to multi-war ear deployment
which is
imo we should create:
- a client-window adapter (as spi) for a 1:1 delegation to the
client-window-api of jsf 2.2+
- a client-window implementation for jsf 2.0 and 2.1
- a window-context similar to what we have in codi (that isn't the
window-scope - see [1])
- scopes + a fine grained api to manage
as mentioned by mark, @ViewScoped is done already.
if we agree on adding @RenderScoped, it can be based on the window-context
infrastructure as well.
@scoped validators and converters:
that's supported by codi as well, but it isn't related to the current topic.
regards,
gerhard
2012/10/15
Gerhard, can you please open a new DISCUSS topic for converters and phase
listeners?
LieGrue,
strub
- Original Message -
From: Gerhard Petracek gerhard.petra...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Monday, October 15, 2012 11:07 AM
Subject: Re: [DISCUSS]
that isn't correct. i thought about that as well, but some people use it
instead of std. cdi conversations to get rid of the disadvantages.
- if you would close (or restart) the window-scope and you don't have an
independent window-context, you would lose the information stored for the
current
All,
Is ViewAccessScoped of CODI considered. For me the most important non std
scope.
regards
Rudy
On 15 October 2012 11:52, Mark Struberg strub...@yahoo.de wrote:
I don't understand. The FacesMessages are held by the FacesContext.
If we talk about a WindowContext we always have to
Yes, this is definitely on our list. Indeed @ViewAccessScoped is one of the
most loved features of CODI.
To all others a quick explanation what CODIs @ViewAccessScoped does. It
basically keeps your bean alive until you do NOT use it on a page anymore. This
is kind of an auto-conversation which
@ #1:
not in case of a redirect. you can keep them by using a jsf-api manually,
but in this case they will be stored in the flash-scope... - you have 2
disadvantages:
1) you have to do it manually
2) you have to wait for jsf 2.2 to get a flash-scope which works as
expected
@ #2:
you are talking
No problem at all with #1, #2 is a bit difficult to solve. Jozef, have you
solved this in Weld 2.0? If so, how do you propose we solve it in DS?
On Mon, Oct 15, 2012 at 2:46 AM, Jozef Hartinger jhart...@redhat.comwrote:
There are two issues I am aware of:
1) The injectable Servlet artifacts
what was the problem actually?
LieGrue,
strub
- Original Message -
From: Jason Porter lightguard...@gmail.com
To: Jozef Hartinger jhart...@redhat.com
Cc: deltaspike-dev@incubator.apache.org
Sent: Monday, October 15, 2012 5:19 PM
Subject: Re: seam-servlet stuff to deltaspike
No
[
https://issues.apache.org/jira/browse/DELTASPIKE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476196#comment-13476196
]
Jason Porter commented on DELTASPIKE-122:
-
I'm fine NOT doing this for the
[
https://issues.apache.org/jira/browse/DELTASPIKE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476199#comment-13476199
]
Jason Porter commented on DELTASPIKE-165:
-
Seems to me like the event is
Hi,
Some ideas from my side, too ([1] and [2]). Unfortunately it is in german.
But everyone of you can read the code. We used an advanced version of that
code to build a Spring-CDI-Bridge in a large project. Unfortunately
meanwhile the project is completely migrated to CDI and the code is lost
in
Thanks Lincoln, indeed that sounds very useful.
Where do you store it between the requests? I guess in the Session, right?
Thus 2 concurrent requests would overwrite each other, isn't?
I think that's another neat example which should actually be per-browser-tab.
LieGrue,
strub
-
Sent from my iPhone
On 2012-10-15, at 3:35, Mark Struberg strub...@yahoo.de wrote:
great stuff, +1!
Just to help me understand a bit better. This module will cover a Spring-CDI
bridge, so you boot Spring and a CDI container and route the beans between
both of them, right?
Yes, except
Sent from my iPhone
On 2012-10-15, at 11:16, Jason Porter lightguard...@gmail.com wrote:
You have my +1 Marius. If we can rouse the CDISource guys (mostly Rick)
they may have some ideas as well.
I talked to Rick at Java One and he said that he'll try.
On Mon, Oct 15, 2012 at 1:53 AM,
Thanks Arne, that looks useful! :)
(I can read German ;))
Sent from my iPhone
On 2012-10-15, at 11:55, Arne Limburg arne.limb...@openknowledge.de wrote:
Hi,
Some ideas from my side, too ([1] and [2]). Unfortunately it is in german.
But everyone of you can read the code. We used an
32 matches
Mail list logo
