RE: [ebxmlms-develop] Problem using axis with hermes

[Ng C. Y. [Cyng] <cy...@cs...>]

Hi,

> I understand why AXIS throws an exception, but the way they check the
> instance type isn't a bad thing to do.

        Yeah... it's not a bad thing. I just wonder we may somehow be tempted
to create a SOAPElement instance directly using one API method and add it to
SOAPHeader but get exception finally.


> I'm still figuring out why the Sun implementation throws an exception when
> a SOAPHeaderElement is passed to it (via a cast). Then it would be possible
> to have the ExtensionElement not only return a SOAPElement, but a
> SOAPHeaderElement when the ExtensionElement is an instance of MessageHeader.

        This is also a good idea. Maybe, I should be more precise in
ExtensionElementImpl, i.e., the construction of ExtensionElementImpl should
call addHeaderElement() and addBodyElement() instead of SOAPFactory.
createElement().

> If you have more information on your problems with axis, we can prevent
> doing duplicate work. I'll draw up a list with our problems tonight
> (CET+2).

        Thanks a lot for your investigation. Please go on.


> The bug/tracker thing of SourceForge does not seem to be used.
> Do you guys have another system for this, accessible by external people?

        You may post to bug/tracker on SF and we will keep a look. But
due to our limited resources, we may not be able to fulfill all requests
as promptly as possible. Please don't mind.

Regards,
CY

----------------------------------------------------------------------------
Ng Chi Yuen, CY.       cy...@ce...       http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------