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

[Ronald v. K. <rv...@ab...>]

I understand why AXIS throws an exception, but the way they check the
instance type isn't a bad thing to do. 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. 

I'll look into that further.

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).
The bug/tracker thing of SourceForge does not seem to be used. Do you guys
have another system for this, accessible by external people?

Ronald

> -----Oorspronkelijk bericht-----
> Van: Ng Chi Yuen [Cyng] [mailto:cy...@cs...]
> Verzonden: donderdag 3 april 2003 4:22
> Aan: freebxml
> Onderwerp: Re: [ebxmlms-develop] Problem using axis with hermes
> 
> 
> Hi,
> 
> > We've been looking into using apache-axis instead of the Sun
> > implementation of jaxm/saaj because it has more functionality (works
> > better with proxies, http keep-alive etc.) and is open-source.
> 
>         For your information, we have also been testing with 
> Apache Axis
> for sometimes. The goal is we can finally support Axis but we 
> still find a
> number of problems in it.
> 
> 
> > org.apache.axis.message.SOAPHeader:
> > --
> >     public SOAPElement* addChildElement*(SOAPElement element)
> >       throws SOAPException
> >     {
> >       if (!(element instanceof* 
> javax.xml.soap.SOAPHeaderElement*)) {
> >        * throw new 
> SOAPException*(Messages.getMessage("badSOAPHeader00"));
> >       }
> >       return super.addChildElement(element);
> >     }
> > --
> >
> > Since I'm not allowed to decompile the Sun implementation 
> ;-) I tried
> > casting extensionElement.getSOAPElement() to 
> SOAPHeaderElement, without
> > success. I get a classcast exception then in the default 
> hermes (without
> > axis).
> 
>         Ideally speaking, since both JAXM and Axis implement 
> javax.xml.soap.*,
> there is no need to change a line of codes in Hermes and 
> simply switching
> between the two libraries should work smoothly.
> 
>         Of course, the world is not so ideal. The 
> ClassCastException thrown
> by Axis is due to the fact that when a SOAPElement is added 
> to SOAPHeader,
> the SOAPHeader would regard this SOAPElement as 
> SOAPHeaderElement (which is
> subtype of SOAPElement) when an iterator of children is retrieved from
> SOAPHeader. We have reported this to Apache and see if this 
> problem will
> be fixed in the coming Axis release.
> 
> 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
----------------------------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
ebxmlms-develop mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop