January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9356) NLS.bind vs MessageFormat.format

by Rob Stryker (JIRA)

NLS.bind vs MessageFormat.format -------------------------------- Key: JBIDE-9356 URL: https://issues.jboss.org/browse/JBIDE-9356 Project: Tools (JBoss Tools) Issue Type: Task Components: Cleanup Affects Versions: 3.3.0.M3 Reporter: Rob Stryker Assignee: Max Rydahl Andersen Fix For: 3.3.0.Final A substantial number of classes use NLS.bind(Messages.SomeString, name) to bind message strings. Another subset of the classes use MessageFormat.format(etc). I believe NLS.bind() is the correct solution which works properly with eclipse osgi and all that jazz. Should this be standardized? Is it confusing to be using two interchangable APIs? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (JBDS-1878) Find a way to set up / install EAP6/WFK repos (automatically)

by Fred Bricon (Created) (JIRA)

Find a way to set up / install EAP6/WFK repos (automatically) ------------------------------------------------------------- Key: JBDS-1878 URL: https://issues.jboss.org/browse/JBDS-1878 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: installer, maven Affects Versions: 5.0.0.M2 Reporter: Fred Bricon Fix For: 5.0.0.CR1 We need to find a way to let users easily use the EAP6 / WFK maven repos. Basically, it boils down to 2 use cases : 1 - The user wants to use the repos from his enterprise repository manager 2 - The user wants to install the repos locally Installation / configuration of the repos can be done either via the JBDS installer (Burr's idea) or a JBDS plugin (Max's idea). 1 - If the user chooses to use a remote repo, then may be open a page detailing the required steps to install EAP6/WFK on nexus/artifactory/archiva. I'm not sure this would be necessary since Joe developper will probably won't have the rights to manage his enterprise repo management app. So we might as well bail and assume he has everything configured. 2 - The user chooses to install the repos locally. We can detect if the repos are already configured before continuing : Check if one remote repository already contains specific jars only available in EAP6/WFK repos or look for a specific snippet in the user / global settingsea. - if nothing is found, unzip and either ask the user to change his settings manually (showing him the right xml snippet) or do it automatically for him (by adding a new profile activated by default) Question is : where are the repos coming from? will they be publicly available, i.e. easily downloadable? -- 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

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1797) JBDS doesn't suggest to add not included capabilities if user uses in code or DnD a component from JBoss Tools Pallete

by Andrei Scherbovich (JIRA)

JBDS doesn't suggest to add not included capabilities if user uses in code or DnD a component from JBoss Tools Pallete ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-1797 URL: http://jira.jboss.com/jira/browse/JBIDE-1797 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.1 Reporter: Andrei Scherbovich Priority: Minor JBDS doesn't suggest to add not included capabilities if user uses in code or DnD a component from JBoss Tools Pallete Steps to reproduce: 1. EXECUTE: Create KickStart JSF project 2. EXECUTE: Open hello.jsp page and DnD from JBoss Tools Pallete <rich:calendar> component 3. ASSERT: <%@ taglib uri="http://richfaces.org/rich" prefix="rich"%> inserted by JBDS. But RichFaces capabilities are not available in the project. It would be handy if JBDS suggests to add RichFaces capabilities after 2-nd step e.g. -- 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

13 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4476) Import taglib without the need to create a project.

by Joao Paulo Viragine (JIRA)

Import taglib without the need to create a project. --------------------------------------------------- Key: JBIDE-4476 URL: https://jira.jboss.org/jira/browse/JBIDE-4476 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: JBDS 2 Reporter: Joao Paulo Viragine It would be great if we could import a taglib in JBoss Tools Palette without the need to create a project like described here: http://docs.jboss.org/tools/3.0.1.GA/en/jsf/html_single/index.html#Adding... Just point to a tld or jar file is far enough. -- 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, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8479) html 5 support in Visual Page Editor

by Max Rydahl Andersen (JIRA)

html 5 support in Visual Page Editor ------------------------------------ Key: JBIDE-8479 URL: https://issues.jboss.org/browse/JBIDE-8479 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Visual Page Editor Templates Reporter: Max Rydahl Andersen Assignee: Yahor Radtsevich Fix For: 3.3.x We should look into how much of HTML 5 we can support with current setup or if we need to something different. Opening this jira as a way to gather the various info/conclusions we find. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-9249) Error in Error log when creating JSF2 Kick Start project

by Vlado Pakan (JIRA)

Error in Error log when creating JSF2 Kick Start project -------------------------------------------------------- Key: JBIDE-9249 URL: https://issues.jboss.org/browse/JBIDE-9249 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M2 Environment: Linux 32bit, JDK Sun 1.6.0_25, JBoss AS 6 final, jbdevstudio-product-linux-gtk-5.0.0.v201106231745R-H7-M2 Reporter: Vlado Pakan Assignee: Alexey Kazakov Fix For: 3.3.0.M3 Create JSF2 Kick Start Project. There is this error in Error Log: !MESSAGE Error initializing facelet registry entry (/opt/jboss-6.0.0.Final/server/default/deployers/jsf.deployer/Mojarra-2.0/jsf-libs/jsf-impl-2.0.3-b05.jar!com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml is invalid at line 453, column 52) !STACK 0 org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'span' not found. (file:///opt/jbdevstudio5.0.0.M2/studio/com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml, 453, 52) at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLLoadImpl.java:83) at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:191) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:242) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1511) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.TagModelLoader.loadFromInputStream(TagModelLoader.java:100) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.processJar(JarFileFaceletTaglibLocator.java:239) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.start(JarFileFaceletTaglibLocator.java:128) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.start(JarFileFaceletTaglibLocator.java:1) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor$1.run(ProjectTaglibDescriptor.java:82) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor.initialize(ProjectTaglibDescriptor.java:71) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor.getTagLibraries(ProjectTaglibDescriptor.java:117) at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.initialize(FaceletTagRegistry.java:183) at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getAllTagLibraries(FaceletTagRegistry.java:129) at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getTagLibrary(FaceletTagRegistry.java:230) at org.eclipse.jst.jsf.facelet.core.internal.metadata.FaceletNamespaceMetaDataLocator.locateMetaDataModelProviders(FaceletNamespaceMetaDataLocator.java:53) at org.eclipse.jst.jsf.common.metadata.internal.DomainLoadingStrategy.locateMetaDataSourceInstances(DomainLoadingStrategy.java:143) at org.eclipse.jst.jsf.common.metadata.internal.DomainLoadingStrategy.load(DomainLoadingStrategy.java:55) at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModel.load(MetaDataModel.java:93) at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelManager.loadMetadata(MetaDataModelManager.java:147) at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelManager.getModel(MetaDataModelManager.java:90) at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getMDModel(MetaDataQueryHelper.java:124) at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getModel(MetaDataQueryHelper.java:59) at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getEntities(MetaDataQueryHelper.java:69) at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getEntity(MetaDataQueryHelper.java:64) at org.eclipse.jst.jsf.metadataprocessors.MetaDataEnabledProcessingFactory.getAttributeValueRuntimeTypeFeatureProcessors(MetaDataEnabledProcessingFactory.java:100) at org.eclipse.jst.jsf.metadataprocessors.MetaDataEnabledProcessingFactory.getAttributeValueRuntimeTypeFeatureProcessors(MetaDataEnabledProcessingFactory.java:146) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateNonELAttributeValue(AttributeValidatingStrategy.java:660) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:637) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:184) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:166) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:142) at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateTag(XMLViewDefnValidator.java:99) at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateRegions(XMLViewDefnValidator.java:177) at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateView(XMLViewDefnValidator.java:134) at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validateFile(HTMLValidator.java:158) at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:108) at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669) at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299) at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:106) at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:65) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:75) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:88) at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219) at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178) at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'span' not found. (file:///opt/jbdevstudio5.0.0.M2/studio/com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml, 453, 52) at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLHandler.java:1777) at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:1023) at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:1001) at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:712) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1363) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181) ... 57 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
5
0 / 0

[JBoss JIRA] (JBDS-1919) Uninstaller leaves behind empty jbdevstudio folder

by Nick Boldt (Created) (JIRA)

Uninstaller leaves behind empty jbdevstudio folder -------------------------------------------------- Key: JBDS-1919 URL: https://issues.jboss.org/browse/JBDS-1919 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 4.1.1.GA, 5.0.0.M4 Environment: Seen on Win7_64 w/ JDK 6u25 32-bit. May occur on other platforms too. Reporter: Nick Boldt Fix For: 5.0.0.Beta1 See JBDS-1918 for steps to repro. This might be an izpack bug or an installer/uninstaller config bug, but either way the install folder - though empty - persists after installation. If you double-click the uninstaller.jar, you'll end up with ~/jbdevstudio/ and ~/jbdevstudio/Uninstaller (both empty folders). If you run the uninstaller from the icon (having tweaked it as follows first), you'll get just the ~/jbdevstudio folder. {code} Target: "C:\Users\nboldt\jbdevstudio/Uninstaller\uninstaller.jar" Start in: (leave blank) {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

7
9
0 / 0

[JBoss JIRA] Created: (JBDS-1631) 3rd party cert: testng 6.0

by Nick Boldt (JIRA)

3rd party cert: testng 6.0 -------------------------- Key: JBDS-1631 URL: https://issues.jboss.org/browse/JBDS-1631 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Reporter: Nick Boldt Fix For: 5.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1627) 3rd party certification for JBDS 5.x

by Nick Boldt (JIRA)

3rd party certification for JBDS 5.x ------------------------------------ Key: JBDS-1627 URL: https://issues.jboss.org/browse/JBDS-1627 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 4.x We should define what kind of certifications we want and then certify 3rd party plugins with JBDS Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees. For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9400) Tooling shows warning for Seam 3 Persistence created EntityManager injection

by Cody Lerum (JIRA)

Tooling shows warning for Seam 3 Persistence created EntityManager injection ---------------------------------------------------------------------------- Key: JBIDE-9400 URL: https://issues.jboss.org/browse/JBIDE-9400 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Cody Lerum Assignee: Alexey Kazakov Create SMPC in Seam 3 Persistence module as shown here http://docs.jboss.org/seam/3/persistence/latest/reference/en-US/html/pers... @Inject EntityManager em; Shows "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]" warning -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
7
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