March 2007 - jbosstools-issues - Jboss List Archives

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-461) Add debug configuration for JBoss 4.2

by Dominik Pospisil (JIRA)

Add debug configuration for JBoss 4.2 ------------------------------------- Key: JBIDE-461 URL: http://jira.jboss.com/jira/browse/JBIDE-461 Project: JBoss IDE Issue Type: Task Affects Versions: 1.6 Reporter: Dominik Pospisil Version 1.6 IDE is to be compatible with Application Platform release. IDE should include specific "JBoss 4.2.x" debug configuration. -- 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

17 years, 1 month

4
8
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-458) Create package NPE (again)

by Max Andersen (JIRA)

Create package NPE (again) -------------------------- Key: JBIDE-458 URL: http://jira.jboss.com/jira/browse/JBIDE-458 Project: JBoss IDE Issue Type: Bug Reporter: Max Andersen clicking create package and i get: java.lang.NullPointerException at org.jboss.ide.eclipse.packages.ui.wizards.pages.PackageInfoWizardPage.validate(PackageInfoWizardPage.java:236) at org.jboss.ide.eclipse.packages.ui.wizards.pages.PackageInfoWizardPage.createControl(PackageInfoWizardPage.java:159) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:180) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:614) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:502) at org.eclipse.jface.window.Window.create(Window.java:426) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1124) at org.eclipse.jface.window.Window.open(Window.java:785) at org.jboss.ide.eclipse.packages.ui.actions.NewJARAction.run(NewJAR -- 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

17 years, 1 month

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-407) Preference page has old logo

by Max Andersen (JIRA)

Preference page has old logo ---------------------------- Key: JBIDE-407 URL: http://jira.jboss.com/jira/browse/JBIDE-407 Project: JBoss IDE Issue Type: Bug Reporter: Max Andersen JBoss Eclipse IDE should be JBoss IDE for Eclipse and have the newer logo. should maybe also have some info text instead of being blank...maybe some general properties ? (no other preference page is as blank ;) -- 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

17 years, 1 month

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-416) EJB3 project wizard is not very informative

by Max Andersen (JIRA)

EJB3 project wizard is not very informative ------------------------------------------- Key: JBIDE-416 URL: http://jira.jboss.com/jira/browse/JBIDE-416 Project: JBoss IDE Issue Type: Feature Request Reporter: Max Andersen If i have no ejb3 capable server runtimes the combo box in EJB3 project is just empty and have a red text (no where else in eclipse is that used) saying that one should remember to create a server that supports EJB3. We should have a text saying "No server runtimes supporting EJB3 exists" IIF no such thing exist. And then say what "supports EJB3" actually means or what to do ... -- 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

17 years, 1 month

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-415) Have Project Explorer in the JBoss perspective

by Max Andersen (JIRA)

Have Project Explorer in the JBoss perspective ---------------------------------------------- Key: JBIDE-415 URL: http://jira.jboss.com/jira/browse/JBIDE-415 Project: JBoss IDE Issue Type: Feature Request Components: JBossAS Adapter Reporter: Max Andersen Assigned To: Robert Stryker Project Explorer has special nodes for WTP projects (or any other kind of content navigator api based extensions) We should have it available in the jboss perspective, maybe next to Package Explorer since they both have their strengths. e.g. Packages supports current working sets, Project Explorer doesn't Project Explorer supports content navigator api, Packages don't -- 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

17 years, 1 month

3
2
0 / 0

[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

17 years, 3 months

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-390) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBIDE-390 URL: http://jira.jboss.com/jira/browse/JBIDE-390 Project: JBoss IDE Issue Type: Feature Request Reporter: Rajesh Rajasekaran Fix For: 1.6.1, 2.0.0.Beta3 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

17 years, 4 months

2
2
0 / 0

[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

17 years, 4 months

2
1
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-441) Support simplified syntax / format for "class" type in the Query Parameters view

by Joseph Marques (JIRA)

Support simplified syntax / format for "class" type in the Query Parameters view -------------------------------------------------------------------------------- Key: JBIDE-441 URL: http://jira.jboss.com/jira/browse/JBIDE-441 Project: JBoss IDE Issue Type: Feature Request Components: Hibernate Tools Affects Versions: 2.0.0.Beta2 Reporter: Joseph Marques Assigned To: Max Andersen Instead of having to specify the fully-qualified name of the class in the Query Parameter section, it would be nice is the value column support a shorthand of the syntaxmm, so the package could be left out. This way, I can say "Item" instead of "com.very.long.package.name.containing.Item". -- 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

17 years, 4 months

2
3
0 / 0

[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

17 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2007