[esb-issues] [JBoss JIRA] Commented: (JBESB-1382) SQL Listener XSD definition assigning suspicious defaults
[ http://jira.jboss.com/jira/browse/JBESB-1382?page=comments#action_12391946 ]
Tom Fennelly commented on JBESB-1382:
-------------------------------------
Sensible defaults are great, but only on stuff like "maxThreads" i.e. where the
app doesn't fall down in a heap if the defaults are used.
IMO, that doesn't apply to any of these fields. The user is most likely to use the
defaults (unwittingly - because they're not forced to add them) and their system is
99.9% guaranteed ( ;-) ) to fall over in a heap (lol), at which point they have to go
rooting around in docs etc. Just make the fields mandatory and their IDE will ask them
for those values from the get-go... leading to a much smoother ride IMO :-)
SQL Listener XSD definition assigning suspicious defaults
---------------------------------------------------------
Key: JBESB-1382
URL: http://jira.jboss.com/jira/browse/JBESB-1382
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2.1
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2.1 CP1
It's assigning defaults to some of the column names. I'd have thought it
shouldn't be defaulting these - they either exist and are configured and used... or
they're not and the code should check for that and/or give an error because it allows
code to continue on blindly thinking everything is cool.
<xsd:attribute default="message_id" name="message-id-column"
<xsd:attribute default="message" name="message-column"
<xsd:attribute default="status" name="status-column"
--
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