[wsas-java-dev] Concerns of bottom-up and top-down approach

amila chinthaka suriarachchi amila at wso2.com
Wed Nov 7 23:21:36 PST 2007


On Wed, 2007-11-07 at 13:08 +0530, saminda abeyruwan wrote:
> Hi All,
> 
> Looking at axis2-user mailing list and WSAS forums, it has been evident 
> that developers would like to create a web service with bottom-up 
> approach (code first) rather than top-down approach. If the time factor 
> get involved to the equation, bottom-up approach is the easiest and 
> fastest.
totally agreed. This is something both I and Azzez try to show in the
RMI disscussion as well.
> 
> Axis2 provides good support for bottom-up approach. It provides entities 
>   to generate WSDL out of POJOs if *RPCMessageReceivers have been used. 
> The current implementations of *RPCMR will be restricted to Java beans, 
> primitives and arrays.
> 
> But most of the developers ask, whether Axis2 can deal with collections. 
>   Thus, it's apparent that if collection can be an argument passed into 
> to out from a web method is an viable option. But it has limitations. 
> Generic collection can hold any type of objects. That's too much. It has 
> to be limited too. Thus, one option would be to use Java 1.5 Generics. ex;
> 
> public List<Employee> getEmployees(List<Department> depts) throws AxisFault
> 
> or
> 
> public Map<String,Person> getPersons() throws AxisFault
> 
> or
> 
> 
> public List getSomething(Vector some) throws AxisFault;
> 
> where List and Vector default to String.
+1 to add support for generics.
Even without generics we can do this. I have shown how we can do this
without generics in RMI disscussion. 
Generics is only available with after jdk 1.5. So if we can build a
system to do this without generics it would be more advantagoes since we
can support list and maps in jdk 1.4 as well. 
> 
> 
> One could argue that JAXWS/JSR 181 is the answer to the above problem. 
> That's right, but it's pretty sleekly and would not address the issue of 
> exposing an existing POJO as a web service.
> 
> If we could support the prior mentioned POJO support in next AXIS2 
> release, I believe, it would make the bottom-up approach aggrandize.

Certainly yes. 


> Your input on prior will be highly appreciated.

I think everyone would agree (as you have told as well) that out code
first approach has not meet the user requirements effectively. So we
must find a better approach. there is no doubt about it.

thanks,
Amila. 
> 
> Thank you
> 
> Saminda
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Wsas-java-dev mailing list
> Wsas-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev





More information about the Wsas-java-dev mailing list