February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7100) Wrond proposals appear in CA Window for CSS styles inside <style></style> tag

by Victor Rubezhny (JIRA)

Wrond proposals appear in CA Window for CSS styles inside <style></style> tag ----------------------------------------------------------------------------- Key: JBIDE-7100 URL: https://jira.jboss.org/browse/JBIDE-7100 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Environment: Eclipse 3.6; WTP 3.2 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Wrong proposals appear in CA Window for CSS styles inside <style></style> tag when: 1. There is at least one whitespace character is placed between opening and closing "style" tags -and- 2. The CA is invoked when the cursor is pointed right before the closing tag (i.e. "<style type="text/css"> |</style>", where "|"-char indicates the cursor position. In such cases WTP suggests proposals for a new tags insertion, but not the CSS proposals. Probably it's WTP's issue, because: 1. WTP decides which kind of proposals are to be calculated at some cursor position. 2. We don't add any computers for CSS proposals since WTP 3.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-2438) Support for backing bean configuration in Spring application context

by Claus Nyhus (JIRA)

Support for backing bean configuration in Spring application context -------------------------------------------------------------------- Key: JBIDE-2438 URL: http://jira.jboss.com/jira/browse/JBIDE-2438 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Claus Nyhus Hi, When using Spring with JSF it is very compelling to define backing beans in Springs application context (either via XML configuration or annotations) rather than in faces-config.xml. The downside of this is that you cannot use completion on properties from the backing beans in JBoss tools when editing JSF pages (e.g. facelets files). It would be very nice if JBoss Tools could pick up backing beans from a Spring application context and treat them the same way backing beans from faces-config.xml is handled. Cheers /Claus References for defining backing beans in an Spring application context: http://prime.com.tr/cagataycivici/?p=92 http://prime.com.tr/cagataycivici/?p=94 -- 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

14 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6883) Smooks wizard throws exception and doesn't open file when wizard finishes

by Brian Fitzpatrick (JIRA)

Smooks wizard throws exception and doesn't open file when wizard finishes ------------------------------------------------------------------------- Key: JBIDE-6883 URL: https://jira.jboss.org/browse/JBIDE-6883 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: smooks Affects Versions: 3.2.x Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta When you use the new Smooks Configuration File wizard to create a Smooks file, it creates the file and then should open it in the editor. Instead, I'm seeing this error: !ENTRY org.jboss.tools.smooks.ui 4 4 2010-08-20 15:46:20.968 !MESSAGE Error !STACK 1 org.eclipse.ui.PartInitException: Unable to open editor, unknown editor ID: org.jboss.tools.smooks.configuration.editors.MultiPageEditor at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:633) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2860) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2682) at org.jboss.tools.smooks.configuration.wizards.SmooksConfigurationFileNewWizard$2.run(SmooksConfigurationFileNewWizard.java:142) 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:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008) at org.jboss.tools.smooks.configuration.wizards.SmooksConfigurationFileNewWizard.performFinish(SmooksConfigurationFileNewWizard.java:87) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) 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:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) 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:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) !SUBENTRY 1 org.eclipse.ui 4 0 2010-08-20 15:46:20.983 !MESSAGE Unable to open editor, unknown editor ID: org.jboss.tools.smooks.configuration.editors.MultiPageEditor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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: (JBDS-1170) ESB Tooling for SOAP Envelopes and schemas Native support

by Gary Lamperillo (JIRA)

ESB Tooling for SOAP Envelopes and schemas Native support --------------------------------------------------------- Key: JBDS-1170 URL: https://jira.jboss.org/jira/browse/JBDS-1170 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Gary Lamperillo Attachments: smooks_transform_from_soap.png SOAP Envelopes and schemas should be handled more natively by the current ESB Tooling. To illustrate the difficulty for the developers when it is not handled natively: When a Web Service transformation is made with Smooks, the entire SOAP Envelope needs to be imported, additional items like security may change based on the service contract, this will cause issues for more than the most basic example. In addition, A Content Base Router could use the Soap Envelope without the need for casts of Message body to Classes, which can cause many exceptions during runtime. The XSLT Actions could also use the entire SOAP Envelope as well. Tooling should be available to import the SOAP Envelope and the defined body and Security Headers etc. the 3 attached screenshots hope to show the need for SOAP Native support. -- 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
13
0 / 0

[JBoss JIRA] Created: (JBIDE-6884) Save and Save All doesn't seem to work with the Smooks editor currently

by Brian Fitzpatrick (JIRA)

Save and Save All doesn't seem to work with the Smooks editor currently ----------------------------------------------------------------------- Key: JBIDE-6884 URL: https://jira.jboss.org/browse/JBIDE-6884 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: smooks Affects Versions: 3.2.x Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.2.0.Beta While testing the new input panel for Java classes that Tom did, I noticed that I'm unable to save a file currently. Save and Save All don't seem to work at all. I'm getting nothing in the console or error log either. Any ideas? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6948) For Java Sources, check that the Project is a valid type

by Tom Fennelly (JIRA)

For Java Sources, check that the Project is a valid type -------------------------------------------------------- Key: JBIDE-6948 URL: https://jira.jboss.org/browse/JBIDE-6948 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.3.x i.e. that it can (e.g. is a Java Project type) and does contain Java classes. See JBIDE-6868 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5358) Change how beans are expanded when added via the bean add dialog

by Tom Fennelly (JIRA)

Change how beans are expanded when added via the bean add dialog ---------------------------------------------------------------- Key: JBIDE-5358 URL: https://jira.jboss.org/jira/browse/JBIDE-5358 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, we iterate down the object model and add all sub-objects etc. This is looking a bit messy because: 1. It requires the user to expand out a tree in the bottom half of the bean creation dialog, selecting the sub-domain objects he/she wants to be added. 2. The beans all land on the canvas at the one time, which requires a load of rearranging etc I think it would be nicer for the user if only the bean class entered in the Bean Creation wizard was dropped on the canvas, with all it's properties, but not drop in the sub-domain classes, wired together etc (as now). If some of the properties are for sub-domain objects, the user should be able to right-click and add, resulting in that sub-domain object being added etc etc. The user can expand it out as they want. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6777) Add CSV reader panel in Process editor

by Xue Peng (JIRA)

Add CSV reader panel in Process editor -------------------------------------- Key: JBIDE-6777 URL: https://jira.jboss.org/browse/JBIDE-6777 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: smooks Reporter: Xue Peng Assignee: Xue Peng 1. generate csv reader ecore model codes 2. re-add the csv reader panel a.create the csv reader detail panel b.re-add codes to generate XML structure model for displaying at the Model view -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5404) Smooks Drag and Drop Editor

by Jim Tyrrell (JIRA)

Smooks Drag and Drop Editor --------------------------- Key: JBIDE-5404 URL: https://jira.jboss.org/jira/browse/JBIDE-5404 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell Just saw a demo here: http://www.screencast.com/users/tfennelly/folders/Camtasia/media/4b184ca6... It would be nice to be able to reorder fields on either side of the graph when you are doing the Java Mapping. In other words it would be nice to not have to have lines cross if at all possible. It would be even better if this would be automatic that fields in an object would order the same way in both views. It would also be nice that dragging a field into a mapping would prompt for a dialogue box to ask/see if all the other like mappings should be applied rather then having to apply them. Quickstarts around the smooks editor that are easily importable into JBDS w/o any messing around with anything. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5294) Add ability to control output result types in Run Configuration

by Tom Fennelly (JIRA)

Add ability to control output result types in Run Configuration --------------------------------------------------------------- Key: JBIDE-5294 URL: https://jira.jboss.org/jira/browse/JBIDE-5294 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, it's outputting everything, which can be information overload. -- 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
6
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 February 2011