[esb-issues] [JBoss JIRA] Commented: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional

Lukas Petrovicky (JIRA) jira-events at lists.jboss.org
Tue Dec 2 05:34:37 EST 2008


    [ https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440706#action_12440706 ] 

Lukas Petrovicky commented on JBESB-2212:
-----------------------------------------

Here:

https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/notifiers

And the test for it here:

https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/tests/src/org/jboss/soa/esb/samples/quickstart/notifiers/NotifiersTest.java

Should you need help running our test suite, contact me on IRC.

> sql-message-filter optional attribute "insert-timestamp-column" actually not optional
> -------------------------------------------------------------------------------------
>
>                 Key: JBESB-2212
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2212
>             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 CP4
>
>
> 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

        



More information about the esb-issues mailing list