September 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4213) Taglibs which defined as facelets.LIBRARIES param in web.xml doesn't show in Web Projects View in Tag Libraries folder.

by Maxim Areshkau (JIRA)

Taglibs which defined as facelets.LIBRARIES param in web.xml doesn't show in Web Projects View in Tag Libraries folder. ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4213 URL: https://jira.jboss.org/jira/browse/JBIDE-4213 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Reporter: Maxim Areshkau Assignee: Viacheslav Kabanovich Fix For: 3.1.0.M1 Steps to reproduce: 1) import into eclipse workspace https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... project 2) open Web Project View 3) open Tag Libraries leaf ASSERT Here should be tag library /tags/facelets.taglib.xml which defined in web.xml as facelets.LIBRARIES context param. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-660) Server search window during installation doesn't close.

by Ondrej Skutka (JIRA)

Server search window during installation doesn't close. ------------------------------------------------------- Key: JBDS-660 URL: https://jira.jboss.org/jira/browse/JBDS-660 Project: Developer Studio Issue Type: Bug Components: installer Affects Versions: 2.0.0.GA Reporter: Ondrej Skutka Attachments: snapshot6.png During installation of JBDS after searching for jboss servers, the 'server search' window (formerly showing progression) doesn't close and is not repainted anymore. It also cannot be closed by window manager. You can however continue in the installation ignoring the top window. -- 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, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-656) Work of adding additional servers in installer is incorrect.

by Anton Klimkovich (JIRA)

Work of adding additional servers in installer is incorrect. ------------------------------------------------------------- Key: JBDS-656 URL: https://jira.jboss.org/jira/browse/JBDS-656 Project: Developer Studio Issue Type: Bug Components: installer, servers Affects Versions: 2.0.0.GA Reporter: Anton Klimkovich EXECUTE: Run installer EXECUTE: Press Add button On step 5 EXECUTE: Press Browse button and select path to JBoss EAP server (\jbdevstudio20GA\jboss-eap\jboss-as) EXECUTE: Set checkbox to EAP and press ok ASSERT: EAP is added EXECUTE: Finish installation and run JBDS EXECUTE: Open JBoss Server view FAILURE: There is no JBoss EAP server in JBoss Server view. Runtime is absent too. Once I also got an exception but can't get it again. !ENTRY org.eclipse.wst.server.core 4 0 2009-03-10 14:32:28.674 !MESSAGE Could not save servers !STACK 0 java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.eclipse.wst.server.core.internal.ResourceManager.saveServersList(ResourceManager.java:536) at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:632) at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:408) at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264) at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:397) at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:421) at org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper.save(ServerAttributeHelper.java:116) at org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper.save(ServerAttributeHelper.java:121) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.save(XPathModel.java:202) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:100) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2532) Defect in GUI. Task Node | Task | Controller Tab Mapped Name displays in the Required Check Box column.

by Steve Hall (JIRA)

Defect in GUI. Task Node | Task | Controller Tab Mapped Name displays in the Required Check Box column. -------------------------------------------------------------------------------------------------------- Key: JBIDE-2532 URL: https://jira.jboss.org/jira/browse/JBIDE-2532 Project: Tools (JBoss Tools) Issue Type: Bug Components: Ganymede Affects Versions: 3.0.0.GA Environment: Eclipse plugin 3.1.3SP2. Installed in Eclipse 3.4.0. Running on Windows XP SP2 Reporter: Steve Hall Priority: Minor Created a Task Node. Added a task. Provided Name in General field. Set Assignment to Swinlane. Filled in the Swimlane Name. On the controller tab I added 6 variables. For each variable, I entered the name and mapped name filed. When I display the data in the GRID, the Mapped Name data shows up under the Required column. This is the associated processdefinition.xml file: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="ProductMusicProducts"> <swimlane name="Talent Scout"> <assignment expression="group(Talent Scout)"></assignment> </swimlane> <swimlane name="Legal Advisor"> <assignment expression="group(Legal Advisor)"></assignment> </swimlane> <swimlane name="Band Member"> <assignment expression="group(Band Member)"></assignment> </swimlane> <swimlane name="Record Producer"> <assignment expression="group(Record Producer)"></assignment> </swimlane> <swimlane name="Artist Development"> <assignment expression="group(Artist Development)"></assignment> </swimlane> <swimlane name="Songwriter"> <assignment expression="group(Songwriter)"></assignment> </swimlane> <swimlane name="Musician"> <assignment expression="group(Musician)"></assignment> </swimlane> <swimlane name="Video Production"> <assignment expression="group(Video Production)"></assignment> </swimlane> <swimlane name="Artist"> <assignment expression="group(Artist)"></assignment> </swimlane> <start-state name="Hold Auditions"> <task name="Hold Auditions" swimlane="Talent Scout"> <description> The hold auditions task </description> <controller> <variable access="read,write,required" name="audDate" mapped-name="Audition Date"></variable> <variable access="read,write,required" name="audLocation" mapped-name="Audition Location"></variable> </controller> </task> <transition to="Select Band Members"></transition> </start-state> <task-node name="Select Band Members"> <task name="Select Band Members" swimlane="Talent Scout"> <description> Assign Band Members </description> <controller> <variable access="read,write,required" name="bm1" mapped-name="Band Member 1"></variable> <variable access="read,write,required" name="bm2" mapped-name="Band Members 2"></variable> <variable access="read,write,required" name="bm3" mapped-name="Band Member 3"></variable> <variable access="read,write" name="bm4" mapped-name="Band Member 4"></variable> <variable access="read,write" name="bm5" mapped-name="Band Member 5"></variable> <variable access="read,write" name="bm6" mapped-name="Band Member 6"></variable> </controller> </task> </task-node> <task-node name="Contract Band Members"> <task name="Contract Band Members"> <controller> <variable access="read,write,required" name="bm1ContractSent" mapped-name="Band Member 1 Contract Sent"></variable> <variable access="read,write,required" name="bm2ContractSent" mapped-name="Band Member 2 Contract Sent"></variable> <variable access="read,write,required" name="bm3ContractSent" mapped-name="Band Member 3 Contract Sent"></variable> <variable access="read,write" name="bm4ContractSent" mapped-name="Band Member 4 Contract Sent"></variable> <variable access="read,write" name="bm5ContractSent" mapped-name="Band Member 5 Contract Sent"></variable> <variable access="read,write" name="bm6ContractSent" mapped-name="Band Member 6 Contract Sent"></variable> </controller> </task> </task-node> <task-node name="All Contracts Agreed"> <task name="All Contracts Agreed" swimlane="Legal Advisor"> <controller> <variable access="read,write,required" name="bm1Agreed" mapped-name="Band Member 1 Agreed"></variable> <variable access="read,write,required" name="bm2Agreed" mapped-name="Band Member 2 Agreed"></variable> <variable access="read,write,required" name="bm3Agreed" mapped-name="Band Member 3 Agreed"></variable> <variable access="read,write" name="bm4Agreed" mapped-name="Band Member 4 Agreed"></variable> <variable access="read,write" name="bm5Agreed" mapped-name="Band Member 5 Agreed"></variable> <variable access="read,write" name="bm6Agreed" mapped-name="Band Member 6 Agreed"></variable> </controller> </task> </task-node> <task-node name="Contract Response"> <task> <controller> <variable access="read,write,required" name="bm1Agreed" mapped-name="BandMember1Agreed"></variable> <variable access="read,write,required" name="bm2Agreed" mapped-name="Band Member 2 Agreed"></variable> <variable access="read,write,required" name="bm3Agreed" mapped-name="Band Member 3 Agreed"></variable> <variable access="read,write" name="bm4Agreed" mapped-name="Band Member 4 Agreed"></variable> <variable access="read,write" name="bm5Agreed" mapped-name="Band Member 5 Agreed"></variable> <variable access="read,write" name="bm6Agreed" mapped-name="Band Member 6 Agreed"></variable> </controller> </task> </task-node> <end-state name="end-state1"></end-state> </process-definition> -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4234) Some errors were detected when validating the file "loose.dtd" via the file "ordermanagement1.jpdl.xml" in Seam DVD Store Example Project

by Anton Klimkovich (JIRA)

Some errors were detected when validating the file "loose.dtd" via the file "ordermanagement1.jpdl.xml" in Seam DVD Store Example Project ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4234 URL: https://jira.jboss.org/jira/browse/JBIDE-4234 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.0.1.GA Reporter: Anton Klimkovich EXECUTE: Download Seam DVD Store Example Project into workspace EXECUTE: Look at Problems view FAILURE: Some errors were detected when validating the file "loose.dtd" via the file "ordermanagement1.jpdl.xml" -- 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, 5 months

7
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4907) Provide consistent categorization/labelling for jBPM

by Koen Aers (JIRA)

Provide consistent categorization/labelling for jBPM ---------------------------------------------------- Key: JBIDE-4907 URL: https://jira.jboss.org/jira/browse/JBIDE-4907 Project: Tools (JBoss Tools) Issue Type: Task Components: jbpm Reporter: Koen Aers Fix For: 3.1.0.M4 Make sure that the categorization/labelling of the jBPM wizards and preference pages is consistent with the current JBT/JBDS way of doing these things -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4676) Eclipse Utility Project not included in EAR /lib directory on rebuild

by Margot Media (JIRA)

Eclipse Utility Project not included in EAR /lib directory on rebuild --------------------------------------------------------------------- Key: JBIDE-4676 URL: https://jira.jboss.org/jira/browse/JBIDE-4676 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5 w/ JBoss Tools 3.1.0 M2. Using the "JBoss v5.0" server instead of the "JBoss AS 5.1". Reporter: Margot Media I have an application with a single MDB .jar file and 3 Utility Module .jar files. The utility projects are set up to appear in the EAR under the /lib directory. The first time the EAR file is deployed to the server, the /lib directory is populated correctly. However, if I change my source code and republish to the server, the /lib directory is not present! If I remove the EAR file from the server, then re-add it, the /lib directory is created properly. The first time, it looks like this: Code: MyEar.ear |- /lib | |- Utility1.jar | |- Utility2.jar | |- Utility3.jar |- /META-INF | |- MANIFEST.MF |- MyMDB.jar If I change the code in MyMDB.jar, the EAR file is generated like: Code: MyEar.ear |- /META-INF | |- MANIFEST.MF |- MyMDB.jar with the obvious class path problems by not having the utility jar files present. Steps to reproduce: 1. Create new "Java EE Enterprise Application Project" called MyEar using default configuration. 2. Create new "Java EE Utility Project" called Utlity 1 using the default configuration and add it to MyEar 3. Create new "Java EJB Project" called MyMdb using the default configuration and add it to MyEar 4. Set the Utility1.jar file to appear in the lib directory of MyEar 5. Create a class in the Utility1 project w/ some code (eg a POJO with one member and setter/getter) 6. Create MDB in the MyMDB project using the "Message-Driven Bean (EJB 3.x)" wizard 7. Add code to the MDB to make it dependent upon the Utility1 project 8. Start JBoss and deploy MyEar to the server. Verify that the EAR file correctly included the Utility1.jar file in the /lib directory 9. Make a change to the code in MyMDB and republish MyEar. Verify that the EAR does not include the /lib directory at all -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2023) Population of Action Class / Process Method

by Tom Cunningham (JIRA)

Population of Action Class / Process Method ------------------------------------------- Key: JBIDE-2023 URL: http://jira.jboss.com/jira/browse/JBIDE-2023 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: Mac OS X, nightly 04/04 JBoss Tools build, Europa JEE eclipse build Reporter: Tom Cunningham It would be nice if the ESB editor could somehow populate an action class drop down or do autocompletion of the class name, while at the same time retaining the ability for the user to type in their action class name. Action classes in the drop down should probably be restricted to classes within project which extend AbstractActionLifecycle or AbstractActionPipelineProcessor and the org.jboss.soa.esb.actions package classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

7
33
0 / 0

[JBoss JIRA] Created: (JBIDE-3378) Seam EL validation does not use same technique as the EL resolver (Continued)

by Tim Evers (JIRA)

Seam EL validation does not use same technique as the EL resolver (Continued) ----------------------------------------------------------------------------- Key: JBIDE-3378 URL: https://jira.jboss.org/jira/browse/JBIDE-3378 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1, 3.0.0.alpha, 2.1.2 Environment: Latest nightly build of JBoss Tools. On eclipse 3.4 SR1. JSF/Facelets/Richfaces/Seam 2.1.x environment Reporter: Tim Evers JBoss Tools does not validate method EL expressions properly if the method name starts with 'is' If I have a method in my SEAM bean like this. public boolean isEditButtonDisplayed() { return true; //removed what this method actually does for example } and then I have in my xhtml this: <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.isEditButtonDisplayed()}" /> When I validate this it says: "isEditButtonDisplayed" cannot be resolved. It looks like when the validation method sees the word 'is' it automatically thinks that the expression is a value expression. This should not be the case. Infact if I end my expression witih '()' it should always look for a method. The behaviour of the EL validation should be exactly the same as what happens when I run the system. But this is not what is happening. If I change my code to what the JBoss Tools autocomplete says to it actually breaks the application. According to JBoss Tools it says I should have this. <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.editButtonDisplayed}" /> Which of course will not work when the app is deployed. This is somewhat related to: https://jira.jboss.org/jira/browse/JBIDE-2673 just a different scenario. The fundamental problem is that the rules of validation are not the same as a running app. -- 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, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4758) EL OpenOns should use new unified EL Resolvers mechanism from org.jboss.tools.common.el

by Alexey Kazakov (JIRA)

EL OpenOns should use new unified EL Resolvers mechanism from org.jboss.tools.common.el --------------------------------------------------------------------------------------- Key: JBIDE-4758 URL: https://jira.jboss.org/jira/browse/JBIDE-4758 Project: JBoss Tools Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.M3 -- 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, 5 months

2
6
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 2009