I think you have another karaf instance running on your box.
Exception in thread JMX Connector Thread
[service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]
java.lang.RuntimeException:
Port already in use: 4;
2014-11-27 3:28 GMT+01:00 Jim Ma mail2ji...@gmail.com:
Hi,
Does
Hi All
Was wondering if anyone knows why in AbstractOutDatabindingInterceptor,
isRequestorRole has a definition of:
protected boolean isRequestor(Message message) {
return
Boolean.TRUE.equals(message.containsKey(Message.REQUESTOR_ROLE));
}
Whereas in AbstractInDatabindingInterceptor
I didn't know there are so many isRequest methods hiding in the code ;-)
I knew only MessageUtils's one, which was probably added later after some time.
The inconsistency that you observed between
AbstractInDatabindingIntereceptor and
AbstractOutDatabindingIntereceptor was the result of this
I will take care of that while finishing up CXF 6118.
regards
On 28/11/2014 12:37 AM, Aki Yoshida elak...@gmail.com wrote:
I didn't know there are so many isRequest methods hiding in the code ;-)
I knew only MessageUtils's one, which was probably added later after some
time.
The
FIX: Document about implementation details is here
https://developer.jboss.org/docs/DOC-52429?uniqueTitle=false
--
View this message in context:
http://cxf.547215.n5.nabble.com/Proposal-WS-Transfer-WS-Fragment-implementation-tp5750975p5751577.html
Sent from the cxf-dev mailing list archive at
