[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on WELD-912:
----------------------------------
>> Does this require any SPI change?
Nope. ;-)
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.1.4.Final
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Nicklas Karlsson (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Nicklas Karlsson commented on WELD-912:
---------------------------------------
Does this require any SPI change?
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.1.4.Final
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on WELD-912:
----------------------------------
>> I'm not sure that this fixes the underlying initialisation order problems, it looks like this is still dependent on the order the BDA's get initalized.
It probably doesn't fix all order issues; e.g. interceptors and decorators
But imo it does fix specialized handling, as bean handling happens in 2 (actually even more) phases.
We first create beans, which we then simply look them up in initialize -- which is where specialized is determined.
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.1.4.Final
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Stuart Douglas (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on WELD-912:
-------------------------------------
I'm not sure that this fixes the underlying initialisation order problems, it looks like this is still dependent on the order the BDA's get initalized.
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.1.4.Final
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Updated) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin updated WELD-912:
-----------------------------
Fix Version/s: 1.1.4.Final
(was: 1.2.0.Beta1)
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.1.4.Final
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on WELD-912:
----------------------------------
Do we have some use / test case where @Alternative doesn't work as it should?
e.g. Fabricio or Matija, can you create an ARQ test with your use case?
(as I only fixed / handled specialized beans atm)
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.2.0.Beta1
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on WELD-912:
----------------------------------
This should be fixed here:
* https://github.com/alesj/core/tree/weld-912
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.2.0.Beta1
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Assigned) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin reassigned WELD-912:
--------------------------------
Assignee: Ales Justin
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.2.0.Beta1
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-912) Specializing beans in different bean archives does not work
by Ales Justin (Commented) (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on WELD-912:
----------------------------------
>> https://github.com/weld/core/pull/138
This test is broken -- it's missing beans.xml in .war. ;-)
But yeah, the problem is still there.
> Specializing beans in different bean archives does not work
> -----------------------------------------------------------
>
> Key: WELD-912
> URL: https://issues.jboss.org/browse/WELD-912
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Fix For: 1.2.0.Beta1
>
> Attachments: test.zip
>
>
> @Specializing a bean that is deployed in a different bean archive fails with the following exception:
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default]
> at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545)
> at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124)
> at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202)
> at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372)
> at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113)
> at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
> ... 4 more
--
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
12 years, 7 months
[JBoss JIRA] (WELD-892) Calling session-scoped components from session initialized observer goes into infinite loop
by Ales Justin (Resolved) (JIRA)
[ https://issues.jboss.org/browse/WELD-892?page=com.atlassian.jira.plugin.s... ]
Ales Justin resolved WELD-892.
------------------------------
Fix Version/s: 1.1.4.Final
Resolution: Done
> Calling session-scoped components from session initialized observer goes into infinite loop
> -------------------------------------------------------------------------------------------
>
> Key: WELD-892
> URL: https://issues.jboss.org/browse/WELD-892
> Project: Weld
> Issue Type: Bug
> Components: Scopes & Contexts
> Affects Versions: 1.1.1.Final
> Reporter: Nicklas Karlsson
> Assignee: Ales Justin
> Fix For: 1.1.4.Final
>
>
> Given a session scoped component
> {code}
> @SessionScoped
> public class Pinger implements Serializable
> {
> public void ping()
> {
> };
> }
> {code}
> and a session initialized observer calling it
> {code}
> public class Observer
> {
> @Inject
> Pinger pinger;
> public void newSession(@Observes @Initialized HttpSession s)
> {
> pinger.ping();
> }
> }
> {code}
> We go off into an infinite loop. Since Pinger doesn't exist, it is created and placed in the session scoped beanstore, which creates a session and fires off the observer. I'm not sure why the session isn't considered created at this point. This is bordering on feature since I think the result would be the same if servlet listeners would be used. Perhaps this could be worked around int the event bridge somehow so that the firing would be prevented if we're already handling the session created event...
--
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
12 years, 7 months