October 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-491) Add failOnWarning functionality to XsltTransformer

by Tomohisa igarashi (Created) (JIRA)

Add failOnWarning functionality to XsltTransformer -------------------------------------------------- Key: SWITCHYARD-491 URL: https://issues.jboss.org/browse/SWITCHYARD-491 Project: SwitchYard Issue Type: Sub-task Reporter: Tomohisa igarashi We need to check the warning using javax.xml.transform.ErrorListener in XsltTransformer and it should be failed if there's warning and failOnWarning=true like JBossESB/XsltAction. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-490) Remove Smooks maven staging repository from parent pom

by Tom Fennelly (Created) (JIRA)

Remove Smooks maven staging repository from parent pom ------------------------------------------------------ Key: SWITCHYARD-490 URL: https://issues.jboss.org/browse/SWITCHYARD-490 Project: SwitchYard Issue Type: Task Components: build Reporter: Tom Fennelly Fix For: 0.3 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-489) Clean up eclipse dependencies in tools project

by Rob Cernich (Created) (JIRA)

Clean up eclipse dependencies in tools project ---------------------------------------------- Key: SWITCHYARD-489 URL: https://issues.jboss.org/browse/SWITCHYARD-489 Project: SwitchYard Issue Type: Bug Components: tooling Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.3 Try to ensure that SY tools can be installed on top of JBDS (i.e. eclipse 3.6), where possible. Create a unique id for the current SY feature (currently, the id's of the feature and the branding plugin are the same). Update project hierarchy to use JBoss tools parent pom, which uses JBoss p2 repositories for build. (This may also address SWITCHYARD-466.) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-488) Upgrade to Forge Beta 3

by Keith Babo (Created) (JIRA)

Upgrade to Forge Beta 3 ----------------------- Key: SWITCHYARD-488 URL: https://issues.jboss.org/browse/SWITCHYARD-488 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.2 Reporter: Keith Babo Fix For: 0.3 We need to upgrade our tooling to Forge Beta 3. Talking to Lincoln, there are going to be some changes in terms of how we package our plugins and possibly API changes as well. There are two parts to this JIRA: 1) Our plugins need to work with Beta 3, so any changes it takes to make things work the same. This includes the ability to install plugins from our distribution into an existing Forge install. 2) Add support for the ability to install plugins from a Git repository and add our plugins to the Forge CPI. Here's some background info on #2. https://docs.jboss.org/author/display/SEAMFORGE/Make+your+Plugin+availabl... https://docs.jboss.org/author/display/SEAMFORGE/Add+your+Plugin+to+the+Ce... Please note that I want to continue to support the existing process (copy Forge plugins to $FORGE_HOME/lib) as closely as possible. I don't want users that have already downloaded our distribution to have to then install all of the plugins from a remote Git repo as well (this involves more downloading and building). -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-487) Re-add quickstarts to AS7 release distro

by Tom Fennelly (Created) (JIRA)

Re-add quickstarts to AS7 release distro ---------------------------------------- Key: SWITCHYARD-487 URL: https://issues.jboss.org/browse/SWITCHYARD-487 Project: SwitchYard Issue Type: Task Components: build Reporter: Tom Fennelly Fix For: 0.3 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-486) Application projects should build without warning

by Keith Babo (Created) (JIRA)

Application projects should build without warning ------------------------------------------------- Key: SWITCHYARD-486 URL: https://issues.jboss.org/browse/SWITCHYARD-486 Project: SwitchYard Issue Type: Sub-task Components: build, tooling Reporter: Keith Babo When building a SwitchYard application project, the user sees several WARNING messages in the test output. We need to investigate these and address them. I suggest walking through the quickstarts and building them one at a time while viewing the build output. For each ERROR/WARNING in the output, do the following: o If it's an issue with the application, fix it. o If it's an issue with SwitchYard core or a component, file an issue. o If it's spurious log output, filter it with log4j. This applies to the quickstart and possibly to the forge/eclipse tooling when creating a new project. Here are some examples from the bean-service quickstart: Why are we looking up commons-cli? Where is this dependency creeping in? Possibly forge-related. {noformat} [WARNING] Could not transfer metadata org.apache.commons:commons-cli:2.0-SNAPSHOT/maven-metadata.xml from/to apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/): No connector available to access repository apache.m1 (http://people.apache.org/repo/m1-snapshot-repository/) of type legacy using the available factories WagonRepositoryConnectorFactory {noformat} This could be chunked encoding returned to the SOAP component. We see this issue in JBESB as well. For now, we can simply file a JIRA against SOAP component and investigate it separately. {noformat} 10:43:25,500 WARN [httpclient.HttpMethodBase] Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {noformat} This needs to be address with a log4j filter. Note that the log4j filter should *only* go in the src/test/resources directory so that it's not packaged with the application. {noformat} 404 [main] WARN org.jboss.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled 404 [main] WARN org.jboss.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled {noformat} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-485) Remove geronimo jars from distros

by Keith Babo (Created) (JIRA)

Remove geronimo jars from distros --------------------------------- Key: SWITCHYARD-485 URL: https://issues.jboss.org/browse/SWITCHYARD-485 Project: SwitchYard Issue Type: Task Components: distribution Affects Versions: 0.2 Reporter: Keith Babo Fix For: 0.3 These are used by tests in the BPEL component. No need to include them in the release distro. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-484) Add BPEL component quickstart

by Gary Brown (Created) (JIRA)

Add BPEL component quickstart ----------------------------- Key: SWITCHYARD-484 URL: https://issues.jboss.org/browse/SWITCHYARD-484 Project: SwitchYard Issue Type: Task Reporter: Gary Brown Add a BPEL quickstart and hook into AS7 test suite. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-483) Create Switchyard NameSpaceHandler

by Alejandro Montenegro (JIRA)

Create Switchyard NameSpaceHandler ---------------------------------- Key: SWITCHYARD-483 URL: https://issues.jboss.org/browse/SWITCHYARD-483 Project: SwitchYard Issue Type: Feature Request Components: component-spring Reporter: Alejandro Montenegro -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues October 2011