January 2012 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-615) Fix namespace of sub-elements in bpel-service/loan_

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-615: ------------------------------------- Summary: Fix namespace of sub-elements in bpel-service/loan_ Key: SWITCHYARD-615 URL: https://issues.jboss.org/browse/SWITCHYARD-615 Project: SwitchYard Issue Type: Bug Reporter: Gary Brown -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-614) JMS Headers not available on Camel Route

by Christos Vasilakis (JIRA)

Christos Vasilakis created SWITCHYARD-614: --------------------------------------------- Summary: JMS Headers not available on Camel Route Key: SWITCHYARD-614 URL: https://issues.jboss.org/browse/SWITCHYARD-614 Project: SwitchYard Issue Type: Bug Components: component-camel Affects Versions: 0.3 Environment: MacOSX 10.7.2, java version "1.6.0_29" jboss-as-7.1.0.CR1b Reporter: Christos Vasilakis When trying to access the JMS headers from a Camel Route, the list returned contains only one property[breadcrumbId]. All other properties are discarded. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-613) Refactor poms to use jboss-parent/jboss-as-parent

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-613: ------------------------------------- Summary: Refactor poms to use jboss-parent/jboss-as-parent Key: SWITCHYARD-613 URL: https://issues.jboss.org/browse/SWITCHYARD-613 Project: SwitchYard Issue Type: Task Reporter: Nick Cross Fix For: 0.4 Refactor poms (primarily parent) to use jboss-as-parent and jboss-parent to simplify dependencies and product integration. This would utilise the versions used by AS so reducing conflicts and simplifying the parent pom. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-612) SwitchYard deployment fails when using EAR

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-612: ------------------------------------- Summary: SwitchYard deployment fails when using EAR Key: SWITCHYARD-612 URL: https://issues.jboss.org/browse/SWITCHYARD-612 Project: SwitchYard Issue Type: Bug Components: deployment Affects Versions: 0.3 Reporter: Keith Babo EAR deployment leads to NPE when our deployer looks for META-INF/switchyard.xml. https://community.jboss.org/thread/177232 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-611) BPEL Quickstart & SoapUI tool

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-611: ------------------------------------- Summary: BPEL Quickstart & SoapUI tool Key: SWITCHYARD-611 URL: https://issues.jboss.org/browse/SWITCHYARD-611 Project: SwitchYard Issue Type: Bug Environment: Fedora 16 Reporter: Nick Cross Fix For: 0.4 Working through the bpel-service quickstart (https://github.com/jboss-switchyard/quickstarts/tree/master/bpel-service) I import the wsdl from src/main/resources/wsdl to create the soap-ui project. Using the sample request in src/test/resources/xml/soap-request.xml works fine but using the XML generated by SoapUI does not. The difference is: SoapUI 4.0.1 generates <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:loan="http://example.com/loan-approval/loanService/"> <soapenv:Header/> <soapenv:Body> <loan:request> <loan:firstName>?</loan:firstName> <loan:name>?</loan:name> <loan:amount>?</loan:amount> </loan:request> </soapenv:Body> </soapenv:Envelope> Compared to src/test/resources/xml/soap-loanreq1.xml <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header/> <soapenv:Body> <ns1:request xmlns:ns1="http://example.com/loan-approval/loanService/"> <firstName>Fred</firstName> <name>Bloggs</name> <amount>100</amount> </ns1:request> </soapenv:Body> </soapenv:Envelope> Email conversation with Keith and Gary Brown - Keith said: " OK, I played with this a bit more. We are not dropping the namespace definition in the SOAP Gateway. Playing with things a bit, it appears that the BPEL process is expecting the loan request elements to have an empty namespace. Generating the request from SoapUI correctly prefixes the element names with the namespace qualifier. You can see in the request message in src/test/resources that the element names beneath <loan:request> are not namespace qualified and there is no default namespace defined. @Gary - if this is a quick fix in the BPEL logic, we might want to patch it up. If not, I can just update the quickstart instructions to tell users to copy in the test message into SoapUI. " -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-610) Clean-up for transaction policy quickstart in AS 7.1

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-610: ------------------------------------- Summary: Clean-up for transaction policy quickstart in AS 7.1 Key: SWITCHYARD-610 URL: https://issues.jboss.org/browse/SWITCHYARD-610 Project: SwitchYard Issue Type: Bug Components: quickstarts Affects Versions: 0.4 Reporter: Keith Babo Fix For: 0.4 A couple of things are off with this quickstart now that we've moved to AS 7.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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-609) Findbugs Version

by Nick Cross (Created) (JIRA)

Findbugs Version ---------------- Key: SWITCHYARD-609 URL: https://issues.jboss.org/browse/SWITCHYARD-609 Project: SwitchYard Issue Type: Task Reporter: Nick Cross Fix For: 0.4 Findbugs version in parent pom is <groupId>org.codehaus.mojo</groupId> <artifactId>findbugs-maven-plugin</artifactId> <version>2.3.2-SNAPSHOT</version> Would be useful if that was 2.3.2 as that exists in brew. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-608) missing jaxp when running switchyard installer with stock ant 1.8.2 in Fedora 16

by Jeffrey Bride (Created) (JIRA)

missing jaxp when running switchyard installer with stock ant 1.8.2 in Fedora 16 -------------------------------------------------------------------------------- Key: SWITCHYARD-608 URL: https://issues.jboss.org/browse/SWITCHYARD-608 Project: SwitchYard Issue Type: Bug Components: deployment Affects Versions: 0.3 Environment: ant.noarch (version 1.8.2-6-c16) from yum repository of Fedora 16 java-1.6.0-openjdk-1.6.0.0-61.1.10.4.fc16.x86_64 from yum repository of Fedora 16 switchyard-installer-0.3 Reporter: Jeffrey Bride Priority: Minor Hi, I'm running the switchyard-installer for forge and ran into a problem in Fedora 16 using the stock ant 1.8.2 from the yum repository. Looks like a jaxp parser is not included in the ant classpath. subsequently, when executing 'ant install' from the switchyard-installer, the following exception is thrown : [java] Caused by: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found [java] at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:127) [java] at org.jboss.forge.parser.xml.XMLParser.parse(XMLParser.java:104) [java] at org.jboss.forge.shell.InstalledPluginRegistry.installPlugin(InstalledPluginRegistry.java:85) [java] at org.switchyard.forge.installer.Installer.install(Installer.java:39) [java] at org.switchyard.forge.installer.Installer.main(Installer.java:47) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [java] at java.lang.reflect.Method.invoke(Method.java:616) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152) [java] ... 33 more [java] Caused by: java.lang.ClassNotFoundException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl [java] at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1361) [java] at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1311) [java] at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1070) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:266) couple of short-term resolutions as follows : 1) download apache ant 1.8.2 from the apache.org and use that distribution rather than the one provided in the yum repositories -- appears that when running with downloaded ant 1.8.2 .... the following jaxp implementation is used from $JAVA_HOME/jre/lib/rt.jar : com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl or 2) hack the switchyard-installer-0.3/build.xml to include the following in the 'forge.installer.classpath' : <fileset dir="/usr/share/java"> <include name="jaxp_parser_impl.jar"/> </fileset> -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-607) Interaction with SwitchYard console generates log errors in AS7

by Murray Todd Williams (Created) (JIRA)

Interaction with SwitchYard console generates log errors in AS7 --------------------------------------------------------------- Key: SWITCHYARD-607 URL: https://issues.jboss.org/browse/SWITCHYARD-607 Project: SwitchYard Issue Type: Bug Components: console Affects Versions: 0.3 Environment: AS7 Reporter: Murray Todd Williams Priority: Minor SwithYard Console generates the following error when it first loads, and whenever any GWT component makes a call to the server: ERROR [org.jboss.remoting.remote] (XNIO NIO Read ##) JBREM00200: Remote connection failed: java.io.IOException: Window open for non-existent channel -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-606) SwitchYard Console CSS formatting fixes

by Murray Todd Williams (Created) (JIRA)

SwitchYard Console CSS formatting fixes --------------------------------------- Key: SWITCHYARD-606 URL: https://issues.jboss.org/browse/SWITCHYARD-606 Project: SwitchYard Issue Type: Bug Components: console Affects Versions: 0.3 Reporter: Murray Todd Williams Priority: Trivial The SwitchYard console's primary "body" container's width expands indefinitely to fit the browser. For browsers with a width exceeding 920 pixels (the width of the SwitchYard banner image in the header), this looks bad. The AS7 console assignes a DOM id of "container" to its primary GWT container, and sets a CSS max-width to that element. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues January 2012