January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1577) using JBDS as updatesite on eclipse works, but causes outofmemory because of name change

by Max Rydahl Andersen (JIRA)

using JBDS as updatesite on eclipse works, but causes outofmemory because of name change ---------------------------------------------------------------------------------------- Key: JBDS-1577 URL: https://issues.jboss.org/browse/JBDS-1577 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 4.0.0.GA Reporter: Max Rydahl Andersen Not sure if this qualifies as a bug or a feature request but I noticed that if I use JBDS 4 updatesite against plain Eclipse things seem to work great until you restart (possible on the second restart) since then it suddenly has zero extra memory allocated. It only started working properly when using the jbdevstudio.app; thus my assumption is that eclipse.ini is ignored and jbdevstudio.ini is looked for instead but this file is nowhere to be found (except inside jbdevstudio.app) Would be good if we could handle this situation more gracefully since the shortcuts users uses still points to eclipse thus they will see it as JBDS running out of memory since when launching it says JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
22
0 / 0

[JBoss JIRA] (JBIDE-10535) 12 tests skipped in org.jboss.tools.ws.jaxrs.core

by Nick Boldt (Created) (JIRA)

12 tests skipped in org.jboss.tools.ws.jaxrs.core ------------------------------------------------- Key: JBIDE-10535 URL: https://issues.jboss.org/browse/JBIDE-10535 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta1 After switching to newer target platform (JBIDE-10289), 12 tests are being skipped: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... {code} shoudCreateEndpointWhenAddingSubresourceLocatorMethodInSubresource shouldAddResourceFieldWhenAddingFieldAnnotatedWithQueryParam shouldDoNothingMethodWhenAddingAnotherAnnotationOnParameter shouldDoNothingMethodWhenChangingAnotherAnnotationOnParameter shouldDoNothingMethodWhenRemovingAnotherAnnotationOnParameter shouldRemoveResourceWhenRemovingBinaryLib shouldUpdateResourceMethodWhenAddingMatrixParamAnnotationOnParameter shouldUpdateResourceMethodWhenAddingThrowsException shouldUpdateResourceMethodWhenChangingMatrixParamAnnotationOnParameter shouldUpdateResourceMethodWhenChangingThrowsException shouldUpdateResourceMethodWhenRemovingMatrixParamAnnotationOnParameter shouldUpdateResourceMethodWhenRemovingThrowsException {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

6
8
0 / 0

[JBoss JIRA] Created: (JBDS-1669) add org.hamcrest bundle to http://download.jboss.org/jbosstools/updates/indigo/M7/

by Andre Dietisheim (JIRA)

add org.hamcrest bundle to http://download.jboss.org/jbosstools/updates/indigo/M7/ ---------------------------------------------------------------------------------- Key: JBDS-1669 URL: https://issues.jboss.org/browse/JBDS-1669 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 5.0.0.M2 Reporter: Andre Dietisheim Assignee: Nick Boldt how to reproduce: 1) import target-platform project into workspace 2) double click jbds.target 3) in target platform editor: click "Set as Target Platform" link (to the right on the top bar) Result: all jboss tools components but org.jboss.ide.eclipse.as.management.as7.tests compile. org.jboss.ide.eclipse.as.management.as7.tests misses required org.hamcrest bundle (which is available in vanilla eclipse jee edition) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8659) Server adapter doesn't change state after changing the remote host it is connected to

by Andre Dietisheim (JIRA)

Server adapter doesn't change state after changing the remote host it is connected to ------------------------------------------------------------------------------------- Key: JBIDE-8659 URL: https://issues.jboss.org/browse/JBIDE-8659 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.1 Reporter: Andre Dietisheim Assignee: Rob Stryker -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8534) BIRT viewer should respect the locale attribute in an xhtml embedded report

by Dimitris Keramidas (JIRA)

BIRT viewer should respect the locale attribute in an xhtml embedded report --------------------------------------------------------------------------- Key: JBIDE-8534 URL: https://issues.jboss.org/browse/JBIDE-8534 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: birt, JBossAS, Seam Affects Versions: 3.2.0.Final Environment: Windows 7 64-bit (x86), Eclipse Helios, Oracle jvm 1.6.0 update 23/24 (32bit), JBossAS 5.1, Seam 2.2.0, JBoss Tools 3.2.0, Birt Reporting Runtime Component 2.6.2 Reporter: Dimitris Keramidas Assignee: Snjezana Peco I have a simple report, using *.properties files for localization. When using the <b:birt/> tag to integrate the report in a .xhtml file (designType="embed"), the locale attribute is ignored. The documentation states that when using the "embed" parameter, only the designName and masterpage attributes may be used. However, this way the report always defaults to the JVM locale, and there is no - apparent - way to change the locale to match the user's preference. This behaviour does not apply when designType is "run" or "frameset". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
10
0 / 0

[JBoss JIRA] (JBDS-1937) CLONE - EDS Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Larry O'Leary (Created) (JIRA)

CLONE - EDS Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem ------------------------------------------------------------------------------------------------------- Key: JBDS-1937 URL: https://issues.jboss.org/browse/JBDS-1937 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: teiid Affects Versions: 4.1.0.GA Reporter: Larry O'Leary Assignee: Van Halbert Priority: Critical In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-10234) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Larry O'Leary (Created) (JIRA)

Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem ------------------------------------------------------------------------------------------- Key: JBIDE-10234 URL: https://issues.jboss.org/browse/JBIDE-10234 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.1.Final Reporter: Larry O'Leary Assignee: Barry LaFond Priority: Critical Attachments: CountryInfoService.wsdl In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

10
17
0 / 0

[JBoss JIRA] Created: (JBIDE-7783) GWT throws exceptions during Java field rename

by Daniel Azarov (JIRA)

GWT throws exceptions during Java field rename ---------------------------------------------- Key: JBIDE-7783 URL: https://jira.jboss.org/browse/JBIDE-7783 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT Affects Versions: 3.2.0.Beta1 Environment: JBoss Tools + GWT plugins Reporter: Daniel Azarov Assignee: Max Andersen Test case: 1. Start JBDS 2. Create 'test' Java project 3. Create 'test' Java package 4. Create 'Test' Java class in 'test' package 5. Create 'int user' field 6. Select field and right-click on it 7. Select menu Source->Generate Getters and Setters then press OK button 8. Select field and right-click on it 9. Select menu Refactor->Rename then type user2 and press Ctrl+Enter 10. See Error log FAIL: java.lang.ClassCastException: org.eclipse.jdt.internal.core.SourceField cannot be cast to org.eclipse.jdt.core.IMethod at com.google.gwt.eclipse.core.refactoring.GWTRenameParticipant.initialize(GWTRenameParticipant.java:115) at com.google.gwt.eclipse.core.refactoring.GWTRenameMemberParticipant.initialize(GWTRenameMemberParticipant.java:38) at com.google.gwt.eclipse.core.refactoring.rpc.PairedMethodRenameParticipant.initialize(PairedMethodRenameParticipant.java:224) at org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.initialize(RefactoringParticipant.java:105) at org.eclipse.ltk.core.refactoring.participants.ParticipantExtensionPoint.getParticipants(ParticipantExtensionPoint.java:100) at org.eclipse.ltk.core.refactoring.participants.ParticipantManager.loadRenameParticipants(ParticipantManager.java:74) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameModifications.loadParticipants(RenameModifications.java:190) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.loadParticipants(JavaRenameProcessor.java:40) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:233) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) java.lang.ClassCastException: org.eclipse.jdt.internal.core.SourceField cannot be cast to org.eclipse.jdt.core.IMethod at com.google.gwt.eclipse.core.refactoring.GWTRenameParticipant.initialize(GWTRenameParticipant.java:115) at com.google.gwt.eclipse.core.refactoring.GWTRenameMemberParticipant.initialize(GWTRenameMemberParticipant.java:38) at org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.initialize(RefactoringParticipant.java:105) at org.eclipse.ltk.core.refactoring.participants.ParticipantExtensionPoint.getParticipants(ParticipantExtensionPoint.java:100) at org.eclipse.ltk.core.refactoring.participants.ParticipantManager.loadRenameParticipants(ParticipantManager.java:74) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameModifications.loadParticipants(RenameModifications.java:190) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.loadParticipants(JavaRenameProcessor.java:40) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:233) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

7
15
0 / 0

[JBoss JIRA] (JBIDE-10596) Use eclipse-repository packaging type for repository in order to materialize-products from them

by Mickael Istria (Created) (JIRA)

Use eclipse-repository packaging type for repository in order to materialize-products from them ----------------------------------------------------------------------------------------------- Key: JBIDE-10596 URL: https://issues.jboss.org/browse/JBIDE-10596 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Affects Versions: 3.3.0.M5 Environment: any Reporter: Mickael Istria Assignee: Nick Boldt The eclipse-repository packaging type is a better way to go: * It reads "category.xml" files (renamed site.xml files) * It supports the materialize-products action to extract the products from it See http://wiki.eclipse.org/Tycho/Packaging_Types#Creating_Product_Zip_Files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8202) OpenOn for @Inject @Resource(<name>)

by Alexey Kazakov (JIRA)

OpenOn for @Inject @Resource(<name>) ------------------------------------- Key: JBIDE-8202 URL: https://issues.jboss.org/browse/JBIDE-8202 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x See Chapter 5. Resource Loading. For example: @Inject @Resource("WEB-INF/beans.xml") URL beansXml; or @Inject @Resource("WEB-INF/web.xml") Collection<InputStream> webXmls; OpenOn should open the corresponding resource which is to be injected. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
9
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 January 2012