[jbosside-issues] [JBoss JIRA] Created: (JBIDE-424) Blank page in NewSessionBeanWizard when nothing is selected
by Max Andersen (JIRA)
Blank page in NewSessionBeanWizard when nothing is selected
-----------------------------------------------------------
Key: JBIDE-424
URL: http://jira.jboss.com/jira/browse/JBIDE-424
Project: JBoss IDE
Issue Type: Patch
Components: EJB3 plugin
Affects Versions: 2.0.0.Beta2
Reporter: Max Andersen
Assigned To: Marshall Culpepper
Found this during the demo at JBW.
When nothing is selected one gets a blank wizard page. Here is the patch i made against JBW_BERLIN tag.
### Eclipse Workspace Patch 1.0
#P org.jboss.ide.eclipse.ejb3.wizards.ui
Index: src/main/org/jboss/ide/eclipse/ejb3/ui/wizards/pages/NewSessionBeanWizardPage.java
===================================================================
RCS file: /cvsroot/jboss/jbosside/ejb3/plugins/org.jboss.ide.eclipse.ejb3.wizards.ui/src/main/org/jboss/ide/eclipse/ejb3/ui/wizards/pages/NewSessionBeanWizardPage.java,v
retrieving revision 1.2
diff -u -r1.2 NewSessionBeanWizardPage.java
--- src/main/org/jboss/ide/eclipse/ejb3/ui/wizards/pages/NewSessionBeanWizardPage.java 6 Nov 2006 17:18:38 -0000 1.2
+++ src/main/org/jboss/ide/eclipse/ejb3/ui/wizards/pages/NewSessionBeanWizardPage.java 29 Nov 2006 10:40:42 -0000
@@ -173,7 +173,7 @@
setControl(composite);
IJavaElement element = getInitialJavaElement(selection);
- if (element.getElementType() == IJavaElement.PACKAGE_FRAGMENT)
+ if (element!=null && element.getElementType() == IJavaElement.PACKAGE_FRAGMENT)
// || element.getElementType() == IJavaElement.PACKAGE_FRAGMENT_ROOT)
{
beanPackageName.setText(element.getElementName());
--
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, 9 months
[JBoss JIRA] Created: (JBIDE-471) JBoss IDE beta update site installation rejects Eclipse 3.3 Mx (... requires feature "org.eclipse.platform (3.2.0)", or equivalent)
by Arjan van Bentem (JIRA)
JBoss IDE beta update site installation rejects Eclipse 3.3 Mx (... requires feature "org.eclipse.platform (3.2.0)", or equivalent)
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-471
URL: http://jira.jboss.com/jira/browse/JBIDE-471
Project: JBoss IDE
Issue Type: Bug
Components: JBossIDE Core
Affects Versions: 2.0.0.Beta2
Environment: Win32, Eclipse 3.3 M6
Reporter: Arjan van Bentem
Assigned To: Marshall Culpepper
JBoss IDE 2.0.0.Beta2 installs fine when using the update site http://download.jboss.org/jbosside/updates/development/ in Eclipse 3.2.x. However, apparently it has some hardcoded reference to a specific Eclipse version number: when using the same update site URL in Eclipse 3.3 M6 then installation halts with the errors listed at the end of this issue.
Maybe somehow relaxing the required Eclipse version will simply enable using the update site in Eclipse 3.3.x as well?
ONLY for the sake of the archives:
I did not try installing the latest version from CVS.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102699 notes something about the dependencies in feature.xml. However, note that simply changing match="equivalent" in feature.xml is NOT sufficient. For example, the following will NOT work:
- install Web Standard Tools (WST) and J2EE Standard Tools (JST) using Help, Software Updates, Find and Install
- download a non-bundle version (such as JBossIDE-2.0.0.Beta2-ALL.zip) and unzip
- in the unzipped folder, in each feature.xml file, replace each occurrence match="equivalent" with match="greaterOrEqual"
- add a local update site using Help, Software Updates, Find and Install, and make it point to the "eclipse" subfolder of the unzipped archive (note that Eclipse caches the feature details; Eclipse needs to be restarted when changing feature.xml on the fly).
Now, all SEEMS to install fine, but it does not run as expected: some plugins are missing, and when in configuration/config.ini the line "eclipse.product=org.eclipse.sdk.ide" is replaced with "eclipse.product=org.jboss.ide.eclipse.product.product" and "jbosside.version=2.0.0.Beta2" then Eclipse does not startup (logs are created though).
JST Common Core (1.5.1.v200608082030--0842282_363739) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Server Core (1.5.1.v200608082030--2PD88P8UBJx787) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Web Core (1.5.1.v200608082030--87cMN7NRVeVWXd) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Enterprise Core (1.5.1.v200609051533--2PD88P8YAGDADJ) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Enterprise UI (1.5.1.v200608082030-pEBq_haA1H4sJf6) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Server Core (1.5.1.v200608082030------1G955G5L7D) requires feature "org.eclipse.rcp (3.2.0)", or equivalent.
WST XML Core (1.5.1.v200608082030--3YIAAYAjGLENFH) requires feature "org.eclipse.rcp (3.2.0)", or equivalent.
WST Web Services Core (1.5.1.v200608082030--4hNDDhDvGTJSLf) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Web Core (1.5.1.v200608082030--4hNDDhDvKRFXQM) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Relational Database Core (1.5.1.v200608082030--3YIAAYAeEKFTFU) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Relational Database Adapters (1.5.1.v200608082030--Cq0bcpdJw4teC8) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JBossIDE JBossAS Adapter Feature (1.0.0.Beta2) requires plug-in "org.eclipse.ui.workbench.texteditor (3.2.0)", or equivalent.
--
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, 10 months
[jbosside-issues] [JBoss JIRA] Created: (JBIDE-440) Enable first-class support of Enum types in the Query Parameters view
by Joseph Marques (JIRA)
Enable first-class support of Enum types in the Query Parameters view
---------------------------------------------------------------------
Key: JBIDE-440
URL: http://jira.jboss.com/jira/browse/JBIDE-440
Project: JBoss IDE
Issue Type: Feature Request
Components: Hibernate Tools
Affects Versions: 2.0.0.Beta2
Reporter: Joseph Marques
Assigned To: Max Andersen
Granted, Enums are persisted as either ints or strings, but that doesn't mean that the Query Parameters view can't support Enums as a first-class construct in the Type column. I suppose there are a few different ways to support this, but let me explain the semantics that I think would make the most sense for supreme usability:
Select "enum" for the "Type" column
Then you specify the class in the "Value" column (identical to how it works when "class" is selected for the "Type" column)
Then, the tools should be able to be clever enough to read the mapping strategy for this enum based on the context of where it is being used in the corresponding hql/jpql statement. The tools would then map the Enum class to it's appropriate int or string representation during query translation / execution. This allows the query writer to be more effective because he/she wouldn't have to know the actual enum mapping strategy to be able to mock up and test the query.
--
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, 10 months
[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
16 years, 10 months
[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
16 years, 10 months
[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
16 years, 10 months