+1 for the basic idea and discussing the module feature by feature
+1 for an own module if we agree on rules for other modules
(e.g. deltaspike modules which use this exception-handler module have
to provide a fallback, because the impl. module isn't a required (runtime)
dependency.)
regards,
short addition:
the branch itself is at [1].
regards,
gerhard
[1] http://s.apache.org/zK
2012/2/28 Gerhard Petracek gerhard.petra...@gmail.com
hi pete,
i pushed a first draft to [1].
it would be great, if you can have a look at the todos
(esp. WeldContainerControl#shutdownContainer)
[
https://issues.apache.org/jira/browse/DELTASPIKE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reassigned DELTASPIKE-92:
--
Assignee: Gerhard Petracek (was: Mark Struberg)
ContainerControl API
unit and integration tests for CdiContainer
---
Key: DELTASPIKE-104
URL: https://issues.apache.org/jira/browse/DELTASPIKE-104
Project: DeltaSpike
Issue Type: Sub-task
Components: CDI-SE,
[
https://issues.apache.org/jira/browse/DELTASPIKE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-99.
Resolution: Fixed
refactor the owb-se example to a generic se-example
With the basic implementation of Identity now in place, it's now a good
time to discuss authentication. The authentication API comes into play
during the user authentication process, and is responsible for ensuring
that the user is who they claim to be, and providing the application
with the
Following on, here's an extremely basic example of an Authenticator. If
a developer were to simply include this class in their application and
perform no further configuration, then it would be used during the
authentication process:
public class SimpleAuthenticator extends BaseAuthenticator
