May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-261) BPMN editor not showing connections on subprocess

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-261?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-261 at 5/11/15 12:58 PM: ------------------------------------------------------------ Hey [~bbrodt] - can you take a quick look at this - I'd bet it's fixed. was (Author: pleacu): Hey [~bbrodt] - can you take a quick look at this - I's bet it's fixed. > BPMN editor not showing connections on subprocess > ------------------------------------------------- > > Key: JBTIS-261 > URL: https://issues.jboss.org/browse/JBTIS-261 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 7.0.0.GA-JBDSIS > Reporter: Jorge Morales > Assignee: Robert (Bob) Brodt > Attachments: 1.png, 2.png > > > When having a process with a subprocess, and this subprocess is pushed down to it's own diagram, connections disappear. If you add new connections these are not shown. If you pull back the diagram up, connections are shown on main editor for the subprocess. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-261) BPMN editor not showing connections on subprocess

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-261?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-261 at 5/11/15 12:58 PM: ------------------------------------------------------------ Hey [~bbrodt] - can you take a quick look at this - I's bet it's fixed. was (Author: pleacu): Hey [~bbrodt] - can you take a quick look at this - I get it's fixed. > BPMN editor not showing connections on subprocess > ------------------------------------------------- > > Key: JBTIS-261 > URL: https://issues.jboss.org/browse/JBTIS-261 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 7.0.0.GA-JBDSIS > Reporter: Jorge Morales > Assignee: Robert (Bob) Brodt > Attachments: 1.png, 2.png > > > When having a process with a subprocess, and this subprocess is pushed down to it's own diagram, connections disappear. If you add new connections these are not shown. If you pull back the diagram up, connections are shown on main editor for the subprocess. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3415) Fuse JMX Navigator is not showing any local processes on windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3415?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3415: ----------------------------------- [~mmalina] Can you replicate this on windows at all? Have you ever seen local processes not showing up for any reason? Check normal stuff before trying out the Fuse situation. Maybe you could ping the IS QE guys to check? Also, it'd be good to verify what versions of all org.jboss.tools.jmx.* plugins they're running with. > Fuse JMX Navigator is not showing any local processes on windows > ---------------------------------------------------------------- > > Key: JBDS-3415 > URL: https://issues.jboss.org/browse/JBDS-3415 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 7.1.1.GA > Environment: Enviroment: Windows 7 Ultimate 32-bit > JDK: 1.7.0_55 and 1.6.0_45 > JBDS: 7.1.1.GA > Reporter: Hooman Broujerdi > Attachments: linux.png, windows.png > > > When I test a simple camel route on my linux machine and on Fuse JMX Navigator tab under local processes I see my camel context according to documentation: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html... > However when testing the same camel route on a windows machine I don't see anything under local processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19786 at 5/11/15 12:10 PM: -------------------------------------------------------------------- discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header (06:08:39 PM) liggitt: 401 without www-challenge means you need a token, but can't get it in an automated way (06:08:42 PM) liggitt: that's the google oauth case (06:09:18 PM) liggitt: in that case, show them the body of the response... we're including messages and a link to where they get the token {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. was (Author: adietish): discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:54 PM) jcantril: liggitt: you probably told me all o fthis before (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header (06:08:39 PM) liggitt: 401 without www-challenge means you need a token, but can't get it in an automated way (06:08:42 PM) liggitt: that's the google oauth case (06:09:18 PM) liggitt: in that case, show them the body of the response... we're including messages and a link to where they get the token {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Attachments: unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19786 at 5/11/15 12:10 PM: -------------------------------------------------------------------- discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:54 PM) jcantril: liggitt: you probably told me all o fthis before (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header (06:08:39 PM) liggitt: 401 without www-challenge means you need a token, but can't get it in an automated way (06:08:42 PM) liggitt: that's the google oauth case (06:09:18 PM) liggitt: in that case, show them the body of the response... we're including messages and a link to where they get the token {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. was (Author: adietish): discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:54 PM) jcantril: liggitt: you probably told me all o fthis before (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Attachments: unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19786: ------------------------------------------ discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:54 PM) jcantril: liggitt: you probably told me all o fthis before (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Attachments: unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19784) Make runtime detection available from server view ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19784?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19784: --------------------------------------------- seems "search" for runtimes in preferences could be exposed directly and it would work for all server adapters. And it looks like our searchForRuntimes does not honor the api and just stop returning servers when the first one found. Seems we could just call our runtimedetection and have it report allt he found server runtimes. > Make runtime detection available from server view ? > --------------------------------------------------- > > Key: JBIDE-19784 > URL: https://issues.jboss.org/browse/JBIDE-19784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > runtime detection is great but it's rather hidden. > Idea is to add a search glass to server view to trigger runtime detection. > Wdyt? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3415) Fuse JMX Navigator is not showing any local processes on windows

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3415?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3415: -------------------------------------- Sprint: Sprint #3 May 2015 > Fuse JMX Navigator is not showing any local processes on windows > ---------------------------------------------------------------- > > Key: JBDS-3415 > URL: https://issues.jboss.org/browse/JBDS-3415 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 7.1.1.GA > Environment: Enviroment: Windows 7 Ultimate 32-bit > JDK: 1.7.0_55 and 1.6.0_45 > JBDS: 7.1.1.GA > Reporter: Hooman Broujerdi > Attachments: linux.png, windows.png > > > When I test a simple camel route on my linux machine and on Fuse JMX Navigator tab under local processes I see my camel context according to documentation: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html... > However when testing the same camel route on a windows machine I don't see anything under local processes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19755: ---------------------------------------- Sprint: Sprint #3 May 2015 > Implement ServerPort portion of wst.servertools API > --------------------------------------------------- > > Key: JBIDE-19755 > URL: https://issues.jboss.org/browse/JBIDE-19755 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it. > Unfortunately, I've been hit by an upstream bug that hinders my progress: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109 > To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3345: -------------------------------------- Sprint: Sprint #2 April 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015) > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Optional > Fix For: 9.0.x > > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, run.sh, runtime_jre.png, server.log > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015