January 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDI-29) Method of accessing contexts regardless of active state

by Nicklas Karlsson (JIRA)

Method of accessing contexts regardless of active state ------------------------------------------------------- Key: CDI-29 URL: https://issues.jboss.org/browse/CDI-29 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Nicklas Karlsson It would be practical to have a way of accessing contexts from the BeanManager regardless of their active state. Currently, contexts cannot be activated (e.g. Conversation) in a portable way because there is no way of getting the inactive context in order to activate it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-27) Support declarative transactions on managed beans

by Pete Muir (JIRA)

Support declarative transactions on managed beans ------------------------------------------------- Key: CDI-27 URL: https://issues.jboss.org/browse/CDI-27 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-26) Embedded Mode

by Pete Muir (JIRA)

Embedded Mode ------------- Key: CDI-26 URL: https://issues.jboss.org/browse/CDI-26 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir Weld and other CDI impls allow an embedded mode. See http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#... for example -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-23) Allow BeanManager to be resolved as though you were in another bean archive

by Pete Muir (JIRA)

Allow BeanManager to be resolved as though you were in another bean archive --------------------------------------------------------------------------- Key: CDI-23 URL: https://issues.jboss.org/browse/CDI-23 Project: CDI Specification Issues Issue Type: Bug Reporter: Pete Muir Currently it's not possible to access beans as though you were in another bean manager, something that is useful for extensions to be able to do. For example, if I want to create a facade over the ELResolver, or access a particular configuration bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-24) Make it easier to build passivating contexts by making sure Contextual objects passed to them are serializable

by Pete Muir (JIRA)

Make it easier to build passivating contexts by making sure Contextual objects passed to them are serializable -------------------------------------------------------------------------------------------------------------- Key: CDI-24 URL: https://issues.jboss.org/browse/CDI-24 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir OWB ensures that any Contextual impl passed to a passivating context is serializable, making it much easier to impl a custom passivating context. We should probably make this required by the spec. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-21) Support PostConstruct callbacks in Extension class

by Sivakumar Thyagarajan (JIRA)

Support PostConstruct callbacks in Extension class -------------------------------------------------- Key: CDI-21 URL: https://jira.jboss.org/browse/CDI-21 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Sivakumar Thyagarajan Priority: Minor It is sometimes useful to get to know after a portable extension class has been instantiated, so that the state of the Extension could be initialized [ie not establishing state in the constructor and having it called twice when the Extension is proxied]. Though the 1.0 specification does not require this, it would be useful to support @PostConstruct callback on Extension class in the next version of the specification. Please see https://jira.jboss.org/browse/WELD-713 for additional information on this issue. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-717) @Observes(propagate = false) - stop event propagation after being handled by an observer

by Walter White (JIRA)

@Observes(propagate = false) - stop event propagation after being handled by an observer ---------------------------------------------------------------------------------------- Key: WELD-717 URL: https://jira.jboss.org/browse/WELD-717 Project: Weld Issue Type: Feature Request Components: Events Affects Versions: 1.0.1.Final Environment: any Reporter: Walter White I would like to have the ability to stop event propagation after it is handled by any observer only for certain situations. Is it possible to add a property to the annotation indicating whether the propagation should continue after being handled by the observer? Alternatively, would it be more concise to add a qualifier annotation which specifies the propagation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-19) Ordering execution on Extensions

by Robson Saraiva Ximenes (JIRA)

Ordering execution on Extensions -------------------------------- Key: CDI-19 URL: https://jira.jboss.org/browse/CDI-19 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.1 Reporter: Robson Saraiva Ximenes Priority: Minor I believe the cdi portable extension could have the load order of extensions the same as it is registered; It is possible that one extension expect some previous preparation of beans from another extension -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-16) Improve EE 6 Managed Bean integration

by Pete Muir (JIRA)

Improve EE 6 Managed Bean integration ------------------------------------- Key: CDI-16 URL: https://jira.jboss.org/browse/CDI-16 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Reporter: Pete Muir Fix For: 1.1 Try to work out if we can improve on this. At least, we should clarify what happens if a CDI managed bean is annotated with @ManagedBean -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-15) Relax @Target annotation for CDI Scopes and Qualifiers

by Stuart Douglas (JIRA)

Relax @Target annotation for CDI Scopes and Qualifiers ------------------------------------------------------ Key: CDI-15 URL: https://jira.jboss.org/browse/CDI-15 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Stuart Douglas In some cases it may make sense to apply a scope or qualifier in a place that was not envisaged by the spec but that would be useful for a portable extension. For example, the @Constructs extension described at http://www.seamframework.org/Weld/PortableExtensionsPackage#H-BeanDeclara... is not possible because scopes and qualifiers can not be placed on constructors -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2011