Keith Babo created SWITCHYARD-738:
-------------------------------------
Summary: Upgrade to Camel 2.9.1
Key: SWITCHYARD-738
URL: https://issues.jboss.org/browse/SWITCHYARD-738
Project: SwitchYard
Issue Type: Task
Components: component-camel
Reporter: Keith Babo
Fix For: 0.5
Upgrade Camel dependencies to 2.9.1. A number of things changed around in core between 2.8.x and 2.9.x, so there may be some more work here than simply bumping the pom version.
--
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
Rob Cernich created SWITCHYARD-737:
--------------------------------------
Summary: Update BPEL schema referenced by SwitchYard to sca-implementation-bpel-1.1-cd03.xsd
Key: SWITCHYARD-737
URL: https://issues.jboss.org/browse/SWITCHYARD-737
Project: SwitchYard
Issue Type: Bug
Components: component-bpel
Affects Versions: 0.4
Reporter: Rob Cernich
Assignee: Rob Cernich
Priority: Minor
Fix For: 0.5
Use the bpel schema provided by the sca schema used by the rest of switchyard.
--
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
Keith Babo created SWITCHYARD-736:
-------------------------------------
Summary: SOAP gateway cannot handle SOAP 1.2 requests
Key: SWITCHYARD-736
URL: https://issues.jboss.org/browse/SWITCHYARD-736
Project: SwitchYard
Issue Type: Bug
Components: component-soap
Affects Versions: 0.4
Reporter: Keith Babo
Fix For: 0.5
SOAP 1.2 bindings fail in our unit test framework and when deployed to AS7. The failure is different between the two environments (JDK WS provider vs. CXF in AS7). To reproduce, take the bean-service quickstart and change the SOAP namespace in OrderService.wsdl to:
http://schemas.xmlsoap.org/wsdl/soap12/
Then change soap-request.xml and change the soap namespace to:
http://www.w3.org/2003/05/soap-envelope
I'm guessing that we need to add a property/metadata when creating the JAX-WS endpoint in order to tell the WS runtime that the SOAP endpoint is 1.2 vs. 1.1.
--
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
Keith Babo created SWITCHYARD-735:
-------------------------------------
Summary: forge formatting is messed up when interface.esb is present
Key: SWITCHYARD-735
URL: https://issues.jboss.org/browse/SWITCHYARD-735
Project: SwitchYard
Issue Type: Bug
Components: tooling
Affects Versions: 0.4
Reporter: Keith Babo
Fix For: 0.5
When a service uses an interface.esb, the formatting of show-config in forge is horked:
{code}
component: JavaDSLBuilder
service: JavaDSL
interface: org.switchyard.quickstarts.camel.service.JavaDSL
reference: XMLService
interface: component: XMLComponent
service: XMLService
interface:
{code}
Note the empty interface value and that XMLComponent has wrapped up into JavaDSLBuilder.
--
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
Keith Babo created SWITCHYARD-734:
-------------------------------------
Summary: forge camel-service command needs to try harder for xml routes
Key: SWITCHYARD-734
URL: https://issues.jboss.org/browse/SWITCHYARD-734
Project: SwitchYard
Issue Type: Enhancement
Components: component-camel
Reporter: Keith Babo
Fix For: 0.5
At the very least, the route should be created inside the implementation with a log processor or something. On top of that, it should be possible to specify the interface type used by the service (this applies to Java and XML routes).
--
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
Keith Babo created SWITCHYARD-733:
-------------------------------------
Summary: Create a script to automate version changes in SY repositories
Key: SWITCHYARD-733
URL: https://issues.jboss.org/browse/SWITCHYARD-733
Project: SwitchYard
Issue Type: Task
Components: build, distribution
Reporter: Keith Babo
Fix For: 0.5
The following things (as a minimum) need to happen in this script:
1) all pom.xml project/version strings need to be changed (e.g. 0.4.0-SNAPSHOT -> 0.4.0.CR1)
2) the version.distro string in release/pom.xml needs to be changed (e.g. 0.4 -> 0.5)
3) the switchyard.tools.url property in release/installer/scripts/installer.properties needs to be updated to point to the release tools URL for the release.
Any clean-up, simplification, or additional changes required would be good too.
--
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
Mario Antollini created SWITCHYARD-732:
------------------------------------------
Summary: add-reference forge command looks up the component service name instead of component name and does not allow wsdl interface type
Key: SWITCHYARD-732
URL: https://issues.jboss.org/browse/SWITCHYARD-732
Project: SwitchYard
Issue Type: Bug
Components: tooling
Affects Versions: 0.4
Reporter: Mario Antollini
Fix For: 0.5
In core's SwitchYardPlugin.java:
Bug:
1) line 460 is looking up the component service name instead of component name. They are the same sometimes, but are not required to be
2) line 477 is not accepting wsdl interface types as is
Suggested Fix:
1) if we are taking the component name, then you need to search the config model for that component name
2) re-write as: if (!interfaceType.equals("java") && !interfaceType.equals("wsdl")) {
--
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
Magesh Bojan created SWITCHYARD-731:
---------------------------------------
Summary: Fix Camel SOAP Proxy quickstart
Key: SWITCHYARD-731
URL: https://issues.jboss.org/browse/SWITCHYARD-731
Project: SwitchYard
Issue Type: Task
Components: quickstarts
Affects Versions: 0.4
Reporter: Magesh Bojan
Assignee: Magesh Bojan
Fix For: 0.5
Currently the service being proxied is not deployed in the server and has to be manually created and deployed. Add a web.xml and create a war deployment for this Webservice.
--
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
Keith Babo created SWITCHYARD-730:
-------------------------------------
Summary: Clustering and distribution support
Key: SWITCHYARD-730
URL: https://issues.jboss.org/browse/SWITCHYARD-730
Project: SwitchYard
Issue Type: Feature Request
Components: core
Reporter: Keith Babo
Assignee: Keith Babo
Priority: Critical
Fix For: 0.5
Provide distributed registry and runtime support to allow for clustering of SwitchYard instances.
--
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
Keith Babo created SWITCHYARD-729:
-------------------------------------
Summary: Support for JBoss ESB gateways
Key: SWITCHYARD-729
URL: https://issues.jboss.org/browse/SWITCHYARD-729
Project: SwitchYard
Issue Type: Feature Request
Reporter: Keith Babo
Priority: Critical
Fix For: 0.5
This is a top-level tracking issue for adding support for all JBoss ESB gateways in SwitchYard. Check the forum thread reference for additional detail.
--
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