August 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Moved: (JBIDE-725) hbm.xml Class label for Component has a grey background

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-725?page=all ] Max Andersen moved EXIN-247 to JBIDE-725: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-725 (was: EXIN-247) > hbm.xml Class label for Component has a grey background > ------------------------------------------------------- > > Key: JBIDE-725 > URL: http://jira.jboss.com/jira/browse/JBIDE-725 > Project: JBoss Tools > Issue Type: Sub-task > Components: Hibernate > Reporter: Max Andersen > Assigned To: Viacheslav Kabanovich > Attachments: grey_component.png > > -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-720) Improve hbm.xml structured editor

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-720?page=all ] Max Andersen moved EXIN-227 to JBIDE-720: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-720 (was: EXIN-227) Component/s: Hibernate (was: Hibernate) Fix Version/s: 2.0.0.Beta3 (was: 1.0.0.beta1) > Improve hbm.xml structured editor > --------------------------------- > > Key: JBIDE-720 > URL: http://jira.jboss.com/jira/browse/JBIDE-720 > Project: JBoss Tools > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Viacheslav Kabanovich > Fix For: 2.0.0.Beta3 > > > Identity what improvements (especially in code completion areas) that the hbm.xml editor could support. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (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=all ] Max Andersen moved EXIN-228 to JBIDE-719: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-719 (was: EXIN-228) Component/s: Hibernate (was: Hibernate) Fix Version/s: 2.0.0.Beta4 (was: 1.0.0.beta2) > 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: JBoss Tools > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Assigned To: Max Andersen > Priority: Critical > Fix For: 2.0.0.Beta4 > > 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-717) When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format)

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-717?page=all ] Max Andersen moved JBIDE-716 to JBIDE-717: ------------------------------------------ Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-717 (was: JBIDE-716) > When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-717 > URL: http://jira.jboss.com/jira/browse/JBIDE-717 > Project: JBoss Tools > Issue Type: Bug > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Attachments: after save.jpg, before save.jpg > > > This was also happening when editing faces-config file with exadel studio. Here are two images: the code before saving and the code after saving. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-716) When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format)

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-716?page=all ] Max Andersen moved RHDS-78 to JBIDE-716: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-716 (was: RHDS-78) > When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-716 > URL: http://jira.jboss.com/jira/browse/JBIDE-716 > Project: JBoss Tools > Issue Type: Bug > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Attachments: after save.jpg, before save.jpg > > > This was also happening when editing faces-config file with exadel studio. Here are two images: the code before saving and the code after saving. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-715) When open components.xml file, it gives a warning about the #{} expressions.

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-715?page=all ] Max Andersen moved RHDS-77 to JBIDE-715: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-715 (was: RHDS-77) > When open components.xml file, it gives a warning about the #{} expressions. > ----------------------------------------------------------------------------- > > Key: JBIDE-715 > URL: http://jira.jboss.com/jira/browse/JBIDE-715 > Project: JBoss Tools > Issue Type: Bug > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Attachments: components.jpg > > -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-600) Source page should have the "tag statusbar"

by Max Andersen (JIRA)

Source page should have the "tag statusbar" ------------------------------------------- Key: JBIDE-600 URL: http://jira.jboss.com/jira/browse/JBIDE-600 Project: JBoss Tools Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen The "tag" statusbar (the line that shows you the nested main elements - e.g. html, h:form, table, tr, td if you are in a TD inside a tr, inside a table and so on) is only visible when doing visual editing, not when just editing source. this should be available (as an option) when editing source too in my opinion. -- 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

18 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-714) Cant install RHDS Beta 1

by Ilya Shaikovsky (JIRA)

Cant install RHDS Beta 1 ------------------------ Key: JBIDE-714 URL: http://jira.jboss.com/jira/browse/JBIDE-714 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta1 Environment: Ubuntu 7.04 Gnome 2.18.1 jdk 1.6 Reporter: Ilya Shaikovsky Assigned To: Max Andersen Priority: Critical After running sudo java -jar rhdevstudio-linux-gtk-1.0.0.beta1.jar exception thrown: Exception in thread "main" java.awt.AWTError: Cannot load AWT toolkit: gnu.java.awt.peer.gtk.GtkToolkit at java.awt.Toolkit.getDefaultToolkit(libgcj.so.70) at java.awt.Font.tk(libgcj.so.70) at java.awt.Font.getPeerFromToolkit(libgcj.so.70) at java.awt.Font.<init>(libgcj.so.70) at javax.swing.plaf.FontUIResource.<init>(libgcj.so.70) at javax.swing.plaf.metal.DefaultMetalTheme.<clinit>(libgcj.so.70) at java.lang.Class.initializeClass(libgcj.so.70) at java.lang.Class.initializeClass(libgcj.so.70) at javax.swing.plaf.metal.MetalLookAndFeel.createDefaultTheme(libgcj.so.70) at javax.swing.plaf.metal.MetalLookAndFeel.<init>(libgcj.so.70) at javax.swing.UIManager.<clinit>(libgcj.so.70) at java.lang.Class.initializeClass(libgcj.so.70) at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(GUIInstaller.java:397) at com.izforge.izpack.installer.GUIInstaller.<init>(GUIInstaller.java:116) at java.lang.Class.newInstance(libgcj.so.70) at com.izforge.izpack.installer.Installer.main(Installer.java:62) Caused by: java.lang.UnsatisfiedLinkError: libgtkpeer: libgtkpeer.so: cannot open shared object file: No such file or directory at java.lang.Runtime._load(libgcj.so.70) at java.lang.Runtime.loadLibrary(libgcj.so.70) at java.lang.System.loadLibrary(libgcj.so.70) at gnu.java.awt.peer.gtk.GtkToolkit.<clinit>(libgcj.so.70) at java.lang.Class.initializeClass(libgcj.so.70) at java.lang.Class.forName(libgcj.so.70) at java.awt.Toolkit.getDefaultToolkit(libgcj.so.70) ...15 more -- 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

18 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-700) Hibernate diagram fails on simplest mapping

by Max Andersen (JIRA)

Hibernate diagram fails on simplest mapping ------------------------------------------- Key: JBIDE-700 URL: http://jira.jboss.com/jira/browse/JBIDE-700 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Assigned To: Mikle Dryakhlenkov Priority: Blocker Fix For: 2.0.0.Beta4 @Entity public class Person { @Id int id; public int getId() { return id; } String name; } or with hbm.xml: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="Person"> <id name="id"> <generator class="assigned"></generator> </id> <property name="name"></property> </class> </hibernate-mapping> gives: ava.lang.ClassCastException: org.hibernate.mapping.Property at org.jboss.tools.hibernate.ui.veditor.editors.model.OrmDiagram.createConnections(OrmDiagram.java:321) at org.jboss.tools.hibernate.ui.veditor.editors.model.OrmDiagram.getOrCreatePersistentClass(OrmDiagram.java:189) at org.jboss.tools.hibernate.ui.veditor.editors.model.OrmDiagram.<init>(OrmDiagram.java:79) at org.jboss.tools.hibernate.ui.veditor.editors.VisualEditor.setInput(VisualEditor.java:106) p.s. we need to get the code in OrmDiagram cleaned up............everything is done via casts - incredibly unmaintainble and unsafe - need to be after beta1. -- 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

18 years, 11 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBIDE-287) Can't view/edit debug configurations with Eclipse 3.2M5

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-287?page=comments#action_12371811 ] Max Andersen commented on JBIDE-287: ------------------------------------ #1 Eclipse 3.3 is what we target for JBoss Tools and Red Hat Developer Studio and we now finally got resources to actually get this thing out in a GA, sorry - but if you want to come in and support 3.2 then contact us and you can get commit rights to maintain that as a branch. #2 I don't get this; if you only want the stop/start button for jboss why don't you just download the AS plugins and leave out the rest ? I don't understand what the complexity is for what is there now. The hibernate integration we provide has nothing to do with what spring can do so please fill me in on what is you don't want ? Again, just download the AS plugins you want and leave everything out. #3 New Server > JBoss 4.2 runtime and you are done and you can start and stop everything...have you tried the latest ? With respect to debug it is the exact same procedure....Right click on the debugged server and add the projects (Btw. we hope to fix that so any registred/deployed project will automatically be on there) Note: this works the exact same way as any other WTP runtime/server .... Do you want us to copy the docs of WTP ? And even I can do that stuff....it is simple....if something is not simple or broken, let us know and we will fix it if possible. #4 See #1 What is wrong with using Eclipse 3.3 ? It's way better then 3.2 and it has changed this stuff to be a public API so it is also much more supportable. > Can't view/edit debug configurations with Eclipse 3.2M5 > ------------------------------------------------------- > > Key: JBIDE-287 > URL: http://jira.jboss.com/jira/browse/JBIDE-287 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Final > Reporter: Bradley Wagner > Attachments: org.jboss.ide.eclipse.launcher.ui_1.5.1.GA.jar, org.jboss.ide.eclipse.launcher.ui_1.5.1.jar > > > This is the error that comes up in the Error Log: > !ENTRY org.eclipse.jface 4 2 2006-02-20 11:35:13.792 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". > !STACK 0 > java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/debug/ui/launcher/JavaLaunchConfigurationTab -- 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

18 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 August 2007