August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-650) Documentation issues

by Jozef Hartinger (JIRA)

Documentation issues -------------------- Key: WELD-650 URL: https://jira.jboss.org/browse/WELD-650 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.0.Beta1 Reporter: Jozef Hartinger Assignee: Pete Muir Attachments: code_samples.png readme.txt - the second paragraph says "This is feature complete release of the CDI specification." IMHO it should say "This is a feature complete implementation of the CDI specification." - the licensing section says "the Apache License, Version 2.0" it should say "ASL 2.0" or "Apache Source License 2.0" - Source code reference should be "http://github.com/weld" not "http://anonsvn.jboss.org/repos/weld" examples/readme.txt - the pastecode example is not mentioned - se/helloworld should be se/hello-world - remove wicket example reference examples/se/numberguess/readme.txt - mentions Web Beans - restricts maven to version 2 (maven 3 users should not be limited) examples/se/helloworld/readme.txt - mentions Web Beans - instructions are wrong (examples/se/hello-world should be used instead of examples/se/numberguess) - restricts maven to version 2 (maven 3 users should not be limited) Javadoc - doc/apidoc contains CDI javadoc only (no Weld-specific docs) Reference documentation - remove wicket references - entire section 7.2 - update SCM references (Chapter 17) - code sample references (numbers) not rendered correctly in the HTML version (see the attached screenshot) -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-62) The Weld Porting Package Impls provided by the TCK should support OSGI

by Kyle Grucci (JIRA)

The Weld Porting Package Impls provided by the TCK should support OSGI ---------------------------------------------------------------------- Key: CDITCK-62 URL: https://jira.jboss.org/jira/browse/CDITCK-62 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: All Reporter: Kyle Grucci Fix For: 1.0.1.CR1 The current porting package impl classes provided with the TCK work with Weld in a non-OSGI environment. It would be great in the future if the impls can also work out of the box with Weld in an OSGI environment. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-206) Tests for OSGi bundle to ensure the correct bundle headers are generated

by Pete Muir (JIRA)

Tests for OSGi bundle to ensure the correct bundle headers are generated ------------------------------------------------------------------------ Key: WELD-206 URL: https://jira.jboss.org/jira/browse/WELD-206 Project: Weld Issue Type: Task Reporter: Pete Muir Assignee: Roger Kitain Priority: Critical Fix For: 1.0.0.CR2 -- 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, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (WELD-261) Tidy up OSGi exports

by Pete Muir (JIRA)

Tidy up OSGi exports -------------------- Key: WELD-261 URL: https://jira.jboss.org/jira/browse/WELD-261 Project: Weld Issue Type: Task Components: OSGi support Reporter: Pete Muir Priority: Critical Fix For: 1.0.1.CR1 -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (WELDSERVLET-28) add beforeContextInitialized and other servlet event

by he youlin (JIRA)

add beforeContextInitialized and other servlet event ---------------------------------------------------- Key: WELDSERVLET-28 URL: https://jira.jboss.org/browse/WELDSERVLET-28 Project: Weld Servlet Issue Type: Feature Request Reporter: he youlin Sometimes i want to get ServletContextEvent weld event after weld container started and before validateBeans,so i can do some init work in weld extension.And I can wrap servletContext as a weld bean in this weld event's observe then i can use the servletContext bean in all weld extension of event's observe after container started.So we can do more init work of servlet container such as tomcat or jetty servlet inject or spring's init work. see http://seamframework.org/Community/ShouldSeamServletEventMoveToWeldservle... -- 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, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (WELD-497) Check for null in BeanManager.getReference()

by Jozef Hartinger (JIRA)

Check for null in BeanManager.getReference() -------------------------------------------- Key: WELD-497 URL: https://jira.jboss.org/jira/browse/WELD-497 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.1.Final Reporter: Jozef Hartinger Assignee: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 Weld currently throws the following exception if the "bean" parameter is null during getReference() invocation Caused by: java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:810) An exception with self-explanatory message should be thrown instead. Also, check the other parameters for null values. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-273) Add GlassFish targets to example POMs

by Pete Muir (JIRA)

Add GlassFish targets to example POMs ------------------------------------- Key: WELD-273 URL: https://jira.jboss.org/jira/browse/WELD-273 Project: Weld Issue Type: Feature Request Components: Examples, GlassFish Integration Reporter: Pete Muir Fix For: 1.0.1.CR1 -- 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, 5 months

1
7
0 / 0

[JBoss JIRA] Created: (WELD-570) Partial export of javasisst from Weld breaks other javasisst clients

by Harald Wellmann (JIRA)

Partial export of javasisst from Weld breaks other javasisst clients -------------------------------------------------------------------- Key: WELD-570 URL: https://jira.jboss.org/browse/WELD-570 Project: Weld Issue Type: Bug Components: OSGi support Affects Versions: 1.1.0.BETA1 Reporter: Harald Wellmann weld-osgi-bundle.jar (as used in Glassfish 3.0 and higher) still contains a buggy version of javasisst causing memory leaks. See WELD-453 and JASSIST-104. Even though Weld itself no longer uses the problematic javassist ProxyFactory, it is still the root cause for a memory leak occurring when HIbernate (or potentially any other Javassist client) is used on Glassfish. The problem exists in Glassfish 3.0.1 and also in the promoted build 3.1-b12 using a 1.1.0 prerelease of Weld, see https://glassfish.dev.java.net/issues/show_bug.cgi?id=12368 weld-osgi-bundle.jar contains a version of javassist which is almost but not fully private. There is a package export for javassist.util.proxy. When deploying a WAR on Glassfish containing Hibernate (3.5.3) and another copy of Javasisst required by Hibernate, then by parent classloader delegation Hibernate will end up using the javassist ProxyFactory from Weld, registering its proxies deep down in the container, and thus causing a memory leak with each redeployment of the WAR. Weld should either keep its included version of javassist fully private or import all of javasisst via Import-Package, relying on javasisst installed in a separate bundle. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-554) org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml

by NIkola Nikolic (JIRA)

org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml --------------------------------------------------------------------------------------------- Key: WELD-554 URL: https://jira.jboss.org/browse/WELD-554 Project: Weld Issue Type: Bug Components: Conversations Environment: Microsoft Windows 7 Professional. Java 1.6.0_18-b07. Glassfish-3.0.1-b20. Reporter: NIkola Nikolic org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml. Let's say that page http://localhost:8080/test6/faces/index.xhtml?cid=1 can be rendered. If conversation time out and user tries to access page again, error page occures with following message: XML Parsing Error: no element found Location: http://localhost:8080/test6/faces/index.xhtml?cid=3 Line Number 1, Column 1: even if rule for exception exists in web.xml <error-page> <exception-type>org.jboss.weld.context.NonexistentConversationException</exception-type> <location>/faces/error.xhtml</location> </error-page> Same error occures if user change url manualy by changing cid number to non existing. -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-659) hello-world example - unexpected behavior

by Jozef Hartinger (JIRA)

hello-world example - unexpected behavior ----------------------------------------- Key: WELD-659 URL: https://jira.jboss.org/browse/WELD-659 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.1.0.Beta1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1.0.Beta2 According to documentation, the example should print "Hello ${name}" where name is an environment property passed to maven i.e. "mvn -Drun -Dname=Pete". However, the following profile configuration <configuration> <mainClass>org.jboss.weld.environment.se.StartMain</mainClass> <arguments> <argument>${project.name}</argument> </arguments> </configuration> results in "Hello Weld Examples: Hello World (Java SE)" to be printed every time independently on the name environment property. -- 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, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010