June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11326) Error in log when selected Seam 2.2 facet with JSF 2.0

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11326: --------------------------------------- Summary: Error in log when selected Seam 2.2 facet with JSF 2.0 Key: JBIDE-11326 URL: https://issues.jboss.org/browse/JBIDE-11326 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Environment: JBDS Beta1e EPP 5.2, EPP 4, Gatein Reporter: Lucia Jelinkova Assignee: Alexey Kazakov Fix For: 3.3.0.CR1 When I create a Dynamic web project with Seam 2.2 facet and JSF 2.0 facet and wait until the build finishes the following error is logged into Error log: {code} ava.io.FileNotFoundException: /home/ljelinko/work/jbds/5.0.0.Beta1e/META-INF/facelet-taglib_1_0.dtd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:120) at org.eclipse.emf.ecore.resource.impl.FileURIHandlerImpl.createInputStream(FileURIHandlerImpl.java:105) at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:350) at org.eclipse.emf.ecore.xmi.impl.XMLHandler.resolveEntity(XMLHandler.java:810) at com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(EntityResolverWrapper.java:107) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntityAsPerStax(XMLEntityManager.java:1018) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1192) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1090) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1003) 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) 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:695) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:672) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:186) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:168) at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:144) 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.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) {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

11 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6878) Seam does not work with JSF 2.0 faces-config.xml

by Alexey Kazakov (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBIDE-6878 URL: https://jira.jboss.org/browse/JBIDE-6878 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x This is an issue of Seam runtime. See https://jira.jboss.org/browse/JBSEAM-4637 But let's have a duplicate it in JBT JIRA to track JBSEAM-4637 -- 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

11 years, 5 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-9950) birt: ajax rendering does not work

by u j (Created) (JIRA)

birt: ajax rendering does not work ---------------------------------- Key: JBIDE-9950 URL: https://issues.jboss.org/browse/JBIDE-9950 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Affects Versions: 3.3.0.M3 Reporter: u j Assignee: Snjezana Peco When ajax-rendering a b:birt component in a JSF application (not Seam), the parameters b:param are not sent to Birt, so you get 10:33:54,187 SEVERE [org.jboss.tools.birt] (ajp-127.0.0.1-127.0.0.1-8009-1) the value of parameter estabId is invalid: org.eclipse.birt.core.exception.CoreException: Can not convert the value of to Integer type. at org.eclipse.birt.core.data.DataTypeUtil.toInteger(DataTypeUtil.java:276) [org.eclipse.birt.runtime_3.7.1.v20110913-1734.jar:] at org.jboss.tools.birt.servlet.JBossBirtServlet.stringToObject(JBossBirtServlet.java:183) [jboss-birt-servlet.jar:] at org.jboss.tools.birt.servlet.JBossBirtServlet.evaluateParameterValues(JBossBirtServlet.java:142) [jboss-birt-servlet.jar:] at org.jboss.tools.birt.servlet.JBossBirtServlet.doGet(JBossBirtServlet.java:108) [jboss-birt-servlet.jar:] at org.jboss.tools.birt.servlet.JBossBirtServlet.doPost(JBossBirtServlet.java:123) [jboss-birt-servlet.jar:] This happens e.g. in a popup or a collapsiblePanel (RichFaces). -- 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

11 years, 5 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-11601) outdated DOCTYPE used in Hibernate Mapping file

by Simon Lo (JIRA)

Simon Lo created JBIDE-11601: -------------------------------- Summary: outdated DOCTYPE used in Hibernate Mapping file Key: JBIDE-11601 URL: https://issues.jboss.org/browse/JBIDE-11601 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Windows 7, Eclipse Indigo SR2, JBoss Tools 3.3 beta Reporter: Simon Lo Priority: Optional The generated hbm file using http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd as dtd location, which was giving a warning log when using along with Hibernate 3.6. However, I can't find any options that I could choose which DTD location to use, or anywhere I can modify this template. -- 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

11 years, 5 months

6
21
0 / 0

[JBoss JIRA] Created: (JBIDE-9106) Adding SQLServerMetaDataDialect to support auto discovery of Identity and guid strategy

by Derk Dukker (JIRA)

Adding SQLServerMetaDataDialect to support auto discovery of Identity and guid strategy --------------------------------------------------------------------------------------- Key: JBIDE-9106 URL: https://issues.jboss.org/browse/JBIDE-9106 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.3.0.M1, LATER Reporter: Derk Dukker Assignee: Max Rydahl Andersen Reverse engineering the MS SQLServer database with hibernate tools does not auto discover the identity fields and uniqueidentifier (guid) fields. So when generated the entities the only annotation you will see is @id. I created a new meta data dialect to discover identity and guid fields. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

7
19
0 / 0

[JBoss JIRA] (JBIDE-12208) clean up update sites on download.jboss.org

by Nick Boldt (JIRA)

11 years, 5 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-11217) Forge: present verbose mode functionality in Forge JBT/JBDS Tooling

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-11217: ---------------------------------- Summary: Forge: present verbose mode functionality in Forge JBT/JBDS Tooling Key: JBIDE-11217 URL: https://issues.jboss.org/browse/JBIDE-11217 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Pavol Srna Assignee: Koen Aers Fix For: 3.3.0.CR1 You can run the command: 'set VERBOSE true' in forge running from standard command line. This is not possible/working in JBDS/JBT Forge console. It would be very helpful to have some preference option where you can turn ON/OFF the verbose mode and probably log all the exceptions to the Eclipse Error log. What do you think? -- 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

11 years, 5 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-12094) Add the JBoss Nexus catalog to the maven core plugin

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12094: ----------------------------------- Summary: Add the JBoss Nexus catalog to the maven core plugin Key: JBIDE-12094 URL: https://issues.jboss.org/browse/JBIDE-12094 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.3.0.CR1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.1 We should add the JBoss catalog to mitigate the loss of functionality caused by JBIDE-12066 : even though jars won't be found anymore, archetypes will still be usable. We need to add the following to our plugin.xml: {code:xml} <extension point="org.eclipse.m2e.core.archetypeCatalogs"> <remote url="https://repository.jboss.org/nexus/content/repositories/releases/archetyp..." description="JBoss Releases Catalog"/> </extension> {code} But that depends on the catalog being available. It's currently broken : JBBUILD-718 -- 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

11 years, 5 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-12127) Provide aggregated report for tests

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12127: -------------------------------------- Summary: Provide aggregated report for tests Key: JBIDE-12127 URL: https://issues.jboss.org/browse/JBIDE-12127 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Mickael Istria Fix For: 3.4.x As requested per JBIDE-11784 , we need to see an aggregated view of the test trend for all components, in order to have a view of how quality evolves. This can be achieved by a Dashboard chart on Jenkins, but it has some limitations. See https://issues.jenkins-ci.org/browse/JENKINS-14045 . -- 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

11 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2720) Need 64-bit windows support

by Samuel Mendenhall (JIRA)

Need 64-bit windows support --------------------------- Key: JBIDE-2720 URL: https://jira.jboss.org/jira/browse/JBIDE-2720 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Samuel Mendenhall Fix For: 3.0.0.alpha, 2.1.2, 2.1.1, 2.1.0.GA JBoss Tools is not usable on a 64-bit Windows machine. -- 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

11 years, 5 months

15
54
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2012