June 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-906) Jetty 7.2+ container incorrectly identified as Jetty 7 container

by Ben Sommerville (JIRA)

Jetty 7.2+ container incorrectly identified as Jetty 7 container ---------------------------------------------------------------- Key: WELD-906 URL: https://issues.jboss.org/browse/WELD-906 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.1.Final Reporter: Ben Sommerville Priority: Minor Weld-servlet can identify a jetty 7.3 or 7.4 environment as a Jetty 7.0 environment (similar problem to WELD-879 but for Jetty not tomcat) In Listener.java it checks for a Jetty 7 container before checking for a Jetty 7.2+ container. The version 7 check looks for the presence of org.eclipse.jetty.servlet.ServletHandler which is present (but not necessarily visible) in all jetty 7.x environments. By default this class won't be found in Jetty 7.2+, but in this case Weld won't actually work. To run Weld under Jetty 7.2+ you need to expose some of the server classes that are normally hidden, and if you don't explicitly exclude the ServletHandler class the environment is detected as Jetty 7 not 7.2+ The suggested fix would be to reverse the order in which containers are checked and check for JettyPost72Container before checking for JettyContainer You can work around this issue by using META-INF/services to specify container or setting the ServletHandler class as a server class so that the web app can't see it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-657) Align instructions for running examples with Jetty

by Jozef Hartinger (JIRA)

Align instructions for running examples with Jetty -------------------------------------------------- Key: WELD-657 URL: https://jira.jboss.org/browse/WELD-657 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.0.Beta1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1.0.Beta2 The examples/jsf/numberguess/readme.txt file describes how to run the example on Jetty using Eclipse. The reference documentation provides instructions for running the example on Jetty both from command line and Eclipse. These two information sources should be merged to provide the same instructions (or reference the other source). -- 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
4
0 / 0

[JBoss JIRA] Created: (WELDX-88) StartMain should support shutdown

by Edvin Syse (JIRA)

StartMain should support shutdown --------------------------------- Key: WELDX-88 URL: https://jira.jboss.org/jira/browse/WELDX-88 Project: Weld Extensions Issue Type: Feature Request Components: Weld Extensions Affects Versions: Java SE 1.0.1 Environment: n/a Reporter: Edvin Syse Priority: Minor When starting a project with org.jboss.weld.environment.se.StartMain, one would assume that weld.shutdown() would be run upon jvm shutdown, but it is not. This could easily be fixed with a minor adjustment. Please see the attached StartMain.java. -- 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
8
0 / 0

[JBoss JIRA] Created: (WELD-407) Provide warnings if AnnotatedType is not sensible

by Pete Muir (JIRA)

Provide warnings if AnnotatedType is not sensible ------------------------------------------------- Key: WELD-407 URL: https://jira.jboss.org/jira/browse/WELD-407 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 For example, if there are no constructors specified at all, or if the javaMember doesn't belong to the actual class hierarchy of the annotatedType -- 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
7
0 / 0

[JBoss JIRA] Created: (WELD-388) Fluent messages

by Nicklas Karlsson (JIRA)

Fluent messages --------------- Key: WELD-388 URL: https://jira.jboss.org/jira/browse/WELD-388 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Priority: Minor Make error messages read more fluent instead of the "Message : detail" format sometimes seen -- 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
8
0 / 0

[JBoss JIRA] Created: (WELD-919) Conversation propagation token that negates the "cid" parameter

by Nicklas Karlsson (JIRA)

Conversation propagation token that negates the "cid" parameter --------------------------------------------------------------- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey("nocid") ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-539) Upgrade Weld examples to use shared Jetty/Tomcat plugins

by Pete Muir (JIRA)

Upgrade Weld examples to use shared Jetty/Tomcat plugins -------------------------------------------------------- Key: WELD-539 URL: https://jira.jboss.org/browse/WELD-539 Project: Weld Issue Type: Task Components: Examples Reporter: Pete Muir Fix For: 1.0.2.CR1 -- 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: (WELD-524) org.jboss.weld.environment.se.discovery.URLScanner does not work with resources inside OSGI bundles

by Morten Christensen (JIRA)

org.jboss.weld.environment.se.discovery.URLScanner does not work with resources inside OSGI bundles ---------------------------------------------------------------------------------------------------- Key: WELD-524 URL: https://jira.jboss.org/jira/browse/WELD-524 Project: Weld Issue Type: Bug Environment: JavaSE 6 + Weld SE Reporter: Morten Christensen Priority: Blocker The class org.jboss.weld.environment.se.discovery.URLScanner does no work with resources inside OSGI bundles. So if one try to start WeldSe inside an OSGI bundle and get around the classloader bug in WeldSE by tempoarily setting the ContextClassLoader you will get an NullPointerException. The problem is OSGI resource url related. For a OSGI bundle you will f.x. get "bundleresource://4.fwk1362875764:1/META-INF/beans.xml" from bundleClassLoader.getResources("META-INF/beans.xml" but this is not a valid filename as URLScanner assumes so one will get this exception: java.lang.NullPointerException at org.jboss.weld.environment.se.discovery.URLScanner.handleDirectory(URLScanner.java:177) at org.jboss.weld.environment.se.discovery.URLScanner.handleDirectory(URLScanner.java:183) at org.jboss.weld.environment.se.discovery.URLScanner.handleDirectory(URLScanner.java:160) at org.jboss.weld.environment.se.discovery.URLScanner.handle(URLScanner.java:122) at org.jboss.weld.environment.se.discovery.URLScanner.scanResources(URLScanner.java:107) at org.jboss.weld.environment.se.discovery.SEWeldDiscovery.scan(SEWeldDiscovery.java:71) at org.jboss.weld.environment.se.discovery.SEWeldDiscovery.<init>(SEWeldDiscovery.java:45) -- 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
6
0 / 0

[JBoss JIRA] Created: (WELD-520) Weld does not work in OSGI container's classloader (and lacks OSGI bundles by the way)

by Morten Christensen (JIRA)

Weld does not work in OSGI container's classloader (and lacks OSGI bundles by the way) -------------------------------------------------------------------------------------- Key: WELD-520 URL: https://jira.jboss.org/jira/browse/WELD-520 Project: Weld Issue Type: Bug Components: OSGi support Affects Versions: 1.0.1.Final Environment: Java SE, Weld 1.01 SE, Felix 2.02 Reporter: Morten Christensen Priority: Critical Weld SE will does not work inside an OSGI bundle. If you try to start WeldSE from within a OSGI bundle, you will get. Error loading Weld bootstrap, check that Weld is on the classpath at org.jboss.weld.environment.se.Weld.<init>(Weld.java:59) Looking at the cause, it seems org.jboss.weld.environment.se.util.Reflections only works with Thread context classloaders and plain Class.forname both of which are NO-NO in osgi. -- 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
9
0 / 0

[JBoss JIRA] Created: (WELD-376) Callouts poorly formatted in HTML docs

by Pete Muir (JIRA)

Callouts poorly formatted in HTML docs -------------------------------------- Key: WELD-376 URL: https://jira.jboss.org/jira/browse/WELD-376 Project: Weld Issue Type: Task Components: Documentation Affects Versions: 1.0.0.GA Reporter: Jozef Hartinger Fix For: 1.0.1.CR1 Global problems - a significant number of links is missing the value of href attribute (these links point nowhere) - JBoss AS 5.2.x have become obsolete recently (changed to 6.0.0.M1) - the documentation references this obsolete version. i.e. Chapters 6, section 18.1 - there is a number of unnecessary blank pages in the PDF version - Section 2.1.2. Scope - there is a missing *want* in the Note in the sentence: "If you don't the bean to live in the session indefinitely..." - Section 6.2 Deploying to JBoss AS - there is a missing space in the sentence "Create a new file namedlocal.build.properties ..." - Section 6.2 Deploying to JBoss AS - is not finished - there is a TODO at the very end of the section - Secion 7.1. The numberguess example in depth - the numbers which mark an important line of a code sample (1), (2), etc... are broken in the second sample of the section (web.xml). They are placed on wrong places (wrong line, beggining of the line instead of end) and they are followed by "ml_plain">" in the HTML version. Besides, I would emphasize more the benefit of the typesafe resolution i.e. in section 1.2 - (that all the unsatisfied and ambiguous dependencies are discovered at the deployment time - you do not need to click anything to find out that the you set some dependencies wrong - more formal verification) - I don't say it is not there already. I just had a feeling that it is not stated explicitly enough. -- 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
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2011