September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12365: -------------------------------------- Summary: Enable JBoss Tools Knowledge Base support for dependencies Key: JBIDE-12365 URL: https://issues.jboss.org/browse/JBIDE-12365 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Reporter: Alexey Kazakov Assignee: Fred Bricon Suppose we have two maven projects. One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). The other is a plain java project. The first one includes the second one as a dependency. When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) So CDI/Seam/JSF (KB included) should be enabled for the first project. And KB should be enabled for the second one. -- 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

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-12021) intermittent test timeout after 1800 seconds in org.jboss.tools.cdi.core.test

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12021: ---------------------------------- Summary: intermittent test timeout after 1800 seconds in org.jboss.tools.cdi.core.test Key: JBIDE-12021 URL: https://issues.jboss.org/browse/JBIDE-12021 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt Build OK, but tests timeout: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.14.1:test (default-test) on project org.jboss.tools.cdi.core.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 1800 seconds -> [Help 1] {code} https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_5.0.indi... However, two builds earlier, we had all the tests pass: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_5.0.indi... -- 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

13 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8481) HTML 5 support in the source editor and validators

by Yahor Radtsevich (JIRA)

HTML 5 support in the source editor and validators -------------------------------------------------- Key: JBIDE-8481 URL: https://issues.jboss.org/browse/JBIDE-8481 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Environment: Add HTML 5 support to the source editor and validators Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Fix For: 3.3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
11
0 / 0

[JBoss JIRA] (JBIDE-10615) Setting "Dynamic Web Project with Seam 2.2" configuration in Project Facets fails

by Tomas Remes (Created) (JIRA)

Setting "Dynamic Web Project with Seam 2.2" configuration in Project Facets fails --------------------------------------------------------------------------------- Key: JBIDE-10615 URL: https://issues.jboss.org/browse/JBIDE-10615 Project: Tools (JBoss Tools) Issue Type: Bug Environment: JBDS 4.1.0.GA Reporter: Tomas Remes -- 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

13 years, 4 months

4
23
0 / 0

[JBoss JIRA] Created: (JBIDE-7958) TestNG tests fail in Seam project

by Jozef Hartinger (JIRA)

TestNG tests fail in Seam project --------------------------------- Key: JBIDE-7958 URL: https://issues.jboss.org/browse/JBIDE-7958 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta2 Reporter: Jozef Hartinger Assignee: Alexey Kazakov Steps to reproduce: 1.) Create new seam web project (EAR) 2.) Create new seam action (using new action wizard) 3.) Run the generated test (i.e. HelloTest.java) as a TestNG test. 4.) Add the following VM argument to the test run configuration -Dsun.lang.ClassLoader.allowArraySyntax=true 5.) Run the test again The test fails with the following stacktrace: FAILED: test_hello java.lang.AssertionError: java.lang.UnsupportedOperationException at org.jboss.seam.mock.AbstractSeamTest$Request.onException(AbstractSeamTest.java:463) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:512) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:499) at org.domain.jbtoolsear.test.HelloTest.test_hello(HelloTest.java:26) 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) at org.testng.internal.Invoker.invokeMethod(Invoker.java:673) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1168) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at org.testng.TestRunner.runWorkers(TestRunner.java:1125) at org.testng.TestRunner.privateRun(TestRunner.java:749) at org.testng.TestRunner.run(TestRunner.java:600) at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274) at org.testng.SuiteRunner.run(SuiteRunner.java:223) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:954) at org.testng.TestNG.runSuitesLocally(TestNG.java:883) at org.testng.TestNG.run(TestNG.java:817) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:110) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:205) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174) Caused by: java.lang.UnsupportedOperationException at javax.faces.context.FacesContext.getAttributes(FacesContext.java:137) at javax.faces.component.UIViewRoot.setViewId(UIViewRoot.java:325) at org.jboss.seam.mock.MockViewHandler.createView(MockViewHandler.java:28) at org.jboss.seam.jsf.SeamViewHandler.createView(SeamViewHandler.java:68) at org.jboss.seam.mock.AbstractSeamTest$Request.restoreViewPhase(AbstractSeamTest.java:734) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:591) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:505) ... 45 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

5
21
0 / 0

[JBoss JIRA] (JBIDE-10188) Shows warning for Seam 3 Conversation injection

by Cody Lerum (Created) (JIRA)

Shows warning for Seam 3 Conversation injection ----------------------------------------------- Key: JBIDE-10188 URL: https://issues.jboss.org/browse/JBIDE-10188 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Seam 3.1 Beta4 Reporter: Cody Lerum @Inject private SeamConversationContext<HttpServletRequest> seamConversationContext; "Give No bean is eligible for injection to the injection point [JSR-299 §5.2.1]" warning even though it is valid. https://github.com/seam/conversation -- 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

13 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-12446) Migrate CDI Tools model to SQL(?) DB instead of using Java collections

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12446: -------------------------------------- Summary: Migrate CDI Tools model to SQL(?) DB instead of using Java collections Key: JBIDE-12446 URL: https://issues.jboss.org/browse/JBIDE-12446 Project: Tools (JBoss Tools) Issue Type: Task Components: CDI Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.4.x Right now we are using Java collections (Maps, Sets, Lists) to store model artifacts. It works ok for small projects. For big projects, we will probably face serious problems with performance and memory usage. Let's investigate what we can do there and what we can benefit of using SQL DB as a storage for big CDI projects. Here is the list of possible steps for this work: # Create a test project or rather a code which will be able to create big test projects. We will use those projects for testing performance/memore usage for different types of storages. # Research different DB/persistence frameworks to find options which are best for our goal. # Split CDI Tools core into core interfaces/services for the storage and storage implementations. # Implement DB storage and test it against our test projects (see step #1) -- 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

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8758) @Inject @Resource(<name>) validation

by Alexey Kazakov (JIRA)

@Inject @Resource(<name>) validation ------------------------------------ Key: JBIDE-8758 URL: https://issues.jboss.org/browse/JBIDE-8758 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x We should validate resource path/name for such injections: {code} @Inject @Resource("WEB-INF/beans.xml") URL beansXml; {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12645) Weld extensions: built in contexts

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12645: -------------------------------------- Summary: Weld extensions: built in contexts Key: JBIDE-12645 URL: https://issues.jboss.org/browse/JBIDE-12645 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: CDI extensions Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.0.x See http://docs.jboss.org/weld/reference/1.1.5.Final/en-US/html/contexts.html... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-12519) Weld extensions

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12519: -------------------------------------- Summary: Weld extensions Key: JBIDE-12519 URL: https://issues.jboss.org/browse/JBIDE-12519 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI extensions Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.0.0.Alpha2 For example @Parameters See http://docs.jboss.org/weld/reference/1.0.0/en-US/html/environments.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2012