[JBoss JIRA] (SWITCHYARD-818) NPE when changing component name in properties view
by Rob Cernich (JIRA)
Rob Cernich created SWITCHYARD-818:
--------------------------------------
Summary: NPE when changing component name in properties view
Key: SWITCHYARD-818
URL: https://issues.jboss.org/browse/SWITCHYARD-818
Project: SwitchYard
Issue Type: Bug
Components: tooling
Affects Versions: 0.5
Reporter: Rob Cernich
Assignee: Brian Fitzpatrick
Fix For: 0.5
{noformat}
java.lang.NullPointerException
at org.switchyard.tools.ui.editor.property.SwitchyardSCAPropertiesMainSection.updateObjectName(SwitchyardSCAPropertiesMainSection.java:114)
at org.switchyard.tools.ui.editor.property.SwitchyardSCAPropertiesMainSection.access$3(SwitchyardSCAPropertiesMainSection.java:95)
at org.switchyard.tools.ui.editor.property.SwitchyardSCAPropertiesMainSection$1.modifyText(SwitchyardSCAPropertiesMainSection.java:81)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
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.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
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: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: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)
{noformat}
--
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, 7 months
[JBoss JIRA] (SWITCHYARD-815) Transformer support in tooling
by Keith Babo (JIRA)
Keith Babo created SWITCHYARD-815:
-------------------------------------
Summary: Transformer support in tooling
Key: SWITCHYARD-815
URL: https://issues.jboss.org/browse/SWITCHYARD-815
Project: SwitchYard
Issue Type: Feature Request
Components: tooling
Affects Versions: 0.5
Reporter: Keith Babo
This is an umbrella JIRA for various transformer-related features. We need to add the following capabilities related to transformers for our tooling:
1) Create a new transformer. There are multiple options (Java, JSON, XSLT, Smooks, JAXB). Each one will result in config and additional artifacts being generated (e.g. an empty XSL transform). I suggest we start with Java as the first option, which would be a Java class with an @Transformer annotation.
2) Detect which types need to be transformed. This is more advanced and can take different forms. Maybe this is just a list of data types when creating a new transformer. Or maybe it's a dynamic hash of from/to types that need to be satisfied for the entire set of services. This information would be culled from the service and reference interface definitions and then presented to the user as a list or maybe as warning icons on the edges between service and reference nodes.
--
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, 7 months
[JBoss JIRA] (SWITCHYARD-813) Provide help in selecting port type for WSDL interfaces
by Keith Babo (JIRA)
Keith Babo created SWITCHYARD-813:
-------------------------------------
Summary: Provide help in selecting port type for WSDL interfaces
Key: SWITCHYARD-813
URL: https://issues.jboss.org/browse/SWITCHYARD-813
Project: SwitchYard
Issue Type: Feature Request
Components: tooling
Affects Versions: 0.5
Reporter: Keith Babo
Fix For: 0.5
If the user selects a WSDL interface type and an existing WSDL, we should provide some help in identifying the port type that will be used. Right now, I do this:
WSDL URI : META-INF/Orders.wsdl#wsdl.porttype(OrdersPortType)
Suggest that this is split up into:
WSDL : META-INF/Orders.wsdl
Port Type : OrdersPortType
Which would produce the above WSDL URI inside the user config. The Port Type input field can have a "..." icon which will parse the referenced WSDL file and list the port types available.
--
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, 7 months