March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11121: ---------------------------------- Summary: Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone Key: JBIDE-11121 URL: https://issues.jboss.org/browse/JBIDE-11121 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.Beta1-soa Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1-soa Generate target platforms for JBT/JBDS SOA Tooling which include: 1. JBT Core TP + last stable JBT Core milestone. 2. JBDS Core TP + last stable JBDS Core milestone. Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones. This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

6
22
0 / 0

[JBoss JIRA] Created: (JBIDE-3526) Code assist for EL variables that come from <ui:param/>

by Alexey Kazakov (JIRA)

Code assist for EL variables that come from <ui:param/> ------------------------------------------------------- Key: JBIDE-3526 URL: https://jira.jboss.org/jira/browse/JBIDE-3526 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0 For example: mainPage.xhtml ... <ui:include src="/layout/incPage.xhtml"> <ui:param name="var1" value="#{someBean}"/> </ui:include> ... /loyout/incPage.xhtml ... <h:outputText value="#{var1.text}"/>  ... -- 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

12 years

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-6135) EL validation failes for valid JSF-EL

by nimo stephan (JIRA)

EL validation failes for valid JSF-EL ------------------------------------- Key: JBIDE-6135 URL: https://jira.jboss.org/jira/browse/JBIDE-6135 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Jboss Tools 3.1 GA, Facelets, JSF 1.2, Eclipse 3.5 Reporter: nimo stephan When using the following valid EL in XHTML: #{myBean.myMap['hobby'].size} the Jboss tools validator throws the following exception: 'size' cannot be resolved. Jboss tools should treat such expressions not as an error. -- 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

12 years

7
15
0 / 0

[JBoss JIRA] Created: (JBIDE-7908) Continue reading DB dialog should have "Never Show again" oprion

by Dmitry Geraskov (JIRA)

Continue reading DB dialog should have "Never Show again" oprion ---------------------------------------------------------------- Key: JBIDE-7908 URL: https://issues.jboss.org/browse/JBIDE-7908 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Optional Fix For: 3.2.0.CR1 Attachments: dialog.PNG Go to Reverce Engeneering Editor -> Type Mappings tab. Press Refresh button. Appeared dialog doesn't have "Never show again" option -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
11
0 / 0

[JBoss JIRA] (JBIDE-11111) move JBT Core Central discovery plugin out of Central component's pom.xml + create matching Jenkins jobs to build + publish

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11111: ---------------------------------- Summary: move JBT Core Central discovery plugin out of Central component's pom.xml + create matching Jenkins jobs to build + publish Key: JBIDE-11111 URL: https://issues.jboss.org/browse/JBIDE-11111 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.Beta1-soa Reporter: Nick Boldt Assignee: Snjezana Peco Fix For: 3.3.0.Beta1-soa Need an org.jboss.tools.central.discovery.soa-tooling plugin akin to [1] or [2] for SOA Tooling contributions to Central in JBoss Tools. [1] https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos... [2] https://svn.jboss.org/repos/devstudio/trunk/product-soa/plugins/com.jboss... Location should either be a new project in JBT SVN repo (or even in github) or else contained in the JBT SOA aggregate site (http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
24
0 / 0

[JBoss JIRA] (JBIDE-11250) PartInitException related with org.jboss.tools.project.examples.wizard.ProjectReadyWizard

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-11250: ------------------------------------- Summary: PartInitException related with org.jboss.tools.project.examples.wizard.ProjectReadyWizard Key: JBIDE-11250 URL: https://issues.jboss.org/browse/JBIDE-11250 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M5 Reporter: Daniel Azarov Assignee: Snjezana Peco Attachments: jboss-seam-jpa.png Test case: 1. Start JBDS 2. Import project "Seam Booking Example - WAR Standalone" 3. Open in Project Explorer jboss-seam-jpa->Deployment Descriptor:jboss-seam-jpa->Listeners !jboss-seam-jpa.png! 4. Double Click on SeamListener FAIL: {code} org.eclipse.ui.PartInitException: Could not get an editor input for the given element at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.throwPartInitException(EditorUtility.java:375) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:172) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:148) at org.eclipse.jst.jee.ui.internal.navigator.OpenJEEResourceAction.run(OpenJEEResourceAction.java:271) at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221) at org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:185) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:866) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:864) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1152) at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1256) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:269) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:309) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.project.examples.wizard.ProjectReadyWizard$1.run(ProjectReadyWizard.java:70) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:344) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9648) Improperly pluralizing Keys in hbm2java

by Caleb none (JIRA)

Improperly pluralizing Keys in hbm2java --------------------------------------- Key: JBIDE-9648 URL: https://issues.jboss.org/browse/JBIDE-9648 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.x Environment: Windows 7 64bit Reporter: Caleb none Assignee: Dmitry Geraskov When I create my POJOs from the XML files using the Hibernate Tools (hbm2java), the word "key" is being pluralized "keies" instead of "keys". For example: "orderTypeKeies" instead of "orderTypeKeys". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

8
20
0 / 0

[JBoss JIRA] Created: (JBIDE-8512) JPA: Type annotation - add typeDef java completion proposals

by Dmitry Geraskov (JIRA)

JPA: Type annotation - add typeDef java completion proposals ------------------------------------------------------------ Key: JBIDE-8512 URL: https://issues.jboss.org/browse/JBIDE-8512 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Minor Fix For: 3.3.x Type name declared as TypeDefs should be proposed in @Type annotation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8631) In VPE selected part color - should be configurable parameter

by Vitali Yemialyanchyk (JIRA)

In VPE selected part color - should be configurable parameter ------------------------------------------------------------- Key: JBIDE-8631 URL: https://issues.jboss.org/browse/JBIDE-8631 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.2.x Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau For some cases - for example there a lot of dark colors in page design or even blue color (which is used for selection) - it will not be possible to distinguish selected element. So it will be good if be possible to configure this parameter. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

7
12
0 / 0

[JBoss JIRA] Created: (JBIDE-9535) JPA: take into account hibernate.default_schema/hibernate.default_catalog when validate Table

by Dmitry Geraskov (JIRA)

JPA: take into account hibernate.default_schema/hibernate.default_catalog when validate Table --------------------------------------------------------------------------------------------- Key: JBIDE-9535 URL: https://issues.jboss.org/browse/JBIDE-9535 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: LATER JPA validator doen't take into account hibernate.default_schema/hibernate.default_catalog when validates Table existance. Test case: 1. Create table mytable in schema test 2. in Persistence.xml add hibernate.default_schema=test 3. cerate Entity Mytable without @Table(schema="test") 4. Make a DTP connection to the databse OBSERVE: wrong error appiared (Table "Mytable" cannot be sesolved) add @Table(schema="test") - error disappeared Probably the properties should be processed like the project properties (Oveddide default schema/catalog) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2012