Saigo-Yama Park at Nakameguro Tokyo

Four men and beers and my lovely bicycle at Saigo-Yama Park.

Souma (Somuch), Shun, Makoto (Mako-tyan), and Me.

Axis2 vs CXF

Service Configuration I want to try is following...

[1. Service Consumer]

|

|

| SOA Interface (SOAP / REST)

|

|

[2. Service Provider on Tomcat]

[2'. Service Consumer on Tomcat]

|

|

| FIMS Interface (http://wiki.amwa.tv/ebu/index.php/Main_Page)

|

|

[3. Service Provider]

I want to make an agent service(2) between Service Consumer(1) and Service Provider(3).

For deploying web services and binding Wsdl and java code,

Axis2 seems to be popular than CXF web developing platform according to some BLOGs.

(http://www.theserverside.com/news/1363958/Axis-Axis2-and-CXF-Surveying-the-WS-Landscape, etc...)

So, first, I try to use to develop Web Service using Axis2.

<< Development Procedure >>

0. Installing Eclipse 3.7 (Indigo) / axis2 1.6.0 bin / axis2 1.6.0 wsdl2java plugin / Tomcat bin / Tomcat plugin v33

1. Service Provider 3 is already hosted on something servlet container, whose WSDL is FIMS Standard v 0.3 (http://wiki.amwa.tv/ebu/index.php/Main_Page)

2. Create [Dynamic Web Service]

3. Create [Web Service Client]

3-1. Server Runtime : Tomcat 7.0

3-2. Web Service Runtime : Apache Axis2

Client Project : xxxx

3-3. Data binding : ADB

# but, the issue arises, which is to unable to convert wsdl to java code by ADB databinding....

3-4. Data binding : Xmlbeans

# I confirmed that wsdl is converted to java code successfully.

3-5. click done

# created java codes are org.xxx / tv.fims.xxx packages.