[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Jason Porter commented on JBIDE-11552: -------------------------------------- Alexey, if you want to contact me (personal email or Red Hat - jporter) that works. We also have an IRC channel: deltaspike on freenode which most of use if you have questions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-11552 at 4/16/12 6:24 PM: ----------------------------------------------------------------- Jason, yes I will contact you when I have questions (I'm pretty sure I will have some ;) Thank you! was (Author: akazakov): Jason, yes I will contact you when I have questions (I'm prery sure I will have some ;) Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11552: ---------------------------------------- Fix Version/s: 3.3.0.CR1 3.3.0.Beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-11552: ---------------------------------------- See Temporary Documentation https://cwiki.apache.org/DeltaSpike/temporary-documentation.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-11552 at 5/3/12 6:08 PM: ----------------------------------------------------------------------- Source: https://github.com/apache/incubator-deltaspike List of features 1. @Excludes Without parameters it is like @Veto, but parameters define dynamic conditions, which it is not clear how to support. 2. @ConfigProperty Injection points with that annotation are provided with beans created from a property. I think all we can do is to exclude such injection point from validation. 3. @MessageBundle An interface annotated with this, should be available for injection point with its type. (DeltaSpike generates beans implementing such interfaces.) That is similar to what we did for Solder. 4. Bean with type MessageContext should be available for injection. Implementation of DeltaSpike provides producer, we just have to provide a buil-in bean for projects that only have API in classpath. That is similar to what we did for Solder. 5. @ExceptionHandler, ExceptionEvent, @Handles. We have to provide validation of correct usage of these annotations. 6. @SecurityBindingType, @Sequres, @SecurityParameterBinding Methods annotated @Sequres have parameters as injection points (like observer and producer methods), but excluding parameters annotated with @SecurityParameterBinding. I think we may implement it by adding fake annotation @Inject to method, and by excluding from validation parameters annotated @SecurityParameterBinding. Also, we have to validate consistency of these annotations usage. 7.@Sequred It is a built-in security binding type. If we implement validation that there is an (unique?) authorizing method for a secured method, then we have to keep in mind that DeltaSpike privides built-in SecuredAnnotationAuthorizer for @Sequred (though it may be missing in the project classpath). was (Author: scabanovich): Source: https://github.com/apache/incubator-deltaspike List of features 1. @Excludes Without parameters it is like @Veto, but parameters dynamic conditions. 2. @ConfigProperty Injection points with that annotation are provided with beans created from a property. I think all we can do is to exclude such injection point from validation. 3. @MessageBundle An interface annotated with this, should be available for injection point with its type. (DeltaSpike generates beans implementing such interfaces.) That is similar to what we did for Solder. 4. Bean with type MessageContext should be available for injection. Implementation of DeltaSpike provides producer, we just have to provide a buil-in bean for projects that only have API in classpath. That is similar to what we did for Solder. 5. @ExceptionHandler, ExceptionEvent, @Handles. We have to provide validation of correct usage of these annotations. 6. @SecurityBindingType, @Sequres, @SecurityParameterBinding Methods annotated @Sequres have parameters as injection points (like observer and producer methods), but excluding parameters annotated with @SecurityParameterBinding. I think we may implement it by adding fake annotation @Inject to method, and by excluding from validation parameters annotated @SecurityParameterBinding. Also, we have to validate consistency of these annotations usage. 7.@Sequred It is a built-in security binding type. If we implement validation that there is an (unique?) authorizing method for a secured method, then we have to keep in mind that DeltaSpike privides built-in SecuredAnnotationAuthorizer for @Sequred (though it may be missing in the project classpath). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-11552: ------------------------------------------ Attachment: SecurityAuthorizerValidation.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-11552: ------------------------------------------ Attachment: OpenOn_of_authorizer.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11552 at 5/24/12 1:52 PM: ------------------------------------------------------------- Once you have your new feature, please be explicit what needs to be done... * include in JBT site? * include in JBT Central (as new or part of existing connector)? * include in JBDS site/installer? * include in JBDS Central (new or part of existing connector)? * include in JBDS Extras site? akazakov> nickboldt: we will need to do the same things that we did for cdi.seam feature org.jboss.tools.cdi.seam.feature not in org.jboss.tools.central.discovery plugin.xml also not in com.jboss.jbds.central.discovery plugin.xml It was simply added to JBT & JBDS aggregate sites. was (Author: nickboldt): Once you have your new feature, please be explicit what needs to be done... * include in JBT site? * include in JBT Central (as new or part of existing connector)? * include in JBDS site/installer? * include in JBDS Central (new or part of existing connector)? * include in JBDS Extras site? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11552?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11552 at 5/25/12 8:55 PM: ------------------------------------------------------------- Once you have your new feature, please be explicit what needs to be done... * include in JBT site? * include in JBT Central (as new or part of existing connector)? * include in JBDS site/installer? * include in JBDS Central (new or part of existing connector)? * include in JBDS Extras site? {quote} akazakov> nickboldt: we will need to do the same things that we did for cdi.seam feature {quote} org.jboss.tools.cdi.seam.feature not in org.jboss.tools.central.discovery plugin.xml also not in com.jboss.jbds.central.discovery plugin.xml It was simply added to JBT & JBDS aggregate sites; therefore we should do the same here, via JBIDE-11999. was (Author: nickboldt): Once you have your new feature, please be explicit what needs to be done... * include in JBT site? * include in JBT Central (as new or part of existing connector)? * include in JBDS site/installer? * include in JBDS Central (new or part of existing connector)? * include in JBDS Extras site? akazakov> nickboldt: we will need to do the same things that we did for cdi.seam feature org.jboss.tools.cdi.seam.feature not in org.jboss.tools.central.discovery plugin.xml also not in com.jboss.jbds.central.discovery plugin.xml It was simply added to JBT & JBDS aggregate sites. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira