[jira] [Resolved] (DELTASPIKE-385) Spurious BeanManagerProvider warnings when used in EAR
[ https://issues.apache.org/jira/browse/DELTASPIKE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-385. -- Resolution: Fixed Fix Version/s: 0.5 Spurious BeanManagerProvider warnings when used in EAR -- Key: DELTASPIKE-385 URL: https://issues.apache.org/jira/browse/DELTASPIKE-385 Project: DeltaSpike Issue Type: Bug Components: Core Affects Versions: 0.4 Environment: JBoss AS 7.2.0.Final (EAP 6.1.0.Alpha1) Reporter: Richard DiCroce Assignee: Mark Struberg Fix For: 0.5 BeanManagerProvider spams the log with this warning, long after the container has been started: When using the BeanManager to retrieve Beans before the Container is started, non-portable behaviour results! The problem appears to be caused by having deltaspike-core-api in the EAR /lib directory and using BeanManagerProvider from inside a WAR module. The warning gets printed when the booted flag for the appropriate BeanManagerInfo is false, and BeanManagerInfo instances initialize it to false when they are created. The only place the booted flag gets changed to true is in cleanupFinalBeanManagers(), which iterates over all the BeanManagerInfo instances that exist at the time it is called. In my case, the only BeanManagerInfo that exists when cleanupFinalBeanManagers() is called is the one that was created when the setBeanManager() observer method was called by the container. But the classloader in use when setBeanManager() was called was the classloader for the entire EAR. Because I don't attempt to use BeanManagerProvider until after cleanupFinalBeanManagers() is called, this means that the BeanManagerInfo for the WAR classloader is created with the booted flag set to false (which is incorrect) and the flag is never changed to true. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DELTASPIKE-385) Spurious BeanManagerProvider warnings when used in EAR
[ https://issues.apache.org/jira/browse/DELTASPIKE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735884#comment-13735884 ] Mark Struberg commented on DELTASPIKE-385: -- Daniel, Richard, could you please try this fix and report if it works now? txs! Spurious BeanManagerProvider warnings when used in EAR -- Key: DELTASPIKE-385 URL: https://issues.apache.org/jira/browse/DELTASPIKE-385 Project: DeltaSpike Issue Type: Bug Components: Core Affects Versions: 0.4 Environment: JBoss AS 7.2.0.Final (EAP 6.1.0.Alpha1) Reporter: Richard DiCroce Assignee: Mark Struberg Fix For: 0.5 BeanManagerProvider spams the log with this warning, long after the container has been started: When using the BeanManager to retrieve Beans before the Container is started, non-portable behaviour results! The problem appears to be caused by having deltaspike-core-api in the EAR /lib directory and using BeanManagerProvider from inside a WAR module. The warning gets printed when the booted flag for the appropriate BeanManagerInfo is false, and BeanManagerInfo instances initialize it to false when they are created. The only place the booted flag gets changed to true is in cleanupFinalBeanManagers(), which iterates over all the BeanManagerInfo instances that exist at the time it is called. In my case, the only BeanManagerInfo that exists when cleanupFinalBeanManagers() is called is the one that was created when the setBeanManager() observer method was called by the container. But the classloader in use when setBeanManager() was called was the classloader for the entire EAR. Because I don't attempt to use BeanManagerProvider until after cleanupFinalBeanManagers() is called, this means that the BeanManagerInfo for the WAR classloader is created with the booted flag set to false (which is incorrect) and the flag is never changed to true. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DELTASPIKE-399) Incorporate Solder's ResourceLoader features into DeltaSpike
[
https://issues.apache.org/jira/browse/DELTASPIKE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735885#comment-13735885
]
Mark Struberg commented on DELTASPIKE-399:
--
did you look at our ConfigSource mechanism already? This provides very similar
features, but much more powerful imo. Please report back if you are missing
something - txs!
Incorporate Solder's ResourceLoader features into DeltaSpike
Key: DELTASPIKE-399
URL: https://issues.apache.org/jira/browse/DELTASPIKE-399
Project: DeltaSpike
Issue Type: New Feature
Components: Core
Affects Versions: 0.4
Reporter: Aaron Siri
Priority: Minor
Seam 3's Solder module had some nice resource loading functionality within
the org.jboss.solder.resourceLoader packages. With it you could do the
following:
// Load a properties file
@Inject @Resource(app.properties)
private Properties appProperties;
or:
@Inject
private ResourceProvider resourceProvider
public Properties getHostProperties() {
String hostname = java.net.InetAddress.getLocalHost().getHostName();
return resourceProvider.loadPropertiesBundle(hostname + .properties);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DELTASPIKE-399) Incorporate Solder's ResourceLoader features into DeltaSpike
[
https://issues.apache.org/jira/browse/DELTASPIKE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735889#comment-13735889
]
Mark Struberg commented on DELTASPIKE-399:
--
great you found it. For completeness:
http://deltaspike.apache.org/configuration.html
Incorporate Solder's ResourceLoader features into DeltaSpike
Key: DELTASPIKE-399
URL: https://issues.apache.org/jira/browse/DELTASPIKE-399
Project: DeltaSpike
Issue Type: New Feature
Components: Core
Affects Versions: 0.4
Reporter: Aaron Siri
Priority: Minor
Seam 3's Solder module had some nice resource loading functionality within
the org.jboss.solder.resourceLoader packages. With it you could do the
following:
// Load a properties file
@Inject @Resource(app.properties)
private Properties appProperties;
or:
@Inject
private ResourceProvider resourceProvider
public Properties getHostProperties() {
String hostname = java.net.InetAddress.getLocalHost().getHostName();
return resourceProvider.loadPropertiesBundle(hostname + .properties);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DELTASPIKE-399) Incorporate Solder's ResourceLoader features into DeltaSpike
[
https://issues.apache.org/jira/browse/DELTASPIKE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735908#comment-13735908
]
Aaron Siri commented on DELTASPIKE-399:
---
The ConfigSource mechanism looks like it'd meet my needs and I'm going to give
it a try but it has a specific purpose. The @Resource/ResourceProvider support
in Solder was more generic and I think would still be useful. It easily allows
for the loading of .xml files, images, etc.
Incorporate Solder's ResourceLoader features into DeltaSpike
Key: DELTASPIKE-399
URL: https://issues.apache.org/jira/browse/DELTASPIKE-399
Project: DeltaSpike
Issue Type: New Feature
Components: Core
Affects Versions: 0.4
Reporter: Aaron Siri
Priority: Minor
Seam 3's Solder module had some nice resource loading functionality within
the org.jboss.solder.resourceLoader packages. With it you could do the
following:
// Load a properties file
@Inject @Resource(app.properties)
private Properties appProperties;
or:
@Inject
private ResourceProvider resourceProvider
public Properties getHostProperties() {
String hostname = java.net.InetAddress.getLocalHost().getHostName();
return resourceProvider.loadPropertiesBundle(hostname + .properties);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
