Any thoughts?
Cheers
Freeman
Freeman Fang wrote:
Hi,
Currently we are using sync way for jms transport which means the
thread get blocked until response messsage is coming or the client
side timeout, see the handleResponse() method of JMSConduit? Is it
possible that we use non-block way f
On Monday 25 August 2008 12:42:43 pm Benson Margulies wrote:
> This whole question turns out to be the following: Is it a valid
> JAX-WS/JAX-B thing to annotate a plain old String bean property for
> MTOM, and expect MTOM to happen? If so, then I need to determine if
> the failure to do so is us or
Dev,
I'm looking at CXF-1758, which presents as the Javascript front end
choking when the SEI and SEB are generics.
In other words, the implementation bean for a service is
SomeGenericOfType, and it has a method like doSomething.
With the simple front end, we get a schema for this with an
xsd:an
This whole question turns out to be the following: Is it a valid
JAX-WS/JAX-B thing to annotate a plain old String bean property for
MTOM, and expect MTOM to happen? If so, then I need to determine if
the failure to do so is us or JAX-B, and if the latter we have to
decide if we care enough to cont
I don't think there is a way to set the threshold in the wsdl. You can turn
it on with a ws-policy fragment, but you cannot set the threshold that way.
If it's jaxws, the easiest way to go about it would be to add a:
@MTOM(enabled = true, threshold = 1000)
annotation onto the interface/impl.
Y
Hi,
Currently we are using sync way for jms transport which means the thread
get blocked until response messsage is coming or the client side
timeout, see the handleResponse() method of JMSConduit? Is it possible
that we use non-block way for JMSConduit, something like implement JMS
MessageL