October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- Dang the luck! Thanks for letting me know Martin! > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Koen Aers edited comment on JBIDE-14305 at 10/1/14 8:18 AM: ------------------------------------------------------------ It turns out that the log4j jar is missing in the hibernate 4.3 plugin. Apparently this is not a problem when the Hibernate Configuration is created using a hibernate.cfg.xml file but it is when the configuration is created using the persistence.xml file. was (Author: koen.aers): It turns out that the log4j jar is missing in the hibernate 4.3 plugin. > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: workspace.zip > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-14305: ----------------------------------- It turns out that the log4j jar is missing in the hibernate 4.3 plugin. > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: workspace.zip > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio resolved JBIDE-18445. ---------------------------------- Resolution: Done > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-18445. -------------------------------- > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18445: --------------------------------- Fix Version/s: 4.2.0.CR2 > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18445: -------------------------------------- The test is here: http://machydra.brq.redhat.com:8080/job/jbosstools.arquillian.bot.tests.poc/ > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18463) Connection Dialog: should be able to save connection even if it is not valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18463: ------------------------------------- Estimated Difficulty: Medium > Connection Dialog: should be able to save connection even if it is not valid > ---------------------------------------------------------------------------- > > Key: JBIDE-18463 > URL: https://issues.jboss.org/browse/JBIDE-18463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Fix For: 4.3.x > > > Currently one can only save a connection if it is valid (the user could connect using a valid server and credentials). If the settings are not valid, the connection is not saved since "Connect" (that saves the connection) wont ever get enabled. > We should allow the user to save a connection even if it is not valid (ex. SSL errors happens even though the conn is valid per se) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18463) Connection Dialog: should be able to save connection even if it is not valid

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-18463: ---------------------------------------- Summary: Connection Dialog: should be able to save connection even if it is not valid Key: JBIDE-18463 URL: https://issues.jboss.org/browse/JBIDE-18463 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.2.0.CR1 Reporter: Andre Dietisheim Currently one can only save a connection if it is valid (the user could connect using a valid server and credentials). If the settings are not valid, the connection is not saved since "Connect" (that saves the connection) wont ever get enabled. We should allow the user to save a connection even if it is not valid (ex. SSL errors happens even though the conn is valid per se) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18463) Connection Dialog: should be able to save connection even if it is not valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18463: ------------------------------------- Fix Version/s: 4.3.x > Connection Dialog: should be able to save connection even if it is not valid > ---------------------------------------------------------------------------- > > Key: JBIDE-18463 > URL: https://issues.jboss.org/browse/JBIDE-18463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Fix For: 4.3.x > > > Currently one can only save a connection if it is valid (the user could connect using a valid server and credentials). If the settings are not valid, the connection is not saved since "Connect" (that saves the connection) wont ever get enabled. > We should allow the user to save a connection even if it is not valid (ex. SSL errors happens even though the conn is valid per se) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014