Google Chrome is a piece of ...

I switched from Firefox to Chrome some time ago, but there is one thing I really hate about Chrome. It's its complete infirmity when it comes to handling XML content.

To view and download WSDL files I have to use Internet Explorer. Why?

First, when you view WSDL in Chrome it displays an empty page, not XML tree, like for example FF or IE. And second, most terifying thing in handling XML content, Chrome is changing camel case elements' names to lowecase when you save/download XML documents. Here are examples of such elements:

<xs:complextype name="cancelBookingResponse">
    <xs:sequence>
      <xs:element name="result" type="xs:boolean" />
    </xs:sequence>
</xs:complextype>
 
<wsdl:porttype name="Warehouse">
     <wsdl:operation name="cancelBooking">
       <wsdl:input message="tns:cancelBooking" name="cancelBooking">
     </wsdl:input>
       <wsdl:output message="tns:cancelBookingResponse" name="cancelBookingResponse">
     </wsdl:output>
    </wsdl:operation>
</wsdl:porttype>

What a disgrace!

Long live IE! :)

Łukasz

» Read the full post...

Implementing simple Web Services Registry using CXF

UDDI is an enterprise-grade solution for Web Services Directory. Most of Java EE application servers are shipped with UDDI applications. I wrote about UDDI and JAXR previously: Preparing for SCDJWS Part 8: UDDI, Fixing jUDDI 0.9rc4 and Scout 1.2 bugs, and Preparing for SCDJWS Part 15: JAXR and Web Services Registries.

Today I will show you a more flyweight approach to Web Services Registry. I will use Apache CXF for it.

» Read the full post...