July 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-350) Investigate SwitchYard configuration errors/warnings

by Tom Fennelly (JIRA)

Investigate SwitchYard configuration errors/warnings ----------------------------------------------------- Key: SWITCHYARD-350 URL: https://issues.jboss.org/browse/SWITCHYARD-350 Project: SwitchYard Issue Type: Task Components: configuration Reporter: Tom Fennelly Fix For: 0.2 Even after registering all the schemas for the config namespaces we use and define, I still see lots of errors in the SwitchYard configs inside IntelliJ (example screenshot attached). I think I remember Daniel saying he say similar errors in Eclipse, but not sure what he was using. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-349) Move the Camel CDI Registry code out into a module of its own

by Tom Fennelly (JIRA)

Move the Camel CDI Registry code out into a module of its own ------------------------------------------------------------- Key: SWITCHYARD-349 URL: https://issues.jboss.org/browse/SWITCHYARD-349 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Tom Fennelly At the moment, it is in with camel-core due to how we are assembling the camel components for AS7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-348) Make it possible to use the camel testing functionality

by Tom Fennelly (JIRA)

Make it possible to use the camel testing functionality ------------------------------------------------------- Key: SWITCHYARD-348 URL: https://issues.jboss.org/browse/SWITCHYARD-348 Project: SwitchYard Issue Type: Feature Request Components: component-camel, test Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 Camel provides test support via extension of it's base TestCase classes. Would be nice to make this available to SwitchYard users, along with the existing test MixIn functionality. I looked at adding the base test class as a MixIn i.e. the users test class would not actually extend the base camel test class. I don't think this is not going to work however because of all the camel test annotations etc. It really needs to be hooked in properly into the test by extension, as designed. Our tests having to extend the SwitchYardTestCase is kinda getting in the way here I think. I'm actually starting to think it may be better to provide our MixIns as annotated properties on the test class, using a TestRunner to wire it all up. I also think this will help us evolve towards tighter integration with Arquillian. Something like... {code} @RunWith(SwitchYardRunner.class) public class CoolTest { @MixIn private CDIMixIn cdiMixIn; // etc... } {code} Then the test can be extended by the camel test classes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-347) SOAP gateway does not detect operation name property for doc/lit

by Keith Babo (JIRA)

SOAP gateway does not detect operation name property for doc/lit ---------------------------------------------------------------- Key: SWITCHYARD-347 URL: https://issues.jboss.org/browse/SWITCHYARD-347 Project: SwitchYard Issue Type: Bug Components: component-soap Reporter: Keith Babo Fix For: 0.2 It looks like the SOAP gateway is assuming that the element in the SOAP:Body always has the same name as the WSDL operation. This is true for doc/lit wrapped, but is not required for doc/lit. See SOAPUtil.getOperationName() and InboundHandler.invoke() for the details. Seems like a small tweak to WSDLUtil.getOperation() could allow for the element name to be passed in (which it currently passes as "operationName") and that can be used to lookup the operation name whether it's doc/lit or doc/lit + wrapped. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-346) Implement population of admin model for as7 deployments

by Rob Cernich (JIRA)

Implement population of admin model for as7 deployments ------------------------------------------------------- Key: SWITCHYARD-346 URL: https://issues.jboss.org/browse/SWITCHYARD-346 Project: SwitchYard Issue Type: Sub-task Components: admin Reporter: Rob Cernich Fix For: 0.2 Populate admin model for as7 deployments. Refer to SWITCHYARD-345. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-345) Enable admin model to be populated during application deployment

by Rob Cernich (JIRA)

Enable admin model to be populated during application deployment ---------------------------------------------------------------- Key: SWITCHYARD-345 URL: https://issues.jboss.org/browse/SWITCHYARD-345 Project: SwitchYard Issue Type: Sub-task Components: admin Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.2 Create a mechanism whereby the administration model can be populated during application deployment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-344) Expose admin interface through as7 management api

by Rob Cernich (JIRA)

Expose admin interface through as7 management api ------------------------------------------------- Key: SWITCHYARD-344 URL: https://issues.jboss.org/browse/SWITCHYARD-344 Project: SwitchYard Issue Type: Feature Request Components: admin Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.2 Create management operations for accessing SwitchYard administrative details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-343) Scanner classpath URL resolution not working properly via surefire

by Tom Fennelly (JIRA)

Scanner classpath URL resolution not working properly via surefire ------------------------------------------------------------------ Key: SWITCHYARD-343 URL: https://issues.jboss.org/browse/SWITCHYARD-343 Project: SwitchYard Issue Type: Bug Components: test Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 Basically... surefire wraps up all the test resources in a single jar and puts them in a tmp folder. SwitchYardTestCase only scans directories (reason - so as to avoid scanning vm jars). The target/classes and target/test-classes folders are not one of the scan urls. Need to work out how we could reliably scan jars from SwitchYardTestCase, without scanning the world :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-342) Integrate CDI bean registry into Camel component

by Tom Fennelly (JIRA)

Integrate CDI bean registry into Camel component ------------------------------------------------ Key: SWITCHYARD-342 URL: https://issues.jboss.org/browse/SWITCHYARD-342 Project: SwitchYard Issue Type: Feature Request Reporter: Tom Fennelly -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-341) Deployment.loadServiceInterface throws uninformative NPE if Service interface class not found

by Tom Fennelly (JIRA)

Deployment.loadServiceInterface throws uninformative NPE if Service interface class not found --------------------------------------------------------------------------------------------- Key: SWITCHYARD-341 URL: https://issues.jboss.org/browse/SWITCHYARD-341 Project: SwitchYard Issue Type: Bug Components: core, deployment Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 It just assumes that the class specified in the InterfaceModel (config) is OK. Add a check and provide a useful error message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues July 2011