[JBoss JIRA] Created: (WELD-821) Include the name of the class declaring the dependency within ResourceLoadingException errors
by Shane Bryzak (JIRA)
Include the name of the class declaring the dependency within ResourceLoadingException errors
---------------------------------------------------------------------------------------------
Key: WELD-821
URL: https://issues.jboss.org/browse/WELD-821
Project: Weld
Issue Type: Feature Request
Reporter: Shane Bryzak
Assignee: Ales Justin
The error message in the following stack trace would be immensely more useful if it included information about the source of the missing dependency:
13:05:28,507 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Create: name=vfs:///home/shane/apps/jboss-6.0.0.Final/server/default/deploy/openid-rp.war_WeldBootstrapBean state=Configured: org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.jboss.seam.persistence.transaction.TransactionInterceptor
at org.jboss.weld.integration.deployer.env.bda.ClassLoaderResourceLoader.classForName(ClassLoaderResourceLoader.java:41) [:6.0.0.Final]
at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:67) [:6.0.0.Final]
at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:55) [:6.0.0.Final]
at com.google.common.collect.Lists$TransformingRandomAccessList.get(Lists.java:435) [:6.0.0.Final]
at java.util.AbstractList$Itr.next(AbstractList.java:345) [:1.6.0_20]
at org.jboss.weld.manager.Enabled.createMetadataMap(Enabled.java:130) [:6.0.0.Final]
at org.jboss.weld.manager.Enabled.<init>(Enabled.java:100) [:6.0.0.Final]
at org.jboss.weld.manager.Enabled.of(Enabled.java:82) [:6.0.0.Final]
at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:103) [:6.0.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:184) [:6.0.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:155) [:6.0.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:286) [:6.0.0.Final]
at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:106) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_20]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20]
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: java.lang.ClassNotFoundException: org.jboss.seam.persistence.transaction.TransactionInterceptor from BaseClassLoader@553675{vfs:///home/shane/apps/jboss-6.0.0.Final/server/default/deploy/openid-rp.war}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:480) [jboss-classloader.jar:2.2.0.GA]
at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [:1.6.0_20]
at org.jboss.weld.integration.deployer.env.bda.ClassLoaderResourceLoader.classForName(ClassLoaderResourceLoader.java:37) [:6.0.0.Final]
... 63 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (WELD-900) Docs: Improve Weld reference. Make it less poetic and more structured.
by Ondrej Zizka (JIRA)
Docs: Improve Weld reference. Make it less poetic and more structured.
----------------------------------------------------------------------
Key: WELD-900
URL: https://issues.jboss.org/browse/WELD-900
Project: Weld
Issue Type: Bug
Components: Documentation
Reporter: Ondrej Zizka
It's nice to have a nice text for a DZone article, but for a reference documentation, we should favor briefness and structure over potential nomination for Man Booker International Prize :)
What I mean is, e.g., if someone starts with Weld, he needs steps 1., 2., 3.
IMO, this should be in **bold** in a special chapter called "Preparing project to use Weld", with a sample code which is verified to work if copied and run, and eventually a reference to a quick-start app:
{quote}
There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml.
{quote}
In contrast, currently this most important information is buried at the end of last paragraph of irrelevantly sounding chapter, "1.1. What is a bean?". Why would anyone read "What is a bean"?
my2p, ymmv
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Commented: (WELD-912) Specializing beans in different bean archives does not work
by Nicklas Karlsson (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Nicklas Karlsson commented on WELD-912:
---------------------------------------
A test could look something like
{code}
package org.jboss.weld.tests.specialization;
import org.jboss.arquillian.api.Deployment;
import org.jboss.shrinkwrap.api.Archive;
import org.jboss.shrinkwrap.api.ArchivePaths;
import org.jboss.shrinkwrap.api.BeanArchive;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.asset.EmptyAsset;
import org.jboss.shrinkwrap.api.spec.JavaArchive;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.Test;
public class AS7Specialization
{
@Deployment
public static Archive<?> deploy()
{
JavaArchive jar = ShrinkWrap.create(BeanArchive.class, "test.jar").addClass(Foo.class);
WebArchive war = ShrinkWrap.create(WebArchive.class, "test.war").addLibrary(jar).addClass(Bar.class).addWebResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml"));
return war;
}
@Test
public void notneeded()
{
// should fail on deployment
}
}
{code}
{code}
public class Foo
{
}
{code}
{code}
@Specializes
public class Bar extends Foo
{
}
{code}
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Updated: (WELD-912) Specializing beans in different bean archives does not work
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas updated WELD-912:
--------------------------------
Summary: Specializing beans in different bean archives does not work (was: Specializing bean in bundled archive doesn't work)
Assignee: (was: Stuart Douglas)
Fix Version/s: 1.2.0.Beta1
Description:
@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
was:
@Specializing a bean by extending it directly from a bundled CDI-archive gives a
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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Commented: (WELD-912) Specializing bean in bundled archive doesn't work
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WELD-912?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on WELD-912:
-------------------------------------
In ManagedBean.specialize there is the following bit of code:
if (environment.getClassBean(getWeldAnnotated().getWeldSuperclass()) == null)
{
throw new DefinitionException(SPECIALIZING_BEAN_MUST_EXTEND_A_BEAN, this);
}
AbstractClassBean<?> specializedBean = environment.getClassBean(getWeldAnnotated().getWeldSuperclass());
The problem is that environment will never contain beans from a different bean archive, furthermore at this point in the deployment process not all beans are deployed yet.
> Specializing bean in bundled archive doesn't 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: Stuart Douglas
> Attachments: test.zip
>
>
> @Specializing a bean by extending it directly from a bundled CDI-archive gives a
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (WELD-784) Servlet / listener / filter injection support for Jetty 7.2
by Ben Sommerville (JIRA)
Servlet / listener / filter injection support for Jetty 7.2
-----------------------------------------------------------
Key: WELD-784
URL: https://issues.jboss.org/browse/WELD-784
Project: Weld
Issue Type: Patch
Components: Servlet Container Support
Affects Versions: 1.1.0.CR1
Reporter: Ben Sommerville
The fix committed for WELD-729 doesn't work under Jetty 7.2. It appears that the Jetty API has changed between 7.1 and 7.2, which results in servlet/etc injection not working.
I haven't tested under 8.0 but I notice that the fix refers to 8.0M0, I had to update that dependency to 8.0M2 in order to get my changes for 7.2 to compile, which meant I also had to change the jetty 8 support to fix those compile errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (WELDRAD-29) circular injection and target unreachable exception for generated webapp using maven archetype jboss-javaee6-webapp
by Gerry Matte (JIRA)
circular injection and target unreachable exception for generated webapp using maven archetype jboss-javaee6-webapp
--------------------------------------------------------------------------------------------------------------------
Key: WELDRAD-29
URL: https://issues.jboss.org/browse/WELDRAD-29
Project: Weld Archetypes
Issue Type: Bug
Components: javaee6-webapp
Affects Versions: javaee6-webapp-1.0.1.Beta3
Environment: Windows 7 x64, Java 1.6.0_24 x64, Jboss Developer 4, Maven 3.0.3, JBoss AS 6.0.0.Final, SEAM 3.0.0.Final Bundle
Reporter: Gerry Matte
Within JbDeveloper I created a new Maven project and selected groupId org.jboss.weld.archetypes, ArtifactId jboss-javaee6-webapp version 1.0.1.CR2 to create a new eclipse project(package name and project name are irrelevant). I then located the default-ds.xml file and marked it as deployable. I then used Jboss Runtime server - clean to republish the project and then I started the server.
There were no errors and only a few warnings.
When I completed the data form and clicked the submit button, an exception was thrown as detailed in the error log below:
16:39:29,456 INFO [org.jboss.ejb3.session.SessionSpecContainer] Starting jboss.j2ee:jar=weldTest.war,name=SeedDataImporter,service=EJB3
16:39:29,456 WARN [org.jboss.ejb3.session.SessionSpecContainer] EJBTHREE-2126: container jboss.j2ee:jar=weldTest.war,name=SeedDataImporter,service=EJB3 does not verify the businessObjectFactory
16:39:29,456 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: foo.data.SeedDataImporter ejbName: SeedDataImporter
16:39:29,472 WARN [org.jboss.ejb3.TimerServiceContainer] EJBTHREE-2193: using deprecated TimerServiceFactory for restoring timers
16:39:29,987 WARN [org.jboss.weld.Bean] WELD-000018 Executing producer field or method [method] @Produces public foo.test.MemberRegistrationTest.produceLog(InjectionPoint) on incomplete declaring bean Managed Bean [class foo.test.MemberRegistrationTest] with qualifiers [@Any @Default] due to circular injection
16:39:30,018 INFO [org.jboss.ejb3.nointerface.impl.jndi.AbstractNoInterfaceViewBinder] Binding the following entry in Global JNDI for bean:SeedDataImporter
SeedDataImporter/no-interface -> EJB3.1 no-interface view
16:39:30,065 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
16:39:30,080 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
16:39:30,080 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final "Neo"] Started in 1m:6s:248ms
16:40:16,075 WARN [org.jboss.weld.Bean] WELD-000018 Executing producer field or method [method] @Produces public foo.test.MemberRegistrationTest.produceLog(InjectionPoint) on incomplete declaring bean Managed Bean [class foo.test.MemberRegistrationTest] with qualifiers [@Any @Default] due to circular injection
16:40:44,725 WARN [org.jboss.weld.Bean] WELD-000018 Executing producer field or method [method] @Produces public foo.test.MemberRegistrationTest.produceLog(InjectionPoint) on incomplete declaring bean Managed Bean [class foo.test.MemberRegistrationTest] with qualifiers [@Any @Default] due to circular injection
16:40:44,731 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] /index.xhtml @21,75 value="#{newMember.name}": Target Unreachable, identifier 'newMember' resolved to null: javax.el.PropertyNotFoundException: /index.xhtml @21,75 value="#{newMember.name}": Target Unreachable, identifier 'newMember' resolved to null
at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:97) [:2.0.3-]
at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:91) [:2.0.3-]
at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1023) [:2.0.3-]
NOTE: the Bug form would not allow me to specify the version 1.0.1.CR2 so it's possible that I used an artifact that is not supposed to be used. However it's the only version of jboss-javaee6-webapp that I could find.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (WELD-870) Add injection point information to exception message when injection into observer fails
by Dan Allen (JIRA)
Add injection point information to exception message when injection into observer fails
---------------------------------------------------------------------------------------
Key: WELD-870
URL: https://issues.jboss.org/browse/WELD-870
Project: Weld
Issue Type: Enhancement
Components: Events
Affects Versions: 1.1.0.Final
Reporter: Dan Allen
Injections that fail when an observer method is invoked are massively hard to track down. Here's the information you get:
org.jboss.weld.exceptions.IllegalArgumentException: WELD-001324 Argument bean must not be null
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:714)
at org.jboss.seam.exception.control.HandlerMethodImpl.notify(HandlerMethodImpl.java:187)
at org.jboss.seam.exception.control.ExceptionHandlerDispatch.executeHandlers(ExceptionHandlerDispatch.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222)
at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:632)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613)
I expect to see the type and qualifiers at the failing injection point.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months