June 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-309) SOAP inbound gateway processes requests sequentially

by Jiri Pechanec (JIRA)

SOAP inbound gateway processes requests sequentially ---------------------------------------------------- Key: SWITCHYARD-309 URL: https://issues.jboss.org/browse/SWITCHYARD-309 Project: SwitchYard Issue Type: Bug Components: component-soap Affects Versions: 0.1 Environment: AS 7 Reporter: Jiri Pechanec I tried to create a service that will simulate long processing (10 secs sleep). If I try to send two request then they are processed sequentially - the first is in process and the second is blocked. As SOAP frequently uses InOut message then such behaviour is not correct as it leads to no scalability. See an example from log 11:34:23,426 INFO [stdout] (Thread-25) Starting long op 11:34:33,426 INFO [stdout] (Thread-25) Long op finished 11:35:07,289 INFO [stdout] (Thread-25) Starting long op 11:35:17,290 INFO [stdout] (Thread-25) Long op finished 11:35:17,318 INFO [stdout] (Thread-25) Starting long op 11:35:27,319 INFO [stdout] (Thread-25) Long op finished 11:53:38,663 INFO [stdout] (Thread-25) Starting long op 11:53:48,663 INFO [stdout] (Thread-25) Long op finished 11:53:48,689 INFO [stdout] (Thread-25) Starting long op 11:53:58,689 INFO [stdout] (Thread-25) Long op finished All requests are process by same thread I am invoking TestService using SOAP UI, two requests at the same time -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-308) Build failure with the [org.switchyard:switchyard-api:0.1.0] versions and Forge

by Len DiMaggio (JIRA)

Build failure with the [org.switchyard:switchyard-api:0.1.0] versions and Forge ------------------------------------------------------------------------------- Key: SWITCHYARD-308 URL: https://issues.jboss.org/browse/SWITCHYARD-308 Project: SwitchYard Issue Type: Bug Components: tooling Affects Versions: 0.1 Environment: Using these versions: Seam Forge, version [ 1.0.0.Alpha3 ] java -version java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.7) (rhel-1.39.1.9.7.el6-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) Reporter: Len DiMaggio Seeing this build failure with the [org.switchyard:switchyard-api:0.1.0] versions and Forge. (Not seeing the failures with [org.switchyard:switchyard-api:0.2.0-SNAPSHOT]) Note: The same failure is being seen with "mvn install" or "mvn package" ---------------------------------------------- Getting these results: ./forge ____ _____ / ___| ___ __ _ _ __ ___ | ___|__ _ __ __ _ ___ \___ \ / _ \/ _` | '_ ` _ \ | |_ / _ \| '__/ _` |/ _ \ \\ ___) | __/ (_| | | | | | | | _| (_) | | | (_| | __/ // |____/ \___|\__,_|_| |_| |_| |_| \___/|_| \__, |\___| |___/ [no project] bin $ new-project --named tempProject --topLevelPackage org.switchyard.examples.forge ***ERROR*** [/jboss/local/forge-1.0.0.Alpha3/bin/tempProject] already contains a project; please use a different folder. Where would you like to create the project? [Press ENTER to use the current directory: bin] Wrote /jboss/local/forge-1.0.0.Alpha3/bin/src/main/resources/META-INF/forge.xml ***SUCCESS*** Created project [tempProject] in new working directory [/jboss/local/forge-1.0.0.Alpha3/bin] [tempProject] bin $ project install-facet switchyard Please select a version to install: 1 - [org.switchyard:switchyard-api:0.1.0-M1] 2 - [org.switchyard:switchyard-api:0.1.0-SNAPSHOT] 3 - [org.switchyard:switchyard-api:0.1.0] 4 - [org.switchyard:switchyard-api:0.2.0-SNAPSHOT] Choose an option by typing the number of the selection: 3 Application name (e.g. myApp) tempProject ***SUCCESS*** Installed [switchyard] successfully. [tempProject] bin $ project install-facet switchyard.bean Please select a version to install: 1 - [org.switchyard.components:switchyard-component-bean:0.1.0-M1] 2 - [org.switchyard.components:switchyard-component-bean:0.1.0-SNAPSHOT] 3 - [org.switchyard.components:switchyard-component-bean:0.1.0] 4 - [org.switchyard.components:switchyard-component-bean:0.2.0-SNAPSHOT] 5 - [org.switchyard.components:switchyard-component-bean:1.0-SNAPSHOT] Choose an option by typing the number of the selection: 3 Wrote /jboss/local/forge-1.0.0.Alpha3/bin/src/main/resources/META-INF/beans.xml ***SUCCESS*** Installed [switchyard.bean] successfully. [tempProject] bin $ bean-service create --serviceName HelloService Wrote /jboss/local/forge-1.0.0.Alpha3/bin/src/main/java/org/switchyard/examples/forge/HelloService.java Wrote /jboss/local/forge-1.0.0.Alpha3/bin/src/main/java/org/switchyard/examples/forge/HelloServiceBean.java Created service interface [HelloService] Created service implementation [HelloServiceBean] NOTE: Run 'mvn package' to make HelloService visible to SwitchYard shell. [tempProject] bin $ mvn install [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.switchyard.examples.forge:tempProject:jar:1.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 41, column 15 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building tempProject 1.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.187s [INFO] Finished at: Tue Jun 21 09:08:30 EDT 2011 [INFO] Final Memory: 2M/71M [INFO] ------------------------------------------------------------------------ [ERROR] Plugin org.switchyard:switchyard-plugin:0.1.0 or one of its dependencies could not be resolved: Failure to find org.switchyard:switchyard-plugin:jar:0.1.0 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-307) Ask once for SwitchYard version in forge tooling

by Keith Babo (JIRA)

Ask once for SwitchYard version in forge tooling ------------------------------------------------ Key: SWITCHYARD-307 URL: https://issues.jboss.org/browse/SWITCHYARD-307 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.1 Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.2 We prompt for a version number each time the user installs a SwitchYard facet. This needs to change to just ask for the version of the first facet (top-level switchyard) and use that for all subsequent SwitchYard facets. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-306) XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom

by Magesh Bojan (JIRA)

XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom ---------------------------------------------------------------------------------------------------------------------------- Key: SWITCHYARD-306 URL: https://issues.jboss.org/browse/SWITCHYARD-306 Project: SwitchYard Issue Type: Bug Components: deployment Affects Versions: 0.1 Environment: AS7 Reporter: Magesh Bojan Assignee: Magesh Bojan Deploying an application with Smooks transformer throws error in AS7 15:22:47,203 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstart-transform-smooks-0.2.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstart-transform-smooks-0.2.0-SNAPSHOT.jar".SwitchYardService: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1696) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.6.0_24] at java.lang.Thread.run(Unknown Source) [:1.6.0_24] Caused by: java.lang.ExceptionInInitializerError at org.milyn.cdr.XMLConfigDigester.digestConfigRecursively(XMLConfigDigester.java:202) at org.milyn.cdr.XMLConfigDigester.digestConfig(XMLConfigDigester.java:184) at org.milyn.cdr.SmooksResourceConfigurationStore.registerResources(SmooksResourceConfigurationStore.java:229) at org.milyn.cdr.SmooksResourceConfigurationStore.registerInstalledResources(SmooksResourceConfigurationStore.java:161) at org.milyn.cdr.SmooksResourceConfigurationStore.<init>(SmooksResourceConfigurationStore.java:114) at org.milyn.container.standalone.StandaloneApplicationContext.<init>(StandaloneApplicationContext.java:59) at org.milyn.Smooks.<init>(Smooks.java:117) at org.milyn.Smooks.<init>(Smooks.java:147) at org.switchyard.transform.smooks.internal.SmooksTransformFactory.newTransformer(SmooksTransformFactory.java:72) at org.switchyard.transform.config.model.TransformerFactory.newTransformers(TransformerFactory.java:80) at org.switchyard.transform.TransformerRegistryLoader.registerTransformers(TransformerRegistryLoader.java:84) at org.switchyard.deploy.internal.Deployment.registerTransformers(Deployment.java:195) at org.switchyard.deploy.internal.Deployment.init(Deployment.java:107) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:74) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:68) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) ... 3 more Caused by: java.lang.RuntimeException: XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory implementation found for the object model: http://java.sun.com/jaxp/xpath/dom at javax.xml.xpath.XPathFactory.newInstance(Unknown Source) [:1.6.0_24] at org.milyn.xml.XmlUtil.<clinit>(XmlUtil.java:433) ... 19 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-305) bean component needs to use message.getContent(<type>) when handling invocations

by Keith Babo (JIRA)

bean component needs to use message.getContent(<type>) when handling invocations -------------------------------------------------------------------------------- Key: SWITCHYARD-305 URL: https://issues.jboss.org/browse/SWITCHYARD-305 Project: SwitchYard Issue Type: Bug Components: component-bean Affects Versions: 0.2 Reporter: Keith Babo Fix For: 0.2 Bean component should check the service interface for the message type and use message.getContent(<type>) to kick in any type conversions. See SWITCHYARD-303 for the gory details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-304) Add a camel-jms-binding quickstart

by Daniel Bevenius (JIRA)

Add a camel-jms-binding quickstart ---------------------------------- Key: SWITCHYARD-304 URL: https://issues.jboss.org/browse/SWITCHYARD-304 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Fix For: 0.2 Add a quickstart that creates a deployment that use Camels JMS Component. The idea would very similar to the existing camel-binding quickstart but instead of binding to a directory this service will be bound to a JMS queue. Add an executable class that sends a message to the JMS Queue and describe the steps to run the quickstart in the Readme file. Do we still need to target JBoss AS6 for version 0.2.0 of SwitchYard? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-303) Transformation code should allow for type conversion as a backup if an explicit transformation by type name is not defined

by Len DiMaggio (JIRA)

Transformation code should allow for type conversion as a backup if an explicit transformation by type name is not defined -------------------------------------------------------------------------------------------------------------------------- Key: SWITCHYARD-303 URL: https://issues.jboss.org/browse/SWITCHYARD-303 Project: SwitchYard Issue Type: Bug Components: transformation Affects Versions: 0.1 Reporter: Len DiMaggio Follow on to JIRA switchyard-301: If the work-around to the WSDL issue described in switchyard-301 is used, this error is then seen when the service is invoked: <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>Transformations not applied. Required payload type of 'java:java.lang.String'. Actual payload type is '{http://webservices.samples.jboss.org/}sayHello'. You must define and register a Transformer to transform between these types.</faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Note from Keith: No transformer has been defined, but I think we need to make it easy to accept XML input as a String in your POJO without defining a transformer. Our transformation code needs to be tweaked to allow for type conversion as a backup if an explicit transformation by type name is not defined. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-302) Add configuration support for Camel Mock component

by Mario Antollini (JIRA)

Add configuration support for Camel Mock component -------------------------------------------------- Key: SWITCHYARD-302 URL: https://issues.jboss.org/browse/SWITCHYARD-302 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Mario Antollini Fix For: 0.2 Add configuration support for Camel Mock component http://camel.apache.org/mock.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-301) SOAP gateway is requiring the WSDL message name to match the operation name

by Len DiMaggio (JIRA)

SOAP gateway is requiring the WSDL message name to match the operation name --------------------------------------------------------------------------- Key: SWITCHYARD-301 URL: https://issues.jboss.org/browse/SWITCHYARD-301 Project: SwitchYard Issue Type: Bug Components: core Affects Versions: 0.1 Reporter: Len DiMaggio See the attached .zip example. This exception is raised when the example is deployed to Switchyard on AS7: <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>Invalid input SOAP payload localNamePart for service operation 'sayHello' (service 'HelloService'). Port defines operation localNamePart as 'HelloWorld_sayHello'. Actual localNamePart on input SOAP message 'sayHello'.</faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Note from Keith: The element name should match in doc/lit, but the message name should just be metadata for the WSDL itself. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-300) @Transformer does not separate namespace and localPart

by Martin Vecera (JIRA)

@Transformer does not separate namespace and localPart ------------------------------------------------------ Key: SWITCHYARD-300 URL: https://issues.jboss.org/browse/SWITCHYARD-300 Project: SwitchYard Issue Type: Bug Components: transformation Affects Versions: 0.1 Reporter: Martin Vecera When I use @Transformer(to = "{urn:switchyard-quickstart-demo:orders:1.0}submitOrderResponse") annotation in a custom Java transformer, it is registered under a transform-to QName constructed like new QName("{urn:switchyard-quickstart-demo:orders:1.0}submitOrderResponse"). This does not separate namespace and localPart. Different constructor should be used - new QName("urn:switchyard-quickstart-demo:orders:1.0", "submitOrderResponse"). IMHO it would be great if I could set each part in @Transformer annotation separately like: @Transformer(toNamescape = "urn:switchyard-quickstart-demo:orders:1.0", toLocalPart = "submitOrderResponse", fromNamespace = "", fromLocalPart = "java:java.lang.String") -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues June 2011