February 2012 - jbosstools-issues

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

10
17
0 / 0

[JBoss JIRA] (JBIDE-10781) Wrong warning message

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-10781: ---------------------------------- Summary: Wrong warning message Key: JBIDE-10781 URL: https://issues.jboss.org/browse/JBIDE-10781 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.3.0.M5 Reporter: Pavol Srna Assignee: Robert (Bob) Brodt Fix For: 3.3.0.Beta1 Attachments: bpel-screen.png -- 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, 10 months

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

7
15
0 / 0

[JBoss JIRA] (JBIDE-10964) use "-Dmaven.test.failure.ignore=true" in component jobs to make test failures appear yellow instead of red

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10964: ---------------------------------- Summary: use "-Dmaven.test.failure.ignore=true" in component jobs to make test failures appear yellow instead of red Key: JBIDE-10964 URL: https://issues.jboss.org/browse/JBIDE-10964 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 3.3.0.CR1 We'd like to see "unstable" (yellow) when tests fail, not "failed" (red). This will also mean checking for missing TEXT-*.xml files (recursing through ${WORKSPACE}/sources/tests/ looking for plugins' target/ folders to see that every test plugin has at least 1 TEST-*.xml file) and generating empty ones should there be an eclipse crash before a test results file can be generated. An empty file should at least alert developers that there's a possible problem w/ their test (or more likely, it's a slave / vnc issue, like JBIDE-10960). -- 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, 10 months

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

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-2707) Extend seam functionality to cover webbeans core

by Max Rydahl Andersen (JIRA)

Extend seam functionality to cover webbeans core ------------------------------------------------ Key: JBIDE-2707 URL: https://jira.jboss.org/jira/browse/JBIDE-2707 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER We need to find a way to have Seam 3/webbeans support; hopefully using the exisiting infrastructure but updated to work with webbeans annotation based way of working. e.g. scopes are not limited, look for @ScopeType in classpath to find them -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6608) Ability to remove drools nature from project

by Libor Zoubek (JIRA)

Ability to remove drools nature from project -------------------------------------------- Key: JBIDE-6608 URL: https://jira.jboss.org/browse/JBIDE-6608 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.1.0.GA Reporter: Libor Zoubek Assignee: Kris Verlaenen Regarding to http://community.jboss.org/message/552490 at this time, there is no possibility to remove drools "nature" (as it is probably not the nature in sense of eclipse nature) We should be able to remove drools from project. Menu item 'Convert to drools project' should be called 'Add drools nature' and when a project has a drools nature it should be called 'Remove drools nature'. Maybe it would be good, not to have 'Convert to drools project' menu item in main context menu, but move it into 'Configure' submenu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
17
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 February 2012