June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12130) OpenShift Explorer: Port forwarding on multiple application selection doesn't work

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12130: -------------------------------------- Summary: OpenShift Explorer: Port forwarding on multiple application selection doesn't work Key: JBIDE-12130 URL: https://issues.jboss.org/browse/JBIDE-12130 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 With multiple applications selected in OpenShift Explorer and clicked on Port forwading, actually only 1 port forwarding dialog is shown and starts port forwarding only on 1 application. Others are ignored, so we should probably disable port forwarding on multiple selection. -- 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
4
0 / 0

[JBoss JIRA] (JBDS-2200) Incorrect(?) version of BPEL feature in CR1b/SOA Tooling Beta3

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2200: ---------------------------------- Summary: Incorrect(?) version of BPEL feature in CR1b/SOA Tooling Beta3 Key: JBDS-2200 URL: https://issues.jboss.org/browse/JBDS-2200 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.Beta3-SOA Environment: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta3.soa... Version: 5.0.0.CR1 Build id: v20120605-2229-H183-CR1 Build date: 20120605-2229 Reporter: Len DiMaggio Assignee: Douglas Palmer Fix For: 5.0.0.CR1 Incorrect(?) version of BPEL feature in CR1b/SOA Tooling Beta3 The runtime plugins match - but "BPEL Commons" and "BPEL Visual Designer" are not in the list displayed here: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta3.soa... And their version numbers don't match com.jboss.jbds.bpel.feature ============================ As displayed in Software Update in CR1b * BPEL Commons 1.0.0.v20120518-1552-H175-CI BPEL Editor 1.1.0.v20120606-2044-H7-Beta3-SOA * BPEL Visual Designer 1.0.0.v20120518-1552-H175-CI Graphical Editing Framework Draw2d 3.7.2.v20110927-2020-4617w3122212803131 Graphical Editing Framework Zest Visualization Toolkit 1.3.0.v20110425-2050-67A18yF6F18CBD5A7N54242 JBoss Developer Studio - Central Discovery - SOA Tooling 1.0.0.v20120606-2044-H7-Beta3-SOA JBoss Drools Core 5.3.2.201206060351 JBoss Drools Guvnor 5.3.2.201206060351 JBoss Drools Task 5.3.2.201206060351 JBoss ESB Tools 1.5.0.v20120606-1401-H7-Beta3-SOA JBoss jBPM Core 5.3.2.201206060351 JBoss jBPM Task 5.3.2.201206060351 JBoss Runtime Drools Detector 1.3.0.v20120606-1603-H4-Beta3-SOA JBoss Runtime ESB Detector 1.3.0.v20120606-1603-H4-Beta3-SOA JBoss Runtime jBPM Detector 1.3.0.v20120606-1603-H4-Beta3-SOA jBPM 3 Tools Commons 4.4.0.v20120606-1036-H4-Beta3-SOA jBPM 3 Tools Runtime 3.2.1.v20120606-1036-H4-Beta3-SOA jBPM Convert 1.0.0.v20120606-1036-H4-Beta3-SOA jBPM jPDL Tools 3.2.1.v20120606-1036-H4-Beta3-SOA ModeShape JCR REST Tools for Eclipse 1.1.0.v20120606-0911-H3-Beta3-SOA ModeShape Tools JCR CND Editor for Eclipse 1.1.0.v20120606-0911-H3-Beta3-SOA * Runtime Adapter for Apache ODE 1.3 1.0.0.v20120518-1552-H175-CI Teiid DataTools Connectivity 7.7.1.v20120606-1010-H8-Beta3-SOA Teiid Designer 7.7.1.v20120606-1010-H8-Beta3-SOA Teiid Designer Runtime 7.7.1.v20120606-1010-H8-Beta3-SOA UML2 End-User Features 3.2.1.v201109082252 ============================ As seen here: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta3.soa... com.jboss.jbds.bpel.feature 1.1.0.v20120606-2044-H7-Beta3-SOA | SOADataServices com.jboss.jbds.central.discovery.soa-tooling.feature 1.0.0.v20120606-2044-H7-Beta3-SOA org.jboss.tools.esb.feature 1.5.0.v20120606-1401-H7-Beta3-SOA | SOADataServices org.jboss.tools.jbpm.common.feature 4.4.0.v20120606-1036-H4-Beta3-SOA org.jboss.tools.jbpm.convert.feature 1.0.0.v20120606-1036-H4-Beta3-SOA | SOADataServices org.jboss.tools.jbpm3.feature 3.2.1.v20120606-1036-H4-Beta3-SOA | SOADataServices org.jboss.tools.modeshape.jcr.feature 1.1.0.v20120606-0911-H3-Beta3-SOA | SOADataServices org.jboss.tools.modeshape.rest.feature 1.1.0.v20120606-0911-H3-Beta3-SOA | SOADataServices org.jboss.tools.runtime.drools.detector.feature 1.3.0.v20120606-1603-H4-Beta3-SOA | BusinessRules | SOADataServices org.jboss.tools.runtime.esb.detector.feature 1.3.0.v20120606-1603-H4-Beta3-SOA | SOADataServices org.jboss.tools.runtime.jbpm.detector.feature 1.3.0.v20120606-1603-H4-Beta3-SOA | BusinessRules | SOADataServices org.drools.eclipse.feature 5.3.2.201206060351 | SOADataServices | BusinessRules org.drools.eclipse.task.feature 5.3.2.201206060351 | SOADataServices | BusinessRules * org.eclipse.bpel.apache.ode.runtime.feature 1.0.0.v20120518-1552-H175-CI org.eclipse.uml2 3.2.1.v201109082252 org.eclipse.zest 1.3.0.v20110425-2050-67A18yF6F18CBD5A7N54242 org.guvnor.tools.feature 5.3.2.201206060351 | BusinessRules org.jbpm.eclipse.feature 5.3.2.201206060351 | BusinessRules org.jbpm.eclipse.task.feature 5.3.2.201206060351 | BusinessRules org.teiid.datatools.connectivity.feature 7.7.1.v20120606-1010-H8-Beta3-SOA | SOADataServices org.teiid.designer.feature 7.7.1.v20120606-1010-H8-Beta3-SOA | SOADataServices org.teiid.designer.runtime.feature 7.7.1.v20120606-1010-H8-Beta3-SOA | SOADataServices -- 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

2
3
0 / 0

[JBoss JIRA] (JBIDE-9893) Browser is not opened for JBDS Project examples

by Dmitry Geraskov (Created) (JIRA)

Browser is not opened for JBDS Project examples ----------------------------------------------- Key: JBIDE-9893 URL: https://issues.jboss.org/browse/JBIDE-9893 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M3 Environment: Windows XP, JBDS 5.0.0.M3, Server which comes with IDE, Seam 2.2 booking example EAR (with tutorial) Reporter: Dmitry Geraskov Assignee: Snjezana Peco Priority: Critical Fix For: 3.3.0.M4 1. Downloaded and install JBDS 5.0.0.M3 with default server 2. New->Seam 2.2 booking example EAR (with tutorial) 3. Right Click on the project -> Run as->Run on Server -- 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
16
0 / 0

[JBoss JIRA] (JBIDE-11978) ds.xml created for Seam 2.3 project has wrong structure

by Martin Malina (JIRA)

Martin Malina created JBIDE-11978: ------------------------------------- Summary: ds.xml created for Seam 2.3 project has wrong structure Key: JBIDE-11978 URL: https://issues.jboss.org/browse/JBIDE-11978 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta3 Environment: jbdevstudio-product-universal-5.0.0.v201205220143N-H1345-CR1.jar Reporter: Martin Malina Assignee: Alexey Kazakov Fix For: 3.3.0.CR1 The datasource descriptor created by Seam Web Project wizard for Seam 2.3 uses wrong schema. It defines <local-tx-datasource> which worked fine with EAP 5, but EAP 6 refuses to accept it. {code} 09:44:41,653 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."myproj-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."myproj-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "myproj-ds.xml" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: IJ010061: Unexpected element: local-tx-datasource at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:89) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] ... 5 more Caused by: org.jboss.jca.common.metadata.ParserException: IJ010061: Unexpected element: local-tx-datasource at org.jboss.jca.common.metadata.ds.v10.DsParser.parseDataSources(DsParser.java:198) at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:124) at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:87) at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:84) ... 6 more {code} Instead, the Seam 2.3 project should have <datasource> element defined. Example of what the -ds.xml should look like can be found in Max' article here: https://community.jboss.org/en/tools/blog/2012/02/28/excited-about-jboss-... -- 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

2
4
0 / 0

[JBoss JIRA] (JBIDE-11482) AS7 / EAP6 not waiting properly for module to load (code cleanup)

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11482: ----------------------------------- Summary: AS7 / EAP6 not waiting properly for module to load (code cleanup) Key: JBIDE-11482 URL: https://issues.jboss.org/browse/JBIDE-11482 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers, jmx Affects Versions: 3.3.0.Beta3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta3 Mixing management code and jmx code in the JBTWebLaunchableClient is not smart coding practice. The remove module state verification should be received somehow through the new extended properties api, through a verifier of some type. Also, some constant types for jmx should be renamed. Using server versions is not appropriate, but rather, types are more reasonable. jmx over jndi, jmx over management, etc. -- 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

2
3
0 / 0

[JBoss JIRA] (JBIDE-11104) ConcurrentModificationException

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11104: ------------------------------------- Summary: ConcurrentModificationException Key: JBIDE-11104 URL: https://issues.jboss.org/browse/JBIDE-11104 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.CR1 Create an OpenShift application. After it has been imported, the project is built, resulting in {code} !MESSAGE Errors running builder 'JAX-RS Builder' on project 'sample2'. !STACK 0 java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.remove(HashMap.java:811) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.unindexElement(JaxrsMetamodel.java:253) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.indexElement(JaxrsMetamodel.java:177) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:158) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.postProcessHttpMethod(ResourceChangedProcessor.java:479) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processHttpMethodChangesOnScopeAdditionOrChange(ResourceChangedProcessor.java:387) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEvent(ResourceChangedProcessor.java:176) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEntireProject(ResourceChangedProcessor.java:108) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processAffectedResources(ResourceChangedProcessor.java:83) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:123) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:83) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-11426) Plug-in org.jboss.tools.ws.jaxrs.core throws warning message into error log also when I am not working with JAX-RS

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11426: ----------------------------------------- Summary: Plug-in org.jboss.tools.ws.jaxrs.core throws warning message into error log also when I am not working with JAX-RS Key: JBIDE-11426 URL: https://issues.jboss.org/browse/JBIDE-11426 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta2 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta3 Attachments: 01_warning.png While I was working a while, I have noticed that some warning message was thrown in error log. The message provider plug-in was org.jboss.tools.ws.jaxrs.core however I didn't work with JAX-RS web services at all. Unfortunately I cannot provide steps to reproduce, it is thrown occasionally. I am attaching the screenshot, I hope it will be helpful to find out why the message is thrown. -- 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

2
4
0 / 0

[JBoss JIRA] (JBIDE-11741) Make sure CDI support enabled for maven projects with deltaspike dependency

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-11741: -------------------------------------- Summary: Make sure CDI support enabled for maven projects with deltaspike dependency Key: JBIDE-11741 URL: https://issues.jboss.org/browse/JBIDE-11741 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: CDI, maven Reporter: Alexey Kazakov Assignee: Fred Bricon Fix For: 3.3.0.CR1 Here is an example of such a dependency: {code} <dependency> <groupId>org.apache.deltaspike.core</groupId> <artifactId>deltaspike-core-api</artifactId> <version>${deltaspike.version}</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.apache.deltaspike.core</groupId> <artifactId>deltaspike-core-impl</artifactId> <version>${deltaspike.version}</version> <scope>runtime</scope> </dependency> {code} See https://cwiki.apache.org/DeltaSpike/temporary-documentation.html#Temporar... for details. -- 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
10
0 / 0

[JBoss JIRA] (JBIDE-12104) CDI support not enabled for maven projects with deltaspike dependency supposed to be pack as jar

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12104: ----------------------------------------- Summary: CDI support not enabled for maven projects with deltaspike dependency supposed to be pack as jar Key: JBIDE-12104 URL: https://issues.jboss.org/browse/JBIDE-12104 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.3.0.CR1 Reporter: Jaroslav Jankovič Assignee: Alexey Kazakov Fix For: 3.3.0.CR1 pom.xml of such a project: {code} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>test</groupId> <artifactId>test.project</artifactId> <version>0.0.1-SNAPSHOT</version> <dependencies> <dependency> <groupId>org.apache.deltaspike.core</groupId> <artifactId>deltaspike-core-api</artifactId> <version>0.2-incubating</version> </dependency> <dependency> <groupId>org.apache.deltaspike.core</groupId> <artifactId>deltaspike-core-impl</artifactId> <version>0.2-incubating</version> </dependency> </dependencies> </project> {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, 10 months

3
6
0 / 0

[JBoss JIRA] (JBDS-1934) (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-1934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBDS-1934: ------------------------------------------ Bugzilla Update: Perform > (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-1934 > URL: https://issues.jboss.org/browse/JBDS-1934 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform , teiid > Affects Versions: 5.x > Environment: JBoss Developer Studio 4.0 > JBoss Developer Studio 4.1 > Reporter: Johnathon Lee > Assignee: Barry LaFond > Fix For: 5.0.0.CR1-SOA > > > /*+ cache */ > CREATE VIRTUAL PROCEDURE > SELECT 'winning'; > BEGIN > END > The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation. > com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314 > The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line: > this.sqlText = sqlDisplayNode.toDisplayString(); -- 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

1
0
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 June 2012