May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19704: --------------------------------------------- does this happen in older versions of tools too ? > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.0.Beta1 > > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3377) Random "not responding" message when installing from central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3377?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3377: -------------------------------------- If the app is still responding but shown by the OS/WS as not responding, I believe it's more something to investigate on the OS side. [~akurtakov] Are you aware of any issue in responsiveness detection with Fedora 20 ? > Random "not responding" message when installing from central > ------------------------------------------------------------ > > Key: JBDS-3377 > URL: https://issues.jboss.org/browse/JBDS-3377 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, ui/branding > Affects Versions: 8.1.0.CR1 > Environment: Fedora 20 64-bit, OpenJDK 1.7.0_75 > Reporter: Jan Richter > Assignee: Mickael Istria > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Trying to install all from central sometimes causes the "not responding" dialog to pop up while the "Calculating Dependencies" dialog is active. The app is still responding when the dialog opens though. > I cannot find a particular pattern to this, it looks completely random. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19707) Remove direct use of the core Hibernate classes and/or Hibernate Proxy classes

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19707?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19707: --------------------------------------------- [~koen.aers] I assume you mean this for Beta1 ? > Remove direct use of the core Hibernate classes and/or Hibernate Proxy classes > ------------------------------------------------------------------------------ > > Key: JBIDE-19707 > URL: https://issues.jboss.org/browse/JBIDE-19707 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: birt, hibernate, seam2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > These uses should ideally be replaced by uses of the Hibernate SPI interfaces. It may be needed to create new SPI interfaces. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19706) Refactor the hibernate service provider implementations

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19706?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19706: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 > Refactor the hibernate service provider implementations > -------------------------------------------------------- > > Key: JBIDE-19706 > URL: https://issues.jboss.org/browse/JBIDE-19706 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > The SPI implementation "proxy" classes need a common superclass that can implement most of the functionality using introspection. In this way probably 70% of the code can be eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19707) Remove direct use of the core Hibernate classes and/or Hibernate Proxy classes

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19707?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19707: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 > Remove direct use of the core Hibernate classes and/or Hibernate Proxy classes > ------------------------------------------------------------------------------ > > Key: JBIDE-19707 > URL: https://issues.jboss.org/browse/JBIDE-19707 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: birt, hibernate, seam2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > These uses should ideally be replaced by uses of the Hibernate SPI interfaces. It may be needed to create new SPI interfaces. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19711: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19224) WFK Spring examples reports error <project root> [in travel] is not on its project's build path

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19224?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19224. -------------------------------- Resolution: Rejected > WFK Spring examples reports error <project root> [in travel] is not on its project's build path > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19224 > URL: https://issues.jboss.org/browse/JBIDE-19224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples, upstream > Affects Versions: 4.2.3.Beta1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > STEP: Download and unpack: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > STEP: Import all projects > STEP: Expand first level of all project trees > STEP: See Error log > ASSERT: No errors should occur -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19224) WFK Spring examples reports error <project root> [in travel] is not on its project's build path

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19224?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-19224: --------------------------------- Affects Version/s: 4.2.3.Beta1 Issue is not replicable anymore, tested with JBDS 8.1.0.GA and 9.0.0.Alpha2 > WFK Spring examples reports error <project root> [in travel] is not on its project's build path > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19224 > URL: https://issues.jboss.org/browse/JBIDE-19224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples, upstream > Affects Versions: 4.2.3.Beta1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > STEP: Download and unpack: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > STEP: Import all projects > STEP: Expand first level of all project trees > STEP: See Error log > ASSERT: No errors should occur -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19637: --------------------------------------- Hmm, so now I tried again in Eclipse Mars M6 with JBT nightly from last week. And it works! And then I tried my JBDS 8.1 installation and that worked as well. But then I tried a new workspace (I had some servers already defined) and with new workspace it does not work in either JBDS 8.1 or JBT nightly. So this is still a reliable way for me to reproduce: 0. Get a mac 1. Start JBDS/JBT with a new workspace 2. Servers view -> New Server -> EAP 6.1+ -> New Runtime 3. Click "Download and install runtime..." - nothing will happen The trick with space bar does work though. I am open to trying to debug this together - feel free to ping me anytime, I'm available most of the time (european time). > Runtime download not working from New Server dialog > --------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.3.0.Beta1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19463: --------------------------------------- [~rob.stryker], hmm, ok. That's definitely good to know. But I have a couple of questions: 1. Could it not work the same way as connection via management api when we have the client jars in the tooling itself? Because we do support this kind of connection to a remote server even without a local runtime. 2. If 1. is not doable, how can we make users aware of this? It can be pretty confusing - you create a server, start it, then see it in the JMX Navigator view, but you double-click it and nothing happens. So I have a couple of ideas: a) We could display an error when a user wants to connect in this situation where we don't support it. But it could be thought of as ugly - we simply don't support it, so why enable it and then show an error. b) We could add a note to the wizard where you create the Server Adapter. Currently we have this: "The selected profile does not require a runtime." (And below is a checkbox for creating a runtime.) So we could add: Note that you won't be able to make a JMX connection without a runtime. Or something like that. c) We do nothing :) If 1. is not doable (also, maybe not worth the time - JMX is not a big priority), then I would probably vote for 2.b). What do you think? > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- 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