July 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2712) Verify quickstarts webservice_wsaddressing -> wiretap

by Kevin Conner (JIRA)

Verify quickstarts webservice_wsaddressing -> wiretap ----------------------------------------------------- Key: JBESB-2712 URL: https://jira.jboss.org/jira/browse/JBESB-2712 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 webservice_wsaddressing webservice_wsproxy_basic webservice_wsproxy_routed webservice_wsproxy_versioning webservice_wssecurity wiretap -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

4
19
0 / 0

[JBoss JIRA] Created: (JBESB-2750) Update mvel to 2.0.12 and place it under jbossesb.sar

by Kevin Conner (JIRA)

Update mvel to 2.0.12 and place it under jbossesb.sar ----------------------------------------------------- Key: JBESB-2750 URL: https://jira.jboss.org/jira/browse/JBESB-2750 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 If Tom is happy with MVEL 2.0.12 for smooks then we need to upgrade to it. The jar should be placed under jbossesb.sar, in the same location as the mvel 1.3.3 jars. Note this does not replace mvel 1.3.3, they co-exist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2747) Document AS5 run.bat error

by Kevin Conner (JIRA)

Document AS5 run.bat error -------------------------- Key: JBESB-2747 URL: https://jira.jboss.org/jira/browse/JBESB-2747 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server, Documentation Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 The AS 5.1.0 GA release contains an error in the run.bat script, the consequence of which is that the JDK tools jar is never applied to the classpath. We need to document this issue as we rely on the compiler for WSDL proxy generation within wise. The specific part in error is the following if exist "%JBOSS_HOME%\bin\run.jar" ( if "x%JAVAC_JAR%" == "x" ( set "RUNJAR=%JAVAC_JAR%;%JBOSS_HOME%\bin\run.jar" ) else ( set "RUNJAR=%JBOSS_HOME%\bin\run.jar" ) ) else ( echo Could not locate "%JBOSS_HOME%\bin\run.jar". echo Please check that you are in the bin directory when running this script. goto END ) The two set commands should be reversed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2749) Use JBossWS jaxws implementation in quickstart classpath

by Kevin Conner (JIRA)

Use JBossWS jaxws implementation in quickstart classpath -------------------------------------------------------- Key: JBESB-2749 URL: https://jira.jboss.org/jira/browse/JBESB-2749 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The as4 version appears to have worked through luck, because of the endorsed lib directory, and the as5 is using the sun rt version. Need to have the JBossWS versions first in the classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2211) Sort out logging for OSGi deployment

by Tom Fennelly (JIRA)

Sort out logging for OSGi deployment ------------------------------------ Key: JBESB-2211 URL: https://jira.jboss.org/jira/browse/JBESB-2211 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Fix For: 5.0 initial development We currently have log4j configs in places where they shouldn't be. There's an OSGi LogService. Not sure how we can log4j into this without polluting code with OSGi code. There should be a way. Maybe there's an OSGi LogService log4j appender , or something like that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2711) Verify quickstarts webservice_consumer_wise2 -> webservice_producer

by Kevin Conner (JIRA)

Verify quickstarts webservice_consumer_wise2 -> webservice_producer ------------------------------------------------------------------- Key: JBESB-2711 URL: https://jira.jboss.org/jira/browse/JBESB-2711 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 webservice_consumer_wise2 webservice_consumer_wise3 webservice_consumer_wise4 webservice_mtom webservice_producer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

4
15
0 / 0

[JBoss JIRA] Created: (JBESB-2672) Create SOAPProxy action

by David Ward (JIRA)

Create SOAPProxy action ----------------------- Key: JBESB-2672 URL: https://jira.jboss.org/jira/browse/JBESB-2672 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Reporter: David Ward Assignee: David Ward Fix For: 4.6 A WS Proxy primarily focuses on the consumption of an external WS endpoint (e.g. hosted on .NET, another external Java-based AS, LAMP) and re-publication of a WS endpoint via the ESB. The ESB sits between the ultimate consumer/client (e.g. .NET WinForm application) and the ultimate producer (e.g. RoR-hosted WS). The purpose of this intermediary is to provide an abstraction layer that solves the following problems: * Provides for more loose coupling between the client & service, they are both completely unaware of each other * The client no longer has a direct connection to the remote service's hostname/IP address * The client will see modified WSDL that changes the inbound/outbound parameters. At a minimum, the WSDL must be tweaked so that the client is pointed to the ESB's exposed endpoint instead of the original, now proxied endpoint. * A transformation of the SOAP envelope/body can be introduced via the ESB action chain both for the inbound request and outbound response * Service versioning is possible since clients can connect to 2 or more proxy endpoints on the ESB, each with its own WSDL and/or XSDs and the ESB will handle the transformation & routing requirements to send the appropriate message to the appropriate endpoint and provide an ultimate response. * Injection of things like WS-Security * Complex context-based routing Current mechanisms of doing this are inappropriate or inadequate: * SOAPClient is used to invoke external web services, not mirror them * SOAPProducer only executes internally-deployed JBoss WS services. * HttpRouter requires too much by-hand configuration * EBWS strips out the SOAP Envelop and only passes along the body With a SOAPProxy action: * it is both a producer and consumer of web services * all that is required is a property pointing to the external wsdl * wsdl can be automatically transformed via the optional wsdlTransform property * multiple transports are automagically detected and handled (only http to be initially implemented, however, but jms in future?) * if using http, any of the HttpRouter properties can also optionally be applied to as overrides -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2707) Verify quickstarts security_jbpm -> spring_helloworld

by Kevin Conner (JIRA)

Verify quickstarts security_jbpm -> spring_helloworld ----------------------------------------------------- Key: JBESB-2707 URL: https://jira.jboss.org/jira/browse/JBESB-2707 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 security_jbpm simple_cbr smooks_file_splitter_router spring_aop spring_helloworld -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2738) Investigate workarounds for wise classloader creation

by Kevin Conner (JIRA)

Investigate workarounds for wise classloader creation ----------------------------------------------------- Key: JBESB-2738 URL: https://jira.jboss.org/jira/browse/JBESB-2738 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.6 Wise does not work on AS5 due to the creation of a classloader, we need to see if there is a quick fix for 4.6. Comment in JBESB-2710 from TomF 'Wise doesn't work on AS5 because it tries to construct its own classloader for wsconsume and it does this based on the assumption that it's running in an AS4 container. ' -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2744) Modify parameter mapping in Wise WSMethod, base it on WS operation meta data

by Kevin Conner (JIRA)

Modify parameter mapping in Wise WSMethod, base it on WS operation meta data ---------------------------------------------------------------------------- Key: JBESB-2744 URL: https://jira.jboss.org/jira/browse/JBESB-2744 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 Currently this may be based on the result of a smooks transformation but the resultant map from that transformation is no longer restricted to the result of the transformation, incorporating the original map values as well as the resultant mappings. The getParmeterInRightPositionArray method needs to be overridden to ignore the parameter map size, using instead the meta data from the WS operation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
1
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 2009