June 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6541) code assist does not show Seam components when Eclipse first starts (until you 'refresh' or clean project)

by Vadim Berezniker (JIRA)

code assist does not show Seam components when Eclipse first starts (until you 'refresh' or clean project) ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6541 URL: https://jira.jboss.org/browse/JBIDE-6541 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.1 Reporter: Vadim Berezniker Relevant forum post is here: https://community.jboss.org/message/549587#549587 As the title says, if I restart Eclipse and open a .xhtml file and try to perform EL code assist, I do not see any Seam components in the list. If I refresh the project, clean the project or expand the project in the 'Seam Components' window then it starts to work. I tried it with a clean workspace with JBoss Tools 3.1.1 with the same results. Tried it on another machine with JBoss Tools 3.1.0 with the same results. I noticed that Eclipse doesn't appear to run builders if the project is in 'pristine' state. That is if the project is built when you close Eclipse, it won't try to build it when you reopen Eclipse. Eclipse version is 3.5.2 It's a pretty minor issue as it's relatively easy to resolve, but it may be confusing to new users if they encounter it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5994) CSS Class dialog allows entering invalid class name

by Libor Zoubek (JIRA)

CSS Class dialog allows entering invalid class name --------------------------------------------------- Key: JBIDE-5994 URL: https://jira.jboss.org/jira/browse/JBIDE-5994 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Libor Zoubek Priority: Minor CSS Class dialog allows entering class name 'aaa;aaa' which is not valid class name. 1. create CSS file 2. Open Class Dialog (Ctrl+Shift+C) 3. Click Add CSS Class 4. enter invalid name -- 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

15 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5979) CSS Properties view does not update values immediately

by Libor Zoubek (JIRA)

CSS Properties view does not update values immediately ------------------------------------------------------ Key: JBIDE-5979 URL: https://jira.jboss.org/jira/browse/JBIDE-5979 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR2 Reporter: Libor Zoubek Priority: Minor 'CSS Properties' view should update values of properties immediately as they are typed. When I type property value in CSS editor, everyting works. When I type in 'Properties View' updating is not working when I change value to empty string or when changing property which is yet not declared in css file. 1.Open any CSS file with CSS style class defined 2.Choose Window -> Show View -> Other -> CSS Properties. Press OK. 3.Mouse click or set cursor on any CSS Style 4.Go to CSS Properties View, select and change some properties, for example, Text color, background-color, font and so on... 5.Open standard Properties view (Window -> Show View -> Other -> General -> Properties View). 6.Edit some properties in standart Properties view and click on CSS Properties view. -- 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

15 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6019) Explicit action to add complex variable initialization in Assign

by Robert (Bob) Brodt (JIRA)

Explicit action to add complex variable initialization in Assign ---------------------------------------------------------------- Key: JBIDE-6019 URL: https://jira.jboss.org/jira/browse/JBIDE-6019 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.1.0.CR2 Reporter: Robert (Bob) Brodt this could easily be solved with the addition of a button to the Assign Properties/Details tab which displays a variables selection dialog. The editor could then generate the appropriate XML to initialize complex variables. Apparently, the Riftsaw engine requires the structure of complex variables to be set before they can be accessed. An alternative would be to add an "Initialize" tab to the Assign Properties, similar to the Variable Property sheet. -- 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

15 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6021) Add hyperlinks to BPEL editor

by Robert (Bob) Brodt (JIRA)

Add hyperlinks to BPEL editor ----------------------------- Key: JBIDE-6021 URL: https://jira.jboss.org/jira/browse/JBIDE-6021 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.1.0.CR2 Reporter: Robert (Bob) Brodt It would be nice to have hyperlinks from the BPEL editor to WSDL/XSD and from WSDL editor to XSD for messages, port types and partner links, which would quickly jump to the definition in the appropriate editor. -- 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

15 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6236) Provide hints/suggestions/tips in the editor

by Lukas Jungmann (JIRA)

Provide hints/suggestions/tips in the editor -------------------------------------------- Key: JBIDE-6236 URL: https://jira.jboss.org/jira/browse/JBIDE-6236 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick For most developers the editor is the place where he is spending most of his working time, therefore we could try to make his life easier by providing web services related editor improvements. These improvements can be made in following categories: -context sensitive code completion/proposals example: user types '@WebService(endpointInterface="|")', invokes code completion at '|' and completion will offer him list of applicable interfaces available in current project/workspace -error checking example: user has an empty class annotated with @WebService - this class compiles fine but is not valid web service due to missing web service operation hence the editor should show some kind of error and provide some hint/proposal so the user can easily fix it; hints could be ie Add ws operation, remove Web Service annotation All these improvements should be based on rules defined in JSR-181 (eventually JSR-224). I don't think all of them should be implemented but having at least some of them can be pretty useful. To start a discussion about what to eventually implement, here is a kind of a spec we could reuse: http://wiki.netbeans.org/SpecWsEditorUI and an umbrella issue[1] in NetBeans bugzilla covering few other related items which might not be in the spec itself [1]: http://netbeans.org/bugzilla/show_bug.cgi?id=78758 -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1109) Recognize/Set a SOA-P Server Runtime

by Stelios Koussouris (JIRA)

Recognize/Set a SOA-P Server Runtime ------------------------------------ Key: JBDS-1109 URL: https://jira.jboss.org/jira/browse/JBDS-1109 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 2.1.1 Reporter: Stelios Koussouris [Stelios] I have one more question. Why when you create a JBoss ESB Project it ONLY offers you the chance to create an EAP Runtime and NOT and ESB Runtime? I create the ESB project and I go to "Add Runtime" but it is an EAP Runtime "Type" that I end up with (although I am pointing it to an ESB Runtime). [Max] When you create an ESB project it needs an EAP runtime (SOA-P is an EAP) and the type if we had one would be SOA-P (not just ESB). The "runtime" you point to here is the complete server runtime (i.e. EAP), not just ESB. Right now we unfortunately don't have a good check if the underlying EAP includes an ESB runtime or not (like we i.e. have for Portal) this is something we will need to work on going forward. The notion of ESB Runtime is something we have for *standalone* ESB, not full platforms (like EAP and SOA-P). To solve/align it better it would be major new functionality that would go into a JBDS 3.1 or even JBDS 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

15 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5936) New ESB Project wizard validation needs to be earlier in the process

by Brian Fitzpatrick (JIRA)

New ESB Project wizard validation needs to be earlier in the process -------------------------------------------------------------------- Key: JBIDE-5936 URL: https://jira.jboss.org/jira/browse/JBIDE-5936 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.CR2 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.next While testing a fix for JBIDE-5916, Rob Stryker discovered the strange and undesirable behavior as documented below while testing against EAP 5.0 instead of SOA-P 5.0: "When I am in the first page of the esb project wizard, automatically selected is my JBoss EAP 5.0 Server Runtime. Below it is also automatically selected "ESB Version: 4.7". Yet when I push forward two pages, it tells me my server does Not have esb 4.7 in it, I then have to go back two pages and change the facet version, then forward two pages to see if the error has disappeared. I finally gave up, as it one by one informed me that I do not have a satisfactory version in my EAP 5.0 runtime at all, which I find as extremely unlikely. At at least one attempt told me I did not even have a runtime selected, when the UI clearly did. (I eventually got confused enough that I did a du -a | grep -i "esb" command to see if the eap server had any jars or anything that mentioned "esb" anywhere in the file name. None did. So now I'm wondering if my install is just odd, but I don't suspect it is. I decide to switch to not using the "Server supplied runtime" and instead creating a new one on the third page, and I again pointed to my jboss-eap-5.0 folder. At no point did this dialog inform me that none of the versions were found. Instead I, once again, had to select each of the 6 versions to find out none were valid for this folder. I finally pointed directly to an actual esb server (jbossesb-server-4.4.GA) and the dialog did auto-fill itself in, though I also remember I was the one who made that fix about 2 months ago after a similarly infuriating attempt at this. However even after I do this, I notice in my Package Explorer that there is NO classpath container containing any ESB jars on hte project. So I check the .classpath file to see if ANYTHING was added at all, and I see this: <classpathentry kind="con" path="server.supplied/SomeName"/> Aside from the ridiculously short and uninformative name "server.supplied", the adept user will note that this entry was not, actually, server supplied at all, but rather the other option, as I outlined above and pointed directly to an esb installation. Aside from that, this "server.supplied" is directly visible in the Java Build Path property page, under the Libraries tab. Which means this constant is exposed to users to see." The issue here seems to be that the runtime validation to see if it actually HAS an ESB installed doesn't occur until page 3 of the wizard. This should be done up front on page 1 of the wizard. If ESB isn't available in a selected runtime, the user should not be able to continue in the wizard and should get an error message saying that the runtime selected doesn't support ESB. Pretty simple. The user should not be forced to go forward/back through the wizard trying different combinations if NONE of the combinations will actually work. This needs to be fixed for the next release. -- 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

15 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6531) vpe.seam test failures

by Nick Boldt (JIRA)

vpe.seam test failures ---------------------- Key: JBIDE-6531 URL: https://jira.jboss.org/browse/JBIDE-6531 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Seam Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... Tests run: 90, FAILUREs: 2, Errors: 0, Skipped: 0, Time elapsed: 86.325 sec <<< FAILURE! testLabel(org.jboss.tools.jsf.vpe.seam.test.SeamComponentContentTest) Time elapsed: 0.503 sec <<< FAILURE! junit.framework.AssertionFailedError: string is"-moz-user-modify: read-write;" but must be "-moz-user-modify: read-only; cursor: pointer;" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareElements(ComponentContentTest.java:131) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:90) at org.jboss.tools.jsf.vpe.seam.test.SeamComponentContentTest.testLabel(SeamComponentContentTest.java:74) -- testSelectDate(org.jboss.tools.jsf.vpe.seam.test.SeamComponentContentTest) Time elapsed: 0.413 sec <<< FAILURE! junit.framework.AssertionFailedError: string is"rich-calendar-input" but must be "rich-calendar-input null" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareElements(ComponentContentTest.java:131) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:90) at org.jboss.tools.jsf.vpe.seam.test.SeamComponentContentTest.testSelectDate(SeamComponentContentTest.java:90) -- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6300) Tycho-based Drools build depends on JSF; refactor out common bot test framework code into tests/ or common/ module

by Nick Boldt (JIRA)

Tycho-based Drools build depends on JSF; refactor out common bot test framework code into tests/ or common/ module ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-6300 URL: https://jira.jboss.org/browse/JBIDE-6300 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.next Reporter: Nick Boldt Assignee: Kris Verlaenen [Software being installed: org.jboss.tools.drools.ui.bot.test 1.0.0.qualifier, Missing requirement: org.jboss.tools.drools.ui.bot.test 1.0.0.qualifier requires 'bundle org.jboss.tools.ui.bot.ext 1.0.0' but it could not be found] Required plugin, org.jboss.tools.ui.bot.ext, is located in jst/tests/org.jboss.tools.ui.bot.ext, which changes the order in which components must be built. Currently, drools only depends on tests and common. To add this new bot test requires either that it now depend on xulrunner & jst, or that the bot.ext plugin be moved upstream into tests/ or common/. I prefer to move it upstream than to push Drools downstream. Can that be done? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
18
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 June 2010