December 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-693) Add a way to get the active context easily

by Pete Muir (JIRA)

Add a way to get the active context easily ------------------------------------------ Key: WELD-693 URL: https://jira.jboss.org/browse/WELD-693 Project: Weld Issue Type: Feature Request Components: Scopes & Contexts Reporter: Pete Muir Fix For: 1.1.0.Beta2 For example @Inject @Active ConversationContext ctx; which would inject null if there was no active context -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-815) Add some design time readable metadata to weld-*.jars for tooling

by Max Andersen (JIRA)

Add some design time readable metadata to weld-*.jars for tooling ----------------------------------------------------------------- Key: WELD-815 URL: https://issues.jboss.org/browse/WELD-815 Project: Weld Issue Type: Feature Request Components: Tooling Reporter: Max Andersen Working on JBIDE-8017 it became obvious that it would be good if Weld (and other spec implementations) jars could say which services they implement (and optionally how) so tooling could validate and navigate based on the classpath. Opening this issue to not forget - suggested approach was to see if one could use the seam-beans.xml format (but under a different name, i.e. design-time-beans.xml) to help guide tooling. This is to include not only spec required services but also additonal ones as for example http://docs.jboss.org/weld/reference/1.1.0.CR1/en-US/html/contexts.html#d... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
9
0 / 0

[JBoss JIRA] Created: (WELD-398) Unable to run translator example with settings for cluster

by Martin Gencur (JIRA)

Unable to run translator example with settings for cluster ---------------------------------------------------------- Key: WELD-398 URL: https://jira.jboss.org/jira/browse/WELD-398 Project: Weld Issue Type: Bug Reporter: Martin Gencur When I try to go to http://localhost:8080/weld-translator after deploying the translator example to JBossAS 6.0.0.M1, exceptions are thrown both at server.log and web browser. The exception are attached as separated files. Steps to reproduce: 1) add <distributable/> tag to web.xml as it's first tag (at WELD/examples/jsf/translator/war/src/main/webapp/WEB-INF/web.xml) 2) add this content to jboss.xml file at WELD/examples/jsf/translator/ejb/src/main/resources/META-INF/jboss.xml : <?xml version="1.0" encoding="UTF-8"?> <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee jboss_5_0.xsd" version="5.0"> <enterprise-beans> <session>  <ejb-name>SentenceTranslator</ejb-name> <clustered>true</clustered> </session> <session>  <ejb-name>TranslatorControllerBean</ejb-name> <clustered>true</clustered> </session> </enterprise-beans> </jboss> 3) download jboss-6.0.0.M1 (for example from http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0....) 4) unzip it twice to different folders 5) now you have to update both the JBoss AS instances with current version of WELD core (from WELD/core) 6) run the first instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default 7) run the second instance from its bin directory: ./run.sh -c all -g DocsPartition -u 239.255.101.101 -b localhost -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01 8) clean and build the application: run mvn clean package in examples/jsf/translator 9) copy resulting ear file (weld-numberguess.war) from translator/ear/target/ directory to serve/all/farm directory at first jbossAS instance 10) go to http://localhost:8080/weld-translator 11) now you can see both exception in server.log and web browser -- 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
21
0 / 0

[JBoss JIRA] Created: (WELD-734) Support @EJB injection in pre-Java EE 6 environments

by Dan Allen (JIRA)

Support @EJB injection in pre-Java EE 6 environments ---------------------------------------------------- Key: WELD-734 URL: https://jira.jboss.org/browse/WELD-734 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Dan Allen Priority: Minor Add support for the injection of EJBs into CDI beans (via the @EJB annotation) in Weld Servlet for use in pre-Java EE 6 environments. This feature would enable more developers to immeidately switch to CDI despite having to use an older platform. The best strategy to take to implement this feature would be to leverage Weld's EjbServices SPI interface (http://docs.jboss.org/weld/reference/latest/en-US/html/ri-spi.html) on a per container basis (in the same way Weld is integrated into the Java EE 6 containers). Currently, the Weld Listener doesn't provide any hooks to register services before it starts the container. We could redesign the Listener to support providing the EjbServices implementation (and perhaps other service implementations) in a listener subclass. It's unlikely we can fully implement EJB integration in pre EE6 environments as (at least in JBoss AS and GlassFish) as some of the hooks (specifically the hooks to remove EJBs on demand) are missing. However, basic injection would cover ~80% of the cases. -- 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
2
0 / 0

[JBoss JIRA] Created: (WELD-902) CLONE - The qualified observer section is incorrect

by Christian Bauer (JIRA)

CLONE - The qualified observer section is incorrect --------------------------------------------------- Key: WELD-902 URL: https://issues.jboss.org/browse/WELD-902 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.0.GA Reporter: Christian Bauer Assignee: Jason Porter Fix For: 1.1.0.CR1 The documentation at http://docs.jboss.org/weld/reference/1.0.0/en-US/html/events.html#d0e3980 is incorrect for the way qualified observers work. The related spec section is 10.2. The docs say all possible observers with any of the qualifiers will be called, which is incorrect. The full signature including all qualifiers must match for the observer to be invoked. -- 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-621) Write tutorial for pastecode for refguide

by Pete Muir (JIRA)

Write tutorial for pastecode for refguide ----------------------------------------- Key: WELD-621 URL: https://jira.jboss.org/browse/WELD-621 Project: Weld Issue Type: Task Components: Examples Reporter: Pete Muir Assignee: Dan Allen -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-622) Write tutorial for permalink for refguide

by Pete Muir (JIRA)

Write tutorial for permalink for refguide ----------------------------------------- Key: WELD-622 URL: https://jira.jboss.org/browse/WELD-622 Project: Weld Issue Type: Task Components: Documentation, Examples Reporter: Pete Muir Assignee: Dan Allen -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-843) Documentation on how to implement a new scope

by José Freitas (JIRA)

Documentation on how to implement a new scope --------------------------------------------- Key: WELD-843 URL: https://issues.jboss.org/browse/WELD-843 Project: Weld Issue Type: Feature Request Components: Documentation Affects Versions: 1.1.0.Final Reporter: José Freitas Priority: Minor Sometimes people need to implement their own scope and there are no specific documentation about it. There's just a teaser saying that "Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam." I think that the weld docs should show what it takes to accomplish such a task. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-923) Error in beans other than BeanManager are injected into a portable extension

by Pete Muir (JIRA)

Error in beans other than BeanManager are injected into a portable extension ---------------------------------------------------------------------------- Key: WELD-923 URL: https://issues.jboss.org/browse/WELD-923 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] (WELD-1028) CLONE - URLScanner can not handle paths containing spaces

by Manuel Hartl (Created) (JIRA)

CLONE - URLScanner can not handle paths containing spaces --------------------------------------------------------- Key: WELD-1028 URL: https://issues.jboss.org/browse/WELD-1028 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.0.Final Environment: Windows, Jetty 7.2.2 Reporter: Manuel Hartl Assignee: Ales Justin Fix For: 1.1.2.Final When actual classpath includes folder that contains spaces, URLScanner throws an exception (java.io.FileNotFoundException). Problem is at line 93 where string holding URL is "converted" to path just by stripping URL scheme prefix. Unfortunately, spaces in URL are expressed either by plus sing or %20 escape sequence, which remains in file path instead of proper URL decoding. For example "file:/C:/with%20space" is converted to "/C:/with%20space" instead of "C:/with space". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2011