September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17973) Application wizard, embed wizard: Obscure database password

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17973: ------------------------------------- Summary: Application wizard, embed wizard: Obscure database password (was: Obscure database password) > Application wizard, embed wizard: Obscure database password > ----------------------------------------------------------- > > Key: JBIDE-17973 > URL: https://issues.jboss.org/browse/JBIDE-17973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard, uxtest > Fix For: 4.3.x > > > When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured. > It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment. > Reproduce steps: > 1. Open new OpenShift Application wizard > 2. Sign in & proceed to next screen > 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen > 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen > 5. Click next on set up project screen > 6. Click finish on next screen > 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5... > Expected: Password on this pop-up should be obscured. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18037) Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18037?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18037: ------------------------------------- Summary: Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection (was: connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection) > Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18037 > URL: https://issues.jboss.org/browse/JBIDE-18037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, server_adapter_wizard > Fix For: 4.3.x > > Attachments: openshift_explorer.png, server_adapter_wizard.png > > > When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS). > !server_adapter_wizard.png! > Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box. > !openshift_explorer.png! > There should be option to choose any connection and on the next wizard pages this connection could be preselected. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18037) Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18037?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18037: ------------------------------------- Labels: connection_wizard server_adapter_wizard (was: connection_wizard) > Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18037 > URL: https://issues.jboss.org/browse/JBIDE-18037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, server_adapter_wizard > Fix For: 4.3.x > > Attachments: openshift_explorer.png, server_adapter_wizard.png > > > When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS). > !server_adapter_wizard.png! > Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box. > !openshift_explorer.png! > There should be option to choose any connection and on the next wizard pages this connection could be preselected. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18037) connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18037?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18037: ------------------------------------- Summary: connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection (was: Server adapter: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection) > connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18037 > URL: https://issues.jboss.org/browse/JBIDE-18037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, server_adapter_wizard > Fix For: 4.3.x > > Attachments: openshift_explorer.png, server_adapter_wizard.png > > > When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS). > !server_adapter_wizard.png! > Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box. > !openshift_explorer.png! > There should be option to choose any connection and on the next wizard pages this connection could be preselected. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18037) connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18037?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18037: ------------------------------------- Labels: connection_wizard (was: server_adapter) > connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18037 > URL: https://issues.jboss.org/browse/JBIDE-18037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, server_adapter_wizard > Fix For: 4.3.x > > Attachments: openshift_explorer.png, server_adapter_wizard.png > > > When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS). > !server_adapter_wizard.png! > Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box. > !openshift_explorer.png! > There should be option to choose any connection and on the next wizard pages this connection could be preselected. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18220) Hibernate Console Configuration doesn't use JPA Project connection

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18220?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-18220. ------------------------------- Resolution: Done > Hibernate Console Configuration doesn't use JPA Project connection > ------------------------------------------------------------------ > > Key: JBIDE-18220 > URL: https://issues.jboss.org/browse/JBIDE-18220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1, GNU/Linux 64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > When Hibernate Configuration uses [JPA Project Configured Connection] it should use Project JPA Configuration connection as a primary source and not persistence.xml details -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18220) Hibernate Console Configuration doesn't use JPA Project connection

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18220?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-18220: ----------------------------------- Solving JBIDE-18181 seems to have also solved this problem. But there are a fair number of scenarios that can go wrong here. If something similar persists, please create a new issue with the detailed scenario on how to reproduce it. > Hibernate Console Configuration doesn't use JPA Project connection > ------------------------------------------------------------------ > > Key: JBIDE-18220 > URL: https://issues.jboss.org/browse/JBIDE-18220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1, GNU/Linux 64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > When Hibernate Configuration uses [JPA Project Configured Connection] it should use Project JPA Configuration connection as a primary source and not persistence.xml details -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18181) Errors when hibernate.cfg.xml not at classpath root

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18181?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18181: ------------------------------ Assignee: Koen Aers (was: Max Rydahl Andersen) > Errors when hibernate.cfg.xml not at classpath root > --------------------------------------------------- > > Key: JBIDE-18181 > URL: https://issues.jboss.org/browse/JBIDE-18181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599, Hibernate 4.1.12 > Reporter: Luke Maurer > Assignee: Koen Aers > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > If a project keeps its hibernate.cfg.xml anywhere besides the root of the classpath, Hibernate Tools will not recognize it. In the Hibernate Configurations tree, expanding either Session Factory or Database gives an error ending in “/hibernate.cfg.xml not found”. (The Configuration subtree appears to work.) > As a workaround, if I go into the directory holding WEB-INF/classes (i.e. where compiled Java bytecode goes) and symlink hibernate.cfg.xml there, it seems to work. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18148) problem with Hibernate package-info.java TypeDefs

by Jeffrey Simpson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18148?page=com.atlassian.jira.plugi... ] Jeffrey Simpson updated JBIDE-18148: ------------------------------------ Attachment: TypeDefError.zip Here is a simple example > problem with Hibernate package-info.java TypeDefs > ------------------------------------------------- > > Key: JBIDE-18148 > URL: https://issues.jboss.org/browse/JBIDE-18148 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: OSX 10.9.4 > Reporter: Jeffrey Simpson > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > Attachments: eclipseErrors.log, TypeDefError.zip > > > I just tried out JBoss Developer Studio 8.0.0.Beta3 and it reports all of my Hibernate types that are defined in a package-info as not being found. I get "Type "common-big-decimal" could not be found" where I use it to define an attribute on an entity. > Here is my Package-info.java > > @org.hibernate.annotations.TypeDefs ( > > { > @org.hibernate.annotations.TypeDef(name="yfu_boolean", typeClass=org.yfu.util.hibernate.TrueFalseBooleanUserType.class), > @org.hibernate.annotations.TypeDef(name="integer_date", typeClass=org.yfu.util.hibernate.IntegerDateUserType.class), > @org.hibernate.annotations.TypeDef(name="integer_local_date", typeClass=org.yfu.util.hibernate.IntegerLocalDateUserType.class), > @org.hibernate.annotations.TypeDef(name="common_big_decimal", typeClass=org.yfu.util.hibernate.NullableBigDecimalUserType.class), > @org.hibernate.annotations.TypeDef(name="common_long", typeClass=org.yfu.util.hibernate.NullableLongUserType.class), > @org.hibernate.annotations.TypeDef(name="common_integer", typeClass=org.yfu.util.hibernate.NullableIntegerUserType.class), > @org.hibernate.annotations.TypeDef(name="common_string", typeClass=org.yfu.util.hibernate.NullableStringUserType.class), > @org.hibernate.annotations.TypeDef(name="common_tf_boolean", typeClass=org.yfu.util.hibernate.NullableTFBooleanUserType.class), > @org.hibernate.annotations.TypeDef(name="common_yn_boolean", typeClass=org.yfu.util.hibernate.NullableYNBoolenaUserType.class), > @org.hibernate.annotations.TypeDef(name="yfu_boolean_integer", typeClass=org.yfu.util.hibernate.YFUBooleanIntegerUserType.class), > > } > ) > package org.yfu.util.hibernate; -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3139: ------------------------------------- As I got it supposed to be available as part of Angular JS EA. > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 8.0.0.CR1 > > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014