August 2008 - jbosstools-issues - Jboss List Archives

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

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on JBIDE-719: ------------------------------------------- Vitali - JPA mode has the persistence.xml configuration file, so what is the difference ? The usecase for this is to *not* having to change your production/test files but still be able to use them within Eclipse when you just have datasourcese listed in the configuration files. It is the exact same for *all* the modes. Furthermore if users can choose a DTP connection profile they dont have to list connection properties just for development in 3 places (hibernate-console.properties, datasource ds.xml and in the DTP source for sql browsing) so this is all about reducing the need for typing. ill look at the patch as soon as i can and tell if it now works. > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: https://jira.jboss.org/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.0.0.beta1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719_20080805.zip, 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2609) The VpeController.visualRefresh() method is called even if the Visual part is minimized

by Snjezana Peco (JIRA)

The VpeController.visualRefresh() method is called even if the Visual part is minimized --------------------------------------------------------------------------------------- Key: JBIDE-2609 URL: https://jira.jboss.org/jira/browse/JBIDE-2609 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 3.0.0.alpha Reporter: Snjezana Peco Assignee: Snjezana Peco See comments https://jira.jboss.org/jira/browse/JBIDE-2588?focusedCommentId=12423203#a... and https://jira.jboss.org/jira/browse/JBIDE-2588?focusedCommentId=12423210#a... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-1406) Package archive configuration is coupled to project name

by Rob Hasselbaum (JIRA)

Package archive configuration is coupled to project name -------------------------------------------------------- Key: JBIDE-1406 URL: http://jira.jboss.com/jira/browse/JBIDE-1406 Project: JBoss Tools Issue Type: Bug Components: Archives Affects Versions: 2.0.0.CR1 Environment: Eclipse 3.3.1.1 on openSUSE 10.3 Reporter: Rob Hasselbaum The ".packages" configuration file contains references to the project name. This is problematic if the configuration is checked into a revision control system, since it requires all checkouts of the project to use the same name in Eclipse. This means a developer cannot have more than one copy of the project in Eclipse at the same time (e.g. different branches), and in addition, all members of a team are forced to use the same project name. I have entered this as a bug rather than an enhancement request because this is a regression from JBoss IDE 1.6. -- 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

17 years, 8 months

4
21
0 / 0

[JBoss JIRA] Created: (JBIDE-2592) Add icon for Hibernate Configurations error messages

by Vitali Yemialyanchyk (JIRA)

Add icon for Hibernate Configurations error messages ---------------------------------------------------- Key: JBIDE-2592 URL: https://jira.jboss.org/jira/browse/JBIDE-2592 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Hibernate Configurations tree items with error messages have no icons - screenshot. Add error sign icons here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2582) Add support of message bundles for new components in vpe, remove and recreate old releasation of message bundles

by Maxim Areshkau (JIRA)

Add support of message bundles for new components in vpe, remove and recreate old releasation of message bundles ---------------------------------------------------------------------------------------------------------------- Key: JBIDE-2582 URL: https://jira.jboss.org/jira/browse/JBIDE-2582 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.2 Reporter: Maxim Areshkau Assignee: Eugene Stherbin Add support for message bundles for templates, if in node from source editor using message bundles value, we should create clone of this node and instead of message bundles keys in clone use value. see JBIDE-2010. Also recreate and clean old realization of message bundles message substitution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2584) create template for #text node

by Maxim Areshkau (JIRA)

create template for #text node ------------------------------ Key: JBIDE-2584 URL: https://jira.jboss.org/jira/browse/JBIDE-2584 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.2 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Creating template for #text node, allow for us avoid for check for node type in classes VpePreviewDomBuilder, VpeSelectionBuilder, VpeSourceDomBuilder and moves all logic for text nodes into one place.(TextNodeTemplate). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2598) hibernatetools & jboss.tools.common plugins together write exceptions to Error Log when I first time open "Hibernate Configuration 3.0 XML Editor"

by Vitali Yemialyanchyk (JIRA)

hibernatetools & jboss.tools.common plugins together write exceptions to Error Log when I first time open "Hibernate Configuration 3.0 XML Editor" --------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2598 URL: https://jira.jboss.org/jira/browse/JBIDE-2598 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Reporter: Vitali Yemialyanchyk Assignee: Viacheslav Kabanovich Priority: Minor I'd like to get "Hibernate Configuration 3.0 XML Editor" in my workspace, I import all jboss.tools.common plugins and get exceptions - I find the reason - telling it shortly - I should import almost all jbosstools plugins into my workspace - so I'll report about the problem as a bug - this is nothing - just about 10 error messages in Error Log - but as a user if I try to use separated hibernatetools - I do not want to see error massages about - org.jboss.tools.jsf.jsfnature - if I wan't to use jsf at all... Also the reason of the problem - in my workspace I have several projects - one of them - SeamTestPrj - has jsfnature - but other project ZZ has no - I try to open hibernate.cfg.xml from ZZ project and get exceptions: 1) Model feature org.jboss.tools.common.meta.impl.adapters.XAdapterProjectsRoot is not registered with extension point org.jboss.tools.common.model.classes java.lang.Exception: Model feature org.jboss.tools.common.meta.impl.adapters.XAdapterProjectsRoot is not registered with extension point org.jboss.tools.common.model.classes at org.jboss.tools.common.model.util.ModelFeatureFactory.createFeatureInstance(ModelFeatureFactory.java:83) at org.jboss.tools.common.meta.impl.AdapterHolder.doGetAdapter(XAttributeImpl.java:236) at org.jboss.tools.common.meta.impl.AdapterHolder.getAdapter(XAttributeImpl.java:220) at org.jboss.tools.common.meta.impl.XAttributeImpl.getAdapter(XAttributeImpl.java:179) 2) Model feature org.jboss.tools.jst.web.tld.model.handlers.JSPAdopt is not registered with extension point org.jboss.tools.common.model.classes java.lang.Exception: Model feature org.jboss.tools.jst.web.tld.model.handlers.JSPAdopt is not registered with extension point org.jboss.tools.common.model.classes at org.jboss.tools.common.model.util.ModelFeatureFactory.createFeatureInstance(ModelFeatureFactory.java:83) at org.jboss.tools.common.model.ui.dnd.ControlDragDrop.<clinit>(ControlDragDrop.java:32) at org.jboss.tools.common.model.ui.outline.XModelObjectContentOutlineProvider.<init>(XModelObjectContentOutlineProvider.java:35) at org.jboss.tools.common.editor.ObjectMultiPageEditor.<init>(ObjectMultiPageEditor.java:80) 3) Model feature org.jboss.tools.jst.web.project.FileSystemsRenameListenerContribution is not registered with extension point org.jboss.tools.common.model.classes java.lang.Exception: Model feature org.jboss.tools.jst.web.project.FileSystemsRenameListenerContribution is not registered with extension point org.jboss.tools.common.model.classes at org.jboss.tools.common.model.util.ModelFeatureFactory.createFeatureInstance(ModelFeatureFactory.java:83) at org.jboss.tools.common.model.filesystems.impl.FileSystemsRenameListener.<clinit>(FileSystemsRenameListener.java:27) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.<init>(FileSystemsImpl.java:33) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 4-14) Missing project nature extension for org.jboss.tools.jsf.jsfnature. org.eclipse.core.internal.resources.ResourceException: Missing project nature extension for org.jboss.tools.jsf.jsfnature. at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:214) at org.eclipse.core.internal.resources.Project.getNature(Project.java:378) at org.jboss.tools.common.model.util.EclipseResourceUtil.getModelNature(EclipseResourceUtil.java:207) at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:91) at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:61) at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:53) at org.jboss.tools.common.model.markers.XMarkerManager.<init>(XMarkerManager.java:37) at org.jboss.tools.common.model.markers.XMarkerManager.getInstance(XMarkerManager.java:28) at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.getErrorState(LabelDecoratorImpl.java:71) at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.decorateImage(LabelDecoratorImpl.java:40) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2602) Ctrl+1 feature for java editor work only in case in the current project has Default Hibernate Console Configuration - should work with empty Default Hibernate Console Configuration

by Vitali Yemialyanchyk (JIRA)

Ctrl+1 feature for java editor work only in case in the current project has Default Hibernate Console Configuration - should work with empty Default Hibernate Console Configuration ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-2602 URL: https://jira.jboss.org/jira/browse/JBIDE-2602 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.alpha Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor 1) Create java project and Enable Hibernate 3 support for it, leave Default Hibernate Console Configuration empty. Create some java class and some method X() in it. public X() { String str = "select from"; } select some word on the string "select from" and press Ctrl+1. 2) Now select some Default Hibernate Console Configuration. Return to our java class, select some word on the string "select from" and press Ctrl+1. I expect the same context menu for both cases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2561) Hibernate Criteria Editor opens with unsaved marker.

by Anton Klimkovich (JIRA)

Hibernate Criteria Editor opens with unsaved marker. ---------------------------------------------------- Key: JBIDE-2561 URL: https://jira.jboss.org/jira/browse/JBIDE-2561 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.alpha Environment: JBossTools-200807220811-nightly-ALL Reporter: Anton Klimkovich Assignee: Vitali Yemialyanchyk Priority: Minor EXECUTE: Create Seam web project EXECUTE: Open Hibernate Configurations view EXECUTE: Right mouse click on the project and select Hibernate Criteria Editor FAILURE: Hibernate Criteria Editor opens with unsaved marker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-2548) Extend XML Catalog for JBoss 4.2

by Juergen Zimmermann (JIRA)

Extend XML Catalog for JBoss 4.2 -------------------------------- Key: JBIDE-2548 URL: https://jira.jboss.org/jira/browse/JBIDE-2548 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.alpha Reporter: Juergen Zimmermann Some entries are missing for JBoss 4.2 (see https://jira.jboss.org/jira/browse/JBIDE-1788): * -//JBoss//DTD MBean Service 4.2//EN ** required for .sar when e.g. authentication is done via database or LDAP instead of .properties ** see file docs\dtd\jboss-service_4_2.dtd * -//JBoss//DTD JBOSS JCA Config 1.5//EN ** required when the app ships a datasource definition in a file xyz-ds.xml within a .sar ** see file docs\dtd\jboss-ds_1_5.dtd * -//JBoss//DTD Web Service Reference 4.2//EN ** required for jboss.xml ** see file docs\dtd\service-ref_4_2.dtd When using JBossWS-native 3.0.2 and using WS-Security then these 2 entries are also required: * http://www.jboss.com/ws-security/config ** see file jboss-ws-security_1_0.xsd in directory "schema" of jboss-ws-native-core.jar * urn:jboss:jaxws-config:2.0 ** see file jaxws-config_2_0.xsd in directory "schema" of jboss-ws-native-core.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 8 months

3
3
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 2008