February 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-392) weld-se handles only one beans.xml.

by Koichi Kobayashi (JIRA)

weld-se handles only one beans.xml. ----------------------------------- Key: WELD-392 URL: https://jira.jboss.org/jira/browse/WELD-392 Project: Weld Issue Type: Bug Environment: weld-se-1.0.0-CR2 Reporter: Koichi Kobayashi Attachments: URLScanner.java.patch 1. make an interceptor and include it in Jar with beans.xml which defined it. <beans> <interceptors>...</interceptors> </beans> 2. other project has own beans.xml in META-INF directory, and add the Jar to CLASSPATH. <beans></beans> 3. weld-se handles only beans.xml in the direcotry, then Interceptor does not work. -- 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

14 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (WELDX-41) mvn install in extensions/trunk/se fails

by Martin Gencur (JIRA)

mvn install in extensions/trunk/se fails ---------------------------------------- Key: WELDX-41 URL: https://jira.jboss.org/jira/browse/WELDX-41 Project: Weld Extensions Issue Type: Bug Reporter: Martin Gencur Fix For: Spring integration 1.0.0.BETA1 When I check-out http://anonsvn.jboss.org/repos/weld/extensions/trunk/ and then run "mvn install" in /se subdirectory, maven outputs an error during compilation phase: (don't be confused with directory structure (Weld/weld-se/se... ) ....weld-se means trunk) [INFO] Compiling 14 source files to /home/mgencur/Java/Weld/weld-se/se/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[21,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[22,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[35,24] cannot find symbol symbol : class LogProvider location: class org.jboss.weld.environment.se.discovery.AbstractScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[32,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[33,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[46,24] cannot find symbol symbol : class LogProvider location: class org.jboss.weld.environment.se.discovery.URLScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[26,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[27,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[33,18] cannot find symbol symbol : class LogProvider location: class org.jboss.weld.environment.se.ShutdownManager /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[35,42] cannot find symbol symbol : variable Logging location: class org.jboss.weld.environment.se.discovery.AbstractScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[46,42] cannot find symbol symbol : variable Logging location: class org.jboss.weld.environment.se.discovery.URLScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[33,36] cannot find symbol symbol : variable Logging location: class org.jboss.weld.environment.se.ShutdownManager [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ -- 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

14 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (WELDX-50) Add new Weld() support for Java SE

by Pete Muir (JIRA)

Add new Weld() support for Java SE ---------------------------------- Key: WELDX-50 URL: https://jira.jboss.org/jira/browse/WELDX-50 Project: Weld Extensions Issue Type: Feature Request Reporter: Pete Muir Priority: Critical Fix For: Java SE 1.0.0.CR3 Add support for: Weld weld = new Weld().initialize(); weld.instance().select(Foo.class).get() weld.event().select(Bar.class).fire( new Bar() ); weld.shutdown(); -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDX-58) Modification to Weld Test to use SE Bootstrap

by Chris Pheby (JIRA)

Modification to Weld Test to use SE Bootstrap --------------------------------------------- Key: WELDX-58 URL: https://jira.jboss.org/jira/browse/WELDX-58 Project: Weld Extensions Issue Type: Patch Components: CDI Test, Java SE Affects Versions: Java SE 1.0.0.CR2, CDI Test 1.0.0.Beta1, CDI Test 1.0.0.Beta2 Environment: Windows Vista, Eclipse / Maven Reporter: Chris Pheby Fix For: CDI Test 1.0.0.Beta2 Thanks very much for Weld which is a great runtime evolved from the Seam framework, and thanks for Weld Test which brings JUnit testing in an elegant manner to the framework. My initial attempts to run Weld Test runtime were unsuccessful. Digging into the framework, I found it was very similar to the bootstrapping found in the SE runtime. Since the test framework runs out of container, it makes sense to reuse the SE runtime directly to benefit from the work going on there and reduce duplication. This patch is an effort to do that, and builds and executes the test using the SE runtime rather the Weld Test's own runtime. -- 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

14 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (WELDX-57) Use BeforeShutdown event

by Peter Royle (JIRA)

Use BeforeShutdown event ------------------------ Key: WELDX-57 URL: https://jira.jboss.org/jira/browse/WELDX-57 Project: Weld Extensions Issue Type: Task Components: Java SE Reporter: Peter Royle Assignee: Peter Royle Fix For: Java SE 1.0.0.CR3 Currently weld listens for the shutdown event when really it should probably be the one firing it. Also it's listening for @Shutdown BeanManager which is proprietary. There is now an appropriate event in the spec: BeforeShutdown. That should be used instead. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-76) Use the valditor's message in HelloWorld in SE Hello World Example

by Wolfgang Frech (JIRA)

Use the valditor's message in HelloWorld in SE Hello World Example ------------------------------------------------------------------ Key: WELDX-76 URL: https://jira.jboss.org/jira/browse/WELDX-76 Project: Weld Extensions Issue Type: Feature Request Components: Weld Extensions Environment: n/a Reporter: Wolfgang Frech It looks like an incomplete refactoring: The CommandLineArgsValidator creates an error message, but the HellWorld class does not read the message from the validator, but prints its own (identical) message. Use for (String message: argsValidator.getErrors()) System.out.println( message ); instead of System.out.println( "Please provide just one argument: your first name" ); in printHello by the way - cosmetic: use emptyList instead of deprecated EMPTY_LIST in CommandLineArgsValidator in SE Hello World Example -- 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

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (WELDX-47) BeanManager ELResolver should work even if JSF loads before Weld

by Dan Allen (JIRA)

BeanManager ELResolver should work even if JSF loads before Weld ---------------------------------------------------------------- Key: WELDX-47 URL: https://jira.jboss.org/jira/browse/WELDX-47 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR1 Reporter: Dan Allen Assignee: Dan Allen If the JSF listener starts before the Weld listener, then the BeanManager ELResolver was not making it into the JSF composite resolver chain. The problem is JSF impl specific, but we should safeguard against this problem anyway and use a forwarding ELResolver to accommodate. All details are provided in the linked issue WELDX-44, which is where the problem was discovered. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-42) mvn install in extensions/trunk/ fails

by Martin Gencur (JIRA)

mvn install in extensions/trunk/ fails -------------------------------------- Key: WELDX-42 URL: https://jira.jboss.org/jira/browse/WELDX-42 Project: Weld Extensions Issue Type: Bug Reporter: Martin Gencur When I check-out http://anonsvn.jboss.org/repos/weld/extensions/trunk/ and then run "mvn install" in the root directory, maven outputs an error during compilation phase: (weld-se in the paths below means trunk/ ) [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: org.jboss.weld.servlet:weld-servlet-int POM Location: /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for org.jboss.weld:weld-logging Reason: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1107) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:877) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:505) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more -- 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

14 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (WELD-281) add ForwardingELResolver to SPI

by Dan Allen (JIRA)

add ForwardingELResolver to SPI ------------------------------- Key: WELD-281 URL: https://jira.jboss.org/jira/browse/WELD-281 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Reporter: Dan Allen Assignee: Pete Muir Priority: Minor Fix For: 1.1.0.BETA1 Move ForwardingELResolver, which appears in both servlet-int and weld-int, to the SPI. -- 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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-401) Add getRemoteInterfaces() to EjbDescriptor

by Pete Muir (JIRA)

Add getRemoteInterfaces() to EjbDescriptor ------------------------------------------ Key: WELD-401 URL: https://jira.jboss.org/jira/browse/WELD-401 Project: Weld Issue Type: Feature Request Components: Weld SPI Reporter: Pete Muir Fix For: 1.1.0.BETA1 Needed to determine if a producer, disposer or observer method is part of the container view -- 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

14 years, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2010