July 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3936) Regression: SOAPProxy no longer handles WSDL imports correctly

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBESB-3936?page=com.atlassian.jira.plugin... ] Tadayoshi Sato commented on JBESB-3936: --------------------------------------- Awesome! Thanks, Magesh. > Regression: SOAPProxy no longer handles WSDL imports correctly > -------------------------------------------------------------- > > Key: JBESB-3936 > URL: https://issues.jboss.org/browse/JBESB-3936 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.12 > Environment: JBoss Enterprise SOA Platform 5 > Reporter: Tadayoshi Sato > Assignee: Magesh Bojan > Labels: regression > Fix For: 4.13 > > > SOAPProxy on SOA-P 5.0.2 (JBoss ESB 4.7 CP2) allowed the customer to use WSDL that contained imports. > This is failing under SOA-P 5.3.1 (JBoss ESB 4.11 CP1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3936) Regression: SOAPProxy no longer handles WSDL imports correctly

by Magesh Bojan (JIRA)

[ https://issues.jboss.org/browse/JBESB-3936?page=com.atlassian.jira.plugin... ] Magesh Bojan updated JBESB-3936: -------------------------------- Fix Version/s: 4.13 > Regression: SOAPProxy no longer handles WSDL imports correctly > -------------------------------------------------------------- > > Key: JBESB-3936 > URL: https://issues.jboss.org/browse/JBESB-3936 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.12 > Environment: JBoss Enterprise SOA Platform 5 > Reporter: Tadayoshi Sato > Assignee: Magesh Bojan > Labels: regression > Fix For: 4.13 > > > SOAPProxy on SOA-P 5.0.2 (JBoss ESB 4.7 CP2) allowed the customer to use WSDL that contained imports. > This is failing under SOA-P 5.3.1 (JBoss ESB 4.11 CP1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3936) Regression: SOAPProxy no longer handles WSDL imports correctly

by Magesh Bojan (JIRA)

[ https://issues.jboss.org/browse/JBESB-3936?page=com.atlassian.jira.plugin... ] Magesh Bojan resolved JBESB-3936. --------------------------------- Assignee: Magesh Bojan Resolution: Done At revision: 38383 > Regression: SOAPProxy no longer handles WSDL imports correctly > -------------------------------------------------------------- > > Key: JBESB-3936 > URL: https://issues.jboss.org/browse/JBESB-3936 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.12 > Environment: JBoss Enterprise SOA Platform 5 > Reporter: Tadayoshi Sato > Assignee: Magesh Bojan > Labels: regression > > SOAPProxy on SOA-P 5.0.2 (JBoss ESB 4.7 CP2) allowed the customer to use WSDL that contained imports. > This is failing under SOA-P 5.3.1 (JBoss ESB 4.11 CP1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3750) Add support for Dependency Injection (Spring Autowiring) to JBoss ESB actions.

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3750?page=com.atlassian.jira.plugin... ] Tom Cunningham commented on JBESB-3750: --------------------------------------- Added the AbstractAutowiredSpringAction to trunk. Duncan said he would be work on contributing a quickstart to demonstrate its use. > Add support for Dependency Injection (Spring Autowiring) to JBoss ESB actions. > ------------------------------------------------------------------------------ > > Key: JBESB-3750 > URL: https://issues.jboss.org/browse/JBESB-3750 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.10 > Environment: JBoss ESB 4.10 > Reporter: Duncan Doyle > Labels: autowire, dependency, injection, spring > > JBoss ESB currently provides basic support for Spring integration via the AbstractSpringAction. This action however has a number of disadvantages. > - Every action loads its own application context. > - Extending from this action ties your code to the JBoss ESB framework (which we try to avoid using JBoss ESB annotations). > - You still need to retrieve the dependency via a 'getBeanFactory().getBean()' call which ties your application code to the Spring Framework. > I've created an initial implementation to support Spring @Autowired annotations in JBoss ESB actions. See my blogpost: http://duncandoyle.blogspot.com/2012/02/autowiring-your-jboss-esb-actions... and my GitHub repo: https://github.com/DuncanDoyle/JBossEsbSpringIntegration > It would be nice to integrate this functionality (AbstractAutowiredSpringAction) in JBoss ESB/SOA-P. > Cheers, > Duncan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3937) ESB is reading all XSDs for every web service on single .esb

by Carlos Oliveira (JIRA)

[ https://issues.jboss.org/browse/JBESB-3937?page=com.atlassian.jira.plugin... ] Carlos Oliveira updated JBESB-3937: ----------------------------------- Description: Hi, On the following class org.jboss.soa.esb.listeners.deployers.mc.as6.WebGatewayBuilder at method createWebserviceWars theres a creation of a map with all the schemas inside the .esb deployed. final Map<String, String> schemasMap = JBossDeployerUtil.getSchemas(esbArchive); (line 151) The problem is the fact that this map is inside the for-loop. I guess this map should be created outside the loop. I have a .esb with 78 web services and 352 .xsds. For every web service all the schemas are read over and over again. I changed this code, recompiled and deployed. Now my startup went down from 3 minutes to 1,5 minutes. Regards, Carlos was: Hi, On the following class org.jboss.soa.esb.listeners.deployers.mc.as6.WebGatewayBuilder at method createWebserviceWars theres a creation of a map with all the schemas inside the .esb deployed. The problem is the fact that this map is inside the for-loop. I guess it should be outside the loop. I have a .esb with 78 web services and 352 .xsds. For every web service all the schemas are read over and over again. I changed this code, recompiled and deployed. Now my startup went down from 3 minutes to 1,5 minutes. Regards, Carlos > ESB is reading all XSDs for every web service on single .esb > ------------------------------------------------------------ > > Key: JBESB-3937 > URL: https://issues.jboss.org/browse/JBESB-3937 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11, 4.12 > Environment: Windows 7 x64 > Reporter: Carlos Oliveira > Priority: Minor > > Hi, > On the following class org.jboss.soa.esb.listeners.deployers.mc.as6.WebGatewayBuilder at method createWebserviceWars theres a creation of a map with all the schemas inside the .esb deployed. > final Map<String, String> schemasMap = JBossDeployerUtil.getSchemas(esbArchive); (line 151) > The problem is the fact that this map is inside the for-loop. I guess this map should be created outside the loop. > I have a .esb with 78 web services and 352 .xsds. For every web service all the schemas are read over and over again. I changed this code, recompiled and deployed. Now my startup went down from 3 minutes to 1,5 minutes. > Regards, > Carlos -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3937) ESB is reading all XSDs for every web service on single .esb

by Carlos Oliveira (JIRA)

Carlos Oliveira created JBESB-3937: -------------------------------------- Summary: ESB is reading all XSDs for every web service on single .esb Key: JBESB-3937 URL: https://issues.jboss.org/browse/JBESB-3937 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.12, 4.11 Environment: Windows 7 x64 Reporter: Carlos Oliveira Priority: Minor Hi, On the following class org.jboss.soa.esb.listeners.deployers.mc.as6.WebGatewayBuilder at method createWebserviceWars theres a creation of a map with all the schemas inside the .esb deployed. The problem is the fact that this map is inside the for-loop. I guess it should be outside the loop. I have a .esb with 78 web services and 352 .xsds. For every web service all the schemas are read over and over again. I changed this code, recompiled and deployed. Now my startup went down from 3 minutes to 1,5 minutes. Regards, Carlos -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3936) Regression: SOAPProxy no longer handles WSDL imports correctly

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBESB-3936?page=com.atlassian.jira.plugin... ] Tadayoshi Sato updated JBESB-3936: ---------------------------------- > Regression: SOAPProxy no longer handles WSDL imports correctly > -------------------------------------------------------------- > > Key: JBESB-3936 > URL: https://issues.jboss.org/browse/JBESB-3936 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.12 > Environment: JBoss Enterprise SOA Platform 5 > Reporter: Tadayoshi Sato > Labels: regression > > SOAPProxy on SOA-P 5.0.2 (JBoss ESB 4.7 CP2) allowed the customer to use WSDL that contained imports. > This is failing under SOA-P 5.3.1 (JBoss ESB 4.11 CP1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3936) Regression: SOAPProxy no longer handles WSDL imports correctly

by Tadayoshi Sato (JIRA)

Tadayoshi Sato created JBESB-3936: ------------------------------------- Summary: Regression: SOAPProxy no longer handles WSDL imports correctly Key: JBESB-3936 URL: https://issues.jboss.org/browse/JBESB-3936 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.12 Environment: JBoss Enterprise SOA Platform 5 Reporter: Tadayoshi Sato SOAPProxy on SOA-P 5.0.2 (JBoss ESB 4.7 CP2) allowed the customer to use WSDL that contained imports. This is failing under SOA-P 5.3.1 (JBoss ESB 4.11 CP1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3935) Upgrade jruby to 1.7.4

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3935?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3935: ---------------------------------- Fix Version/s: 4.13 (was: 4.11 CP2) > Upgrade jruby to 1.7.4 > ---------------------- > > Key: JBESB-3935 > URL: https://issues.jboss.org/browse/JBESB-3935 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.13 > > > Upgrade the jruby JAR found in scripting_chain to 1.7.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3934) Upgrade jruby to 1.7.4

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3934?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3934. --------------------------------- > Upgrade jruby to 1.7.4 > ---------------------- > > Key: JBESB-3934 > URL: https://issues.jboss.org/browse/JBESB-3934 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > Upgrade the jruby JAR found in scripting_chain to 1.7.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2013