June 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-474) WTP API for incremental publish possibly incomplete for nested projects

by Rob Stryker (JIRA)

WTP API for incremental publish possibly incomplete for nested projects ----------------------------------------------------------------------- Key: JBIDE-474 URL: http://jira.jboss.com/jira/browse/JBIDE-474 Project: JBoss Tools Issue Type: Task Components: JBossAS Adapter Reporter: Rob Stryker Assigned To: Robert Stryker Awaiting word from WTP mailing list. If it turns out the API is incomplete, a workaround to ensure incremental publishes will be required. -- 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
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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-500) JBoss Tools (nightly) Prevents any Eclipse Plug-in Update

by Todd Flinders (JIRA)

JBoss Tools (nightly) Prevents any Eclipse Plug-in Update --------------------------------------------------------- Key: JBIDE-500 URL: http://jira.jboss.com/jira/browse/JBIDE-500 Project: JBoss Tools Issue Type: Bug Components: EJB3 plugin Environment: Eclipse Europa 3..3 (stable) JBossTools-200706290355-nightly-ALL-linux-gtk java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing) openSUSE 10.2 Linux HQISB-7Y2GF61 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 i686 i386 GNU/Linux Reporter: Todd Flinders Assigned To: Max Andersen After installing the nightly JBoss Tools nightly build on Eclipse 3.3 stable, updates are prevented due to the following error: org.jboss.ide.eclipse.ejb3.feature (1.0.0.200706290355-nightly) requires plug-in "org.eclipse.wst.server.core". It should be noted I'm referring to JBoss Tools nightly build installed by unpacking the zip file downloaded from http://download.jboss.org/jbosstools/builds/nightly/200706290355-nightly/.... This is not to be confused with the JBossIDE Beta 2. The problem can be demonstrated by attempting to install subclipse (for example). The steps to recreate the problem are: 1. Install a fresh Eclipse 3.3. 2. Unzip JBossTools-200706290355-nightly-ALL-linux-gtk to the Eclipse 3.3 directory 3. In Eclipse: Help | Software Updates | Find and Install | Search for new features to install 4. Add a new remote site. In my case I added Subclipse with the update URL of http://subclipse.tigris.org/update_1.2.x 5. Select a feature to install, in my case Subclipse | Subclipse Plugin 6. The error is displayed at the top of the Updates window: org.jboss.ide.eclipse.ejb3.feature (1.0.0.200706290355-nightly) requires plug-in "org.eclipse.wst.server.core". -- 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

5
16
0 / 0

[JBoss JIRA] Created: (JBIDE-497) Edit Hibernate configuration Wizard

by Krasimir Goutcev (JIRA)

Edit Hibernate configuration Wizard ----------------------------------- Key: JBIDE-497 URL: http://jira.jboss.com/jira/browse/JBIDE-497 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Tools Reporter: Krasimir Goutcev Assigned To: Max Andersen -- 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

[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

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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-495) Hibernate configuration can not be created

by Mikle Dryakhlenkov (JIRA)

Hibernate configuration can not be created ------------------------------------------ Key: JBIDE-495 URL: http://jira.jboss.com/jira/browse/JBIDE-495 Project: JBoss Tools Issue Type: Bug Components: Hibernate Tools Environment: MS Windows 2000 Advanced Server. Eclipse 3.3.0 RC4 build id: I20070608-1718. WST Project SDK 2.0.0 v200706041905 & dependency (EMF 2.3.0 v200706200000, GEF 3.3.0 v 20070620) . Plugins from https://svn.jboss.org/repos/jbosstools/trunk/hibernatetools. Reporter: Mikle Dryakhlenkov Assigned To: Max Andersen On creating hibernate configuration in test project https://svn.jboss.org/repos/jbosstools/trunk/hibernatetools/sampleproject... nothing happens. Dialog "Properties for hibernate" with parameters Type: core, Project: org.jboss.tools.hibernate.sampleproject.mappingtypes, Configuration file: \org.jboss.tools.hibernate.sampleproject.mappingtypes\src\hibernate.cfg.xml is closed at pressing button "OK", but configuration not creating. The same actions in the same test project worked correctly in Eclipse 3.2. -- 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

2
3
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, 10 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

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

16 years, 10 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 June 2007