October 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDX-42) mvn install in extensions/trunk/ fails

by Martin Gencur (JIRA)

mvn install in extensions/trunk/ fails -------------------------------------- Key: WELDX-42 URL: https://jira.jboss.org/jira/browse/WELDX-42 Project: Weld Extensions Issue Type: Bug Reporter: Martin Gencur When I check-out http://anonsvn.jboss.org/repos/weld/extensions/trunk/ and then run "mvn install" in the root directory, maven outputs an error during compilation phase: (weld-se in the paths below means trunk/ ) [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: org.jboss.weld.servlet:weld-servlet-int POM Location: /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for org.jboss.weld:weld-logging Reason: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1107) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:877) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:505) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (WELD-222) Coordinate with Mojarra to get Weld JSF app working from Maven central

by Dan Allen (JIRA)

Coordinate with Mojarra to get Weld JSF app working from Maven central ---------------------------------------------------------------------- Key: WELD-222 URL: https://jira.jboss.org/jira/browse/WELD-222 Project: Weld Issue Type: Feature Request Components: Infrastructure Reporter: Dan Allen Fix For: 1.0.0.CR2 Although the Weld artifacts are published to the Maven central repository, it's still not possible to get a JSF app built without relying on the JBoss Maven repository. The problem is JSF. See output below. We have sent a request to the Mojarra team to publish their artifacts in the central repository. When they do, we need to align with that version. Missing: ---------- 1) javax.faces:jsf-api:jar:2.0.0-RC Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.example:helloworld:war:0.0.1-SNAPSHOT 2) javax.faces:jsf-api:jar:2.0.0-RC ---------- 1 required artifact is missing. for artifact: org.example:helloworld:war:0.0.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) However, if you add java.net repository and override the JSF versions to use the 2.0 release, you get errors on startup INFO: Weld 1.0.0-CR1 2009-10-21 21:58:22.119::WARN: Failed startup of context org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@66f4652{/jsf2,/home/lily/workspace/jsf2/0_helloworld/src/main/webapp} java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.java:1101) at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.parseAnnotations(Jetty6MavenConfiguration.java:135) at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configure(AbstractConfiguration.java:119) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180) at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configureWebApp(AbstractConfiguration.java:96) at org.mortbay.jetty.plus.webapp.Configuration.configureWebApp(Configuration.java:149) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
18
0 / 0

[JBoss JIRA] Created: (WELDINT-19) Bind BeanManager to java:comp/BeanManager not java:app/BeanManager

by Pete Muir (JIRA)

Bind BeanManager to java:comp/BeanManager not java:app/BeanManager ------------------------------------------------------------------ Key: WELDINT-19 URL: https://jira.jboss.org/jira/browse/WELDINT-19 Project: Weld Integration Issue Type: Bug Components: Deployer Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.2.0.Beta4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (WELDINT-23) ProcessAnnotatedType not fired for Filter, Tag Library Listener, Servlet Listener and JSF Managed Bean

by Jozef Hartinger (JIRA)

ProcessAnnotatedType not fired for Filter, Tag Library Listener, Servlet Listener and JSF Managed Bean ------------------------------------------------------------------------------------------------------ Key: WELDINT-23 URL: https://jira.jboss.org/jira/browse/WELDINT-23 Project: Weld Integration Issue Type: Bug Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 5.2.0.Beta5 org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForFilter() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForJsfManagedBean() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForTagLibraryListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForServletListener() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-240) Incorrect detection of Tomcat

by Daniel Munzinger (JIRA)

Incorrect detection of Tomcat ----------------------------- Key: WELD-240 URL: https://jira.jboss.org/jira/browse/WELD-240 Project: Weld Issue Type: Bug Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Environment: Windows, Tomcat 7.0.0 from trunk, Weld Servlet 1.0.0.CR1 Reporter: Daniel Munzinger Priority: Minor I've been playing around with the Tomcat 7 development stream from SVN trunk when I came across this litte message: "JSR-299 injection will not be available in Servlets, Filters etc. This facility is only available in Tomcat" I managed to locate the source of this message at org.jboss.weld.environment.servlet.Listener:114 when calling Reflections.classForName("org.apache.AnnotationProcessor"); This class is not present in the current code base which makes "tomcat = false" and Weld thinks that there is no tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
1
0 / 0

[JBoss JIRA] Created: (WELDINT-21) Wrong classloader used in InterceptorMethodHandler.readObject in JBoss AS

by Pete Muir (JIRA)

Wrong classloader used in InterceptorMethodHandler.readObject in JBoss AS ------------------------------------------------------------------------- Key: WELDINT-21 URL: https://jira.jboss.org/jira/browse/WELDINT-21 Project: Weld Integration Issue Type: Bug Reporter: Pete Muir Assignee: Marius Bogoevici Fix For: 5.2.0.Beta5 See org.jboss.weld.test.unit.interceptor.passivation.PassivationActivationTest.testPassivationAndActivation() It looks to me like the classloader of jboss-interceptor (the classloader for the deployer) is used to deserialize the proxy, whilst the WeldImpl exists on the application classloader -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (WELDINT-20) Interceptors and decorators defined on stateful EJBs must be passivated/activated

by Marius Bogoevici (JIRA)

Interceptors and decorators defined on stateful EJBs must be passivated/activated --------------------------------------------------------------------------------- Key: WELDINT-20 URL: https://jira.jboss.org/jira/browse/WELDINT-20 Project: Weld Integration Issue Type: Bug Components: JBoss EJB 3.0 integration Affects Versions: 5.2.0.Beta4 Reporter: Marius Bogoevici Assignee: Pete Muir Fix For: 5.2.0.Beta5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (WELD-204) ProcessInjectionTarget not fired for Servlet, Filter, Servlet Listener and Tag Library Listener

by Jozef Hartinger (JIRA)

ProcessInjectionTarget not fired for Servlet, Filter, Servlet Listener and Tag Library Listener ----------------------------------------------------------------------------------------------- Key: WELD-204 URL: https://jira.jboss.org/jira/browse/WELD-204 Project: Weld Issue Type: Bug Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForServletListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForTagLibraryListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForServlet() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForFilter() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (WELD-215) Deployment issues with numberguess example

by Christian Bauer (JIRA)

Deployment issues with numberguess example ------------------------------------------ Key: WELD-215 URL: https://jira.jboss.org/jira/browse/WELD-215 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.CR1 Reporter: Christian Bauer Priority: Minor The CR1 release has the following issues with /examples/wicket/numberguess: 1. There is an empty org/jboss/webbeans/examples/ directory in the src/ folder. 2. slf4j is completely missing in the WAR, neither API nor implementation is deployed. 3. The main Weld JARs are also missing, only weld-wicket.jar is being deployed. 4. After copying slf4j, log4j, and weld-servlet.jar, I get this exception on startup: Oct 19, 2009 4:17:20 PM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter wicket.numberguess-example org.apache.wicket.WicketRuntimeException: There is no application attached to current thread main at org.apache.wicket.Application.get(Application.java:179) at org.jboss.weld.wicket.BeanManagerLookup.getBeanManager(BeanManagerLookup.java:76) at org.jboss.weld.wicket.WeldApplication.<init>(WeldApplication.java:39) at org.jboss.weld.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:678) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3800) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4450) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) (Which is btw the same I get in my own weld-wicket test app after upgrading from webbeans 10-day-old-SVN trunk.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (WELDX-36) Dependence on portlet-api due to scanning of a class

by Pete Muir (JIRA)

Dependence on portlet-api due to scanning of a class ---------------------------------------------------- Key: WELDX-36 URL: https://jira.jboss.org/jira/browse/WELDX-36 Project: Weld Extensions Issue Type: Bug Components: Wicket support Reporter: Pete Muir Fix For: Wicket 1.0.0.BETA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2009