December 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2216) sql-message-filter optional attribute "insert-timestamp-column" actually not optional

by Kevin Conner (JIRA)

sql-message-filter optional attribute "insert-timestamp-column" actually not optional ------------------------------------------------------------------------------------- Key: JBESB-2216 URL: https://jira.jboss.org/jira/browse/JBESB-2216 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP4 Reporter: Lukas Petrovicky Priority: Blocker Fix For: 4.2.1 CP5 XSD for jboss-esb.xml clearly states that the parameter "insert-timestamp-column" for sql-message-filter is optional. However, when you don't supply it, following queries are executed, which causes the whole SQL provider not to work correctly (notice the missing column name): update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET 2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234 This is what I have in the jboss-esb.xml: <sql-message-filter tablename="NOTIFICATIONS_TABLE" status-column="STATUS_COL" message-id-column="UNIQUE_ID" message-column="MESSAGECONTENTS" /> This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a regression as it worked fine on SOA-P 4.2.0 CP02. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2252) JBossRemotingMessageComposer should have the security extractors as fields and not create them everytime.

by Daniel Bevenius (JIRA)

JBossRemotingMessageComposer should have the security extractors as fields and not create them everytime. --------------------------------------------------------------------------------------------------------- Key: JBESB-2252 URL: https://jira.jboss.org/jira/browse/JBESB-2252 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP1 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 This task mainly concerns the WSSecurityInfoExtractor which uses Smooks and the current impl will in effect create a new Smooks instance upon every call. Making this a field will have it create only once. I'd did this so I bow my head in shame :( I discovered this issue when investigating this user forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198266#4198266 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2246) Document required client libs and properties files.

by Daniel Bevenius (JIRA)

Document required client libs and properties files. --------------------------------------------------- Key: JBESB-2246 URL: https://jira.jboss.org/jira/browse/JBESB-2246 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Documentation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 Document the required libraries and properties files that a clients that uses the ServiceInvoker from a remote JVM needs. The following jars are required: jbossesb-config-model-1.0.1.jar jbossesb-rosetta.jar jbossts-common.jar log4j-1.2.14.jar stax-1.2.0.jar stax-api-1.0.1.jar jbossall-client.jar scout-1.0rc2.aop.jar xbean-2.2.0.jar commons-logging-1.1.jar jboss-aop-jdk50-1.5.6.GA.jar javassist-3.6.0.GA.jar trove.jar juddi-client-2.0rc5.jar jboss-messaging-client.jar jboss-remoting.jar commons-codec-1.3.jar wstx-asl-3.2.0.jar xercesImpl-2.8.0.jar -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2250) Update ProgrammersGuide.pdf

by Daniel Bevenius (JIRA)

Update ProgrammersGuide.pdf --------------------------- Key: JBESB-2250 URL: https://jira.jboss.org/jira/browse/JBESB-2250 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 * "3.2 Figure 3.1 and Figure 3.2 - each describes the same but have different structure (missing pieces in the figures)" >Diagrams are derived from the ESB Programmers Guide & I believe 3.1 is supposed to be a much generalized image. Guidance please. This what Figure 3.1 looks like in the ESB Projects ProgrammersGuide: <?xml version = "1.0" encoding = "UTF-8"?> <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."> <services> <service category="Retail" name="ShoeStore" description="Acme Shoe Store Service"> <actions> <action name="println" class="org.jboss.soa.esb.actions.SystemPrintln" /> </actions> </service> </services> </jbossesb> The "missing pieces would in this case be the provider configuration and the listener configurations, unless the invm transport is assumed. The two diagrams do not describe the same thing, unless I'm missing something. I don't think that action should be taken here. * "3.2.4 The name for any given named object in a message must be unique or an exception will be thrown. - is it really true? How can this happen?" No, this is not true (the report is correct that is). This is simply a Hashtable and adding a new named object will replace the old one. This is also present in the ESB Programmers Guide on page 28 which needs to be updated * "3.2.5 Creating different body types - there is org.jboss.soa.esb.message.body.content.Payload class for this purpose >List of different message bodies - there are duplicate items" There are no duplicates in the ESB projects programmers Guide. See page 24. * "4.1 Routers are in the section name but are not mentioned in the text - also need to explain difference between routers and notifiers. >Would be also good to mention that it is not necessary to provide the information to listener - the reference to provider for given transport is typically used Routers are not mentioned in the ESB Programmers Guide, not in this section. Update required. * "5 This chapter should contain also Service orchestration section" >Update content in ESB Programmers Guide The "Service orchestration section" is located in the ESB projects document "ServicesGuide.pdf". It could be lifted into the SOA Platform document. * "page 73 - Note and page 34 - Note: The latter says that the gateway EPRs are not stored in registry and the former says they are" Page 41 of ESB ProgrammersGuide: Note: It is possible that multiple EPRs may be present in the Registry with the same Service Name/Category and that some of these EPRs may not be ESB-aware, e.g., Gateways. If the ServiceInvoker receives ESB-unaware EPRs from the Registry then it will ignore them. You may see the warning: "Invalid EPR for service (probably ESB-unaware)". Page 77 of ESB ProgrammersGuide: Note: For each gateway listener defined in a service, an ESB aware listener (or "native") listener must also be defined as gateway listeners do not define bidirectional endpoints, but rather "startpoints" into the ESB. From within the ESB you cannot send a message to a Gateway. Also, note that since a gateway is not an endpoint, it does not have an Endpoint Reference (EPR) persisted in the registry. This will need to be updated. * "Chapter 10 - the is new style functionality related to WS - EBWS (ESB services exposed as Web Services)" This needs to be added to the ESB projecs ProgrammersGuide. This is no currently in the main trunk but will be shortly. * "Appendix A - there is nothing in the text that justifies the inclusion of this Appendix - for what the JAXB is used in ESB context?" The appendix is for "JAXB Introductions" (http://www.jboss.org/community/docs/DOC-10075) and not JAXB isself. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2249) SFTP certificate passphrase is not optional when using certificates

by Mark Little (JIRA)

SFTP certificate passphrase is not optional when using certificates ------------------------------------------------------------------- Key: JBESB-2249 URL: https://jira.jboss.org/jira/browse/JBESB-2249 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 TP2, 4.4, 4.4 CP1 Reporter: Kevin Conner Assignee: Mark Little Priority: Minor Fix For: 4.2.1 TP3, 4.5, 4.4 CP2 The certificate-passphrase should be optional but there is a bug in the ListenerUtil which prevents this. The resulting stacktrace is as follows 15:27:02,642 ERROR [STDERR] java.lang.IllegalArgumentException 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.addressing.eprs.SFTPEpr.setPassphrase(SFTPEpr.java:196) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.addressing.eprs.SFTPEpr.<init>(SFTPEpr.java:127) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.listeners.ListenerUtil.fileEprFromElement(ListenerUtil.java:233) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.listeners.ListenerUtil.assembleEpr(ListenerUtil.java:94) -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2173) SFTP certificate passphrase is not optional when using certificates

by Kevin Conner (JIRA)

SFTP certificate passphrase is not optional when using certificates ------------------------------------------------------------------- Key: JBESB-2173 URL: https://jira.jboss.org/jira/browse/JBESB-2173 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1, 4.4, 4.2.1 TP2 Reporter: Kevin Conner Priority: Minor Fix For: 4.2.1 TP3, 4.4 CP2, 4.5 The certificate-passphrase should be optional but there is a bug in the ListenerUtil which prevents this. The resulting stacktrace is as follows 15:27:02,642 ERROR [STDERR] java.lang.IllegalArgumentException 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.addressing.eprs.SFTPEpr.setPassphrase(SFTPEpr.java:196) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.addressing.eprs.SFTPEpr.<init>(SFTPEpr.java:127) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.listeners.ListenerUtil.fileEprFromElement(ListenerUtil.java:233) 15:27:02,644 ERROR [STDERR] at org.jboss.soa.esb.listeners.ListenerUtil.assembleEpr(ListenerUtil.java:94) -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2141) Document client automatical XA transaction enlistment

by Martin Vecera (JIRA)

Document client automatical XA transaction enlistment ----------------------------------------------------- Key: JBESB-2141 URL: https://jira.jboss.org/jira/browse/JBESB-2141 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Rosetta, Transports Affects Versions: 4.4 Reporter: Martin Vecera ESB client (e.g. ServiceInvoker) always uses XA transaction when sending JMS message using JBM. This automatic transaction enlistment should be documented. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1958) JBoss Remoting Gateway not providing HTTP query string in composed message

by Tom Fennelly (JIRA)

JBoss Remoting Gateway not providing HTTP query string in composed message -------------------------------------------------------------------------- Key: JBESB-1958 URL: https://jira.jboss.org/jira/browse/JBESB-1958 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x This happens because the JBR CoyoteInvoker doesn't forward the query string in the request parameters object. -- 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, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-2247) typo in jUDDI related code sample

by Mark Little (JIRA)

typo in jUDDI related code sample --------------------------------- Key: JBESB-2247 URL: https://jira.jboss.org/jira/browse/JBESB-2247 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP1, 4.2.1 CP3 Reporter: Mark Little Assignee: Mark Little Fix For: 4.2.1 CP4, 4.5 -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2049) Check for invalid synchronous invocations within a transactional context

by Kevin Conner (JIRA)

Check for invalid synchronous invocations within a transactional context ------------------------------------------------------------------------ Key: JBESB-2049 URL: https://jira.jboss.org/jira/browse/JBESB-2049 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner We support a number of transports which integrate with transactions in a manner such that the delivery of the message will not occur until the transaction has been committed. If these transports are used to delivery a synchronous message then the result is a timeout/failure. We should introduce a mechanism where we can identify these situations and throw a different exception, clarifying the failure for our users. -- 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, 2 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2008