Bug 778827 (SOA-1275) - Undocumented ESB listeners
Summary: Undocumented ESB listeners
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1275
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: FUTURE
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-07 23:58 UTC by Aaron Pestel
Modified: 2011-12-02 21:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-02 21:49:31 UTC
Type: Feature Request


Attachments (Terms of Use)


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

Description Aaron Pestel 2009-04-07 23:58:00 UTC
Date of First Response: 2009-10-27 15:44:49
project_key: SOA

The following gateways/listeners are not document in the programmer's guide:  http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Programmers_Guide/index.html#sect-SOA_ESB_Programmers_Guide-Configuration-Transport_Specific_Type_Implementations

1.)  JBR/HTTP(S)
2.)  JBR/Socket
3.)  JCA/Mail

The only listener that appears to be very well document is FTP.

Comment 1 Burr Sutter 2009-10-27 19:44:49 UTC
Darrin, I think this one should be assigned to you, I think it is more of a bug than a feature

Comment 2 Kevin Conner 2009-10-27 19:51:05 UTC
We never officially supported JCA/Mail integration in the project because the mail resource adapter was buggy.  Has this been fixed?  Do we now support the adapter?

Comment 3 Burr Sutter 2009-10-29 13:38:42 UTC
It is my understanding that there is  "patch" for the JCA adapter and that it is supported at the product-level.  I am not sure if that patch founds its way back into the jboss.org AS stream.   

With that said, do we agree that the HTTP & Socket areas need better/more complete docs at least?


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