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

[Lahiru Sandakith]

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.
>
> 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.
>
>
> 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.
+1 for extending the POJO support with JAVA generics, it was being a 
long asked feature in the mailing-lists. But as I see the problem, it is 
also tightly coupled with moving the code base to 1.5, then the issue 
with doing that is, there are too large set of production environments 
that will need web services extensions in 1.4 that we can not afford to  
loose. Therefore moving the code base is not an option and I don't see 
this is going to be changed in near future also. So I am thinking that 
if we can add this feature as an extension to the WSAS which can be 
activated with a param in configuration xml file. So the person who is 
activating this will be responsible for making sure that the server is 
running on appropriate version of the jdk and so on. If we can do this 
it will be a ice breaker for the users in bottom-up approach as I think.

Thanks
Sandakith.
>
> Your input on prior will be highly appreciated.
>
> Thank you
>
> Saminda
>
>
>
>
>
>
>
>
> _______________________________________________
> Wsas-java-dev mailing list
> Wsas-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>

-- 
Thanks
Lahiru Sandakith

http://www.wso2.org 
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC  1AB1 FE5E 7464 1F01 9A0F