November 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-855) Typo: Creating a new java project shows Director instead of Directory

by Shaun Appleton (JIRA)

Typo: Creating a new java project shows Director instead of Directory --------------------------------------------------------------------- Key: JBDS-855 URL: https://jira.jboss.org/jira/browse/JBDS-855 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Shaun Appleton Priority: Trivial Within JBDS File -> New -> Project Select Java Project Select Next Select Radio Button 'Create project from existing source' Observe 'Director' instead of 'Directory' underneath radio button. -- 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

16 years, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5247) Endless cycling in org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner.getRegion(IDocument, int) under some conditions

by Victor Rubezhny (JIRA)

Endless cycling in org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner.getRegion(IDocument, int) under some conditions ------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5247 URL: https://jira.jboss.org/jira/browse/JBIDE-5247 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.M4 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Priority: Critical Fix For: 3.1.0.CR1 In case of having a node with non-ended expression with no body typed as the node value in XHTML text (for example, <s:div>#{</s:div> ), if you try to make a hyperlink on that EL the org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner.getRegion(IDocument, int) method comes into an endless cycle. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDS-817) NullPointerException reported in Error Log View after first start of JBDS

by Denis Golovin (JIRA)

NullPointerException reported in Error Log View after first start of JBDS ------------------------------------------------------------------------- Key: JBDS-817 URL: https://jira.jboss.org/jira/browse/JBDS-817 Project: Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 2.1.0, 3.0.0.M3 JBDS Installer without EAP used and JBoss AS 4.2.2.GA server was added to the server list -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5242) NPE in JBoss4xEarFacetInstallListener

by Snjezana Peco (JIRA)

NPE in JBoss4xEarFacetInstallListener ------------------------------------- Key: JBIDE-5242 URL: https://jira.jboss.org/jira/browse/JBIDE-5242 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M4 Reporter: Snjezana Peco Assignee: Rob Stryker Steps to reproduce: - call the New EAR Application Project wizard - select <None> as Target Runtime - click Finish You will get the following exception: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.JBoss4xEarFacetInstallListener.handleEvent(JBoss4xEarFacetInstallListener.java:57) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1317) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:451) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1171) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1107) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1089) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1099) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:1958) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:279) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) The solution is that the JBoss4xEarFacetInstallListener.handleEvent() does nothing if the project doesn't have any runtime. -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBIDE-4851) Configurable font size and family for Mapping Diagram Viewer

by Vitali Yemialyanchyk (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4851?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk updated JBIDE-4851: ---------------------------------------- Fix Version/s: LATER (was: 3.1.0.CR1) > Configurable font size and family for Mapping Diagram Viewer > ------------------------------------------------------------ > > Key: JBIDE-4851 > URL: https://jira.jboss.org/jira/browse/JBIDE-4851 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Affects Versions: 3.1.0.M4 > Reporter: Vitali Yemialyanchyk > Assignee: Vitali Yemialyanchyk > Priority: Optional > Fix For: LATER > > > Current default font size is 8,5 - possible to use font with the size 4 - it is readable on the paper and reduce number of print pages. > JBIDE-4756 - enhance "Print" functionality, but this also could be useful. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-4851) Configurable font size and family for Mapping Diagram Viewer

by Vitali Yemialyanchyk (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4851?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk updated JBIDE-4851: ---------------------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] > Configurable font size and family for Mapping Diagram Viewer > ------------------------------------------------------------ > > Key: JBIDE-4851 > URL: https://jira.jboss.org/jira/browse/JBIDE-4851 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Affects Versions: 3.1.0.M4 > Reporter: Vitali Yemialyanchyk > Assignee: Vitali Yemialyanchyk > Priority: Optional > Fix For: LATER > > > Current default font size is 8,5 - possible to use font with the size 4 - it is readable on the paper and reduce number of print pages. > JBIDE-4756 - enhance "Print" functionality, but this also could be useful. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-948) Open On works if path was set using EL variable

by Svetlana mukhina (JIRA)

Open On works if path was set using EL variable ----------------------------------------------- Key: JBDS-948 URL: https://jira.jboss.org/jira/browse/JBDS-948 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc update openon section -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss

by Alexander Lengson (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ] Alexander Lengson commented on JBIDE-4706: ------------------------------------------ Snjezana, Thank you very much for your work. Alex. > Maven integration issues: setting facets on maven projects and deploying ear on JBoss > ------------------------------------------------------------------------------------- > > Key: JBIDE-4706 > URL: https://jira.jboss.org/jira/browse/JBIDE-4706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Environment: Eclipse 3.5 > m2eclipse (0.9.9.20090720) > JBoss Tools AS M3 developer version > Subclipse SVN plugin 1.6.3 > Reporter: Alexander Lengson > Assignee: Snjezana Peco > Fix For: 3.1.0.CR1 > > Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.zip, without_vars_pure_maven.zip > > > Using Maven command line, I created four projects: > container - the parent Maven project. It also serves as a container for other projects > prj-jar - a shared library used by all other EJBs > prj-ejb - sample EJB > prj-ear - EE container for jar and ejb > Apache plugins for Maven (both for ejb and ear) are used. > I've performed the following steps: > * imported container into SVN > * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720) > * right-clicked on container and chosen "Checkout as Maven project" > * waited for the process to be finished > And the following likely are bugs and/or open questions: > * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ear: the same. > * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements? > * for prj-ejb: there is no Project Facet checked at all. > * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled) > * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed) > * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View: > EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart > * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml) > * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory: > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-ear-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <includeLibInApplicationXml>true</includeLibInApplicationXml> > ... > That builds the EAR which contains lib/ folder inside and all references libs like: > drools-api-5.0.1.jar > drools-core-5.0.1.jar > hsqldb-1.8.0.10.jar > joda-time-1.6.jar > mvel2-2.0.10.jar > prj-jar-1.0-SNAPSHOT.jar > That can be assured by running command: > container>mvn install > Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors. > It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3456) application.xml is missing in Seam project when debug on server option is selected for the web application

by Dirk Pitt (JIRA)

application.xml is missing in Seam project when debug on server option is selected for the web application ---------------------------------------------------------------------------------------------------------- Key: JBIDE-3456 URL: https://jira.jboss.org/jira/browse/JBIDE-3456 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.cr1 Reporter: Dirk Pitt My project is not generated from the seamgen or from JBoss Tools Seam Wizard. I created from Wesley Hayes maven archetype and installed necessary facets in eclipse configuration (Seam Facet and Seam Settings).. If I build it with maven and deploy it, everything works fine. But if I say in the web project in eclipse, debug on the server, I am getting the exception during deployment that application.xml is not there and it is not really there under \.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_AS_4.2.3_Server\deploy... My project configuration seems to be valid one because I am getting all the content assist information for the seam and project runs correctly if it deployed externally to JBoss... May be JBoss Tools and m2eclipse plugin are colliding but it is very hard for me to tell that.. I am attaching my sample project also so may be you can also reproduce it... -- 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

16 years, 4 months

4
24
0 / 0

[JBoss JIRA] Created: (JBDS-785) JSF Portlet not working with EPP run time

by Prabhat Jha (JIRA)

JSF Portlet not working with EPP run time ----------------------------------------- Key: JBDS-785 URL: https://jira.jboss.org/jira/browse/JBDS-785 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Prabhat Jha When I try to create a Dynamic Web project and select JBoss Portlets->JBoss JSF Portlet, I get : - JBoss JSF Portlet 1.0 requires JBoss Core Portlet 1.0 or newer" - JBoss JSF Portlet 1.0 requires JavaServer Faces 1.2 or newer" I configure run time as following: Select JBoss Enterprise Applicaiton Platform 4.3 Runtime and point it to /home/prabhat/as/jboss-epp-4.3/jboss-as which basically is unzipped JBoss EPP 4.3 CP01. -- 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

16 years, 4 months

3
10
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 November 2009