September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9269) Possibility of providing template for #document element

by Maxim Areshkau (JIRA)

Possibility of providing template for #document element ------------------------------------------------------- Key: JBIDE-9269 URL: https://issues.jboss.org/browse/JBIDE-9269 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Maxim Areshkau Assignee: Yahor Radtsevich Priority: Critical We need possibility of providing template for #document element. For example this template can add same standard header and footer for docbook xml editor, of for user specific files. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-9421) MBean explorer AS7 connection does not work

by Dominik Pospisil (JIRA)

MBean explorer AS7 connection does not work ------------------------------------------- Key: JBIDE-9421 URL: https://issues.jboss.org/browse/JBIDE-9421 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 3.3.0.M2 Reporter: Dominik Pospisil Assignee: Rob Stryker By adding AS7 server, related connection is created in MBean explorer. However, the connection is allways inactive even if the server is up an running. Manually adding connection for AS7 works. Steps to reproduce: 1) Ad AS7 final server 2) Start the server 3) Open MBean view 4) Try to connect to AS7 via JMX 5) Nothing happens -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8720) NPE when BPMN2jPDL export finished when no export folder is selected

by Jiri Peterka (JIRA)

NPE when BPMN2jPDL export finished when no export folder is selected -------------------------------------------------------------------- Key: JBIDE-8720 URL: https://issues.jboss.org/browse/JBIDE-8720 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.2.1 Environment: JBDS 4.1.CR1 H237 Reporter: Jiri Peterka There is NPE when BPMN2jPDL export is Finished before selecting a folder. Steps: 1. Create project 2. Create BPMN process 3. Try to export, click finish button as soon as it's availabe ERROR: NPE is here. Solution would be to disable "Finish" button until no folder is selected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
24
0 / 0

[JBoss JIRA] Created: (JBIDE-9294) Possibility set repeat times for c:foreach tag

by Maxim Areshkau (JIRA)

Possibility set repeat times for c:foreach tag ---------------------------------------------- Key: JBIDE-9294 URL: https://issues.jboss.org/browse/JBIDE-9294 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.3.0.M1 Reporter: Maxim Areshkau Assignee: Denis Maliarevich c:forEach repeats it's content 3 time and doesn't provide possibility to change it. It will be good if templates-writer can set how many times the template will be repeat it content. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9454) Adding the JSF Facet (< 2.0) completely overwrites the project web.xml with m2e-wtp 0.13.x

by Fred Bricon (JIRA)

Adding the JSF Facet (< 2.0) completely overwrites the project web.xml with m2e-wtp 0.13.x ------------------------------------------------------------------------------------------ Key: JBIDE-9454 URL: https://issues.jboss.org/browse/JBIDE-9454 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, UpStream Affects Versions: 3.3.0.M2 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.0.M3 This bug is an upstream issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=353834), I discovered it while investigating on JBIDE-6228. Since m2e-wtp 0.13.0, a typical maven-powered dynamic web project defines 2 folders in its .component : 1 - target/m2e/web-resources/ : contains generated files 2 - src/main/webapp/ : contains user resources under SCM Both folders are deployed via the WTP server adapter. The target folder is put in first position because we sometimes need to override user resources (ex. dynamically replacing placeholders in configuration files) and WTP deploys the first resource it finds. When you add the JSF Facet to such project, and ask to add the faces servlet to the web.xml, the JSFFacetInstallDelegate pretty much does the following : - looks for the first folder found in .component (finds target/*) - finds no web.xml so generates an empty webxml model - serialize the new model to the web.xml it finds in src/main/webapp => the user web.xml is then totally overwritten. Easiest solution is to disable the Faces Servlet configuration for all JSF projects. That'd also fix JBIDE-6228. Twisted hack would be to change the configuration order in .component before and after changing adding the JSF Facet Time consuming solution would be to disable the Faces Servlet configuration during Facet install then, rewrite the web.xml update logic to add the missing Faces servlet config. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6228) "JBoss Maven Seam Integration" modifies web.xml during project import

by Clemens Fuchslocher (JIRA)

"JBoss Maven Seam Integration" modifies web.xml during project import --------------------------------------------------------------------- Key: JBIDE-6228 URL: https://jira.jboss.org/jira/browse/JBIDE-6228 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration, maven, Seam Affects Versions: 3.1.0.GA Environment: Eclipse 3.5.2, m2eclipse 0.10.0, JBoss Tools 3.1.0, 1.6.0-20, Debian GNU/Linux 5.0 Reporter: Clemens Fuchslocher Used software: * Eclipse IDE for Java EE Developers (http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/...) * m2eclipse 0.10.0.20100209-0800 (http://m2eclipse.sonatype.org/sites/m2e) * JBoss Maven Integration 1.0.0.v201003050540R-H56-GA (http://download.jboss.org/jbosstools/updates/stable/galileo/) * JBoss Maven Seam Integration 1.0.0.v201003050540R-H56-GA (http://download.jboss.org/jbosstools/updates/stable/galileo/) Steps to reproduce: 1. Import the seamIntegration project from http://anonsvn.jboss.org/repos/richfaces/tags/3.3.3.Final/samples/seamInt...: File -> New -> Other... -> Checkout Maven Projects from SCM -> Next -> SCM URL: svn, http://anonsvn.jboss.org/repos/richfaces/tags/3.3.3.Final/samples/seamInt... -> Finish 2. Compare the imported web.xml with the original one: http://anonsvn.jboss.org/repos/richfaces/tags/3.3.3.Final/samples/seamInt.... 3. Problem: The file is completely rewritten. All comments are lost. -- 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, 7 months

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-9237) Wrong tag library insertion when dnd from palette to JSP Document.

by Denis Vinnichek (JIRA)

Wrong tag library insertion when dnd from palette to JSP Document. ------------------------------------------------------------------ Key: JBIDE-9237 URL: https://issues.jboss.org/browse/JBIDE-9237 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.3.0.M1 Reporter: Denis Vinnichek Assignee: Alexey Kazakov Fix For: 3.3.0.M2 Drag any element from palette and drop it to any opened *.jspx file. As a result tag library is declared in a JSP manner (i.e using the taglib directive), but this syntax is not allowed in JSP documents. To declare a tag library in a JSP document, one should use the xmlns attribute, which is used to declare namespaces according to the XML standard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9583) CDI validator doesn't validate project if it is a dependency of another not-CDI project

by Alexey Kazakov (JIRA)

CDI validator doesn't validate project if it is a dependency of another not-CDI project --------------------------------------------------------------------------------------- Key: JBIDE-9583 URL: https://issues.jboss.org/browse/JBIDE-9583 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 EXECUTE: Create two CDI projects: Project 1 and Project 2. Project 2 must depend on Project 1. EXECUTE: Disable CDI support in project 2. EXECUTE: Build the project. FAILURE: Project 1 is not validated by CDI Tools any more. The reason of this failure is that CDIProject 1 still has a link to removed CDI Nature of Project 2. So CDI validator can't compute project dependencies using this broken link in CDI Nature of Project 1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9362) EL code completion should work in Java sources of any KB project.

by Alexey Kazakov (JIRA)

EL code completion should work in Java sources of any KB project. ----------------------------------------------------------------- Key: JBIDE-9362 URL: https://issues.jboss.org/browse/JBIDE-9362 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich We should provide EL code completion in Java sources for any project with KB builder. Not only for CDI or Seam project. EXECUTE: Create JSF 2 KickStart project. EXECUTE: Open User.java EXECUTE: Add the following string to User(): String s = "#{user.name}"; ASSERT: Code completion for #{user.| should suggest "name". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Closed: (JBIDE-6464) Running a SeamTest when multiple projects are open in the Eclipse workspace fails

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin... ] Pavol Srna closed JBIDE-6464. ----------------------------- > Running a SeamTest when multiple projects are open in the Eclipse workspace fails > --------------------------------------------------------------------------------- > > Key: JBIDE-6464 > URL: https://issues.jboss.org/browse/JBIDE-6464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Environment: XP, JBoss 5.1.0 GA, Seam 2.2.0 GA, JBoss Tools 3.1.0 GA > Reporter: Shu-Wei Tan > Assignee: Alexey Kazakov > Fix For: 3.3.0.M3 > > > My eclipse workspace contains 2 JBoss Tools generated Seam projects: > - Project1.war > - Project1.ear > - Project1.ejb > - Project1.test > - Project2.war > - Project2.ear > - Project2.ejb > - Project2.test > Project2.ear depends on both Project1.ejb and Project2.ejb. > Project2.test contains a SeamTest test case. When running that test case, I get an exception saying TimerServiceDispatcher already deployed. This is because jboss-seam.jar seems to be picked up twice by the bootstrap process, once from Project1.ear and once from Project2.ear. > If I close the Project1.ear project in Eclipse then rerun the test, it works. > Here's the exception (the actual project name is different from my simplified example above): > ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfsjar:file:/E:/gbahn/SeamProjects/General/General-ear/EarContent/jboss-seam.jar!/ state=PostClassLoader mode=Manual requiredState=Real > org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158) > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) > at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127) > at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289) > at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:19) > at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024) > at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) > at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) > 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) > at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:607) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:417) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:154) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284) > at org.testng.SuiteRunner.run(SuiteRunner.java:204) > at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877) > at org.testng.TestNG.runSuitesLocally(TestNG.java:842) > at org.testng.TestNG.run(TestNG.java:751) > at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) > at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) > Caused by: org.jboss.deployers.spi.DeploymentException: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:540) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486) > at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:468) > at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:434) > at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:376) > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145) > ... 36 more > Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:128) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:536) > ... 41 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
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 2011