Re: [VOTE] Release of Apache DeltaSpike 0.1-incubating
+1 (hope to work on generic beans in 0.2 ;-) ) Antoine Le 6 févr. 2012 à 09:44, Shane Bryzak a écrit : +1 here. On 04/02/12 11:22, Gerhard Petracek wrote: Hi, I'd like to call a VOTE on releasing Apache DeltaSpike 0.1-incubating. Maven staging repository: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/ Source release: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/org/apache/deltaspike/deltaspike-project/0.1-incubating/deltaspike-project-0.1-incubating-source-release.zip Git release branch: http://s.apache.org/PbX (The branch will be pushed after the required votes passed.) Please take a look at the 0.1-incubating artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes of PPMC (or IPMC) members. This vote is open for 72 hours. [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why ... Thanks, Gerhard
Re: [VOTE] Release of Apache DeltaSpike 0.1-incubating
+1 On 4 Feb 2012, at 01:22, Gerhard Petracek wrote: Hi, I'd like to call a VOTE on releasing Apache DeltaSpike 0.1-incubating. Maven staging repository: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/ Source release: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/org/apache/deltaspike/deltaspike-project/0.1-incubating/deltaspike-project-0.1-incubating-source-release.zip Git release branch: http://s.apache.org/PbX (The branch will be pushed after the required votes passed.) Please take a look at the 0.1-incubating artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes of PPMC (or IPMC) members. This vote is open for 72 hours. [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why ... Thanks, Gerhard
[jira] [Resolved] (DELTASPIKE-64) review and discuss @Secured
[
https://issues.apache.org/jira/browse/DELTASPIKE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-64.
Resolution: Fixed
we agreed on adding it based on DELTASPIKE-65 - we will review the result
review and discuss @Secured
---
Key: DELTASPIKE-64
URL: https://issues.apache.org/jira/browse/DELTASPIKE-64
Project: DeltaSpike
Issue Type: Sub-task
Components: Security-Module
Affects Versions: 0.1-incubating
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek
Fix For: 0.2-incubating
this feature is listed at
https://cwiki.apache.org/confluence/display/DeltaSpike/SE+Feature+Ranking and
part of myfaces codi-core.
@Secured is a simple cdi interceptor annotation which allows to filter method
calls to cdi beans based on custom rules.
it's possible to specify 1-n custom implementations of AccessDecisionVoter.
those voters get invoked before the call is forwarded to the target method (a
voter is a cdi bean which gets resolved by its concrete type). an
implementation of AccessDecisionVoter can access the InvocationContext to get
further details about the target method to trigger the corresponding
evaluation. as a result voters return a set of violations
(SecurityViolation). if there is no violation, the target-method gets
executed. if there is at least one violation, an AccessDeniedException will
be thrown.
in addition an AccessDecisionVoterContext is needed to detect if there is an
ongoing security check (e.g. it's possible to use it in a custom scope to
avoid that a security check postpones the expiration).
(in myfaces codi it's also used to secure views via view-configs, however, we
will exclude this part for now.)
users can use those simple and generic apis to implement their own access
control and it will get used by other deltaspike modules automatically (if
they use the security-api).
(in an AccessDecisionVoter it's possible to integrate 3rd party
security-frameworks.)
usage of @Secured:
//...
@Secured({MyAccessDecisionVoter1.class, MyAccessDecisionVoter2.class})
public class SecuredBean
{
//...
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DELTASPIKE-65) review and discuss @SecurityBindingType
[ https://issues.apache.org/jira/browse/DELTASPIKE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-65. Resolution: Fixed review and discuss @SecurityBindingType --- Key: DELTASPIKE-65 URL: https://issues.apache.org/jira/browse/DELTASPIKE-65 Project: DeltaSpike Issue Type: Sub-task Components: Security-Module Affects Versions: 0.1-incubating Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 0.2-incubating -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DELTASPIKE-69) @SecurityBindingType
@SecurityBindingType Key: DELTASPIKE-69 URL: https://issues.apache.org/jira/browse/DELTASPIKE-69 Project: DeltaSpike Issue Type: New Feature Components: Security-Module Affects Versions: 0.2-incubating Reporter: Gerhard Petracek Assignee: Shane Bryzak Fix For: 0.3-incubating we agreed on adding it after v0.1 is released (see http://s.apache.org/jT) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DELTASPIKE-70) @Secured
@Secured Key: DELTASPIKE-70 URL: https://issues.apache.org/jira/browse/DELTASPIKE-70 Project: DeltaSpike Issue Type: New Feature Components: Security-Module Affects Versions: 0.1-incubating Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.2-incubating we agreed on implementing it based on DELTASPIKE-69 (see http://s.apache.org/jT ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DELTASPIKE-69) @SecurityBindingType
[ https://issues.apache.org/jira/browse/DELTASPIKE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-69: --- Affects Version/s: (was: 0.2-incubating) 0.1-incubating Fix Version/s: (was: 0.3-incubating) 0.2-incubating @SecurityBindingType Key: DELTASPIKE-69 URL: https://issues.apache.org/jira/browse/DELTASPIKE-69 Project: DeltaSpike Issue Type: New Feature Components: Security-Module Affects Versions: 0.1-incubating Reporter: Gerhard Petracek Assignee: Shane Bryzak Fix For: 0.2-incubating we agreed on adding it after v0.1 is released (see http://s.apache.org/jT ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DELTASPIKE-71) create deltaspike security module
create deltaspike security module - Key: DELTASPIKE-71 URL: https://issues.apache.org/jira/browse/DELTASPIKE-71 Project: DeltaSpike Issue Type: Task Components: Security-Module Affects Versions: 0.1-incubating Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.2-incubating -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DELTASPIKE-62) Discuss security module
[ https://issues.apache.org/jira/browse/DELTASPIKE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-62: --- Issue Type: Task (was: New Feature) Discuss security module --- Key: DELTASPIKE-62 URL: https://issues.apache.org/jira/browse/DELTASPIKE-62 Project: DeltaSpike Issue Type: Task Reporter: Dan Allen Assignee: Gerhard Petracek Application security can be extremely confusing and frustrating, especially for Java EE developers. Yet, it's an absolute requirement for nearly every application. An integration with a strong security framework is desperately needed. DeltaSpike could offer a module that makes security very approachable and integrate well with CDI and other Java EE technologies. Apache Shiro [1] appears to be an ideal candidate. The goals for the project seem to align perfectly with this need, as Les explains in this article [2]. Apache Shiro has many things going for it that make it a good match for DeltaSpike: * a top level Apache project * actively developed * mature (nearly a decade) * pluggable extensible (the key for CDI integration) * works in web, ejb *and* java se environments * supports all aspects of security (authentication, authorization, permissions, certificates, ciphers) * easy to use * subjective bonus: has a cool name and logo It seems like Shiro could really use some CDI integration to make it even simpler. (Several integrations have already been explored [3]). We can start with some producers and then build on the declarative functionality that has previously been explored in Seam. [1] http://shiro.apache.org/index.html [2] http://www.infoq.com/articles/apache-shiro [3] http://shiro.apache.org/integration.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DELTASPIKE-56) Add BeanManagerProvider.getRequiredBeanManager() method
[ https://issues.apache.org/jira/browse/DELTASPIKE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-56. Resolution: Won't Fix Fix Version/s: 0.2-incubating we agreed on a different approach (see http://s.apache.org/9MC) - there will be a new jira issue for it Add BeanManagerProvider.getRequiredBeanManager() method --- Key: DELTASPIKE-56 URL: https://issues.apache.org/jira/browse/DELTASPIKE-56 Project: DeltaSpike Issue Type: Improvement Components: Core Reporter: Christian Kaltepoth Assignee: Gerhard Petracek Priority: Minor Fix For: 0.2-incubating Attachments: DELTASPIKE-56.patch While reviewing the implementation of BeanManagerProvider I saw that getBeanManager() may return null in some rare circumstances. Unfortunately this forces everyone calling this method to check the result for null. I think most code calling the method absolutely requires the BeanManager and cannot proceed without it. Therefore it would be nice to have some alternative getBeanManager() method that doesn't return null if the BeanManager is not available but instead throws a meaningful runtime exception. That's what Solder does per default. Calling Solder's BeanManagerLocator.getBeanManager() without a BeanManager being available will result in a BeanManagerUnavailableException. The attached patch adds a method getRequiredBeanManager() to the BeanManagerProvider implementing this behavior. I'm not sure if this minor thing should be discussed on the mailing list. If you think this should be discussed, please let me know, then I'll start a topic on deltaspike-dev. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DELTASPIKE-72) BeanManagerProvider#getBeanManager should fail fast if there is no bean-manager
BeanManagerProvider#getBeanManager should fail fast if there is no bean-manager --- Key: DELTASPIKE-72 URL: https://issues.apache.org/jira/browse/DELTASPIKE-72 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 0.1-incubating Reporter: Christian Kaltepoth Assignee: Christian Kaltepoth Priority: Minor Fix For: 0.2-incubating we agreed on failing fast if there is no bean-manager (see http://s.apache.org/9MC ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (DELTASPIKE-56) Add BeanManagerProvider.getRequiredBeanManager() method
[ https://issues.apache.org/jira/browse/DELTASPIKE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13201389#comment-13201389 ] Gerhard Petracek edited comment on DELTASPIKE-56 at 2/6/12 4:52 PM: we agreed on a different approach (see http://s.apache.org/9MC ) - there will be a new jira issue for it was (Author: gpetracek): we agreed on a different approach (see http://s.apache.org/9MC) - there will be a new jira issue for it Add BeanManagerProvider.getRequiredBeanManager() method --- Key: DELTASPIKE-56 URL: https://issues.apache.org/jira/browse/DELTASPIKE-56 Project: DeltaSpike Issue Type: Improvement Components: Core Reporter: Christian Kaltepoth Assignee: Gerhard Petracek Priority: Minor Fix For: 0.2-incubating Attachments: DELTASPIKE-56.patch While reviewing the implementation of BeanManagerProvider I saw that getBeanManager() may return null in some rare circumstances. Unfortunately this forces everyone calling this method to check the result for null. I think most code calling the method absolutely requires the BeanManager and cannot proceed without it. Therefore it would be nice to have some alternative getBeanManager() method that doesn't return null if the BeanManager is not available but instead throws a meaningful runtime exception. That's what Solder does per default. Calling Solder's BeanManagerLocator.getBeanManager() without a BeanManager being available will result in a BeanManagerUnavailableException. The attached patch adds a method getRequiredBeanManager() to the BeanManagerProvider implementing this behavior. I'm not sure if this minor thing should be discussed on the mailing list. If you think this should be discussed, please let me know, then I'll start a topic on deltaspike-dev. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release of Apache DeltaSpike 0.1-incubating
+1 looks good On Mon, Feb 6, 2012 at 9:28 AM, Pete Muir pm...@redhat.com wrote: +1 On 4 Feb 2012, at 01:22, Gerhard Petracek wrote: Hi, I'd like to call a VOTE on releasing Apache DeltaSpike 0.1-incubating. Maven staging repository: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/ Source release: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/org/apache/deltaspike/deltaspike-project/0.1-incubating/deltaspike-project-0.1-incubating-source-release.zip Git release branch: http://s.apache.org/PbX (The branch will be pushed after the required votes passed.) Please take a look at the 0.1-incubating artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes of PPMC (or IPMC) members. This vote is open for 72 hours. [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why ... Thanks, Gerhard -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com Keep it Simple
[jira] [Assigned] (DELTASPIKE-73) Discuss GenericBeans
[ https://issues.apache.org/jira/browse/DELTASPIKE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek reassigned DELTASPIKE-73: -- Assignee: John Ament (was: Gerhard Petracek) please close it as duplicated - see DELTASPIKE-14 Discuss GenericBeans Key: DELTASPIKE-73 URL: https://issues.apache.org/jira/browse/DELTASPIKE-73 Project: DeltaSpike Issue Type: Task Reporter: John D. Ament Assignee: John Ament At a high level, generic beans are meant to provide reusable business logic and dynamically provide interface implementations by using code generation practices (runtime, rather than compile time code generation). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DELTASPIKE-73) Discuss GenericBeans
[ https://issues.apache.org/jira/browse/DELTASPIKE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek reassigned DELTASPIKE-73: -- Assignee: John D. Ament (was: John Ament) Discuss GenericBeans Key: DELTASPIKE-73 URL: https://issues.apache.org/jira/browse/DELTASPIKE-73 Project: DeltaSpike Issue Type: Task Reporter: John D. Ament Assignee: John D. Ament At a high level, generic beans are meant to provide reusable business logic and dynamically provide interface implementations by using code generation practices (runtime, rather than compile time code generation). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DELTASPIKE-73) Discuss GenericBeans
[ https://issues.apache.org/jira/browse/DELTASPIKE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed DELTASPIKE-73. --- Resolution: Duplicate Discuss GenericBeans Key: DELTASPIKE-73 URL: https://issues.apache.org/jira/browse/DELTASPIKE-73 Project: DeltaSpike Issue Type: Task Reporter: John D. Ament Assignee: John D. Ament At a high level, generic beans are meant to provide reusable business logic and dynamically provide interface implementations by using code generation practices (runtime, rather than compile time code generation). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DELTASPIKE-73) Discuss GenericBeans
[ https://issues.apache.org/jira/browse/DELTASPIKE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13201434#comment-13201434 ] John D. Ament commented on DELTASPIKE-73: - Sorry missed the original. Discuss GenericBeans Key: DELTASPIKE-73 URL: https://issues.apache.org/jira/browse/DELTASPIKE-73 Project: DeltaSpike Issue Type: Task Reporter: John D. Ament Assignee: John D. Ament At a high level, generic beans are meant to provide reusable business logic and dynamically provide interface implementations by using code generation practices (runtime, rather than compile time code generation). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Incubator PMC/Board report for Feb 2012 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 February 2012, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Feb 1st). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/February2012 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: [VOTE] Release of Apache DeltaSpike 0.1-incubating
+1 On 12-02-03 05:22 PM, Gerhard Petracek wrote: Hi, I'd like to call a VOTE on releasing Apache DeltaSpike 0.1-incubating. Maven staging repository: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/ Source release: https://repository.apache.org/content/repositories/orgapachedeltaspike-187/org/apache/deltaspike/deltaspike-project/0.1-incubating/deltaspike-project-0.1-incubating-source-release.zip Git release branch: http://s.apache.org/PbX (The branch will be pushed after the required votes passed.) Please take a look at the 0.1-incubating artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes of PPMC (or IPMC) members. This vote is open for 72 hours. [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why ... Thanks, Gerhard
[jira] [Commented] (DELTASPIKE-70) @Secured
[ https://issues.apache.org/jira/browse/DELTASPIKE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13201899#comment-13201899 ] Gerhard Petracek commented on DELTASPIKE-70: i pushed a first draft to https://github.com/os890/DS_Discuss/tree/DS70 - as soon as we found the issue with arquillian and the v0.1 release is done, i'll push it. @Secured Key: DELTASPIKE-70 URL: https://issues.apache.org/jira/browse/DELTASPIKE-70 Project: DeltaSpike Issue Type: New Feature Components: Security-Module Affects Versions: 0.1-incubating Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.2-incubating we agreed on implementing it based on DELTASPIKE-69 (see http://s.apache.org/jT ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
