[JBoss JIRA] Created: (JBESB-807) JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)
by Tom Fennelly (JIRA)
JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)
------------------------------------------------------------------------
Key: JBESB-807
URL: http://jira.jboss.com/jira/browse/JBESB-807
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 3
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2.1
Talked with Ron Sigal and he thinks we might have to explicitly use the Servlet transport (i.e. the CoyoteInvoker might not be configurable for BASIC auth).
Here's what Ron said exactly.....
"1. HTTPServerInvoker is obsolete. It's been replaced by CoyoteInvoker.
2. According to my O'Reilly Tomcat book, BASIC authorization is configured in the web.xml file by the <login-config> element. But CoyoteInvoker doesn't use the full Tomcat implementation, just the Coyote adapter. I'm really not sure if the Coyote adapter has anything to do with the web.xml file.
3. There is another Remoting transport, the servlet transport, which really does use Tomcat. It uses a servlet as a front end to the server invoker. There's even a web.xml file: src\etc\web\web.xml in the Remoting project directory."
--
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
14 years, 8 months
[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default
by Tom Fennelly (JIRA)
Make action, listener etc configuration setting by setter method the default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface, their IDE (or at least compiler - if using a stone ax) will complain immediately that they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be implemented.
So I suggest making the interface (that all these things implement) contain a setter method that takes the config. The mandate on the implementation is that they contain a public default constructor.
--
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
14 years, 8 months