Amila Suriarachchi wrote:
On 5/26/07, *Dennis Sosnoski* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
...the compile error in the generated stub for callback
classes when asynchronous is enabled (5-18 email):
http://marc.info/?t=117885569800001&r=1&w=2
<http://marc.info/?t=117885569800001&r=1&w=2>
Since asynchronous code generation is enabled by default this seems to
be an especially serious problem. If I get a chance today I'll add a
Jira for the callback issue, unless you've already fixed that.
Please log a jira.
Azeez report me a similar bug and I just fixed it in trunk. There the
promblem is
the in callback handler I have not handle the response correctly with
response unwrapping.
Yes, this is the same issue. I misstated it in this last email where I
said it was a compile-time error rather than a runtime exception. The
original email referenced above stated it correctly.
As for the rest of the issues, I personally believe that the number of
problems present in the 1.2 release would justify a 1.2.1 release. Axis2
is intended for use in enterprise software development, and IMHO
enterprise software requires a high degree of confidence in the
components. If there are significant known problems with easy solutions
in a release, I think these should be corrected in order to give both
new users and those moving up from a prior release the best possible
experience. But I accept that the majority of the Axis2 developers
consider the 1.2 problems minor, and will not push the issue further.
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
