July 2007 - jbosstools-issues - Jboss List Archives

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-436) Support comment-naming of tabs in the Hibernate Query Result view

by Joseph Marques (JIRA)

Support comment-naming of tabs in the Hibernate Query Result view ----------------------------------------------------------------- Key: JBIDE-436 URL: http://jira.jboss.com/jira/browse/JBIDE-436 Project: JBoss IDE Issue Type: Feature Request Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen Let's pretend some long query looks like this: "select a from A a inner join a.bs b inner join b.cs c where b.nested.prop = :bval and c.nested.prop = :cval" When I execute this query a tab is created in the Hibernate Query Result view with the title equal to the entire query itself. I propose that the HQL editor allow some simple form of comments above the query, which will then act as logic name for the tab. In other words: // A.getAsByComplexBCSubselect "select a from A a inner join a.bs b inner join b.cs c where b.nested.prop = :bval and c.nested.prop = :cval" Then, if the user highlights both of these lines, he is intentioning that he wants the tab to be named by using the contents in the first line comment. And if the first line isn't a comment, well then you could always default back to the classic functionality of putting the entire query into the tab title. Optionally, if the user doesn't have a specific name for it, but still doesn't want a tab that spans the entire length of the IDE, he could use something like: // "select a from A a inner join a.bs b inner join b.cs c where b.nested.prop = :bval and c.nested.prop = :cval" to intimate that he wants the tab to show up as something short. It could be as simple as "unnamed1", "unnamed2", "unnamed3", etc, just as long as it's short and sweet and allows for more than one tab title to be seen simultaneously for long queries. -- 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, 8 months

2
2
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-437) Support @NamedQuery auto-completion and syntax-highlighting when query is broken across lines

by Joseph Marques (JIRA)

Support @NamedQuery auto-completion and syntax-highlighting when query is broken across lines --------------------------------------------------------------------------------------------- Key: JBIDE-437 URL: http://jira.jboss.com/jira/browse/JBIDE-437 Project: JBoss IDE Issue Type: Feature Request Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen Currently, the auto-completion and syntax-highlighting for @NamedQuery annotations works great, but only if the entire query is in a single-line string. On a daily basis I deal with queries that are almost never under 200 characters in length. This makes writing queries on a single-line extremely awkward. However, as soon as I break any part of the query to a new line, I also break Hibernate's annotation processing. So I'm looking for the best of both worlds here - syntax highlighting when the query is split across an arbitrary number of lines. -- 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, 8 months

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-438) Support sorting/grouping of the items in the Session Factory section of the Hiberate Configurations view

by Joseph Marques (JIRA)

Support sorting/grouping of the items in the Session Factory section of the Hiberate Configurations view -------------------------------------------------------------------------------------------------------- Key: JBIDE-438 URL: http://jira.jboss.com/jira/browse/JBIDE-438 Project: JBoss IDE Issue Type: Feature Request Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen I'm working with a domain model that has over 100 entities. It would be nice to have a consistent ordering of these items...maybe based off of the fully-qualified class name? It would be even nicer if they could be grouped by their different packages, which is how I've more naturally navigated to them in the past. Of course the packages should also be alpha-sorted, and each each of entities within a package sorted as well. -- 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, 8 months

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-434) support configurable strategy for "format HQL" function in HQL editor

by Joseph Marques (JIRA)

support configurable strategy for "format HQL" function in HQL editor --------------------------------------------------------------------- Key: JBIDE-434 URL: http://jira.jboss.com/jira/browse/JBIDE-434 Project: JBoss IDE Issue Type: Feature Request Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen I use the HQL editor to mock up new JPQL statements, and then copy and paste them from there over into some @NamedQuery definition on the appropriate class. Persons responsible for maintaining multiple back-end codebases, or those motivated individuals that have personal projects on the side, might have to adhere to multiple code conventions across these different bases. In order to facilitate more control in this arena, which I believe would also add significant value to the tool, the HQL editor could support formatting statements based on a configurable strategy. Here are some suggestions: 1) Alias with "AS" - yes / no - determines whether all aliases should have "AS" inserted before it, if missing, or not 2) Captialization - ALLCAPS / allsmall / Firstletter 3) Relationship syntax - legacy / modern - determine whether inner joins shoudl be "IN (obj.relationships) rel" / "INNER JOIN obj.relationships rel 4) Explicit inner/outer - yes/no - determine whether the optional "inner" and "outer" keywords should be part of the formatted hql/jpql But that's just to start. In an ideal world, every part of the formatting would be configurable (similar to how Eclipse offers extermely flexible code formatting) including: * before / after / or both before & after what hql/jpql keywords the statement should break to the next line * whether aliases should be automatically introduced (when they don't exist) for better readability -- 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, 8 months

2
2
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-435) Error message when opening HQL editor from the Hibernate Configurations view

by Joseph Marques (JIRA)

Error message when opening HQL editor from the Hibernate Configurations view ---------------------------------------------------------------------------- Key: JBIDE-435 URL: http://jira.jboss.com/jira/browse/JBIDE-435 Project: JBoss IDE Issue Type: Bug Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen If you don't explicitly select some Configuration from the HIbernate Configurations view before clicking on the "Open HQL Editor" in the upper-right hand side of that view, you'll get an Eclipse error msg box that reads "An Error has occurred. See error log for more details." At this very least, this can be handled more gracefully as a warning. Though, it would be nice to see the icon/button greyed out / made inactive if some configuration is not selected. This way, the HQL Editor can't be opened unless some configuration is selected. To really polish it off, if there is only one Configuration defined, then the HQL editor should automatically default to that one. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBIDE-298) Problem with SEAM skeleton generator and column char(1)

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-298?page=all ] Max Andersen closed JBIDE-298. ------------------------------ Resolution: Out of Date seam templates are completly different now > Problem with SEAM skeleton generator and column char(1) > ------------------------------------------------------- > > Key: JBIDE-298 > URL: http://jira.jboss.com/jira/browse/JBIDE-298 > Project: JBoss Tools > Issue Type: Bug > Components: Hibernate > Affects Versions: 1.5.1 > Environment: windows XP , Eclipse, JBoss, ASA9 > Reporter: Ivan Rosina > > The reverse engineering tool for Seam skeleton generator generate getter methods with a return type of char for database columns of type char(1). > In the corresponding finder Bean class the return type is checked against a null value: this is obviously a problem for a primitive type. -- 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, 8 months

1
0
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-433) support case-insensitive hql/jpql syntax highlighting in HQL editor

by Joseph Marques (JIRA)

support case-insensitive hql/jpql syntax highlighting in HQL editor ------------------------------------------------------------------- Key: JBIDE-433 URL: http://jira.jboss.com/jira/browse/JBIDE-433 Project: JBoss IDE Issue Type: Feature Request Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen Currently, the HQL editor only changes hql/jpql keywords to maroon/purple-ish if the entire word is lower-case. Some people like to put all keywords in caps. Others prefer the first letter of the word to be capitalized. It would be nice to see a case-insensitive coloring strategy to give a more natural, user-friendly feel to the HQL editor that satisfies a variety of these tastes. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-594) Invalid thread access in New Seam Project Wizard

by Max Andersen (JIRA)

Invalid thread access in New Seam Project Wizard ------------------------------------------------- Key: JBIDE-594 URL: http://jira.jboss.com/jira/browse/JBIDE-594 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen Assigned To: Denis Golovin fill in the details, click finish and I get the following: org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:3547) at org.eclipse.swt.SWT.error(SWT.java:3465) at org.eclipse.swt.SWT.error(SWT.java:3436) at org.eclipse.swt.widgets.Widget.error(Widget.java:438) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:377) at org.eclipse.swt.widgets.Control.setEnabled(Control.java:3159) at org.eclipse.jface.wizard.WizardDialog.updateButtons(WizardDialog.java:1247) at org.eclipse.jface.wizard.WizardPage.setPageComplete(WizardPage.java:299) at org.jboss.tools.seam.ui.internal.project.facet.DataModelValidatorDelegate.validateUntillError(DataModelValidatorDelegate.java:76) at org.jboss.tools.seam.ui.internal.project.facet.DataModelValidatorDelegate.propertyChanged(DataModelValidatorDelegate.java:68) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:346) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:337) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:183) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172) at org.jboss.tools.seam.internal.core.project.facet.SeamFacetInstallDelegete.execute(SeamFacetInstallDelegete.java:152) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1201) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:394) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:288) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:270) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-602) hook into JSF WTP facet install to enable our JSF features

by Max Andersen (JIRA)

hook into JSF WTP facet install to enable our JSF features ---------------------------------------------------------- Key: JBIDE-602 URL: http://jira.jboss.com/jira/browse/JBIDE-602 Project: JBoss Tools Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen Fix For: 2.0.0.Beta4 the best option ? -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBIDE-622) Obsolete Menu

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-622?page=all ] Viacheslav Kabanovich resolved JBIDE-622. ----------------------------------------- Resolution: Done > Obsolete Menu > ------------- > > Key: JBIDE-622 > URL: http://jira.jboss.com/jira/browse/JBIDE-622 > Project: JBoss Tools > Issue Type: Bug > Environment: nightly build 200707261652-nightly > Reporter: Krasimir Goutcev > Assigned To: Viacheslav Kabanovich > > when do right click on some files there is menuItem > Red Hat Developer Studio -> Verify > Run > Generate Java Code -- 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, 8 months

1
0
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 July 2007