come back to your server even before the original request is
finished.
LieGrue,
strub
- Original Message -
From: Alan D. Cabrera l...@toolazydogs.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Wednesday, April 4, 2012 12:50 AM
Subject: Re: Custom Context utilities
I
before the original request is
finished.
LieGrue,
strub
- Original Message -
From: Alan D. Cabrera l...@toolazydogs.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Wednesday, April 4, 2012 12:50 AM
Subject: Re: Custom Context utilities
I understand most
to hold in a Conversation at all, but that's another story).
LieGrue,
strub
- Original Message -
From: Alan D. Cabrera l...@toolazydogs.com
To: deltaspike-dev@incubator.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Sent: Wednesday, April 4, 2012 2:15 PM
Subject: Re: Custom Context
world projects.
LieGrue,
strub
- Original Message -
From: Mark Struberg strub...@yahoo.de
To: deltaspike-dev@incubator.apache.org
deltaspike-dev@incubator.apache.org
Cc:
Sent: Wednesday, April 4, 2012 5:32 PM
Subject: Re: Custom Context utilities
See CDI spec 6.7.4
If you are happy to be tied to a specific CDI implementation, you could use the
Weld bound conversations -
http://docs.jboss.org/weld/reference/1.1.5.Final/en-US/html/contexts.html#d0e5506
- which can be backed by two maps, one representing the session and one the
request. Or, you could take a
That's actually the code I was looking at before I started this thread. This
led me to think, if I need it then I'm pretty sure that other framework
developers would need it as well, my needs being pretty straightforward.
Regards,
Alan
On Apr 3, 2012, at 3:44 AM, Pete Muir wrote:
If
IMO it would be better if CDI offered reusable conversations, like we did with
Weld, rather than it being an extension. So you can just take advantage of
Weld's conversation stuff, or OWB's.
Maybe there is a need to have something before we get this in CDI 1.1?
On 3 Apr 2012, at 13:55, Alan D.
since instance
has
another meaning in CDI...
Regards,
Arne
-Ursprüngliche Nachricht-
Von: Pete Muir [mailto:pm...@redhat.com]
Gesendet: Dienstag, 3. April 2012 15:20
An: deltaspike-dev@incubator.apache.org; Mark Struberg
Betreff: Re: Custom Context utilities
Given that it's
That would be ideal. I had always thought of deltaspike as a CDI incubator of
sorts.
Regards,
Alan
On Apr 3, 2012, at 5:57 AM, Pete Muir wrote:
IMO it would be better if CDI offered reusable conversations, like we did
with Weld, rather than it being an extension. So you can just take
On Apr 3, 2012, at 6:17 AM, Mark Struberg wrote:
I'm not sure if the CDI Conversation scope is a good example as it is widely
considered pretty much broken ;)
Can you provide background on your opinion for those of us who have come to the
party late? :)
Regards,
Alan
name for that class since instance
has another meaning in CDI...
Regards,
Arne
-Ursprüngliche Nachricht-
Von: Pete Muir [mailto:pm...@redhat.com]
Gesendet: Dienstag, 3. April 2012 15:20
An: deltaspike-dev@incubator.apache.org; Mark Struberg
Betreff: Re: Custom Context utilities
hi alan,
see e.g. [1]
regards,
gerhard
[1] http://s.apache.org/tj
2012/4/4 Alan D. Cabrera l...@toolazydogs.com
On Apr 3, 2012, at 6:17 AM, Mark Struberg wrote:
I'm not sure if the CDI Conversation scope is a good example as it is
widely considered pretty much broken ;)
Can you
I understand most of what the relevant slides discuss.
What is does failed conversion/validation mean? Is this the bit where all
the type information is collected and validated?
Regards,
Alan
On Apr 3, 2012, at 3:14 PM, Gerhard Petracek wrote:
hi alan,
see e.g. [1]
regards,
hi alan,
that's specific to jsf and the corresponding phase in the jsf
request-lifecycle.
regards,
gerhard
2012/4/4 Alan D. Cabrera l...@toolazydogs.com
I understand most of what the relevant slides discuss.
What is does failed conversion/validation mean? Is this the bit where
all the
I'm not quite sure what this would constitute, beyond a trivial base class or a
consistent start/stop API. Every context has quite different requirements in my
experience, and the hard part is linking the context to the start/stop points,
and to whatever backs the context, not the actual
hi alan,
if there is no use-case for accessing the same state-machine across browser
windows/tabs and you access the state-machine only during jsf requests, you
can use scopes provided by myfaces codi.
(we will discuss them here later on.)
regards,
gerhard
2012/4/2 Alan D. Cabrera
I'm not writing a web app but, I think that I could use the latter. I'll take
a look at it. Thanks!
Regards,
Alan
On Apr 2, 2012, at 1:41 PM, Gerhard Petracek wrote:
hi alan,
if there is no use-case for accessing the same state-machine across browser
windows/tabs and you access the
It sure would be handy if there were a set of utilities available to help
framework developers who wish to implement custom Contexts. Maybe I missed
something during my perusal or maybe it's not all that tough.
The context that I need to implement is something of a conversational nature.
18 matches
Mail list logo