June 2010 - weld-issues - Jboss List Archives

[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

13 years, 9 months

2
18
0 / 0

[JBoss JIRA] Created: (WELD-542) Exception messages missing useful information: "Injection point has unsatisfied/ambiguous dependencies

by Lincoln Baxter III (JIRA)

Exception messages missing useful information: "Injection point has unsatisfied/ambiguous dependencies ------------------------------------------------------------------------------------------------------ Key: WELD-542 URL: https://jira.jboss.org/browse/WELD-542 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.1.Final Reporter: Lincoln Baxter III I feel like the following exception message is missing some very useful information (e.g, the type of the object that could not be satisfied;) I don't want to have to look at the injection point in order to see what it couldn't find. Also, I have to skim over a few words before I get the information that really tells me what's going on. "Unsatisfied dependencies" should be the primary focus of the message. WELD-001408 Injection point has unsatisfied dependencies. Injection point: field org.jboss.seam.faces.status.MessagesAdapter.context; Qualifiers: [@javax.enterprise.inject.Default()] The message should probably look something like this, instead: WELD-001408 Unsatisfied dependencies for type [org.jboss.seam.international.status.Messages] at injection point [field] [org.jboss.seam.faces.status.MessagesAdapter.context]. Qualifiers: [@javax.enterprise.inject.Default()] This way, I immediately know that I have unsatisfied dependencies, and the type that cannot be resolved. From there, I can see where the type is being requested and its qualifiers. I'd like to see the same thing done for the Ambiguous dependencies exception message: Existing: Injection point has ambiguous dependencies. Injection point: field org.jboss.seam.faces.status.MessagesAdapter.context; Qualifiers: [@javax.enterprise.inject.Default()]; Possible dependencies: [org.jboss.seam.international.status.Messages1, org.jboss.seam.international.status.Messages2] Proposed: Ambiguous dependencies for type [org.jboss.seam.international.status.Messages] at injection point [field] [org.jboss.seam.faces.status.MessagesAdapter.context]. Qualifiers: [@javax.enterprise.inject.Default()]; Possible dependencies: [org.jboss.seam.international.status.Messages1, org.jboss.seam.international.status.Messages2] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-87) weldContainer.instance().select().iterator() contains null element

by Samuli Saarinen (JIRA)

weldContainer.instance().select().iterator() contains null element ------------------------------------------------------------------ Key: WELDX-87 URL: https://jira.jboss.org/jira/browse/WELDX-87 Project: Weld Extensions Issue Type: Bug Components: Java SE Environment: Java 1.6, weld-se.1.0.1-Final Reporter: Samuli Saarinen {code} private Weld weld; private WeldContainer container; @BeforeMethod public void beforeMethod() throws Exception { weld = new Weld(); container = weld.initialize(); } @Test public void testSelect() throws Exception { Iterator<Object> iter = container.instance().select().iterator(); while (iter.hasNext()) { assertNotNull(iter.next()); } } @AfterMethod public void afterMethod() { weld.shutdown(); } {code} -- 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

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-557) InjectionTarget methods called with a proxied instance

by Jozef Hartinger (JIRA)

InjectionTarget methods called with a proxied instance ------------------------------------------------------ Key: WELD-557 URL: https://jira.jboss.org/browse/WELD-557 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Jozef Hartinger Priority: Critical Fix For: 1.0.2.CR1 Let's have a bean whose InjectionTarget is wrapped by an extension to provide additional dependency injection, etc... Although it is not explicitly stated in the spec, it is obvious that inject(), postConstruct() and preDestroy() methods of the InjectionTarget should be called with the actual raw bean instance and not with a client proxy. org.jboss.weld.tests.extensions.injectionTarget.InjectionTargetTest (Consider moving the test into the TCK if the presumtion can be implied) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-552) CDI-API is leaking TestNG to everyone

by Aslak Knutsen (JIRA)

CDI-API is leaking TestNG to everyone ------------------------------------- Key: WELD-552 URL: https://jira.jboss.org/browse/WELD-552 Project: Weld Issue Type: Bug Components: CDI API Reporter: Aslak Knutsen Assignee: Aslak Knutsen CDI-API now has a TestCase, but the TestNG dependency is set to default(compile) which means anyone depending on CDI-API will be forced to use TestNG. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-546) Beans producing stuff have their proxies proxying the product

by Nicklas Karlsson (JIRA)

Beans producing stuff have their proxies proxying the product ------------------------------------------------------------- Key: WELD-546 URL: https://jira.jboss.org/browse/WELD-546 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Assignee: David Allen Given @Model public class GreetingBean { @Produces @Model Greeting greeting = new Greeting(); public void ping() { } } #{greetingBean.ping} gives an "Method not found" exception because the GreetingBean_$$_WeldProxy is actually proxing Greeting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (WELDINT-47) Create 6.0.0.Beta7_VFS3_int branch to merge VFS3 changes

by John Bailey (JIRA)

Create 6.0.0.Beta7_VFS3_int branch to merge VFS3 changes --------------------------------------------------------- Key: WELDINT-47 URL: https://jira.jboss.org/jira/browse/WELDINT-47 Project: Weld Integration Issue Type: Task Affects Versions: 6.0.0.Beta7 Reporter: John Bailey Assignee: Pete Muir Fix For: 6.0.0.Beta8 Need to create branch 6.0.0.Beta7_VFS3_int to create a Beta8 release with VFS3 support. -- 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

13 years, 9 months

2
3
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

13 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (WELD-462) Injection into EJB Interceptor classes does not occur

by Ian (JIRA)

Injection into EJB Interceptor classes does not occur ----------------------------------------------------- Key: WELD-462 URL: https://jira.jboss.org/jira/browse/WELD-462 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: JBoss 6.0.0 M2 with Weld 1.0.1 Final, on Windows XP SP3 and JDK 1.6 Reporter: Ian An interceptor for an EJB (not a Weld interceptor) is a contained managed class, yet it is not being injected with any dependencies. Some example code: public class FaultBarrierInterceptor { @Inject private Logger log; @AroundInvoke public Object intercept(final InvocationContext invocationContext) throws Exception { try { return invocationContext.proceed(); } catch (RuntimeException e) { log.error("An uncaught exception was caught: \n-METHOD: " + invocationContext.getMethod() + "\n-PARAMS: " + Arrays.toString(invocationContext.getParameters())); throw new MyUncaughtException(e); } } } When you debug this code, the logger variable is not injected. The code for the EJB has a local interface (it's an EJB 3.0 structure, not 3.1). The interceptor definition is: @Stateless @Interceptors( {FaultBarrierInterceptor.class}) public class OptinServiceBean implements OptinService { } -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (WELDINT-50) Create 6.0.0.Alpha8 release for weld-int

by John Bailey (JIRA)

Create 6.0.0.Alpha8 release for weld-int ---------------------------------------- Key: WELDINT-50 URL: https://jira.jboss.org/jira/browse/WELDINT-50 Project: Weld Integration Issue Type: Release Affects Versions: 6.0.0.Beta8 Reporter: John Bailey Assignee: John Bailey Fix For: 6.0.0.Beta7 Create the release 6.0.0.Alpha8 for weld-int -- 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

13 years, 9 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2010