April 2007 - jbosstools-issues - Jboss List Archives

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-466) XDoclet not implementing generics in generated EJB Interfaces

by iamapony (JIRA)

XDoclet not implementing generics in generated EJB Interfaces ------------------------------------------------------------- Key: JBIDE-466 URL: http://jira.jboss.com/jira/browse/JBIDE-466 Project: JBoss IDE Issue Type: Bug Components: EJB3 plugin Affects Versions: 2.0.0.Beta2 Environment: Windows XP, Eclipse 3.2.1, JBoss IDE 2.0.0.Beta2 Reporter: iamapony Assigned To: Max Andersen In an EJB BeanImpl the method reads: public List<MyInfo> getMyInfo() {...} When XDoclet is used to generate the interface the resulting method signature is: public List getMyInfo() throws java.rmi.RemoteException; The method signature in the interface SHOULD be: public List<MyInfo> getMyInfo() throws java.rmi.RemoteException; >From the forum post, it looks like this was fixed in 1.5, but somehow the fix didn't get into 2.0.0.Beta2 -- 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, 7 months

3
3
0 / 0

[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

16 years, 7 months

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

16 years, 7 months

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

16 years, 7 months

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

16 years, 7 months

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

16 years, 7 months

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

16 years, 8 months

2
1
0 / 0

[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, 9 months

3
4
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

16 years, 9 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

16 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2007