[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, 3 months
[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, 3 months
[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, 3 months
[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, 3 months
[JBoss JIRA] Created: (JBIDE-1012) Failed to delete project
by Slava Litskevich (JIRA)
Failed to delete project
------------------------
Key: JBIDE-1012
URL: http://jira.jboss.com/jira/browse/JBIDE-1012
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.Beta4
Environment: RHDS 1.0.0 beta 2
JDK 1.5.0_12
Reporter: Slava Litskevich
Fix For: 2.0.0.Beta4
Create new Seam Web Project:
1. File -> New -> Seam Web Project: new project dialog opens
2. Specifiy project name -> Next
3. Mark "Java Persistence" -> Next -> Next -> Next
4. Mark "Server Supplied JSF Implementation" -> Next -> Finish
5. File -> New -> Seam Generate Entities
Try to delete the project with the project content:
6. Rightclick the project -> Delete -> choose to delete the project content
Deletion fails. Error message dialog appears. Details window content:
Problems encountered while deleting resources.
Could not delete '/aa3'.
Problems encountered while deleting resources.
Problems encountered while deleting files.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ui.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ioc.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-pdf.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-remoting.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-mail.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-debug.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\oscache-2.3.2.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-digester-1.6.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jbpm-3.1.4.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\ajax4jsf-1.1.1-SNAPSHOT.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-collections-3.1.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jsf-facelets.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-beanutils-1.7.0.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\janino-2.4.3.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-janino-2.4.3.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-2.7.6.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-3.0ea8.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-core-1.0-406301.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-compiler-3.0.5.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-core-3.0.5.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\stringtemplate-2.3b6.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\hsqldb.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent.
Could not delete: D:\projects\workspace\seam-rhds\aa3.
Problems encountered while deleting files.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ui.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ioc.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-pdf.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-remoting.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-mail.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-debug.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\oscache-2.3.2.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-digester-1.6.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jbpm-3.1.4.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\ajax4jsf-1.1.1-SNAPSHOT.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-collections-3.1.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jsf-facelets.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-beanutils-1.7.0.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\janino-2.4.3.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-janino-2.4.3.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-2.7.6.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-3.0ea8.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-core-1.0-406301.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-compiler-3.0.5.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-core-3.0.5.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\stringtemplate-2.3b6.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\hsqldb.jar.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF.
Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent.
Could not delete: D:\projects\workspace\seam-rhds\aa3.
--
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, 4 months
[JBoss JIRA] Created: (JBDS-535) workflow/usability questions - Step 4: Select Java VM
by Nick Boldt (JIRA)
workflow/usability questions - Step 4: Select Java VM
-----------------------------------------------------
Key: JBDS-535
URL: https://jira.jboss.org/jira/browse/JBDS-535
Project: Developer Studio
Issue Type: Quality Risk
Components: installer
Affects Versions: 2.0.0.cr1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Attachments: Screenshot- JBoss Developer Studio 2.0.0.CR1.png
Actually, it says "gij" but on my monitor the text is cut off and it looks like a q, not a g.
Perhaps we could rework this as follows:
"JBoss Developer Studio requires a Java 5 or later runtime. Gnu Java (gij) is not supported; Open JDK 6 is recommended. Choose the Java VM to use with JBoss Developer Studio.
( ) Default Java VM (defined by PATH)
( ) Alternate Java VM (user-defined)"
Of course that assumes that JDBS *does in fact support JDK6*, and that we'd like to encourage people to use the latest and greatest Open JDK [1] (offered OOTB in Fedora 9 and later [2]), rather than letting them pick Sun, IBM, or BEA's JDKs.
[1] http://openjdk.java.net/
[2] http://fedoraproject.org/wiki/JavaFAQ
Also, does the installer check if the version of java used to run it is a compatible one? For example, will the installer run with 1.4, or with blackdown or gij, but require that JBDS itself use 5.0+?
And, since this selection is a prereq before JBDS will work at all, should this page be step 1, not 4?
--
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