May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12067) JBT installation from Marketplace takes about one hour

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-12067: ------------------------------------ Summary: JBT installation from Marketplace takes about one hour Key: JBIDE-12067 URL: https://issues.jboss.org/browse/JBIDE-12067 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.Beta3 Environment: JBT 3.3.0.Beta2 Reporter: Jiri Peterka Priority: Critical Fix For: 3.3.0.Final When installing JBT from Marketplace it took me around half an hour of downloading metadata and calculating dependencies. Another half an hour for rest of installation. Reported speed is between 20kB/s - 40kB/s. This is really very slow even in comparison with slowest update site I've seen. This speed is not acceptable for users I guess. Some actions related to servers, infrastructure and traffic control should be taken. -- 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
13
0 / 0

[JBoss JIRA] (JBIDE-11841) Make OpenShift Explorer actions available from Server Adapter and Project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11841: ------------------------------------- Summary: Make OpenShift Explorer actions available from Server Adapter and Project Key: JBIDE-11841 URL: https://issues.jboss.org/browse/JBIDE-11841 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta2 Reporter: Xavier Coulon Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 get the actions available on nodes in openshift explorer such as Show console, Show Environment and port forwarding should be available on the openshift server adapter too so you dont necessarily have to jump between the various views to work with openshift apps. -- 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

6
11
0 / 0

[JBoss JIRA] (JBIDE-11781) webservice_producer/client quickstarts have build errors on 3.3.0.beta1

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-11781: ------------------------------------ Summary: webservice_producer/client quickstarts have build errors on 3.3.0.beta1 Key: JBIDE-11781 URL: https://issues.jboss.org/browse/JBIDE-11781 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.Beta1-SOA Environment: eclipse-jee-indigo-SR2-RC3-linux-gtk-x86_64 http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta3.core/ java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Red Hat Enterprise Linux Workstation release 6.2 (Santiago) Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Priority: Blocker Fix For: 3.3.0.Beta1-SOA The build path for these ESB 5.0 quickstarts is incorrect when JBT is used with an SOA-P 5.3.0.ER2 server. The build path does not find the EAP runtime in that SOA-P server. The other quickstarts look OK - and this problem is not being seen on JBDS 5.0.0.beta3 See the attached screenshots for an illustration. -- 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
20
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-12000) Random "Unable to publish to ther server" error

by George Lindholm (JIRA)

George Lindholm created JBIDE-12000: --------------------------------------- Summary: Random "Unable to publish to ther server" error Key: JBIDE-12000 URL: https://issues.jboss.org/browse/JBIDE-12000 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.x Environment: JBoss 6.1.1 server Reporter: George Lindholm Assignee: Rob Stryker Priority: Minor What steps will reproduce the problem? 1. Unknown, randomnly happens 2. 3. -- Error Details -- Date: Thu May 24 13:35:41 PDT 2012 Message: Could not publish to the server. Severity: Error Product: Eclipse 1.4.2.20120131-1457 (org.eclipse.epp.package.jee.product) Plugin: org.eclipse.wst.server.core Session Data: eclipse.buildId=M20120208-0800 java.version=1.7.0_04 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_CA Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data e:\java\workspace Exception Stack Trace: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.server.internal.ExtendedServerPropertiesAdapterFactory.getExtendedProperties(ExtendedServerPropertiesAdapterFactory.java:53) at org.jboss.ide.eclipse.as.core.server.internal.ExtendedServerPropertiesAdapterFactory.getAdapter(ExtendedServerPropertiesAdapterFactory.java:42) at org.jboss.ide.eclipse.as.core.server.internal.ExtendedServerPropertiesAdapterFactory.getJBossExtendedProperties(ExtendedServerPropertiesAdapterFactory.java:32) at org.jboss.ide.eclipse.as.jmx.integration.JBoss3To6ConnectionProvider.belongsHere(JBoss3To6ConnectionProvider.java:37) at org.jboss.ide.eclipse.as.jmx.integration.AbstractJBossJMXConnectionProvider.getConnections(AbstractJBossJMXConnectionProvider.java:106) at org.jboss.ide.eclipse.as.jmx.integration.AbstractJBossJMXConnectionProvider.findConnection(AbstractJBossJMXConnectionProvider.java:94) at org.jboss.ide.eclipse.as.jmx.integration.JBossJMXConnectionProviderModel.getConnection(JBossJMXConnectionProviderModel.java:59) at org.jboss.ide.eclipse.as.jmx.integration.JBossJMXConnectionProviderModel.run(JBossJMXConnectionProviderModel.java:76) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerJMXRunner.run(JBossServerJMXRunner.java:33) at org.jboss.ide.eclipse.as.core.server.internal.LocalJBossBehaviorDelegate.publishStart(LocalJBossBehaviorDelegate.java:211) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.publishStart(DelegatingServerBehavior.java:139) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:927) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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
12
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 May 2012