Sorry Ron, I hadn't put a watch on this Thread until now.
"ron.sigal(a)jboss.com" wrote : But there's something strange about your line
numbers - they don't match what I see under
https://svn.jboss.org/repos/jbossremoting/remoting2/tags/2.5.0.SP2 . Don't know
what's going on there.
The wrong line numbers may be due to that we had a version of ServletSocketInvoker in
WEB-INF/classes of the test, and I'd copied from an older log. But after that issue
was resolved, the problem I explained in the previous post persisted. Something's not
lining up between the release JARs and what I can build from tags...
"ron.sigal(a)jboss.com" wrote : So, for example, the ObjectName for the EJB2
servlet invoker I'm playing with right now is
"jboss.remoting:dataType=invocation,host=127.0.0.1,marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller,port=8080,return-exception=true,service=invoker,transport=servlet,unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller".
Just tried the ObjectName of that form from my JMX console; same
IllegalArgumentException.
"ron.sigal(a)jboss.com" wrote : By the way, I didn't even know there was a
servlet test in the EJB3 test suite. I'll take a look at that. But not tonight. :)
Great.
We'll plan to move this out of EJB3 and into AS (as the EJB3 component responsibility
ends with invoking upon the correct endpoint) once it's passing. For the time being I
have this marked as a "known issue" to help us track true regressions.
BTW we've got a Thread on this regression over here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201180
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201181#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...