December 2009 - jbosstools-issues

[JBoss JIRA] Closed: (JBIDE-4863) BPEL Process Versioning

by Aliaksey Nis (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4863?page=com.atlassian.jira.plu... ] Aliaksey Nis closed JBIDE-4863. ------------------------------- Duplicate issue. Closed. > BPEL Process Versioning > ----------------------- > > Key: JBIDE-4863 > URL: https://jira.jboss.org/jira/browse/JBIDE-4863 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Brian Fitzpatrick > Assignee: Denny Xu > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The process versioning requirement is to support an optional 'version' attribute on the top level 'deploy' element in the bpel-deploy.xml deployment descriptor, and > provide: > 1) Extension to ODE deployment descriptor editor to allow user to define the version. > 2) When BPEL project is deployed to AS server, if a version has been specified, then it should be used as the suffix of the jar name. > The version attribute should be defined in its own namespace - open to suggestions? -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-5292) Move xstream jar to smooks.core project

by Xue Peng (JIRA)

Move xstream jar to smooks.core project --------------------------------------- Key: JBIDE-5292 URL: https://jira.jboss.org/jira/browse/JBIDE-5292 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.M4 Reporter: Xue Peng Assignee: Tom Fennelly Fix For: 3.1.0.CR1 Move the xstream.jar to smooks.core project. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2918) rich:dataTable must be redesigned

by Sergey Dzmitrovich (JIRA)

rich:dataTable must be redesigned --------------------------------- Key: JBIDE-2918 URL: https://jira.jboss.org/jira/browse/JBIDE-2918 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Sergey Dzmitrovich Assignee: Sergey Dzmitrovich Priority: Minor Fix For: 3.0.0.cr1 rich:dataTable(may be and subTable and columnGroup) must be redesigned as subTable and columnGroup are processed incorrectly ( for instance we can't select them) -- 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

14 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-819) Driver properties for DefaultDS connection profile cannot be changed in Connection Profile properties dialog

by Denis Golovin (JIRA)

Driver properties for DefaultDS connection profile cannot be changed in Connection Profile properties dialog ------------------------------------------------------------------------------------------------------------ Key: JBDS-819 URL: https://jira.jboss.org/jira/browse/JBDS-819 Project: Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Denis Golovin Fix For: 2.1.0, 3.0.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

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5384) Hibernate Mapping Diagram adjust popup menu, main menu and toolbar

by Vitali Yemialyanchyk (JIRA)

Hibernate Mapping Diagram adjust popup menu, main menu and toolbar ------------------------------------------------------------------ Key: JBIDE-5384 URL: https://jira.jboss.org/jira/browse/JBIDE-5384 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.GA 1) Show|Hide connection - toolbar dropdown button items: Select manhattan connection router & Select fan connection router move these into main View menu and rename into Connections -> submenu a) Straight lines b) Routed 2) change popup menu items order - should be: a) Open Source file; b) Open Mapping file -- c) Shape(s) -> c0) Select all c1) Show|Hide c2) Expand|Collapse; d) Connections -> same popup menu as "Show|Hide connections", just rename items as (1) describe -- e) Auto layout; f) Export as Image; 3) same changes as in (2) for outline popup menu -- 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

14 years, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5111) Fix failed junit tests after changing selection mechanizm

by Maxim Areshkau (JIRA)

Fix failed junit tests after changing selection mechanizm --------------------------------------------------------- Key: JBIDE-5111 URL: https://jira.jboss.org/jira/browse/JBIDE-5111 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Yura Zhishko Fix For: 3.1.0.CR1 For driving selection border for element we have used inFlasher xpcom interface. Now we draw this border modifying style attribute, adding such lines to style "border: 2px solid blue;". See function XulRunnerEditor.drawElementOutline(...).https://jira.jboss.org/jira/brows... Some of test begin failed with following exception, fix them. junit.framework.AssertionFailedError: string is"border: 2px solid blue; width: 1000px; background-color: white;" but must be "width: 1000px; background-color: white;" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareElements(ComponentContentTest.java:136) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:95) at org.jboss.tools.jsf.vpe.richfaces.test.RichFacesComponentContentTest.testPageWithWidthsPixels(RichFacesComponentContentTest.java:356) 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:585) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:114) 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:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) 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.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:46) 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:585) 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4373) Recreate OpenOn mechanizm for Visual Part of VPE

by Maxim Areshkau (JIRA)

Recreate OpenOn mechanizm for Visual Part of VPE ------------------------------------------------ Key: JBIDE-4373 URL: https://jira.jboss.org/jira/browse/JBIDE-4373 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0.M1 We can call open on action from visual part and from source part. Now we have two difference implementations of openOn from source and visual part. We should use one source implementation. -- 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

14 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4812) JSF 2: CSS as a resource

by Juergen Zimmermann (JIRA)

JSF 2: CSS as a resource ------------------------ Key: JBIDE-4812 URL: https://jira.jboss.org/jira/browse/JBIDE-4812 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Environment: Eclipse 3.5.0, WTP 3.1, JBossTools nightly 200908211801-H205 Reporter: Juergen Zimmermann Fix For: 3.1.0.M3 CSS is not considered when using JSF 2. A CSS file can be referenced as a resource: <link rel="stylesheet" type="text/css" href="#{resource['css:hska.css']}"/> This is just the same resource referencing as for images. See https://jira.jboss.org/jira/browse/JBIDE-2550 -- 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

14 years, 6 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4509) OpenOn from taglib definition file

by Maxim Areshkau (JIRA)

OpenOn from taglib definition file ---------------------------------- Key: JBIDE-4509 URL: https://jira.jboss.org/jira/browse/JBIDE-4509 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Maxim Areshkau Assignee: Maxim Areshkau -- 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

14 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5397) BPEL Plugin - Apache ODE Deployment Descriptor Save appears to not save

by Brad Maxwell (JIRA)

BPEL Plugin - Apache ODE Deployment Descriptor Save appears to not save ------------------------------------------------------------------------ Key: JBIDE-5397 URL: https://jira.jboss.org/jira/browse/JBIDE-5397 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5 jee-galileo-SR1 + JBoss Tools 1.0.0.v200912010817N-H2-RC1 Reporter: Brad Maxwell The bpel-deploy.xml file is actually saved, however appears to not be saved by 2 visual indicators: the Save icon in the tool bar and the file name *bpel-deploy.xml in the Tab To reproduce: 1) Click File / New / Other 2) Select Apache ODE Deployment Descriptor 3) Click Finish 4) Change something in the Deployment descriptor, such as checking/unchecking "Run this process in memory" 5) The Save icon on the toolbar is now enabled 6) Click the Save icon in the toolbar 7) The Save button in the toolbar is still enabled and in the Tab with the file name "bpel-deploy.xml" still shows "*bpel-deploy.xml", which makes it look like the file has not been saved even though it has. -- 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

14 years, 6 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009