October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1242) Correct ReplyTo/FaultTo processing for ActionProcessingPipeline

by Kevin Conner (JIRA)

Correct ReplyTo/FaultTo processing for ActionProcessingPipeline --------------------------------------------------------------- Key: JBESB-1242 URL: http://jira.jboss.com/jira/browse/JBESB-1242 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Blocker Fix For: 4.2.1 Remove From address processing and create reply based on original settings. -- 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

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1249) Tidy up terminal actions

by Kevin Conner (JIRA)

Tidy up terminal actions ------------------------ Key: JBESB-1249 URL: http://jira.jboss.com/jira/browse/JBESB-1249 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management, Rosetta Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 >From looking through the codebase the following actions should be terminal. product/services/jbossesb/src/main/java/org/jboss/soa/esb/actions/MessagePersister.java product/services/jbossesb/src/main/java/org/jboss/soa/esb/actions/MessageRedeliverer.java product/tools/console/management/src/main/java/org/jboss/soa/esb/monitoring/server/FilerAction.java product/tools/console/management/src/main/java/org/jboss/soa/esb/monitoring/server/DataFilerAction.java product/tools/console/management/src/main/java/org/jboss/soa/esb/monitoring/client/OperationsCollectorAction.java product/tools/console/management/src/main/java/org/jboss/soa/esb/monitoring/client/InvokerAction.java product/tools/console/management/src/main/java/org/jboss/soa/esb/monitoring/client/DataCollectorAction.java -- 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

16 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1248) jBPM CommandInterpreter sends explicit responses

by Kevin Conner (JIRA)

jBPM CommandInterpreter sends explicit responses ------------------------------------------------ Key: JBESB-1248 URL: http://jira.jboss.com/jira/browse/JBESB-1248 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 The jBPM command interpreter sends an explicit response message as well as returning the response message to the action pipeline. The configuration of this message is not valid and the explicit action will cause duplicate responses to be sent. -- 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

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1231) webservice_wssecurity dependencies need checking

by Tom Cunningham (JIRA)

webservice_wssecurity dependencies need checking ------------------------------------------------ Key: JBESB-1231 URL: http://jira.jboss.com/jira/browse/JBESB-1231 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 The README.html for webservice_wssecurity says that it needs a patched jboss-remoting jar and JBoss WS. This QS doesn't specify what version of JBossWS is suggested, so I installed JBossWS 2-1.0.1.GA onto JBoss AS 4.2.1.GA, and applied the jar. One of the dependency checks for this QS is whether ws-intros is installed, but it doesn't seem like JBossWS installs this : <available property="ws-intros" file="${org.jboss.esb.server.deploy.dir}/jbossws.sar/jboss-jaxb-intros.jar"/> drseuss:~/esb/jboss-4.2.1.GA/server/default/deploy tcunning$ ls jbossws.sar/ META-INF jbossws-context.war stax-api.jar jaxb-api.jar jbossws-core.jar wsdl4j.jar jaxb-impl.jar jbossws-jboss42.jar wstx.jar jboss-jaxrpc.jar jbossws-native.jar xmlsec.jar jboss-jaxws.jar jbossws.beans jboss-saaj.jar policy.jar This QS should also have a readme.txt - which is the standard instruction file for QS, and should provide better instructions for installing jbossws - it says to follow directions in install/readme.txt which doesn't exist in the QS or in JBossWS. -- 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

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1207) Update juddi

by Kevin Conner (JIRA)

Update juddi ------------ Key: JBESB-1207 URL: http://jira.jboss.com/jira/browse/JBESB-1207 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Tom Cunningham Fix For: 4.2.1 We are closing issues against jUDDI fixes but do not have an update jUDDI. We need to update the jUUDI jars and verify that our issues have been fixed. -- 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

16 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1161) Introduce a new EPR type to represent a service category/name.

by Kevin Conner (JIRA)

Introduce a new EPR type to represent a service category/name. -------------------------------------------------------------- Key: JBESB-1161 URL: http://jira.jboss.com/jira/browse/JBESB-1161 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR1 Reporter: Kevin Conner Assigned To: Tom Fennelly Fix For: 4.2.1 IR2 One of the biggest issues when sending a message is that the originator would like to specify a service using the service category/name instead of a hardcoded EPR. We need to have an EPR which consists of the service category/name and resolves to the physical transport EPR when it is (eventually) used to send a message. -- 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

16 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1183) MessageCounter.update() algo for calculating message size needs to be enhanced

by Tom Fennelly (JIRA)

MessageCounter.update() algo for calculating message size needs to be enhanced ------------------------------------------------------------------------------ Key: JBESB-1183 URL: http://jira.jboss.com/jira/browse/JBESB-1183 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management, Rosetta Affects Versions: 4.2.1 IR1 Reporter: Tom Fennelly Assigned To: Tom Cunningham Fix For: 4.2.1 It used to only take into account byte arrays in the BytesBody.BYTES_LOCATION. Does it need to iterate over all body locations + take into account other payload types i.e. non byte[] -- 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

16 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1104) Make esb dependencies implicit

by Kevin Conner (JIRA)

Make esb dependencies implicit ------------------------------ Key: JBESB-1104 URL: http://jira.jboss.com/jira/browse/JBESB-1104 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 The jbossesb.esb dependency is now implicit. Similar dependencies can be created by checking the actions in use. -- 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

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1127) UUID service startup fails when using Oracle database

by Jiri Pechanec (JIRA)

UUID service startup fails when using Oracle database ----------------------------------------------------- Key: JBESB-1127 URL: http://jira.jboss.com/jira/browse/JBESB-1127 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Documentation Affects Versions: 4.2.1 IR1 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor If the UUID service should create the table for UUID generators and in another schema in the same database the table exists then it is false identified as already existing in current user scheme. The workaround is to use table name in jboss-service.xml file fully qualified inluding schema name. This fact should be stated in the comment of the file or in the documentation. -- 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

16 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1126) MessageStore usage has serious impact on message size

by Jiri Pechanec (JIRA)

MessageStore usage has serious impact on message size ----------------------------------------------------- Key: JBESB-1126 URL: http://jira.jboss.com/jira/browse/JBESB-1126 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Message Store Affects Versions: 4.2.1 IR1 Reporter: Jiri Pechanec Assigned To: Mark Little If the MessageStore is used then the size of message is depending on underlyingi database used ad is significantly smaller then can be use in JMS. This deficiency either needs to be eliminated by using BLOB columns for storing contents or this fact needs to be clearly stated in the documentation. -- 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

16 years, 8 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2007