This content has been marked as final.
Show 4 replies
-
1. Re: Dropping http-invoker.sar?
adrian.brock Oct 10, 2008 11:10 AM (in response to starksm64)"scott.stark@jboss.org" wrote:
The http invoker service depends on the legacy jmx invoker approach as welling as naming service details that are not going to remain the same. I think we should drop this and just have a remoting via http configuration documented/tested in its place.
Like I said before, we should move all the old invoker configurations
to docs/examples/legacy-remoting
They're still required for 4.x <-> 5.x
where 4.x doesn't have jboss-remoting or the unified invoker. -
2. Re: Dropping http-invoker.sar?
starksm64 Oct 10, 2008 11:46 AM (in response to starksm64)https://jira.jboss.org/jira/browse/JBAS-6072 is for the http-invoker.sar move.
JBAS-6071 is a parent task for all legacy invoker configurations. -
3. Re: Dropping http-invoker.sar?
starksm64 Oct 27, 2008 4:52 PM (in response to starksm64)Just an FYI followup, this was rolled back last week as there are several tests that depend on the http invoker. These would have to be refactored into a separate http-invoker testsuite config, and its not likely we'll do this for GA.
-
4. Re: Dropping http-invoker.sar?
anil.saldhana Oct 28, 2008 4:18 AM (in response to starksm64)"scott.stark@jboss.org" wrote:
Just an FYI followup, this was rolled back last week as there are several tests that depend on the http invoker. These would have to be refactored into a separate http-invoker testsuite config, and its not likely we'll do this for GA.
What % of tests were affected, Scott?