January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10690) deprecate & remove all refs to ~/trunk/build/build.xml

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10690: ---------------------------------- Summary: deprecate & remove all refs to ~/trunk/build/build.xml Key: JBIDE-10690 URL: https://issues.jboss.org/browse/JBIDE-10690 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 Pretty sure this old ant script is no longer needed. It should be removed, albeit carefully. -- 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

14 years, 1 month

2
15
0 / 0

[JBoss JIRA] Created: (JBIDE-9801) CDI Searcher doesn't look for beans in dependent projects

by Alexey Kazakov (JIRA)

CDI Searcher doesn't look for beans in dependent projects --------------------------------------------------------- Key: JBIDE-9801 URL: https://issues.jboss.org/browse/JBIDE-9801 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M4 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.M4 EXECUTE: Create two CDI projects: ProjectA and ProjectB. ProjectB depends on ProjectA. EXECUTE: Create a bean in ProjectA: {code} @Named("cdiBean") public class CDIBeanTest { } {code} EXECUTE: Create another bean in ProjectB: {code} public class TestBean { @Inject @Named("cdiBean") Object foo; } {code} EXECUTE: Select CDIBeanTest class name in CDIBeanTest.java and press Ctrl+Shift+G ASSERT: TestBean.foo should be found as an injection point which gets the wanted bean. Now it's working only if you have both beans in the same project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

7
7
0 / 0

[JBoss JIRA] (JBIDE-10564) Open CDI Named Bean Toolbar button and navigaton Menu item is always visible (even if no CDI-related perspective is activated)

by Victor Rubezhny (Created) (JIRA)

Open CDI Named Bean Toolbar button and navigaton Menu item is always visible (even if no CDI-related perspective is activated) ------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-10564 URL: https://issues.jboss.org/browse/JBIDE-10564 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M5 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.3.0.Beta1 Open CDI Named Bean Toolbar button and navigaton Menu item is always visible. Even if CDI-related perspectives are closed. It should be visible when: - JBoss Perspective is active - JEE Perspective is active - Debug Perspective is active -- 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

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] (JBIDE-10425) Sometimes, the 'JAX-RS REST Web Services' node remains in a 'Building..' state

by Xavier Coulon (Created) (JIRA)

Sometimes, the 'JAX-RS REST Web Services' node remains in a 'Building..' state ------------------------------------------------------------------------------ Key: JBIDE-10425 URL: https://issues.jboss.org/browse/JBIDE-10425 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Minor Fix For: 3.3.0.Beta1 This seems to happen only at the workbench start and only if the jax-rs metamodel is empty -> the UI is not notified of the build end because there is not element to display on the UI :-( A 'clean' build solves the issue and restore the project explorer view in its expected state, though.. Solution: should force the UI notification at the end of a 'full build' even if nothing needs to be displayed. -- 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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] (JBIDE-10020) Hot key for VPE refresh

by Vitali Yemialyanchyk (Created) (JIRA)

Hot key for VPE refresh ----------------------- Key: JBIDE-10020 URL: https://issues.jboss.org/browse/JBIDE-10020 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.3.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich I can propose several variants... I'd like: F5, Ctrl+F5, and/or Ctrl+R -- 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

14 years, 1 month

9
13
0 / 0

[JBoss JIRA] (JBIDE-10205) Provide a mean to disable JAX-RS validation at project level

by Xavier Coulon (Created) (JIRA)

Provide a mean to disable JAX-RS validation at project level ------------------------------------------------------------ Key: JBIDE-10205 URL: https://issues.jboss.org/browse/JBIDE-10205 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon If JAX-RS elements validation fails (ie, reports false errors/warnings), the users should be able to disable it to avoid the unwanted noise. -- 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

14 years, 1 month

7
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7997) Server View: Delete shortcut does not work on multiple selection

by Yahor Radtsevich (JIRA)

Server View: Delete shortcut does not work on multiple selection ---------------------------------------------------------------- Key: JBIDE-7997 URL: https://issues.jboss.org/browse/JBIDE-7997 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta2 Reporter: Yahor Radtsevich Assignee: Rob Stryker Attachments: screenshot-1.png If one project is selected in the Server View, the project can be deleted using the Delete button. But if I want to delete several projects from a server, this shortcut does not work. See screenshot-1.png. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
15
0 / 0

[JBoss JIRA] Created: (JBDS-1848) Expander syntax for Drools can't find dsl file

by Joel Tosi (JIRA)

Expander syntax for Drools can't find dsl file ---------------------------------------------- Key: JBDS-1848 URL: https://issues.jboss.org/browse/JBDS-1848 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.GA Environment: JBDS 4.1.0 GA, OpenJDK 1.6, Fedora 14, Reporter: Joel Tosi Created a dsl, then went to use the dsl in a dslr. Entered the expander syntax along with the dsl filename, expander errors and says it cannot find the file. I have tried putting the dsl in the /src/main/rules directory, in the same package as the dslr, and tried placing the dsl in its own package and then importing it or complete path it in the expander - all provide an error still. [ERR 107] Line 5:0 mismatched input 'expander' expecting one of the following tokens: '{ identifier }'. DSLClassUpgradeRule.dslr /JBTravel/src/main/rules/biz/jbtravel/classup line 5 Drools Error -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2791) "duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)" error after creating a newseam project

by Riccardo Serafin (JIRA)

"duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)" error after creating a newseam project ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2791 URL: https://jira.jboss.org/jira/browse/JBIDE-2791 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.alpha Environment: Windows XP, Eclipse 3.4.0, JBoss AS 4.2.3-GA, Seam 2.1.0-BETA1, Java 1.6.0_10-rc Reporter: Riccardo Serafin After creating a new Seam project via the wizard (EAR packaging, configuration "Dynamic Web project with Seam 2.0"), starting up JBoss produces the following error: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) Even after removing jboss-seam.jar from the war MANIFEST.INF as suggested here (http://www.seamframework.org/Community/HowToUpdateProjectFrom20To21Seam) the error still occurs. This is the only other reference that I've found to this error (http://jira.jboss.com/jira/browse/JBSEAM-2981) but it looks slightly unrelated to me. Stack trace: 19:05:32,116 ERROR [[/hellome]] Excepción enviando evento inicializado de contexto a instancia de escuchador de clase org.jboss.seam.servlet.SeamListener java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:222) at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:215) at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:278) at org.jboss.seam.init.Initialization.installComponents(Initialization.java:983) at org.jboss.seam.init.Initialization.init(Initialization.java:631) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) .... I believe also these others warnings might be related to the same problem (which i suspect is duplicate jar in the classpath of the war): 19:49:24,506 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ 19:49:25,506 INFO [EARDeployer] Init J2EE application: file:/D:/Java/jboss-4.2.3.GA/server/default/deploy/hellome-ear.ear/ 19:49:35,459 WARN [MainDeployer] Found non-jar deployer for jboss-seam.jar: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer] 19:49:42,381 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: seam.jboss.org:loader=hellome, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false) 19:50:00,679 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment 19:50:04,976 INFO [TomcatDeployer] deploy, ctxPath=/hellome, warUrl=.../deploy/hellome-ear.ear/hellome.war/ 19:50:13,554 WARN [SeamPhaseListener] There should only be one Seam phase listener per application 19:50:20,726 INFO [ServletContextListener] Welcome to Seam 2.1.0.BETA1 -- 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, 1 month

5
10
0 / 0

[JBoss JIRA] (JBIDE-10141) CDI Tools: Extend JBoss Perspective

by Alexey Kazakov (Created) (JIRA)

CDI Tools: Extend JBoss Perspective ----------------------------------- Key: JBIDE-10141 URL: https://issues.jboss.org/browse/JBIDE-10141 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: CDI Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 -- 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

14 years, 1 month

4
3
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 January 2012