August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5197) Unhandled event loop exception during blocked modal context: exception is occured after project deletion with opened JSF/XHTML page in VPE.

by Anton Klimkovich (JIRA)

Unhandled event loop exception during blocked modal context: exception is occured after project deletion with opened JSF/XHTML page in VPE. ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5197 URL: https://jira.jboss.org/jira/browse/JBIDE-5197 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov EXECUTE: Create JSF with Facelets project EXECUTE: Open greeting.xhtml EXECUTE: Delete project FAILURE: Unhandled event loop exception during blocked modal context: is occured. -- 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

12 years

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-2497) Add support of nested com

by Andrei Scherbovich (JIRA)

Add support of nested com ------------------------- Key: JBIDE-2497 URL: http://jira.jboss.com/jira/browse/JBIDE-2497 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Andrei Scherbovich -- 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

12 years

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-3793) Increase a code coverage by junit tests

by Maxim Areshkau (JIRA)

Increase a code coverage by junit tests ---------------------------------------- Key: JBIDE-3793 URL: https://jira.jboss.org/jira/browse/JBIDE-3793 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.0.0.GA Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0 Increase a code coverage by junit tests -- 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

12 years

5
17
0 / 0

[JBoss JIRA] Created: (JBIDE-2710) jsf validator should warn against empty id (id="")

by Max Rydahl Andersen (JIRA)

jsf validator should warn against empty id (id="") -------------------------------------------------- Key: JBIDE-2710 URL: https://jira.jboss.org/jira/browse/JBIDE-2710 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Minor Fix For: 3.0.0.beta1 See JBIDE-2631 for what happens if users have id="" Would be good if we could implement this as a validation. -- 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

12 years

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-293) properties editor very slow

by Martin Trummer (JIRA)

properties editor very slow --------------------------- Key: JBDS-293 URL: http://jira.jboss.com/jira/browse/JBDS-293 Project: Developer Studio Issue Type: Bug Components: visualeditor Affects Versions: 1.0.0.GA Reporter: Martin Trummer Assigned To: Max Andersen unfortunately I can't provide a recipe to reproduce the problem. However: It seems to happen when: I open 2 properties files - each about 300 lines I have the properties files open for some time (not using it) then I add a line and save it: in this case eclipse is stuck for 1-2 seconds. I only have about 300 properties in the editor. -- 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

12 years

6
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2101) XPath pattern matches disappear

by Galder Zamarreno (JIRA)

XPath pattern matches disappear ------------------------------- Key: JBIDE-2101 URL: http://jira.jboss.com/jira/browse/JBIDE-2101 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.beta1 Reporter: Galder Zamarreno I created a new category in the XML configuration view of the server called Server and added a new XPath like this: Name: jmx invoker XPath Pattern: /server/mbean/xmbean/operation/descriptors/interceptors/interceptor It worked fine first time around but now, although I can see the XPath, I can't see the matched XML files. Same happens in the "Ports" category. I'll attach screenshot. -- 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

12 years

3
18
0 / 0

[JBoss JIRA] Created: (JBDS-994) Enable ejbql code completion in Seam components.xml (framework:entity-query)

by Joao Paulo Viragine (JIRA)

Enable ejbql code completion in Seam components.xml (framework:entity-query) ---------------------------------------------------------------------------- Key: JBDS-994 URL: https://jira.jboss.org/jira/browse/JBDS-994 Project: JBoss Developer Studio Issue Type: Feature Request Components: seam Reporter: Joao Paulo Viragine Enable ejbql code completion in Seam components.xml as we have in @NamedQuery (http://docs.jboss.org/tools/movies/demos/java_hql_editing_and_validation/...) Eg: <framework:entity-query name="empresas" ejbql="" /> -- 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

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6018) Improve BPEL refactoring

by Robert (Bob) Brodt (JIRA)

Improve BPEL refactoring ------------------------ Key: JBIDE-6018 URL: https://jira.jboss.org/jira/browse/JBIDE-6018 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Reporter: Robert (Bob) Brodt Often times I find myself changing the names of variables, port types, partner links, etc. either in the Property sheet or directly on the editor canvas without thinking; what I really wanted to do was refactor the name change and have it propagate through to the WSDL or XSD where the element is defined. It would be simple enough to provide a change listener that prompts you with "Hey, I noticed you changed the name of this <thing> - did you intend to refactor instead?" possibly with a "Don't ask me again!" checkbox. The same functionality should be provided for the WSDL and XSD editor. This would go a long way to better integration within the tooling. -- 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

12 years, 1 month

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4233) Support for fine grained pages.xml editing

by Max Rydahl Andersen (JIRA)

Support for fine grained pages.xml editing ------------------------------------------ Key: JBIDE-4233 URL: https://jira.jboss.org/jira/browse/JBIDE-4233 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Critical Fix For: 3.1.0.M3 Add support for fine grained page.xml (now we have support for coarse grained pages.xml) in the graphical pages.xml editor. I imagine an additonal tab or a toggle on the current tab that when enabled shows not just the pages that are in the single file, but also includes any info from other *.page.xml files. In the first iteration we can just make this a read only mode for any external files and then double click for editing (maybe that will be too cumbersome for the users ?) -- 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

12 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4727) Support distribution defining "New Project" dependencies

by Pete Muir (JIRA)

Support distribution defining "New Project" dependencies -------------------------------------------------------- Key: JBIDE-4727 URL: https://jira.jboss.org/jira/browse/JBIDE-4727 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Pete Muir Summary: Move the responsibility for defining a "New Seam Project"'s dependencies (libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to define the dependencies. Use Maven POM profiles to support different use cases for Seam projects. Reason: Currently JBoss Tools defines the project dependencies which causes issues very time Seam changes either the dependency set of a new seam project, or the layout of libraries in the distribution. Use Maven 2 POM format as it is already a well defined and understood model. Use of Maven POM profiles can further increase the flexibility and support various use cases for Seam (for example, Seam with jBPM or Seam with ICEFaces). Details: JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml, ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite modules of an EAR project. The standard Maven scopes are used: compile to indicate compile/runtime dependencies of the project, test to indicate extra dependencies required in the test project. Maven profiles are used to define additional dependency sets for new seam projects, allowing the user to optionally add extra dependencies to his project. To make this extensible, and not require JBossTools to use a well-known list of profile ids, an xml namespace will be used to add additional metadata to the profile. This allows JBossTools to identify the possible profiles: <profile> <id>drools5</id> <jbt:profile> <jbt:description>Drools 5 support (Tech Preview)</jbt:description> </jbt:profile>  </profile> <profile> <id>ICEFaces</id> <jbt:profile> <jbt:description>ICEFaces</jbt:description> </jbt:profile>  </profile> JBossTools can recognize the jbt:profile element, and use the jbt:description element to as a descriptive element to present to the user: [x] ICEFaces [x] Drools 5 support (Tech Preview) displayed in the New Seam Project Wizard. We should allow for additional information to be placed in the POM and in the future beyond dependency information. For example, additional configuration files to include in the generated project, however this is not a critical feature. We should also consider allowing JBoss Tools to retrieve the POMs from a Maven repository. This would require a user to simply specify the version of Seam they require, and have JBoss Tools download the seam-gen artifact containing all templates and resources. -- 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

12 years, 1 month

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2010