Bug 779169 (SOA-1564) - UDP Gateway - default hanlder class is hard-coded in schema
Summary: UDP Gateway - default hanlder class is hard-coded in schema
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1564
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.0 ER1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: FUTURE
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-27 14:39 UTC by Jiri Pechanec
Modified: 2011-04-08 20:01 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-04-08 20:01:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1564 0 None None None Never

Description Jiri Pechanec 2009-10-27 14:39:57 UTC
Date of First Response: 2009-12-09 05:47:19
project_key: SOA

UDP Gateway requires handler class. ESB provides a default one and this is hard-coded in XSD schema. I think that this is implementation detail that should not be present in XSD schema.

Comment 1 Kevin Conner 2009-12-09 10:47:19 UTC
Schema file is locked and will not be changed, we can look at this for a future release.

Comment 2 David Le Sage 2010-02-10 04:07:20 UTC
I have documented this for the Release Notes.  Here is the draft text:


https://jira.jboss.org/jira/browse/SOA-1564

    Currently, the default ESB handler class for the UDP Gateway is hard-coded into the XSD
    schema and cannot be changed or removed.


Comment 3 Kevin Conner 2010-02-11 09:43:33 UTC
It may be worth emphasising that it is only the default value for the handler which cannot be altered, in a global sense, and that the gateway does allow the handler to be specified for each individual gateway.


Note You need to log in before you can comment on or make changes to this bug.