WELD-862 and Seam Cron
by Peter Royle
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks. Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which prevents Cron from running properly with Weld. I have been able to carry on developing Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future versions will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will work with the version of Weld already deployed in JBoss AS and Glassfish, which will contain the bug. The workaround mentioned in the bug report is to deep copy the InvocationContext. I attempted to do this by serialising and unserialising the InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any advice for me about how I might be able to work around this bug to support existing versions of Weld?
Cheers,
Pete R
2 months, 3 weeks
Exploring the Fun and Mystery of Anonymous Chat Platforms !
by William Lord
In today’s digital world, connecting with strangers from around the globe has become easier than ever. Anonymous chat platforms offer a unique space where you can strike up conversations without giving away your identity, fostering spontaneous, genuine interactions. Among these platforms, Omegle stands out as one of the pioneers, providing a simple yet intriguing way to meet new people anonymously. If you’re curious about how to play or just want to experience the interesting world of anonymous chatting, this guide will walk you through everything you need to know about Omegle and similar sites.
Introduction to Anonymous Chatting and Omegle https://omegleweb.io
Anonymous chat platforms allow users to engage in conversations without revealing their personal details or requiring any sign-up. Omegle, launched in 2009, popularized this concept by offering a straightforward text and video chat service that pairs you with random strangers instantly. The charm of Omegle lies in its unpredictability—you never know who you’ll meet or what you’ll talk about, making every chat session a new adventure.
If you want to dive in, you can visit Omegle to get started right away. The platform’s minimalist approach ensures that you can focus solely on the chatting experience without distractions.
7 months, 2 weeks
What is the expected impact of calling BeanConfiguratorImpl.name(String name) for a created bean?
by Scott Marlow
I'm running the following code in WildFly to create an EntityManagerFactory
CDI bean for application deployments to use but I don't seem to be able to
use the passed bean name ("pu1") in a test that has:
"
@Inject
@Named("pu1")
EntityManagerFactory entityManagerFactoryByPuName;
"
I expect that the following container code is naming the created bean but I
thought the passed name would work with @Named but it doesn't seem to. The
following EE container code (AfterBeanDiscovery callback) is doing the
following which includes a call to
"beanConfigurator.name(persistenceUnitMetadata.getPersistenceUnitName()):".
Should setting the bean name this way allow @Named references to the passed
name ("pu1" in this case) lookup the created bean as I am showing above?
"
private void entityManagerFactory(
AfterBeanDiscovery afterBeanDiscovery,
PersistenceUnitMetadata persistenceUnitMetadata,
List<String> qualifiers,
IntegrationWithCDIBag integrationWithCDIBag) throws
InstantiationException, IllegalAccessException {
String scope = applicationScoped;
// EntityManagerFactory setup
BeanConfigurator<EntityManagerFactory> beanConfigurator =
afterBeanDiscovery.addBean();
beanConfigurator.addTransitiveTypeClosure(EntityManagerFactory.class);
try {
if (!persistenceUnitMetadata.isDuplicate()) {
beanConfigurator.name(persistenceUnitMetadata.getPersistenceUnitName());
String qualifier = "jakarta.inject.Named";
final Class<? extends Annotation> qualifierType =
persistenceUnitMetadata.getClassLoader()
.loadClass(qualifier)
.asSubclass(Annotation.class);
beanConfigurator.addQualifier(ScopeProxy.createProxy(qualifierType));
}
Class<? extends Annotation> scopeAnnotation =
persistenceUnitMetadata.getClassLoader().loadClass(scope).asSubclass(Annotation.class);
beanConfigurator.scope(scopeAnnotation);
for (String qualifier : qualifiers) {
final Class<? extends Annotation> qualifierType =
persistenceUnitMetadata.getClassLoader()
.loadClass(qualifier)
.asSubclass(Annotation.class);
beanConfigurator.addQualifier(ScopeProxy.createProxy(qualifierType));
}
Class<?> entityManagerFactoryClass = EntityManagerFactory.class;
beanConfigurator.beanClass(entityManagerFactoryClass);
beanConfigurator.produceWith(c -> {
return integrationWithCDIBag.getEntityManagerFactory();
}
);
} catch (ClassNotFoundException e) {
throw JpaLogger.ROOT_LOGGER.classNotFound(e,
persistenceUnitMetadata.getScopedPersistenceUnitName());
}
}
"
Thanks,
Scott
8 months
Commonhaus related commotion
by Matej Novotny
All,
you might have spotted a recent clean up and commotion in the Weld project
space.
This is to adapt Weld to the requirements[1] of Commonhaus Foundation which
we are now part of.
As part of this task, I have done the following:
* Multiple long inactive projects have been archived (as public archives)
* Remaining projects have all been given license if missing and Developer
Certificate of Origin (DOC)
* There is an org-wide repository[2] which holds common documents for all
Weld projects. This includes CONTRIBUTING.md, CODE_OF_CONDUCT.md and
GOVERNANCE.md
* I also cleaned up the organization teams/groups WRT to permissions and
repository access and only kept very basic groups which correspond to the
current setup
The most important documents I want to draw attention to are probably
GOVERNANCE.md[3] and CONTRIBUTING.md[4]. The former outlines how the
project is "run", what roles are there and how to gain and revoke a role.
The latter is obvious from the name but no less important.
I tried to draft an initial workable version of both. The emphasis is on
the initial version; it is not set in stone and we can change it if we
decide to.
in case you have some objections, ideas, suggestions or you think
you spotted something wrong, don't hesitate to reach out!
Regards
Matej
Weld Project Lead
__________________________________________
[1]
https://github.com/commonhaus/foundation/blob/main/templates/panda/README.md
[2] https://github.com/weld/.github
[3] https://github.com/weld/.github/blob/main/GOVERNANCE.md
[4] github.com/weld/.github/blob/main/CONTRIBUTING.md
8 months, 1 week
Any idea what is wrong with my annotation loading code that causes Weld-core 5.1.6.Final org.jboss.weld.util.Bindings#validateQualifiers() to throw error?
by Scott Marlow
Any suggestions for what is wrong in [1] that
causes org.jboss.weld.util.Bindings#validateQualifiers() to throw
"MetadataLogger.LOG.notAQualifier" error [2]?
I tried a few variations of loading an application class that should be
a jakarta.inject.Qualifier but doesn't seem to work correctly.
In summary, I'm trying to implement the [3] feature that integrates
Persistence + CDI access from a Jakarta EE 11 implementation.
Thanks,
Scott
[1]
https://github.com/wildfly/wildfly/compare/main...scottmarlow:wildfly:WFL...
[2]
2025-07-17 12:55:53,714 INFO [org.jboss.as.jpa] (ServerService Thread Pool
-- 84) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service
'CDIPersistenceTestCase.jar#pu1'
2025-07-17 12:55:54,364 ERROR [org.jboss.msc.service.fail] (MSC service
thread 1-6) MSC000001: Failed to start service
jboss.deployment.unit."CDIPersistenceTestCase.jar".WeldStartService:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."CDIPersistenceTestCase.jar".WeldStartService: Failed
to start service
at org.jboss.msc(a)1.5.6.Final
//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1545)
at org.jboss.msc(a)1.5.6.Final
//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1374)
at org.jboss.threads(a)3.9.1
//org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
at org.jboss.threads(a)3.9.1
//org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2651)
at org.jboss.threads(a)3.9.1
//org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2630)
at org.jboss.threads(a)3.9.1
//org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1622)
at org.jboss.threads(a)3.9.1
//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1589)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: jakarta.enterprise.inject.spi.DefinitionException:
org.jboss.weld.exceptions.DefinitionException: WELD-001111: interface
jakarta.inject.Qualifier defined on Configurator Bean [interface
jakarta.persistence.EntityManager, types: Object, EntityManager,
qualifiers: @Any @Qualifier] is not a qualifier
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.finish(AfterBeanDiscoveryImpl.java:200)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:76)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:463)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:87)
at org.jboss.as.weld(a)37.0.0.Final-SNAPSHOT
//org.jboss.as.weld.WeldStartService.start(WeldStartService.java:80)
at org.jboss.msc(a)1.5.6.Final
//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1553)
at org.jboss.msc(a)1.5.6.Final
//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1516)
... 7 more
Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001111:
interface jakarta.inject.Qualifier defined on Configurator Bean [interface
jakarta.persistence.EntityManager, types: Object, EntityManager,
qualifiers: @Any @Qualifier] is not a qualifier
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.util.Bindings.validateQualifiers(Bindings.java:77)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateQualifiers(ExternalBeanAttributesFactory.java:89)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateBeanAttributes(ExternalBeanAttributesFactory.java:71)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.processBeanRegistration(AfterBeanDiscoveryImpl.java:212)
at org.jboss.weld.core(a)5.1.6.Final
//org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.finish(AfterBeanDiscoveryImpl.java:194)
... 13 more
[3]
https://jakarta.ee/specifications/platform/11/jakarta-platform-spec-11.0#...
8 months, 1 week
