June 2011 - weld-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (WELD-914) WARN if beans.xml is missing in standalone mode.

by Ondrej Zizka (JIRA)

WARN if beans.xml is missing in standalone mode. ------------------------------------------------ Key: WELD-914 URL: https://issues.jboss.org/browse/WELD-914 Project: Weld Issue Type: Enhancement Reporter: Ondrej Zizka STR: 1) Get the attached project, or, svn co http://ondrazizka.googlecode.com/svn/trunk/CdiTry -r 219 2) Remove beans.xml (if present) 3) Run You'll get an exception {code} 33 [main] INFO org.jboss.weld.Version - WELD-000900 1.1.1 (Final) 54 [main] INFO org.jboss.weld.Bootstrap - WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously. 273 [main] WARN org.jboss.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled 273 [main] WARN org.jboss.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled Exception in thread "main" org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [class org.jboss.myapp.MyApp]; Bindings: [@javax.enterprise.inject.Default()] at org.jboss.weld.manager.BeanManagerImpl.getBean(BeanManagerImpl.java:809) at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:108) at org.jboss.jawabot.JawaBotAppWeld.main(JawaBotAppWeld.java:17) {code} There should be a WARN if beans.xml is not found in standalone mode to make it easier to figure it out. (I was tending to believe that there's something much more complex going on.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-869) Weld OSGi bundle reports version as ${parsedVersion.osgiVersion}

by Dan Allen (JIRA)

Weld OSGi bundle reports version as ${parsedVersion.osgiVersion} ---------------------------------------------------------------- Key: WELD-869 URL: https://issues.jboss.org/browse/WELD-869 Project: Weld Issue Type: Bug Components: OSGi support Affects Versions: 1.1.0.Final Reporter: Dan Allen Priority: Minor When Weld starts on GlassFish, it reports it's version as: WELD-000900 ${parsedVersion (osgiVersion}) The version is read from the MANIFEST.MF, which has this line: Specification-Version: ${parsedVersion.osgiVersion} The replacement doesn't seem to be working properly in the osgi build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (WELDX-51) Create a single jar file for Weld SE that includes all dependencies

by Pete Muir (JIRA)

Create a single jar file for Weld SE that includes all dependencies ------------------------------------------------------------------- Key: WELDX-51 URL: https://jira.jboss.org/jira/browse/WELDX-51 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Pete Muir Fix For: Java SE 1.0.0.CR3 To make using Weld SE easy, we should create a single jar (primarily for use at runtime, at compile time you would depend just on cdi-api of course) * cdi-api * weld-api * weld-spi * weld-core * weld-se -- 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

5
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2011