August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Closed: (WELD-606) Use shared library mode in Servlet containers, allowing packaging as a shared library mode

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-606?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed WELD-606. -------------------------- Assignee: Pete Muir Fix Version/s: (was: 1.1.0.Beta2) Resolution: Won't Fix Now that Matija got all the support in one jar, I don't think this is worth it. > Use shared library mode in Servlet containers, allowing packaging as a shared library mode > ------------------------------------------------------------------------------------------ > > Key: WELD-606 > URL: https://jira.jboss.org/browse/WELD-606 > Project: Weld > Issue Type: Feature Request > Components: Servlet Container Support > Reporter: Pete Muir > Assignee: Pete Muir > -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-523) Weld SE ignores org.jboss.weld.resources.spi.ResourceLoader

by Morten Christensen (JIRA)

Weld SE ignores org.jboss.weld.resources.spi.ResourceLoader ----------------------------------------------------------- Key: WELD-523 URL: https://jira.jboss.org/jira/browse/WELD-523 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: Weld SE + Java 6 Reporter: Morten Christensen Priority: Critical According to the docs "org.jboss.weld.resources.spi.ResourceLoader" is responsible for resource loading/class creation and if it worked it would appear to solve a lot of potential integration problems, f.x. with OSGI (see issue 520). Unfortunately, Weld SE does not apper to use ResourceLoaders and it ignores any implementations of this service that the Java SE app supplies. Even worse, Weld SE classloading behavior is hardcoded in "org.jboss.weld.environment.se.util.Reflections". This makes it impossible to use Weld SE where classloading does not work with the Thread's context class loader such as OSGI etc. Weld SE should be changed to look for service implementations of "org.jboss.weld.resources.spi.ResourceLoader" (i.e. actually work according to its own documentation). P.S: It would also be nice if Weld SE would allow users to supply a Classloader to the constructor for org.jboss.weld.environment.se.Weld -- 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, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (WELD-408) weld-servlet-javadoc.jar missing

by Wolfgang Frech (JIRA)

weld-servlet-javadoc.jar missing --------------------------------- Key: WELD-408 URL: https://jira.jboss.org/jira/browse/WELD-408 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Environment: n/a Reporter: Wolfgang Frech Priority: Trivial weld-servlet-javadoc.jar missing in distribution package weld-1.0.0.SP1.zip. All other JARs in folder artifacts have companion JARs with source and javadoc. Sorry for setting the priority to trivial. Saw note too late. Hope that committers agree. -- 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, 7 months

2
11
0 / 0

[JBoss JIRA] Updated: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-31: -------------------------- Fix Version/s: TBC > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://jira.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Roger Kitain > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-30) Include instructions in ref guide and readme's on how to run examples with GlassFish

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-30?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-30: -------------------------- Fix Version/s: TBC > Include instructions in ref guide and readme's on how to run examples with GlassFish > ------------------------------------------------------------------------------------ > > Key: WELD-30 > URL: https://jira.jboss.org/browse/WELD-30 > Project: Weld > Issue Type: Feature Request > Components: Examples, GlassFish Integration > Environment: GlassFish > Reporter: Roger Kitain > Assignee: Roger Kitain > Priority: Critical > Fix For: TBC > > > JBoss runs WebBeans example applications with GlassFish. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-17) Brazilian Portuguese translation of Web Beans Reference Documentation

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-17?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-17: -------------------------- Fix Version/s: TBC > Brazilian Portuguese translation of Web Beans Reference Documentation > --------------------------------------------------------------------- > > Key: WELD-17 > URL: https://jira.jboss.org/browse/WELD-17 > Project: Weld > Issue Type: Task > Components: Documentation > Reporter: Joao Paulo Viragine > Fix For: TBC > > > I would like to translate Web Beans Reference Documentation to Brazilian Portuguese. (pt-BR) -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (WELDX-132) Automatically add @Any qualifier to beans created with BeanBuilder

by Stuart Douglas (JIRA)

Automatically add @Any qualifier to beans created with BeanBuilder ------------------------------------------------------------------ Key: WELDX-132 URL: https://jira.jboss.org/browse/WELDX-132 Project: Weld Extensions Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 1.0.0.Alpha3 -- 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

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-647) CLONE -jsf/permalink example fails with "identifier 'blog' resolved to null"

by sreekanth manga (JIRA)

CLONE -jsf/permalink example fails with "identifier 'blog' resolved to null" ---------------------------------------------------------------------------- Key: WELD-647 URL: https://jira.jboss.org/browse/WELD-647 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.GA Environment: JBoss_5_2_0_Beta1 date=200911091833 Sun JDK 1.6.0_16-b01 Linux 32bit Reporter: sreekanth manga Fix For: 1.0.0.GA jsf/permalink example deploys, but when accessing the application it fails with following exception: 13:56:27,628 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception javax.el.PropertyNotFoundException: /home.xhtml @30,78 listener="#{blog.loadLatestEntries}": Target Unreachable, identifier 'blog' resolved to null at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:100) at com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:112) at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2342) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:1993) at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:1941) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:285) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:243) at org.jboss.weld.integration.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:336) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:114) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Closed: (WELD-644) WeldDeployer should ignore classes which cause ClassNotFoundException and NoClassDefFoundError

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-644?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed WELD-644. -------------------------- Resolution: Done With the changes due to WELD-521, classloading for bean definition is now done inside Weld, so we can catch these errors and log them. Heiko, please test BETA1 (out Monday with luck) with your scenario, and let me know if you still see any problems - it's possible I haven't protected all paths. > WeldDeployer should ignore classes which cause ClassNotFoundException and NoClassDefFoundError > ---------------------------------------------------------------------------------------------- > > Key: WELD-644 > URL: https://jira.jboss.org/browse/WELD-644 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API > Affects Versions: 1.0.1.Final > Reporter: Heiko Braun > Assignee: Pete Muir > Fix For: 1.1.0.BETA1 > > > We are working on the GWT/CDI integration. If an application packages GWT client classes that depend on gwt-user.jar and the weld deployer kicks in it chokes in classes that import GWT client API. This happens because the usage of reflection to scan for annotation meta data, loads all classes and forces all dependencies to be present. > These classes can be excluded from the web application packaging, but it's nothing people usally do, > because they are required when running the GWT hosted mode. > So in order to simplify things, I would suggest we simply log and skip classes that cannot be scanned due to CNFE and the like, instead of preventing the deployment at all. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-521) Support for dual SE and EE applications that uses weld

by Morten Christensen (JIRA)

Support for dual SE and EE applications that uses weld ------------------------------------------------------ Key: WELD-521 URL: https://jira.jboss.org/jira/browse/WELD-521 Project: Weld Issue Type: Feature Request Environment: Java SE and Java EE + weld Reporter: Morten Christensen Better support for dual SE and EE applications. I have some weld-using jar's that can be deployed on a Java EE and work standalone. It is possible to get this to work using both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE and weld EE OR there should at least be some support for having weld ignoring some of my classes/packages depending on which environment it is running under. -- 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, 7 months

2
37
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010