April 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBIDE-509) intelligent navigation support for seam variable names

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-509?page=all ] Max Andersen updated JBIDE-509: ------------------------------- Fix Version/s: 2.1.0.beta1 (was: 2.1) batch update of issues with 2.1 fix instead of the correct 2.1.b1 > intelligent navigation support for seam variable names > ------------------------------------------------------ > > Key: JBIDE-509 > URL: http://jira.jboss.com/jira/browse/JBIDE-509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Seam > Reporter: Max Andersen > Assigned To: Victor Rubezhny > Fix For: 2.1.0.beta1 > > Attachments: ctrl-g-conflict.jpg, ctrl-shift-g-action.jpg, ctrl-shift-g-conflict.jpg, ctrl-shift-g-result.jpg > > > @DataModel > private List<Message> messageList; > @Factory("messageList") > public void findMessages() > { > messageList = em.createQuery("from Message msg order by msg.datetime desc").getResultList(); > } > - link from messageList to its @Factory method, and link from "messageList" to the property. > - ctrl+G shows related locations in .java, .xhtml, components.xml, etc. > Case A: Link from the Seam Variable Name in the @Factory annotation value attribute to its declaration (for example, @Factory("mess|ageList"), where "|" is the current cursor position): > 1.a. User moves the mouse cursor over the Seam Variable Name in the value of the @Factory annotation within the component while Ctrl key is pressed. The variable is highlighted and underlined in the editor. User clicks left mouse button while Ctrl-key still is pressed. > - or - > 1.b. User sets the cursor into or selects the Seam Variable Name in the value of the @Factory annotation within the component and then presses F3 key. > 2. The following steps will be performed: > 2.a. If return type of the selected factory method is void we have to search for the declaration (@Out/@DataBinder) in the same component. If it is found it will be revealed and selected in the editor > (if it is contained in super-class, the appropriate class will be openned in the editor). > 2.b Else if return type of the selected factory method is not void then the factory itself decrares the Seam variable - the factory itself to be selected. > Case B: Link from Seam Variable name used in Seam EL expression (XHTML/XML/Java Strings in JavaEditor) to it's declaration/factory (for example, #{mess|ageList.size}, where "|" is the current cursor position): > 1.a. User moves the mouse cursor over the Seam Variable Name in the Seam EL expression while Ctrl key is pressed. The variable is highlighted and underlined in the editor. User clicks left mouse button while Ctrl-key still is pressed. > - or - > 1.b. User sets the cursor into or selects the Seam Variable Name in the Seam EL expression and then presses F3 key. > 2. The following steps will be performed: > 2.a. The @Name or @Role annotations with the same name will be found in the Seam model of the project. If there will be at least one @Name or @Role annotation found the source file with that annotation will be opened in the editor (or brought to front if the editor is already openned), and the annotation found will be revealed and selected in the editor. > 2.b. If not, The @Factory annotation with the same name will be found in the Seam model of the project. If there will be at least one @Factory annotation found the source file with that annotation will be opened in the editor (or brought to front if the editor is already openned), and the annotation found will be revealed and selected in the editor. > 2.c. If not, The @Out/@DataBinder annotation with the same name will be found in the Seam model of the project. If there will be at least one @Out/@DataBinder annotation found the source file with that annotation will be opened in the editor (or brought to front if the editor is already openned), and the annotation found will be revealed and selected in the editor. > 2.d. If not, no linkage will be performed. Error message will appear in the editor's status line > Case C: Find References of a Seam Variable (Ctrl-Shift-G). > 1. User selects the Seam Variable Name in Seam EL expression (XHTML/JSP/XML files) or in value attribute of annotations @Name/@Role/@Factory/@In/@Out/@DataBinder in component class file or in components.xml file and then presses Ctrl-Shift-G to find the references to variables those name equals the name of selected variable. > 2. The references to selected variable will be searched through the files of Seam model referenced projects (Seam model may contain the references to more that one project), the @In annotation are also to be search. > 3. The Search View will be openned and will show the results of search performed. > Case D: Find Declarations of a Seam Variable (Ctrl-G). > 1. User selects the Seam Variable Name in Seam EL expression (XHTML/JSP/XML files) or in value attribute of annotations @Name/@Role/@Factory/@In/@Out/@DataBinder in component class file or in components.xml file and then presses Ctrl-G to find the declarations of variables named as the selected variable. > 2. The declarations of selected variable will be searched through the Seam model (@Name, @Role, @Out/DataBinder annotations and components.xml files). > 3. The Search View will be openned and will show the results of search performed. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-1793) Can not deploy any files to server at the same time.

by Anton Klimkovich (JIRA)

Can not deploy any files to server at the same time. ---------------------------------------------------- Key: JBIDE-1793 URL: http://jira.jboss.com/jira/browse/JBIDE-1793 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.0.1, 2.1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create JSF 1.2 KickStart project EXECUTE: Select two files using Ctrl button (Screenshot attached) EXECUTE: Right mouse click on selected files and choose Deploy To Server ASSERT: Two files should be added to Server FAILURE: Only first selected file was added. -- 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

18 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1633) Build shold be on one platform, tests run after from the same build

by Max Andersen (JIRA)

Build shold be on one platform, tests run after from the same build ------------------------------------------------------------------- Key: JBIDE-1633 URL: http://jira.jboss.com/jira/browse/JBIDE-1633 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Reporter: Max Andersen Assigned To: Marshall Culpepper shouldnt be necessary to build all the source etc. on every os. -- 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

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1794) NullPointerException at Mapping Diagramm

by Dima Geraskov (JIRA)

NullPointerException at Mapping Diagramm ---------------------------------------- Key: JBIDE-1794 URL: http://jira.jboss.com/jira/browse/JBIDE-1794 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Dima Geraskov Assigned To: Dima Geraskov Fix For: 2.1 If we have mapping when id class not embedded in the entity NullPointer occured when you select id-property at the mapping diagramm. For ex: <class name="Customer"> <composite-id class="CustomerId" mapped="true"> <key-property name="orgName" column="org_name"/> <key-property name="customerName" column="cust_name"/> </composite-id> </class> (See "mapping.idclass" pack in test mapping project ). Persistance class for the property is null. (Properties view demands it). I'll change it to return null (when it threw NullPointerException). But for the Composite properties Diagram uses SpecialPersistanceClas, as properties view demands it, we have here some inconsistency between shown Persistance class in Properties view and real Persistance class (think about Address object - properties view will show it like Persistance class for the street, but real persistance class is null). -- 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

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-894) Clean out jst component

by Denis Golovin (JIRA)

Clean out jst component ----------------------- Key: JBIDE-894 URL: http://jira.jboss.com/jira/browse/JBIDE-894 Project: JBoss Tools Issue Type: Sub-task Affects Versions: 2.0.0.Beta3 Reporter: Denis Golovin Fix For: 2.0.0.Beta4 -- 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

18 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1902) contributing own completion metadata is impossible (contibutions to org.jboss.tools.common.kb.tldResource must come from org.jboss.tools.common.kb)

by Heiner Westphal (JIRA)

contributing own completion metadata is impossible (contibutions to org.jboss.tools.common.kb.tldResource must come from org.jboss.tools.common.kb) --------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1902 URL: http://jira.jboss.com/jira/browse/JBIDE-1902 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.0.0.GA Environment: eclipse 3.3.2 with WTP 2.0.2 on Windows XP Reporter: Heiner Westphal We want to contribute to extension point "org.jboss.tools.common.kb.tldResource" supplying our own meta data in our own plugin. But the schema-location is not interpreted relative to our plugin: org.jboss.tools.common.kb/src/org/jboss/tools/common/kb/KbTldStore.java ... File shemaLocation = new File(kbPluginLocation, location); .. Contributing plugins will not put their schema files inside the org.jboss.tools.common.kb plugin, thus the location should be resolved relative to the contributing plugin, not relative to org.jboss.tools.common.kb. As a workaround I used a path containing ../pluginname_version/...: <?xml version="1.0" encoding="UTF-8"?> <?eclipse version="3.0"?> <plugin> <extension point="org.jboss.tools.common.kb.tldResource"> <tld jsf="true" name="My Components" schema-location="../some.company.jsf.kb.mycomponents_1.0.0/tldschema/MyComponents.xml" uri="http://www.company.some/mycomponents"/> </extension> </plugin> -- 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

18 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1858) Add esb module to build

by Max Andersen (JIRA)

Add esb module to build ----------------------- Key: JBIDE-1858 URL: http://jira.jboss.com/jira/browse/JBIDE-1858 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Max Andersen Assigned To: Marshall Culpepper Fix For: 2.1 -- 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

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1778) Improve updating package structure in Seam project

by Viacheslav Kabanovich (JIRA)

Improve updating package structure in Seam project -------------------------------------------------- Key: JBIDE-1778 URL: http://jira.jboss.com/jira/browse/JBIDE-1778 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Viacheslav Kabanovich Assigned To: Viacheslav Kabanovich Fix For: 2.1 In current implementation, loading each component is followed by exhausting checking of seam package structure. This is redundant and time consuming, loading N components results in ~ N * N checks, which is inadmissible for large projects. 1) Remove exhausting checking of seam package structure. 2) Implement incremental modification of seam package structure at adding/removing/modifying a seam component. Testing: already existing tests for seam model should not fail. -- 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

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1885) Add Context references to JBossTools wizards

by Denis Golovin (JIRA)

Add Context references to JBossTools wizards -------------------------------------------- Key: JBIDE-1885 URL: http://jira.jboss.com/jira/browse/JBIDE-1885 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 2.1 Reporter: Denis Golovin Assigned To: Daniel Azarov Fix For: 2.1 -- 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

18 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1820) Please use the standard Eclipse files for project dependencies the org.jboss.tools.jst.web.xml is a complete mess

by Stephen Westbom (JIRA)

Please use the standard Eclipse files for project dependencies the org.jboss.tools.jst.web.xml is a complete mess ----------------------------------------------------------------------------------------------------------------- Key: JBIDE-1820 URL: http://jira.jboss.com/jira/browse/JBIDE-1820 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Cleanup Affects Versions: 2.0.0.GA Environment: Windows, any really Reporter: Stephen Westbom Priority: Critical The org.jboss.tools.jst.web.xml file duplicates information that is already contained in the .classpath file and the org.eclipse.wst.common.component file in the settings directory and does it pretty badly (no java environment variables supported, it puts jar files in the web-inf/lib directory that Eclipse should do at build time only). This just adds yet another place to configure a project's artifacts, lots of broken project settings because of conflicts and incompatibility with Maven 2. Can this be cleaned up in future releases? It is as if the plugin was built with no prior knowledge of Eclipse. These changes are critical to having a usable tool. Right now I cannot use the plugin for much more than editing JSF pages and building broken deployments. -- 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

18 years, 3 months

4
4
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 April 2008