May 2011 - weld-issues - Jboss List Archives

[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

12 years, 9 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

12 years, 9 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

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (WELDX-34) Split out user API for SE module, and move to the api project/BOM

by Pete Muir (JIRA)

Split out user API for SE module, and move to the api project/BOM ----------------------------------------------------------------- Key: WELDX-34 URL: https://jira.jboss.org/jira/browse/WELDX-34 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Pete Muir We maintain a separate API project (SVN trunk etc.), BOM etc. Any developer-visible API for the SE extension (so perhaps any non-spec events you can observe?) should go here -- 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

12 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-669) Ensure we build with Java 5

by Pete Muir (JIRA)

Ensure we build with Java 5 --------------------------- Key: WELD-669 URL: https://jira.jboss.org/browse/WELD-669 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Pete Muir Assignee: Pete Muir Priority: Critical Fix For: 1.1.0.Beta2 It looks like the Hudson builds got switched to Java 6 at some point... As a result of this, some Java 6 deps have crept in, the first of which is javax.inject api. -- 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

12 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-835) Make sure all examples have instructions for importing and deploying via JBoss Tools.

by Pete Muir (JIRA)

Make sure all examples have instructions for importing and deploying via JBoss Tools. ------------------------------------------------------------------------------------- Key: WELD-835 URL: https://issues.jboss.org/browse/WELD-835 Project: Weld Issue Type: Task Reporter: Pete Muir Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
17
0 / 0

[JBoss JIRA] Created: (WELD-629) Full review of sub-module licenses for Weld and Examples

by Pete Muir (JIRA)

Full review of sub-module licenses for Weld and Examples -------------------------------------------------------- Key: WELD-629 URL: https://jira.jboss.org/browse/WELD-629 Project: Weld Issue Type: Task Reporter: Pete Muir Assignee: Pete Muir Priority: Critical Fix For: 1.1.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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-824) injection/initializer/observer inheritance broken on Beans registered through BBD.addAnnotatedType()

by Jozef Hartinger (JIRA)

injection/initializer/observer inheritance broken on Beans registered through BBD.addAnnotatedType() ---------------------------------------------------------------------------------------------------- Key: WELD-824 URL: https://issues.jboss.org/browse/WELD-824 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Affects Versions: 1.1.0.CR4 Reporter: Jozef Hartinger I am having two classes: Foo and Bar where Bar extends Foo. Both these classes are outside of BDA (a jar with no beans.xml placed in WEB-INF/lib of a web app that has beans.xml) The Bar class is registered through a portable Extension (BeforeBeanDiscovery.addAnnotatedType()). The problem is that while injection/initializers/event observers defined on the Bar class work as expected, the ones defined on the Foo class are never called. (Note that the Foo class itself is not registered as a Bean - Nevertheless, CDI services should be enabled on Bar's superclasses according to the spec) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-901) config change: handle translate.jboss.org upgrade to Zanata 1.3

by Sean Flanigan (JIRA)

config change: handle translate.jboss.org upgrade to Zanata 1.3 --------------------------------------------------------------- Key: WELD-901 URL: https://issues.jboss.org/browse/WELD-901 Project: Weld Issue Type: Task Components: Documentation Reporter: Sean Flanigan Assignee: Sean Flanigan We're finalising the rename from Flies to Zanata in 1.3, which we plan to deploy on https://translate.jboss.org/ this week (probably Thursday). Unfortunately, there a few small changes needed to your config files. Sorry! When we deploy Zanata on translate.jboss.org, the Maven Flies client will stop working, so you will need to make these changes then: Steps to take: 1. Rename ~/.config/flies.ini to ~/.config/zanata.ini (or create a symlink...) NB: If your flies.ini has an entry for https://translate.jboss.org/flies/, please change it to https://translate.jboss.org/ 2. For each of your projects on translate.jboss.org, rename flies.xml to zanata.xml, and change xmlns to http://zanata.org/namespace/config/, ie <config xmlns="http://zanata.org/namespace/config/"> Please check that you are using the URL https://translate.jboss.org/ not the old URL https://translate.jboss.org/flies/. 3. If you use the Maven client, edit your pom.xml and any helper scripts: plugin group: org.zanata plugin artifact: zanata-maven-plugin version: 1.3 eg <plugin> <groupId>org.zanata</groupId> <artifactId>zanata-maven-plugin</artifactId> <version>1.3</version> </plugin> Any scripts will need to use the zanata: prefix instead of flies:. Also, properties such as flies.srcDir have been renamed to zanata.srcDir. For instance mvn flies:publican-push -Dflies.srcDir=. should become mvn zanata:publican-push -Dzanata.srcDir=. I have already made the required Weld changes, so I will be submitting a pull request on github. But it would probably be best not to merge it in until translate.jboss.org has been upgraded to Zanata, because the Zanata client won't work with the old Flies server. Also if you have a Hudson job which executes the flies_* scripts, it will need to use zanata_* instead. (Or I can rename them back to flies_* if you prefer.) Again, I do apologise for the inconvenience, and let me know if I can help with anything. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-780) Place beans.xml under WEB-INF instead of WEB-INF/classes/META-INF in jsf/permalink example

by Sivakumar Thyagarajan (JIRA)

Place beans.xml under WEB-INF instead of WEB-INF/classes/META-INF in jsf/permalink example ------------------------------------------------------------------------------------------ Key: WELD-780 URL: https://jira.jboss.org/browse/WELD-780 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.1.0.Beta2 Reporter: Sivakumar Thyagarajan Priority: Minor As per Section 12.1 of CDI 1.0 specification: > • The WEB-INF/classes directory of a war is a bean archive if there is a file named beans.xml in the WEB-INF directory of the war. > • A directory in the JVM classpath is a bean archive if it has a file named beans.xml in the META-INF directory. However the jsf/permalink sample bundles beans.xml under WEB-INF/classes/META-INF. This may not work in other containers (for instance see http://java.net/jira/browse/GLASSFISH-15009 ). So request to move the file (in weld-core): from examples/jsf/permalink/src/main/resources/META-INF/beans.xml to examples/jsf/permalink/src/main/webapp/WEB-INF/beans.xml -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues May 2011