July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-687) Rename webservice_jbossws_adapter_01

by Burr Sutter (JIRA)

Rename webservice_jbossws_adapter_01 ------------------------------------ Key: JBESB-687 URL: http://jira.jboss.com/jira/browse/JBESB-687 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Burr Sutter Assigned To: Mark Little Rename webservice_jbossws_adapter_01 to be "webservice_producer" as it no longer contains the "JBossWS Adapter" specifically. It is now a generic example of how the ESB 4.2 architecture handles publishing a WS through the bus. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-588) Migrate JBossWSAdapter to use JBossWS 2.1 codebase.

by Tom Fennelly (JIRA)

Migrate JBossWSAdapter to use JBossWS 2.1 codebase. --------------------------------------------------- Key: JBESB-588 URL: http://jira.jboss.com/jira/browse/JBESB-588 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 We were dependent on a non-public API. The JBossWS team have added a public API to the 2.1 codebase in support of the functionality we require. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-682) [FilterManager] GatewayFilter error

by Kurt Stam (JIRA)

[FilterManager] GatewayFilter error ------------------------------------ Key: JBESB-682 URL: http://jira.jboss.com/jira/browse/JBESB-682 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2 Milestone Release 3 I see this error all the time running the esb. 11:23:15,250 WARN [FilterManager] GatewayFilter encountered problem during JMS config check. org.jboss.soa.esb.ConfigurationException: Missing or invalid <destination-name> attribute at org.jboss.soa.esb.listeners.ListenerUtil.obtainAtt(ListenerUtil.java:342) at org.jboss.internal.soa.esb.message.filter.GatewayFilter.onOutput(GatewayFilter.java:91) at org.jboss.soa.esb.filter.FilterManager.doOutputWork(FilterManager.java:81) at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.doRun(AbstractFileGateway.java:170) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-664) 2 Versions of jBPM Action Handler: ESBAction2 and ESBActionHandler

by Burr Sutter (JIRA)

2 Versions of jBPM Action Handler: ESBAction2 and ESBActionHandler ------------------------------------------------------------------ Key: JBESB-664 URL: http://jira.jboss.com/jira/browse/JBESB-664 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Milestone Release 3 We have 2 versions of the jBPM to ESB action handler. The older one looks like: <action name="action2" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler"> <esbCategoryName>BPM_Orchestration_Service1</esbCategoryName> <esbServiceName>Service1</esbServiceName> <millisToWaitForResponse>5000</millisToWaitForResponse> <jbpmToEsb_variables>theBody</jbpmToEsb_variables> <jbpmToEsb_esbNames>BODY_CONTENT</jbpmToEsb_esbNames> <return_variables>theBody</return_variables> <return_esbNames>BODY_CONTENT</return_esbNames> </action> The new one looks like: <action name="action2" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbAction2"> <esbCategoryName>BPM_Orchestration_Service1</esbCategoryName> <esbServiceName>Service1</esbServiceName> <millisToWaitForResponse>5000</millisToWaitForResponse> <jbpmToEsbVars> <mapping jbpm-name="theBody" esb-name="BODY_CONTENT" /> </jbpmToEsbVars> <returnVars> <mapping jbpm-name="theBody" esb-name="BODY_CONTENT" /> </returnVars> </action> Both examples are shown in quickstart bpm_orchestration1 We need to remove EsbActionHandler and rename EsbAction2 to EsbActionHandler, then correct the various BPM-based quickstarts so they use the correct version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-575) Standardize on a message delivery mechanism...

by Tom Fennelly (JIRA)

Standardize on a message delivery mechanism... ---------------------------------------------- Key: JBESB-575 URL: http://jira.jboss.com/jira/browse/JBESB-575 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 A few "(anti-)patterns" have developed re ESB-Aware message delivery to an endpoint: 1. Raw code that deals right down to the level of EPRs and Couiers (Yeuukieee...). The code is littered with this stuff :-( 2. Classes like the ServiceInvoker (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...) and MessageDeliveryAdapter (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...). Both of these classes essentially do the same thing. They're created against a Service Cat:Name combo and they take care of looking up EPRs and Couriers etc. Basically, I think we should settle on using one of classes listed in #2, and (where the opportunity arises) remove that ugly code described in #1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-671) Fix broken scoping tests

by Kevin Conner (JIRA)

Fix broken scoping tests ------------------------ Key: JBESB-671 URL: http://jira.jboss.com/jira/browse/JBESB-671 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 3 There are some standalone tests in the qa/junit directory which test esb scoping. These tests are currently broken and, from the svn logs, could not possibly have worked since at least March. The specific tests (from issue 670) are > ant one-test -Dtest=server (for the SimpleUnitTestCase) > > (and -Dtest=server/jca, and -Dtest=server/ftp for jca and ftp). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-670) Scoped class loader seems broken

by Kurt Stam (JIRA)

Scoped class loader seems broken -------------------------------- Key: JBESB-670 URL: http://jira.jboss.com/jira/browse/JBESB-670 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Kurt Stam Assigned To: Mark Little Priority: Critical Fix For: 4.2 Probably because somebody broke the scoped classloader integration I did :) Kurt T Stam wrote: > Basically I want to you use the JBossTest harnass to run the QSs (or > what will be the QA test). TomC and I started that but I have the > following issues > > 1. I can run the qa server tests from the qa/junit directory doing > > ant one-test -Dtest=server (for the SimpleUnitTestCase) > > (and -Dtest=server/jca, and -Dtest=server/ftp for jca and ftp). > > Now, the SimpleUnitTestCase has a "testScope()" which should evaluate to > "scope2", but > it evaluates to "scope1" for me. > > Am I the only one? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-672) WS-Discovery and WS-MetaData Exchange approaches in the architecture

by Mark Little (JIRA)

WS-Discovery and WS-MetaData Exchange approaches in the architecture -------------------------------------------------------------------- Key: JBESB-672 URL: http://jira.jboss.com/jira/browse/JBESB-672 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-427) Roll-your-own Gateway example and docs

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-427?page=all ] Mark Little updated JBESB-427: ------------------------------ Fix Version/s: (was: 4.2) > Roll-your-own Gateway example and docs > -------------------------------------- > > Key: JBESB-427 > URL: http://jira.jboss.com/jira/browse/JBESB-427 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Documentation > Reporter: Mark Little > Assigned To: Esteban Schifman > > Provide enough infrastructure and documentation so the end-user of our ESB can relatively easily add their own gateway/listener (BC) to a proprietary protocol that they wish to enable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-661) The jBPM service does not work in "bootstrapper" mode

by Burr Sutter (JIRA)

The jBPM service does not work in "bootstrapper" mode ----------------------------------------------------- Key: JBESB-661 URL: http://jira.jboss.com/jira/browse/JBESB-661 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Priority: Minor Fix For: 5.0 Review quickstart: bpm_orchestration2. Comment out the run and runtest targets in the build.xml so that those are inherited from the base-build.xml Then following the instructions in the readme.txt for standalone bootstrapper. You will see the error during the "runtest" operation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007