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
The main things being added in this release are going to be Security and
the SE start / stop? Exception handling would be nice, but there hasn't
been much feedback yet on exception handlers (at least not enough for what
I feel is a consensus to move forward).
On Mon, Apr 2, 2012 at 05:52, Gerhard
+1 for a release next week.
I'll try to get the cdictrl down to the floor.
LieGrue,
strub
- Original Message -
From: Gerhard Petracek gerhard.petra...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc: Ken Finnigan kfinn...@redhat.com
Sent: Monday, April 2, 2012 5:58 PM
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
Hi folks,
Currently I'm working to integrate DS into our project to provide
authentication and authorization to REST resources (
https://github.com/abstractj/aerogear-security/blob/deltaspike/README.md).
I was digging into the latest Lincoln's commits (
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
