December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-750) German translation of Weld Reference Documentation

by Thorsten Spaeth (JIRA)

German translation of Weld Reference Documentation -------------------------------------------------- Key: WELD-750 URL: https://jira.jboss.org/browse/WELD-750 Project: Weld Issue Type: Task Components: Documentation Reporter: Thorsten Spaeth Priority: Trivial Fix For: TBC I am currently starting to translate the Weld Reference Documentation to German (de-DE). I'd like to contribute that bit by bit to the repository. -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Closed: (WELD-17) Brazilian Portuguese translation of Web Beans Reference Documentation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/WELD-17?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed WELD-17. ------------------------- Assignee: Pete Muir Fix Version/s: (was: TBC) Resolution: Out of Date Translations should now be contributed via translate.jboss.org, updated instructions at http://www.seamframework.org/Weld/TranslatingWeldIntoYourOwnLanguage > Brazilian Portuguese translation of Web Beans Reference Documentation > --------------------------------------------------------------------- > > Key: WELD-17 > URL: https://issues.jboss.org/browse/WELD-17 > Project: Weld > Issue Type: Task > Components: Documentation > Reporter: Joao Viragine > Assignee: Pete Muir > > I would like to translate Web Beans Reference Documentation to Brazilian Portuguese. (pt-BR) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (WELD-791) Publican-compatible documentation

by Laura Bailey (JIRA)

Publican-compatible documentation --------------------------------- Key: WELD-791 URL: https://issues.jboss.org/browse/WELD-791 Project: Weld Issue Type: Feature Request Components: Documentation Reporter: Laura Bailey Make Weld documentation buildable in Maven for the community project and in Publican for the enterprise product. Pull request https://github.com/weld/core/pull/82 submitted for the following changes: * moved publican.cfg file from reference to reference/src/main/docbook alongside the lang directories * uncommented brand: JBoss from publican.cfg file * removed lang="en" from the <book> * renamed master.xml to Weld_-_JSR-299_Reference_Implementation.xml * modified the reference/pom.xml to use the Weld_-_JSR-299_Reference_Implementation.xml file instead of the master.xml file as a base by adding <sourceDocumentName> element to maven-jdocbook-plugin configuration. * added the Weld_-_JSR-299_Reference_Implementation.ent file for Publican * altered the part ids in Weld_-_JSR-299_Reference_Implementation.xml to part-# instead of just #, since Publican does not allow ids to start with a digit. * moved the <para> that was outside the last <section> in weldexamples.xml, inside the section, since publican does not allow trailing paragraphs. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (WELD-792) Change Chinese locale mappings for Flies integration

by Sean Flanigan (JIRA)

Change Chinese locale mappings for Flies integration ---------------------------------------------------- Key: WELD-792 URL: https://issues.jboss.org/browse/WELD-792 Project: Weld Issue Type: Thirdparty Change Components: Documentation Affects Versions: 1.1.0.Beta2 Reporter: Sean Flanigan The Chinese locale codes on translate.jboss.org (zh-CN-Hans and zh-TW-Hant) were basically wrong, due to a bug in Flies 1.0. Scripts like Han Simplified and Han Traditional should actually come before country codes, so zh-Hans-CN and zh-Hant-TW would be better. On translate.jboss.org, these codes have now been replaced by zh-Hans and zh-Hant, which is better still because each of these scripts is used in more than one country. I have already imported the affected translations again, but the locale mappings in flies.xml will need to be updated for future pushes. The github pull request is forthcoming... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (WELD-790) Validation of InjectionTargets prevents firing of ProcessInjectionTarget<X> for non-contextual EE components

by Sivakumar Thyagarajan (JIRA)

Validation of InjectionTargets prevents firing of ProcessInjectionTarget<X> for non-contextual EE components ------------------------------------------------------------------------------------------------------------ Key: WELD-790 URL: https://issues.jboss.org/browse/WELD-790 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.1.0.CR1 Reporter: Sivakumar Thyagarajan Fix For: 1.1.0.Final The eager validation of InjectionTargets introduced via [1] to fix WELD-761 results in an issue when a container tries to fire ProcessInjectionTarget<T> events for injection into non-contextual Java EE components. When the container fires ProcessInjectionTarget events before Beans are deployed via bootstrap.deployBeans, the BDA processing is not complete and hence resolution fails during validation as shown below. The container also needs to fire these events before AfterBeanDiscovery as pointed at [2] and hence this eager validation is an issue. -- Error with a local integration of GF3.1 trunk and WELD 1.1.0.CR1 ---- [#|2010-12-14T14:31:10.044+0530|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=109;_ThreadName=admin-thread-pool-4848(1);|Exception while loading the app : WELD-001408 Unsatisfied dependencies for type [TestBean] with qualifiers [@Default] at injection point [[field] @Inject TestServlet.tb] org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [TestBean] with qualifiers [@Default] at injection point [[field] @Inject TestServlet.tb] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305) at org.jboss.weld.manager.SimpleInjectionTarget.<init>(SimpleInjectionTarget.java:107) at org.jboss.weld.manager.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1032) at org.jboss.weld.manager.BeanManagerImpl.fireProcessInjectionTarget(BeanManagerImpl.java:1220) at org.glassfish.weld.WeldDeployer.fireProcessInjectionTargetEvents(WeldDeployer.java:237) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:161) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:266) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:459) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:369) -- Error with a local integration of GF3.1 trunk and WELD 1.1.0.CR1 ---- [1] https://github.com/weld/core/commit/eb0f2020ee8e79ff04fe8d929837b0bedf80b19b [2] http://java.net/jira/browse/GLASSFISH-11135?focusedCommentId=130738&page=... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-199) ProcessObserverMethod Type parameters and CDITCK-174

by Gurkan Erdogdu (JIRA)

ProcessObserverMethod Type parameters and CDITCK-174 ---------------------------------------------------- Key: CDITCK-199 URL: https://issues.jboss.org/browse/CDITCK-199 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Gurkan Erdogdu Hi; Recently TCK 1.0.2 SP1 contains some tests that must be excluded. Those tests are located in org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest testGetAnnotatedMethod(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testProcessObserverMethodEventsSent(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) testGetObserverMethod(org.jboss.jsr299.tck.tests.extensions.observer.ProcessObserverMethodEventTest) Those tests uses uses wrong type arguments according to the JavaDoc (public interface ProcessObserverMethod<T,X>). For example, http://fisheye.jboss.org/browse/weld/cdi-tck/trunk/impl/src/main/java/org... contains public void observeObserverMethodForEventB(@Observes ProcessObserverMethod<?, EventB> event) {} It must be public void observeObserverMethodForEventB(@Observes ProcessObserverMethod<EventB, ?> event) {} Because JavaDoc is higher importancy than spec, those test must be excluded or changed. Also this issue was disccussed on mailing list, http://markmail.org/message/g6c4zsuuzckeai26 Please exclude those tests from TCK 1.0.2 SP1. Otherwise OWB failes to pass TCK. Thanks; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-191) double slash in Converstaion test urls break redirect

by David Jencks (JIRA)

double slash in Converstaion test urls break redirect ----------------------------------------------------- Key: CDITCK-191 URL: https://jira.jboss.org/browse/CDITCK-191 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: David Jencks The Conversation tests all call AbstractConversationTest.getPath() with strings starting with / such as /storm.jspx. Since the method tacks a / at the end of the context root you end up with urls for the form foo//bar.jsf. While tomcat appears to think that this is the same url as foo/bar.jsf, jetty doesn't. This breaks the redirect in LongRunningConversationPropagatedByFacesContextTest.testConversationPropagatedOverRedirect. Removing the / from the arguments to getPath fixes the problem. -- 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

14 years

2
13
0 / 0

[JBoss JIRA] Created: (WELD-779) Integrate Reference Guide with Flies translation server

by Sean Flanigan (JIRA)

Integrate Reference Guide with Flies translation server ------------------------------------------------------- Key: WELD-779 URL: https://jira.jboss.org/browse/WELD-779 Project: Weld Issue Type: Task Reporter: Sean Flanigan Tracking issue for Flies integration -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
9
0 / 0

[JBoss JIRA] Created: (CDITCK-186) TCK does not properly test for inhertance of observer methods

by Igor Vaynberg (JIRA)

TCK does not properly test for inhertance of observer methods ------------------------------------------------------------- Key: CDITCK-186 URL: https://jira.jboss.org/browse/CDITCK-186 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Igor Vaynberg EventTest has a bug in it. According to section 4.2 of the spec {code} If X declares an initializer, non-static observer, @PostConstruct or @PreDestroy method x() then Y inherits x() if and only if neither Y nor any intermediate class that is a subclass of X and a superclass of Y overrides the method x(). {code} both IntermediateStockWatcher and IndirectStockWatcher which extend StockWatcher should inherit its observer method: {code} StockWatcher#public void observeStockPrice(@Observes StockPrice price) {code} However, EventTest on line 149 asserts there is only one observer method, when in fact there should be three: {code} 147: StockPrice price = new StockPrice(); 148: Set<ObserverMethod<? super StockPrice>> observers = getCurrentManager().resolveObserverMethods(price); 149: assert observers.size() == 1; {code} -- 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

14 years

4
10
0 / 0

[JBoss JIRA] Created: (WELD-762) ThreadLocal leak with Weld Servlet

by Aslak Knutsen (JIRA)

ThreadLocal leak with Weld Servlet ---------------------------------- Key: WELD-762 URL: https://jira.jboss.org/browse/WELD-762 Project: Weld Issue Type: Bug Components: Servlet Container Support Reporter: Aslak Knutsen Nov 22, 2010 7:13:40 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web application [/active1] created a ThreadLocal with key of type [null] (value [org.jboss.weld.injection.CurrentInjectionPoint$1@30b95f2]) and a value of type [java.util.Stack] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak. Weld Servlet 1.1.0-SNAPSHOT / Beta2 / Beta1 on Tomcat 6 Not sure if this is Weld Servlet or Weld Core. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010