Hi Ian
I'm happy to wait now that I know it'll come along in the 1.0.1 release. So
that I can manage expectations is there a timeframe when this is likely to
appear?
We have had to make quite a few changes already (i.e. changing the Axis2
dependency to version 1.3 from 1.2, support WAR deployment, JMS and
VFS/File transport enhancements, etc) Thus we may decide to make it a
1.1 release probably targeted to end of October - to ensure a good round
of testing as well. We will be releasing release candidates earlier and
you could give us feedback to make sure the release would address your
concerns correctly. Will this work for you?
One other question that's related. If a reply destination is specified, is
the correlation id something that needs to be set or is this managed by the
endpoint?
Do you want to provide a custom correlation ID to the request message?
If you want this could be done.. but usually this will not be a problem
as the JMS service implementation would use whatever message ID of the
incoming message as the correlation ID for the response message that it
will write to the reply destination.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
