February 2008 - jbosstools-issues

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=comments#action_12397884 ] Max Andersen commented on JBIDE-719: ------------------------------------ Just one line as in my previous comment and it should be possible to say it is not something that should be used. > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Vitali Yemialyanchyk > Priority: Optional > Fix For: 2.1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfigNew.JPG, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Vitali Yemialyanchyk (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=comments#action_12397879 ] Vitali Yemialyanchyk commented on JBIDE-719: -------------------------------------------- Max, is EditConsolleConfigNew look like what you expected? may be also enable checkbox is necessary for new part (with name Import DB config)? or separate dialog? > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Vitali Yemialyanchyk > Priority: Optional > Fix For: 2.1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfigNew.JPG, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=comments#action_12397877 ] Max Andersen commented on JBIDE-719: ------------------------------------ Just one setting is needed: connection profile name with the option of choosing "Use JPA project setting" from Dali (or our own hibernate project setting if relevant) > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Vitali Yemialyanchyk > Priority: Optional > Fix For: 2.1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfigNew.JPG, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Vitali Yemialyanchyk (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=all ] Vitali Yemialyanchyk updated JBIDE-719: --------------------------------------- Attachment: EditConsolleConfig.JPG > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Vitali Yemialyanchyk > Priority: Optional > Fix For: 2.1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfigNew.JPG, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Vitali Yemialyanchyk (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=all ] Vitali Yemialyanchyk updated JBIDE-719: --------------------------------------- Attachment: NewSeamProj.JPG > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Vitali Yemialyanchyk > Priority: Optional > Fix For: 2.1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfigNew.JPG, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Vitali Yemialyanchyk (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=all ] Vitali Yemialyanchyk updated JBIDE-719: --------------------------------------- Attachment: EditConsolleConfigNew.JPG > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Vitali Yemialyanchyk > Priority: Optional > Fix For: 2.1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfigNew.JPG, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-351) Clean out bad exception handling

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-351?page=comments#action_12397772 ] Max Andersen commented on JBIDE-351: ------------------------------------ why was this reopened again ? didn't we fix these for the version set ? > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: http://jira.jboss.com/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Andersen > Assigned To: Denis Golovin > Priority: Critical > Fix For: 2.1 > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of them ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBIDE-351) Clean out bad exception handling

by Denis Golovin (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-351?page=all ] Denis Golovin reopened JBIDE-351: --------------------------------- > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: http://jira.jboss.com/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Andersen > Assigned To: Denis Golovin > Priority: Critical > Fix For: 2.1 > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of them ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-351) Clean out bad exception handling

by Denis Golovin (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-351?page=all ] Denis Golovin updated JBIDE-351: -------------------------------- Component/s: Cleanup Fix Version/s: 2.1 (was: 2.0.0.CR1) Affects Version/s: 2.0.0.GA > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: http://jira.jboss.com/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Andersen > Assigned To: Denis Golovin > Priority: Critical > Fix For: 2.1 > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of them ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-1657) Imported Project's classpath container assuming server exists

by Rob Stryker (JIRA)

Imported Project's classpath container assuming server exists ------------------------------------------------------------- Key: JBIDE-1657 URL: http://jira.jboss.com/jira/browse/JBIDE-1657 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Rob Stryker Fix For: 2.0.1 java.lang.NullPointerException at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider$RuntimeClasspathContainer.getDescription(ProjectRuntimeClasspathProvider.java:120) at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getCPListElementText(CPListLabelProvider.java:261) at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getText(CPListLabelProvider.java:78) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getText(WrappedViewerLabelProvider.java:108) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:164) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:135) at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:386) My guess is that your classpath container thinks the server exists...which it wont do in this case when he is creating a new project. That should be fixed in .0.1 Workaround for user: delete the classpath entry about JBoss 4 server in classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2008