June 2012 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-847) Add generated transformers to Transforms list

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-847: ------------------------------------- Summary: Add generated transformers to Transforms list Key: SWITCHYARD-847 URL: https://issues.jboss.org/browse/SWITCHYARD-847 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.5 Reporter: Keith Babo Fix For: 0.5 Add generated transformers to the list of transforms displayed in the composite property page. The strategy should go something like this: 1) the list should display all transformers - those in src and those generated 2) you should be able to create transformers, which would put an entry in src 3) you should be able to delete transformers, but only those declared in src -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-846) Add remove button to binding property page to allow removing bindings from the list

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created SWITCHYARD-846: -------------------------------------------- Summary: Add remove button to binding property page to allow removing bindings from the list Key: SWITCHYARD-846 URL: https://issues.jboss.org/browse/SWITCHYARD-846 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.5 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 0.5 The plan was to have add & remove buttons for the Binding property page so you could add and remove bindings right there. Currently we don't have a good way to add bindings (i.e. the older wizard we had that offered a list of binding choices, select one, click next to see the proper wizard page, click finish) so we won't add an Add button. Even so, that functionality is handled by the palette and drag/drop of bindings onto service/reference objects. But we do need a Remove button to allow users to remove bindings from the list. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-845) First time you select a component, the implementation property page throws a NPE

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created SWITCHYARD-845: -------------------------------------------- Summary: First time you select a component, the implementation property page throws a NPE Key: SWITCHYARD-845 URL: https://issues.jboss.org/browse/SWITCHYARD-845 Project: SwitchYard Issue Type: Bug Components: tooling Affects Versions: 0.5 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Minor Fix For: 0.5 Witnessed during Keith's demo and reproduced locally. 1) Click on a service component 2) Click on the Properties view 3) Select the Implementation property tab 4) See NPE {code} !ENTRY org.eclipse.jface 4 2 2012-06-06 13:38:52.501 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at org.switchyard.tools.ui.editor.property.SwitchyardSCAPropertiesMainSection.updateObjectName(SwitchyardSCAPropertiesMainSection.java:180) at org.switchyard.tools.ui.editor.property.SwitchyardSCAPropertiesMainSection.access$3(SwitchyardSCAPropertiesMainSection.java:163) at org.switchyard.tools.ui.editor.property.SwitchyardSCAPropertiesMainSection$1.focusLost(SwitchyardSCAPropertiesMainSection.java:111) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:143) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058) at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822) at org.eclipse.swt.widgets.Widget.wmKillFocus(Widget.java:1921) at org.eclipse.swt.widgets.Control.WM_KILLFOCUS(Control.java:4900) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4562) at org.eclipse.swt.widgets.Text.windowProc(Text.java:2254) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method) at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1098) at org.eclipse.swt.widgets.Control.setFocus(Control.java:3303) at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1040) at org.eclipse.swt.widgets.Control.fixFocus(Control.java:1053) at org.eclipse.swt.widgets.Control.setVisible(Control.java:3762) at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage$SelectionChangedListener.hideTab(TabbedPropertySheetPage.java:259) at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage$SelectionChangedListener.selectionChanged(TabbedPropertySheetPage.java:200) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) 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.Viewer.fireSelectionChanged(Viewer.java:162) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774) at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.select(TabbedPropertyList.java:664) at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList$2.mouseUp(TabbedPropertyList.java:156) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:219) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-844) Component destroy method not called

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-844: ------------------------------------- Summary: Component destroy method not called Key: SWITCHYARD-844 URL: https://issues.jboss.org/browse/SWITCHYARD-844 Project: SwitchYard Issue Type: Bug Reporter: Gary Brown Fix For: 0.5 The destroy method does not appear to be called from the SwitchYard test cases or AS7 deployment. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-843) Component init method not called from SwitchYardTestCase

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-843: ------------------------------------- Summary: Component init method not called from SwitchYardTestCase Key: SWITCHYARD-843 URL: https://issues.jboss.org/browse/SWITCHYARD-843 Project: SwitchYard Issue Type: Bug Reporter: Gary Brown Fix For: 0.5 When running a SwitchYard testcase, the init and destroy methods do not appear to be called. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-842) processDefinition cannot be null

by David Ward (JIRA)

David Ward created SWITCHYARD-842: ------------------------------------- Summary: processDefinition cannot be null Key: SWITCHYARD-842 URL: https://issues.jboss.org/browse/SWITCHYARD-842 Project: SwitchYard Issue Type: Bug Components: component-bpm Affects Versions: 0.4 Reporter: David Ward Assignee: David Ward Priority: Blocker Fix For: 0.5 Doing this: <bpm:implementation.bpm processId="com.foo.bar"> <resource location="/META-INF/ChangeSet.xml" type="CHANGE_SET"/> </bpm:implementation.bpm> results in this: Failed to execute goal org.switchyard:switchyard-plugin:0.5.0-SNAPSHOT:configure (default) on project FooBar: Model [org.switchyard.config.model.switchyard.v1.V1SwitchYardModel] is invalid: cvc-complex-type.4: Attribute 'processDefinition' must appear on element 'bpm:implementation.bpm'. -> [Help 1] [ERROR] Fixing this is a bit more work than just changing the schema in bpm-v1.xsd so that the processDefinition is 'optional' instead of 'required'. The DroolsBPMExchangeHandler appears to assume it to never be null as well. The reason we should not have to set the processDefinition attribute is that it should be able to be defined in the change set and gotten from Guvnor too, not just the "other" resources. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-841) WebServiceContext is null when running in AS7

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-841: --------------------------------------- Summary: WebServiceContext is null when running in AS7 Key: SWITCHYARD-841 URL: https://issues.jboss.org/browse/SWITCHYARD-841 Project: SwitchYard Issue Type: Bug Components: component-soap, distribution Affects Versions: 0.4 Reporter: Magesh Bojan Assignee: Magesh Bojan Priority: Blocker Fix For: 0.5 A @Resource injection of WebServiceContext does not seem to work in AS7. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-840) Faults not getting propagated through SOAP gateway

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-840: ------------------------------------- Summary: Faults not getting propagated through SOAP gateway Key: SWITCHYARD-840 URL: https://issues.jboss.org/browse/SWITCHYARD-840 Project: SwitchYard Issue Type: Bug Components: component-soap Affects Versions: 0.5 Reporter: Keith Babo Fix For: 0.5 Send a SOAP message to a service that's missing a transformer and you'll see this in the log: {code} 20:24:03,168 ERROR [org.switchyard.internal.DefaultHandlerChain] (http-localhost-127.0.0.1-8080-1) org.switchyard.HandlerException was thrown by handler(transformation): Transformations not applied. Required payload type of 'java:com.example.switchyard.demo1.Invoice'. Actual payload type is '{urn:com.example.switchyard:demo1:0.0.1-SNAPSHOT}submit'. You must define and register a Transformer to transform between these types. {code} But this is the SOAP response: {code} <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Server</faultcode> <faultstring>org.switchyard.exception.SwitchYardException: Cannot convert from 'org.switchyard.HandlerException' to 'org.w3c.dom.Node'. No registered Transformer available for transforming from 'java:org.switchyard.HandlerException' to 'java:org.w3c.dom.Node'. A Transformer must be registered.</faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> {code} There's an issue with fault processing in the SOAP gateway and maybe something more general in the fault handling logic in core as well. Investigate and fix. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-839) Change multi-page editor to not allow editing on source tab

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created SWITCHYARD-839: -------------------------------------------- Summary: Change multi-page editor to not allow editing on source tab Key: SWITCHYARD-839 URL: https://issues.jboss.org/browse/SWITCHYARD-839 Project: SwitchYard Issue Type: Bug Components: tooling Affects Versions: 0.5 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 0.5 When editing the XML source in the source tab currently, the diagram will crash. This is bad. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-838) Add operationSelector to all Camel gateway binding configs

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-838: ------------------------------------- Summary: Add operationSelector to all Camel gateway binding configs Key: SWITCHYARD-838 URL: https://issues.jboss.org/browse/SWITCHYARD-838 Project: SwitchYard Issue Type: Task Components: tooling Affects Versions: 0.5 Reporter: Keith Babo Assignee: Brian Fitzpatrick Fix For: 0.5 I missed this important config parameter in my forum posts on binding configuration. Each Camel binding supports this configuration element: {code} <element name="operationSelector" type="camel:CamelOperationSelectorType" minOccurs="0" maxOccurs="1"/> {code} An example: {code} <camel:binding.jms> <camel:operationSelector operationName="greet"/> <camel:queue>GreetingServiceQueue</camel:queue> <camel:connectionFactory>#ConnectionFactory</camel:connectionFactory> </camel:binding.jms> {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

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues June 2012