August 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4733) Generated DDL should be optionally executed in db

by Dmitry Geraskov (JIRA)

Generated DDL should be optionally executed in db ------------------------------------------------- Key: JBIDE-4733 URL: https://jira.jboss.org/jira/browse/JBIDE-4733 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0.M4 Jpa-Generate DDL for hibernate platform is executed in db automatically. Should be optional. -- 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

16 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4590) provide update site zip to replace 4 platform-specific "ALL plugins" zips

by Nick Boldt (JIRA)

provide update site zip to replace 4 platform-specific "ALL plugins" zips ------------------------------------------------------------------------- Key: JBIDE-4590 URL: https://jira.jboss.org/jira/browse/JBIDE-4590 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.1.0.M2 Replace Win32, Lin32, Lin64 and MacCarbon32 zips w/ a single Update Site zip. Currently, these zips range from 74-84M each. First pass was 175M (included both packed and unpacked plugin jars). Second pass is 66M. With 4 platforms' contributions in a single site zip, we're saving 314 - 66 = 248M per build. -- 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

16 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4620) Mapping Diagram - toggle show/hide all connection types

by Vitali Yemialyanchyk (JIRA)

Mapping Diagram - toggle show/hide all connection types ------------------------------------------------------- Key: JBIDE-4620 URL: https://jira.jboss.org/jira/browse/JBIDE-4620 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M3 there are 3 types of connection arrows: 1) POJO class -> DB table; 2) POJO class -> POJO class; 3) class field -> table field; on a rather big diagram is difficult to clear visualize all connections cause too many arrows - it will be nice feature to show/hide some of them. add 3 toggle toolbar buttons here - for every connection type. -- 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

16 years, 6 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2550) Preliminary support for JSF 2.0

by Juergen Zimmermann (JIRA)

Preliminary support for JSF 2.0 ------------------------------- Key: JBIDE-2550 URL: https://jira.jboss.org/jira/browse/JBIDE-2550 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 3.0.0.alpha Reporter: Juergen Zimmermann JSF 2.0 EDR1 is available. I tested it with my up and found only one issue: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=748 I tested the fix with Mojarra r5055 and it works fine. However, the VPE cannot support previewing. There are only a couple of changes: 1) There is also <h:head> and <h:body> instead of plain <head> and <body> 2) Images can be included this way: <h:graphicImage value="#{resource['hskaCore:myImg.jpg']}" /> The default implementation will look for resources in two locations and in the following order: a) /resources this location represents resources in the webapp itself and if present, must be in the root of the web application b) /META-INF/resources this location represents resources on the classpath -- 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

16 years, 6 months

4
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4815) Model feature org.jboss.tools.seam.internal.core.el.SeamPromptingProvider is not registered with extension point org.jboss.tools.common.model.classes

by Krasimir Goutcev (JIRA)

Model feature org.jboss.tools.seam.internal.core.el.SeamPromptingProvider is not registered with extension point org.jboss.tools.common.model.classes ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4815 URL: https://jira.jboss.org/jira/browse/JBIDE-4815 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M3 Environment: JBoss Tools - H208 eclipse.buildId=I20090611-1540 java.version=1.6.0_10-beta java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -clean Reporter: Krasimir Goutcev java.lang.Exception: Model feature org.jboss.tools.seam.internal.core.el.SeamPromptingProvider is not registered with extension point org.jboss.tools.common.model.classes at org.jboss.tools.common.model.util.ModelFeatureFactory.createFeatureInstance(ModelFeatureFactory.java:74) at org.jboss.tools.jst.jsp.outline.ValueHelper.<clinit>(ValueHelper.java:67) at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.<init>(JSPPropertySourceAdapter.java:76) at org.jboss.tools.jst.jsp.outline.JSPPropertySheetConfiguration$JSPPropertySourceProvider0.getPropertySource(JSPPropertySheetConfiguration.java:56) at org.eclipse.ui.views.properties.PropertySheetEntry.getPropertySource(PropertySheetEntry.java:470) at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:752) at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:973) at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:510) at org.eclipse.wst.sse.ui.internal.properties.ConfigurablePropertySheetPage.selectionChanged(ConfigurablePropertySheetPage.java:174) at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:344) at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156) at org.eclipse.ui.internal.AbstractSelectionService.setActivePart(AbstractSelectionService.java:282) at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:60) at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3531) at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:614) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2869) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.jboss.tools.common.editor.OpenEditorWizard.execute(OpenEditorWizard.java:80) at org.jboss.tools.common.model.handlers.OpenEditorHandler.executeHandler(OpenEditorHandler.java:31) at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65) at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:96) at org.jboss.tools.common.model.ui.action.XModelObjectActionInvoker.execute(XModelObjectActionInvoker.java:36) at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:53) at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:40) at org.jboss.tools.common.model.ui.select.SelectObjectWizard.openEditor(SelectObjectWizard.java:142) at org.jboss.tools.common.model.ui.select.SelectObjectWizard.execute(SelectObjectWizard.java:47) at org.jboss.tools.common.model.util.FindObjectHelper.findModelObject(FindObjectHelper.java:40) at org.jboss.tools.common.model.files.handlers.CreateFileSupport$1.run(CreateFileSupport.java:215) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2544) Build JBossTools SDK

by Denis Golovin (JIRA)

Build JBossTools SDK -------------------- Key: JBIDE-2544 URL: https://jira.jboss.org/jira/browse/JBIDE-2544 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Denis Golovin Assignee: Denis Golovin Project is growing pretty fast, so that would be nice have SDK so any contributor can install it and and then checkout from SVN only particular component for development. -- 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

16 years, 6 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4795) Use NamingStrategy for explicit mapping

by Dmitry Geraskov (JIRA)

Use NamingStrategy for explicit mapping --------------------------------------- Key: JBIDE-4795 URL: https://jira.jboss.org/jira/browse/JBIDE-4795 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.1.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0.M4 -- 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

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2062) resource bundle code completion is not complete

by Max Rydahl Andersen (JIRA)

resource bundle code completion is not complete ----------------------------------------------- Key: JBIDE-2062 URL: http://jira.jboss.com/jira/browse/JBIDE-2062 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.1.0.cr1 Reporter: Max Rydahl Andersen Fix For: 2.1 Messages completion now at least uses the correct [] syntax for long names but now code completion does not work within the [] brackets. -- 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, 6 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2332) CA with proposal list for comonent's atributes doesn't work before double quotes.

by Anton Klimkovich (JIRA)

CA with proposal list for comonent's atributes doesn't work before double quotes. ---------------------------------------------------------------------------------- Key: JBIDE-2332 URL: http://jira.jboss.com/jira/browse/JBIDE-2332 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.1.0.GA Reporter: Anton Klimkovich EXECUTE: Create seam project EXECUTE: Open home.xhtml EXECUTE: Type <h:outputText "#{applicationScope}" /> EXECUTE: Set cursor before "#{applicationScope}" (Example : <h:outputText {cursor}"#{applicationScope}" /> ) EXECUTE: Call CA FAILLURE: CA is not available. There is no proposal list. -- 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, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4617) when create a partner link, in the property view, detail tab, the partner link type should be disable because the original value of the partner link type is none

by Feng Qian (JIRA)

when create a partner link, in the property view, detail tab, the partner link type should be disable because the original value of the partner link type is none ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4617 URL: https://jira.jboss.org/jira/browse/JBIDE-4617 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.1.0.M3 -- 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

16 years, 6 months

1
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 2009