October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10299) aggregate SOA source features into a single site

by Nick Boldt (Created) (JIRA)

aggregate SOA source features into a single site ------------------------------------------------ Key: JBIDE-10299 URL: https://issues.jboss.org/browse/JBIDE-10299 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Reporter: Nick Boldt Fix For: 3.3.0.Beta1 -- 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, 4 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-12785) Missing "Create JSF2 composite..." context menu item

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-12785: ----------------------------------- Summary: Missing "Create JSF2 composite..." context menu item Key: JBIDE-12785 URL: https://issues.jboss.org/browse/JBIDE-12785 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.0.0.Alpha2 Environment: Linux 64bit, Eclipse SDK 4.2.1, JBT 4.0.0.Alpha2-v20121002-1149-B19 Reporter: Vlado Pakan Assignee: Alexey Kazakov Fix For: 4.0.0.Beta1 1. Create JSF2 project 2. Open 3. Right click in the source of page ERROR: Menu "Create JSF2 composite..." is not present in VPE context menu !noCreateJSF(a)CompositeMenu.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
16
0 / 0

[JBoss JIRA] (JBIDE-12866) New icons for New Service Provider Wizard

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12866: -------------------------------------- Summary: New icons for New Service Provider Wizard Key: JBIDE-12866 URL: https://issues.jboss.org/browse/JBIDE-12866 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: common/jst/core Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 4.0.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-10983) openshift properties should show username and host as separate values

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10983: ------------------------------------------- Summary: openshift properties should show username and host as separate values Key: JBIDE-10983 URL: https://issues.jboss.org/browse/JBIDE-10983 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 its nice to easily copy the git url - should also provide the username and host for easy copy/paste for ssh command line -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 fail deployment after some time

by Jesper Skov (JIRA)

Jesper Skov created JBIDE-11215: ----------------------------------- Summary: JbossTools 3.3.0M5 fail deployment after some time Key: JBIDE-11215 URL: https://issues.jboss.org/browse/JBIDE-11215 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Windows XP, Eclipse 3.7.sr2 Reporter: Jesper Skov Assignee: Rob Stryker JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many successful deployments). Similar behavior from the nightly build 2012.02.27. M4 is working without problems, and this is the version we revert to when restarts of Eclipse with M5 gets too tedious. The Eclipse log shows JMX console login problems as the (propable) cause, see below. We use admin/admin credentials for the JMX console, and don't change these during the day. Hard to reproduce, but (obviously) we are willing and happy to test any build you might feel should fix this. We don't want to get stranded at M4 :) (I will attach a snapshot of the server configuration page when I get a chance.) Let me know if there is any logging we can tweak to help you find and fix the cause of this. Log output from the 2012.02.27 nightly build: {code} java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source) at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) at $Proxy30.invoke(Unknown Source) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65) at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71) at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55) at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128) at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735) at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91) at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128) at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102) at org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232) at org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161) at org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149) {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, 4 months

5
56
0 / 0

[JBoss JIRA] (JBIDE-12643) Deployment to EAP 5.1 does not work after stopping and starting the deployer using JMX

by Martin Malina (JIRA)

Martin Malina created JBIDE-12643: ------------------------------------- Summary: Deployment to EAP 5.1 does not work after stopping and starting the deployer using JMX Key: JBIDE-12643 URL: https://issues.jboss.org/browse/JBIDE-12643 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.0.0.Alpha1 Environment: JBDS 6.0.0.Alpha1 H25 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.0.0.Alpha2 (This issue was discovered by rawagner and I was able to reproduce it myself.) If you disable and then enable again the deployment on an EAP 5.1 server using JMX and then try to deploy something, it doesn't get deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-12364) Cannot add a condition into "If" activity

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-12364: ----------------------------------------- Summary: Cannot add a condition into "If" activity Key: JBIDE-12364 URL: https://issues.jboss.org/browse/JBIDE-12364 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.4.x Environment: Eclipse Juno EE Reporter: Andrej Podhradsky Assignee: Robert (Bob) Brodt Cannot add a condition into "If" activity. -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] (JBIDE-12794) regenerate multiple.target file from an existing local/target/REPO/ folder to pull in new IU versions

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12794: ---------------------------------- Summary: regenerate multiple.target file from an existing local/target/REPO/ folder to pull in new IU versions Key: JBIDE-12794 URL: https://issues.jboss.org/browse/JBIDE-12794 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, target-platform Affects Versions: 4.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.0.Beta1 Code for this already exists in http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/tar... - just need to port it over to work in the new http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platforms/sc... folder and ensure it works to produce an updated multiple.target file, which can then be diffed against SVN/Git before committing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBDS-2269) 5.0 SOA and BRMS Tooling - cannot be installed into JBDS 6.0.Alpha1

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2269: ---------------------------------- Summary: 5.0 SOA and BRMS Tooling - cannot be installed into JBDS 6.0.Alpha1 Key: JBDS-2269 URL: https://issues.jboss.org/browse/JBDS-2269 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 6.0.0.Alpha1 Environment: Version: 6.0.0.H12 Build id: Alpha1-v20120904-0259-H12 Build date: 20120904-0259 http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.GA.soa-to... Reporter: Len DiMaggio Assignee: Douglas Palmer Fix For: 6.0.0.Alpha1-SOA This is a known issue - logging this JIRA to track the resolution Installing SOA: Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Runtime jBPM Detector 1.3.0.v20120717-1304-H9-GA-SOA (org.jboss.tools.runtime.jbpm.detector.feature.feature.group 1.3.0.v20120717-1304-H9-GA-SOA) Software currently installed: JBoss Developer Studio (Branded Product) 6.0.0.Alpha1-v20120904-0259-H12 (com.jboss.jbds.all 6.0.0.Alpha1-v20120904-0259-H12) Only one of the following can be installed at once: Eclipse UI 3.103.0.v20120521-2329 (org.eclipse.ui 3.103.0.v20120521-2329) Eclipse UI 3.7.0.v20110928-1505 (org.eclipse.ui 3.7.0.v20110928-1505) Cannot satisfy dependency: From: JBoss Developer Studio (Branded Product) 6.0.0.Alpha1-v20120904-0259-H12 (com.jboss.jbds.all 6.0.0.Alpha1-v20120904-0259-H12) To: com.jboss.jbds.product.feature.feature.group [6.0.0.Alpha1-v20120904-0259-H12] Cannot satisfy dependency: From: JBoss Developer Studio (Core Features) 6.0.0.Alpha1-v20120904-0259-H12 (com.jboss.jbds.product.feature.feature.group 6.0.0.Alpha1-v20120904-0259-H12) To: org.eclipse.platform.feature.group [4.2.0.v20120608-135145-9JF7BHV8FyMteji0Oi_ePMz0xuZ8TVo7lV0z0ecb] Cannot satisfy dependency: From: Eclipse Platform 4.2.0.v20120608-135145-9JF7BHV8FyMteji0Oi_ePMz0xuZ8TVo7lV0z0ecb (org.eclipse.platform.feature.group 4.2.0.v20120608-135145-9JF7BHV8FyMteji0Oi_ePMz0xuZ8TVo7lV0z0ecb) To: org.eclipse.rcp.feature.group [4.2.0.v20120528-1648-7IAPA7BrHQicRpNdOz-Obz-rlRCA] Cannot satisfy dependency: From: Eclipse RCP 4.2.0.v20120528-1648-7IAPA7BrHQicRpNdOz-Obz-rlRCA (org.eclipse.rcp.feature.group 4.2.0.v20120528-1648-7IAPA7BrHQicRpNdOz-Obz-rlRCA) To: org.eclipse.ui [3.103.0.v20120521-2329] Cannot satisfy dependency: From: JBoss Runtime jBPM Detector 1.3.0.v20120717-1304-H9-GA-SOA (org.jboss.tools.runtime.jbpm.detector 1.3.0.v20120717-1304-H9-GA-SOA) To: bundle org.eclipse.ui [3.7.0,3.8.0) Cannot satisfy dependency: From: JBoss Runtime jBPM Detector 1.3.0.v20120717-1304-H9-GA-SOA (org.jboss.tools.runtime.jbpm.detector.feature.feature.group 1.3.0.v20120717-1304-H9-GA-SOA) To: org.jboss.tools.runtime.jbpm.detector [1.3.0.v20120717-1304-H9-GA-SOA] Installing BRMS: Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Runtime jBPM Detector 1.3.0.v20120717-1304-H9-GA-SOA (org.jboss.tools.runtime.jbpm.detector.feature.feature.group 1.3.0.v20120717-1304-H9-GA-SOA) Software currently installed: JBoss Developer Studio (Branded Product) 6.0.0.Alpha1-v20120904-0259-H12 (com.jboss.jbds.all 6.0.0.Alpha1-v20120904-0259-H12) Only one of the following can be installed at once: Core Runtime 3.8.0.v20120521-2346 (org.eclipse.core.runtime 3.8.0.v20120521-2346) Core Runtime 3.7.0.v20110110 (org.eclipse.core.runtime 3.7.0.v20110110) Cannot satisfy dependency: From: JBoss Developer Studio (Branded Product) 6.0.0.Alpha1-v20120904-0259-H12 (com.jboss.jbds.all 6.0.0.Alpha1-v20120904-0259-H12) To: toolingcom.jboss.jbds.all.configuration [6.0.0.Alpha1-v20120904-0259-H12] Cannot satisfy dependency: From: JBoss Runtime jBPM Detector 1.3.0.v20120717-1304-H9-GA-SOA (org.jboss.tools.runtime.jbpm.detector 1.3.0.v20120717-1304-H9-GA-SOA) To: bundle org.eclipse.core.runtime [3.7.0,3.8.0) Cannot satisfy dependency: From: JBoss Runtime jBPM Detector 1.3.0.v20120717-1304-H9-GA-SOA (org.jboss.tools.runtime.jbpm.detector.feature.feature.group 1.3.0.v20120717-1304-H9-GA-SOA) To: org.jboss.tools.runtime.jbpm.detector [1.3.0.v20120717-1304-H9-GA-SOA] Cannot satisfy dependency: From: toolingcom.jboss.jbds.all.configuration 6.0.0.Alpha1-v20120904-0259-H12 To: toolinggtk.linux.x86_64org.eclipse.core.runtime [6.0.0.Alpha1-v20120904-0259-H12] Cannot satisfy dependency: From: toolinggtk.linux.x86_64org.eclipse.core.runtime 6.0.0.Alpha1-v20120904-0259-H12 To: bundle org.eclipse.core.runtime 3.8.0.v20120521-2346 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8132) Changes in Source tab are not synchronized with Design (graphical) tab for extension activities

by Robert (Bob) Brodt (JIRA)

Changes in Source tab are not synchronized with Design (graphical) tab for extension activities ----------------------------------------------------------------------------------------------- Key: JBIDE-8132 URL: https://issues.jboss.org/browse/JBIDE-8132 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.x This was reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=332926 I have applied a patch to the BPEL editor code line at eclipse.org, but it needs to be merged into jboss code. Also, we need to build a SWTBot test that exercises extension activities. It should include a real-life sample (maybe the model and UI extensions from SMILA?) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
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 October 2012