[jira] [Resolved] (DELTASPIKE-100) improve the bootstrapping module for java-se for simple use-cases
[ https://issues.apache.org/jira/browse/DELTASPIKE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-100. -- Resolution: Fixed the servlet-api is now optional improve the bootstrapping module for java-se for simple use-cases - Key: DELTASPIKE-100 URL: https://issues.apache.org/jira/browse/DELTASPIKE-100 Project: DeltaSpike Issue Type: Improvement Components: CdiControl Affects Versions: 0.1-incubating Reporter: Gerhard Petracek Assignee: Mark Struberg Fix For: 0.2-incubating #1 if users don't need the (mocked) web scopes in an java-se application, it should be possible to start the cdi container without the current dependency to the servlet-api. #2 allow a fine grained container handling (supported already) and a simplified control (just something like #start and #stop) -- 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-92) ContainerControl API + impls
[ https://issues.apache.org/jira/browse/DELTASPIKE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-92. - Resolution: Fixed ContainerControl API + impls Key: DELTASPIKE-92 URL: https://issues.apache.org/jira/browse/DELTASPIKE-92 Project: DeltaSpike Issue Type: New Feature Components: CdiControl Affects Versions: 0.1-incubating Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 0.2-incubating Java SE applications need a way to control the container. They need to start/stop it and control the lifecycle of the built-in Contexts (see http://s.apache.org/Rej ) -- 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-159) unit and integration tests for @ExceptionHandler
[ https://issues.apache.org/jira/browse/DELTASPIKE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-159. -- Resolution: Fixed I've set this to resolved so far as there are lots of tests already. If we need additional tests then please open a new issue. unit and integration tests for @ExceptionHandler Key: DELTASPIKE-159 URL: https://issues.apache.org/jira/browse/DELTASPIKE-159 Project: DeltaSpike Issue Type: Sub-task Components: Core, ExceptionControl-Module, Tests Reporter: Gerhard Petracek Assignee: Jason Porter 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] [Resolved] (DELTASPIKE-137) [CdiControl] implement ContainerControl for embedded OpenEJB + OWB
[ https://issues.apache.org/jira/browse/DELTASPIKE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-137. -- Resolution: Fixed implemented. @dblevins plz review [CdiControl] implement ContainerControl for embedded OpenEJB + OWB -- Key: DELTASPIKE-137 URL: https://issues.apache.org/jira/browse/DELTASPIKE-137 Project: DeltaSpike Issue Type: New Feature Components: CDI-SE Affects Versions: 0.1-incubating Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 0.2-incubating implement ContainerControl for embedded OpenEJB + OWB -- 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-136) [CdiControl] cdictrl-owb should only use the Session mocks if the servlet-api is available
[ https://issues.apache.org/jira/browse/DELTASPIKE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-136. -- Resolution: Fixed [CdiControl] cdictrl-owb should only use the Session mocks if the servlet-api is available -- Key: DELTASPIKE-136 URL: https://issues.apache.org/jira/browse/DELTASPIKE-136 Project: DeltaSpike Issue Type: Bug Components: CDI-SE Affects Versions: 0.1-incubating Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 0.2-incubating currently cdictrl-owb mandatorily needs the servlet-api on the classpath. But this is in fact only needed if the openwebbeans-web plugin is being used which automatically brings a servlet based cdi lifecycle plugin with it. So if we don't have the servlet-api on the ClassPath, we don't need to create any Session and ServletContext mocks at all. -- 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-135) [CdiControl] make Weld and OWB dependencies scopeprovided
[ https://issues.apache.org/jira/browse/DELTASPIKE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-135. -- Resolution: Fixed [CdiControl] make Weld and OWB dependencies scopeprovided --- Key: DELTASPIKE-135 URL: https://issues.apache.org/jira/browse/DELTASPIKE-135 Project: DeltaSpike Issue Type: Bug Components: CDI-SE Affects Versions: 0.1-incubating Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 0.2-incubating Currently all OWB and Weld dependencies are treated as transitive dependencies in our CdiControl modules. This might create problems, especially in EE environments. Thus we must change the scope in maven to *provided* for all those artifacts. -- 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-120) BeanProvider: add convenience methods without the 'optional' flag
[ https://issues.apache.org/jira/browse/DELTASPIKE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-120. -- Resolution: Fixed implemented BeanProvider: add convenience methods without the 'optional' flag - Key: DELTASPIKE-120 URL: https://issues.apache.org/jira/browse/DELTASPIKE-120 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 0.1-incubating Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 0.2-incubating The BeanProvider methods #getContextualReference(String name, boolean optional) and #getContextualReference(Type t, boolean optional, Annotation... qualifiers) will in 90% of the cases get called with optional=false to throw an IllegalStateException if no bean could be found. Thus we shall introduce 2 convenient methods without the boolean parameter which will fail if none of the requested beans exist. We don't need to do this for methods like getContextualReferences (plural) as those methods are not used that frequently. -- 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-123) convenience methods for CdiContainer
[ https://issues.apache.org/jira/browse/DELTASPIKE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-123. -- Resolution: Won't Fix nope, I deliberately left this out. This did lead to many confusion when we had both ways. There is simply no good name which expresses those options unambiguously. Currently it's very clear what needs to be done. And there are quite a few cases where you must NOT start the contexts. Especially in SE there is no clear single way how it must be done but really depending on the use case. convenience methods for CdiContainer Key: DELTASPIKE-123 URL: https://issues.apache.org/jira/browse/DELTASPIKE-123 Project: DeltaSpike Issue Type: Improvement Components: CDI-SE Reporter: Gerhard Petracek Assignee: Mark Struberg Fix For: 0.2-incubating Attachments: DELTASPIKE-123.patch in most cases users always have to call: CdiContainer#boot CdiContainer#getContextControl#startContexts as well as: CdiContainer#getContextControl#stop CdiContainer#shutdown imo we should think about convenience methods - e.g.: CdiContainer#start CdiContainer#stop -- 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-18) unit and integration tests for BeanManagerProvider
[ https://issues.apache.org/jira/browse/DELTASPIKE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-18. - Resolution: Fixed Fix Version/s: 0.1-SNAPSHOT unit and integration tests for BeanManagerProvider -- Key: DELTASPIKE-18 URL: https://issues.apache.org/jira/browse/DELTASPIKE-18 Project: DeltaSpike Issue Type: Sub-task Components: Core Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.1-SNAPSHOT we need tests for: - after a container is bootstrapped, BeanManagerProvider.getInstance().getBeanManager() has to return a bm - usage in shared lib scenarios - shutdown of a container - cleanup has to be successful -- 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-21) ProjectStage
[ https://issues.apache.org/jira/browse/DELTASPIKE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-21. - Resolution: Fixed Fix Version/s: 0.1-SNAPSHOT Implementation finished ProjectStage Key: DELTASPIKE-21 URL: https://issues.apache.org/jira/browse/DELTASPIKE-21 Project: DeltaSpike Issue Type: New Feature Components: Core Reporter: Gerhard Petracek Assignee: Mark Struberg Fix For: 0.1-SNAPSHOT original feature: https://issues.apache.org/jira/browse/EXTCDI-9 -- 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-20) move util methods to CdiUtils
[ https://issues.apache.org/jira/browse/DELTASPIKE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-20. - Resolution: Fixed Fix Version/s: 0.1-SNAPSHOT resolved as part of the work for DELTASPIKE-17 move util methods to CdiUtils - Key: DELTASPIKE-20 URL: https://issues.apache.org/jira/browse/DELTASPIKE-20 Project: DeltaSpike Issue Type: Sub-task Components: Core Reporter: Gerhard Petracek Assignee: Mark Struberg Fix For: 0.1-SNAPSHOT public T T getContextualReference(ClassT type, boolean optionalBeanAllowed, Annotation... qualifiers) public T T getContextualReference(String name, boolean optionalBeanAllowed, ClassT targetType) public T T getContextualReference(BeanT bean, boolean optionalBeanAllowed, ClassT targetType) public T ListT getContextualReferences(ClassT type, boolean optionalBeanAllowed, Annotation... qualifiers) -- 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
