Re: [ebxmlms-develop] Sun WSDP1.2 without jaxm

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

Ng Chi Yuen [Cyng] probeerde het volgende duidelijk te maken op 
24-6-2003 16:06:

>Hi,
>
>  
>
>>I just read the releasenotes of  WSDP 1.2 and there does not seem to be
>>a  JAXM anymore (neither in j2ee 1.4 draft 3). Not that I realy care for
>>that, but since it is not there anymore, shoudn't we try to remove it
>>from Hermes as well?
>>Can anybody summarize what the open issues are to fully move to axis? I
>>still have limited time, but in a few weeks I could give it a try
>>    
>>
>
>        I note that the name "SAAJ" is still in the description. According
>to my interpretation, since JAXM 1.1.1, those classes under
>javax.xml.soap.* (such as SOAPMessage) are grouped into SAAJ while
>those under javax.xml.messaging.* (such as JAXMServlet, ProviderConnection)
>are so-called JAXM. It seems that SAAJ are used for over 90% of the time
>for composing SOAPMessage (and thus ebMS packaging), implementations
>of ProviderConnection, ReqRespListener for ebMS are seldom met.
>
>        So, it's really a great idea to remove all these kinds of stuff
>(SAAJ and JAXM) from Hermes. 
>
Axis saaj compliant (the api), so i think you mean removing  the sun 
reference-implementation of saaj? Or do you realy want to start using 
the lowlevel axis api of jdom? Personally I wouldn't do that. Just stick 
with saaj and use the axis implementation. (doesn't axis use jdom?)

>In the current 1.0 branch, Http.java has
>already sent a SOAPMessage using direct HTTP (HttpURLConnection) instead
>
Great, on an internal project we currently have thrown all sun http 
classes overboard and use commons-httpclient  from apache. This gives us 
better proxy support (including authentication, even NTLM) because the 
Sun has some issues there, especially with M$ proxies. And 
http-keepalive, which especially on busy connections, leads to 300% 
performance gain.

>of SAAJ's SOAPConnection.call(). Patrick also implemented the file-based
>EbxmlMessage by adding our own PayloadContainer instead of SAAJ's
>AttachmentPart. The remaining work should be on SOAPMessage inside
>EbxmlMessage only. After removing this part, Hermes should be SAAJ and
>JAXM free. SAAJ just rides on DOM4J which then rides on JavaMail's
>MimeMultipart. Personally speaking, I like jdom which works much
>faster and efficient. How about if we introduce jdom into packaging/* ?
>
Doesn't axis use jdom and Sun dom4j?.... I'l have a look So if  the sun 
implementation of saaj is not used anymore we could switch to whatever 
we want.

btw, did you ever have a look at  jxpath.... I you want clean code....e.g.

Address address = null;
Collection locations = vendor.getLocations();
Iterator it = locations.iterator();
while (it.hasNext()){
    Location location = (Location)it.next();
    String zipCode = location.getAddress().getZipCode();
    if (zipCode.equals("90210")){
      address = location.getAddress();
      break;
    }
}


can be written as


    Address address = (Address)JXPathContext.newContext(vendor).

         getValue("locations[address/zipCode='90210']/address");  

    

especially the manipulation of the ebxmlmessage would then be realy 
clean... just learn the xsd


>
>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: INetU
>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>_______________________________________________
>ebxmlms-develop mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>  
>